negapo
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Apple Pay / Google PayThere must me an issue here:
“any WooCommerce default checkout field you mark as required, such as billing address or phone number, will also be prompted within the Apple Pay or Google Pay flow so the customer can provide those details there.”With apple pay ang google pay, we received some orders without the phone number which is a crucial piece of information.
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Warning: Undefined array key “type”Hi, we have the same exact problem, on our logs, several error lines:
PHP Warning: Undefined array key “type” in /home/customer/www/XXXX/public_html/wp-content/plugins/woocommerce-gateway-stripe/includes/payment-methods/class-wc-stripe-express-checkout-element.php on line 420Thanks Anca, i thing every user of TranslatePress would benefit from small and continuous improvements in efficiency.
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Spyware on your plug-in?In the meantime, anyone who wishes to stop this data collection, for performance or compliance reasons, use this code:
add_filter( ‘wc_stripe_load_scripts_on_product_page_when_prbs_disabled’, function( $should_load ) {
return false;
});Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Spyware on your plug-in?I’m thankful for your answers and for not hiding behind a general canned response.
I need to address this publicly because this is an important issue with a simple solution.
Every user of this plugin in Europe must understand that when a user does not give consent for data collection, there is currently no way to prevent this plugin from sending unauthorized data. Therefore, it is not GDPR compliant, and one of two things should happen: either the plugin is corrected to provide a way to opt out, or it should no longer be made available in European countries.Even the Radar documentation (https://docs.stripe.com/radar/integration) states that it is recommended, but not required, to include the JavaScript on every page. So not including it should not break any functionality.
Moreover, your plugin already includes a flag that could control this behavior:
WC_Stripe_Helper::should_load_scripts_on_product_page()Additionally, the amount of data being collected is quite substantial.
If this is not corrected in the next release — with a simple option to exclude the loading of the JavaScript on site/product/catalog/cart pages (only loading it where it is strictly necessary) — I will file a complaint with the Data Protection Authority of my country, and I will inform Automattic (as the developer of the plugin, from what I can see) and Stripe of the details of the complaint.The right thing to do is to comply with privacy laws, or at the very least inform users so that they can make an informed decision — neither of which has happened so far.
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Spyware on your plug-in?Thank you for your prompt reply. This is a serious issue that needs to be addressed on the plugin side. While I won’t dispute that the data collection seems unethical, there’s no clear indication that it happens when the plugin is installed. The obfuscation of this process is also concerning. More alarmingly, it appears we’re feeding a machine learning system unnecessarily. My site gets 15 million page views annually, so we’re collecting 30 million data points on Stripe, most of which come from users who never even use Stripe to pay. This is excessive and should be limited to the checkout page, only collecting data when a user selects Stripe as a payment method.
It’s crucial to note that this type of data is protected under GDPR in Europe, and explicit consent is required before collecting it. This situation is illegal.
You must take action by allowing users to disable this feature at the plugin level. The plugin should only be active on the checkout page and collect minimal data necessary for secure payments.
You have to understand, this is a serious issue and needs to be addressed.Forum: Plugins
In reply to: [Moloni] Atenção, houve um erro ao inserir o documentoOlá Francisco,
O erro parece ser devido ao envio por transportadora não ter uma taxa de IVA e não estar configurado, nas opções do plug-in, uma razão para a isenção dos portes no envio. Basta escolher uma razão de isenção, ou optar por cobrar IVA no transporte (que é o mais frequente). Se optar por cobrar IVA no transporte a configuração é feita no WooCommerce, nos métodos de envio tem de marcar a opção Situação fiscal: Tributável.
Forum: Plugins
In reply to: [Moloni] Escolher o estado da encomenda para emissão de FaturaMuito bom trabalho, obrigado.
Forum: Plugins
In reply to: [Moloni] Hook depois de criado uma Nota de CréditoPerfeito, muito obrigado, acho que vai facilitar muito a integração do plug-in com lógicas de negócio mais avançadas.
Sure, sorry for the lack of details:
In list view, the media library opens in edit mode which is different from last version, and the fields Title and Alt text cannot be edit, if you click save or cancel nothing happens. Take a look:
https://ibb.co/F8FDPDw
WC 8.5.2
WP 6.4.3
Store Front and no additional plug-ins
No console js errors.Forum: Plugins
In reply to: [Moloni] Código AT no meta da encomenda?Boa dica, obrigado pelo código.
Just a side note, that’s not a filter, that’s a function, not a good idea to change core functions but if this a temporary issue there is no problem. The main thing is the last post, thats what we want to hear, this is not a environment or installation issue, its a bug thats being addressed.
For anyone who finds it usefull:
function sg_security_add_roles( $roles ) { $roles[] = 'role_id_name'; return $roles; } add_filter( "sg_security_2fa_roles", "sg_security_add_roles");Sorry, there is already a filter: “sg_security_2fa_roles”
I didn’t read the code to the end
We have the same problem, will you do anything at the plug-in side on future versions to solve this?
The above code isn’t a filter right, its a core WP function, should we overwrite it?