3mma

Hello Jathin and thank you for your answer!
I just created a ticket on the WP Event Manager support (##17421##), so I’m waiting hearing from you through this new channel. And of course, I stay available to give you more infos if needed.
Have a good day,

Thank you Igor for keeping track of this issue!

Yes, as you can see, the problem is not there anymore because I forced manually this cookie to be a “unclassified” (means always activated) cookie. I couldn’t let my client without a payment possibility on her website, so I used this workaround as soon as I found it.

Stripe defines this cookie like this: “Registers data on visitors’ website-behaviour. This is used for internal analysis and website optimization.” I’ll now let the developer have a look. I’m the author of this GitHub report, yes.

Thank you for your help!

• This reply was modified 1 year, 10 months ago by 3mma.

Hello,

I just wanted to keep you in touch about the issue: it appears that it’s not linked to your plugin.

It is a cookie problem:
– I use Cookiebot and the last scan / update of the cookie list of the website was done at the same day of the update of your plugin.
– The payment was working when I was logged because I use to desactivate the cookie banner in my settings when I’m logged.

I write here the rootcause in order to help others if they face the same problem:
Stripe uses 4 new cookies (1, _mf, _ab and id). “1” is a tracking cookie but the Woocommerce Payment Stripe Gateway plugin currently needs it to be there in order to work well. So, just put this cookie as necessary for the moment (I open an issue on the GitHub of the plugin and hope the bug will disappear soon).

Sorry for the confusion, and thank you for your help!

Thank you Saif for your answer.

I don’t get why all Stripe cookies would be necessary: this “1”-cookie is obviously a tracking cookie (it’s written in its description itself).

Adding the code that you proposed me doesn’t change anything because the scripts needs to be loaded on the checkout cart anyway, and that they are not loading without this “1” cookie.

This “1” cookie is a new one from Stripe (the 3 unclassified – _mf, _ab and id – too): they appeared for the first time during the last scan of this website by Cookiebot on the 21st of March. It means that potentially other people will have this problem, so I’ll create an Issue in GitHub in order to check and try to anticipate!

Hello Igor,

Thank you for checking.

It appears that putting the 3 unclassified cookies as “necessary” doesn’t solve the problem.

I continue to search among the cookies. In order to solve it, I have to change the category another Stripe cookie (stripe_1, normally placed in the Statistics tab) and to put it as “necessary”. I don’t like it because this cookie is clearly tracking the visitor (description of this cookie: “Registers data on visitors’ website-behaviour. This is used for internal analysis and website optimization.”)… and putting it as “necessary” would violate the visitors’ rights. It means that there is a bug: the checkout fields should be available also without accepting this cookie.

In the documentation of your plugin, it’s written that “The new Stripe Checkout is not part of the WooCommerce Stripe payment gateway. This is an open enhancement and further details and any future development will be linked from this GitHub Issue.” (https://woocommerce.com/document/stripe/#stripe-checkout)
Does it mean that I have to contact Stripe itself to solve the problem?

Hello Igor,
First, thank you for your really quick answer, I appreciate it!
When you said it works for you, I was quite surprised because I tried on several devices, clearing the cache of my navigators… and then I had a flash: I always “refuse the cookies” on the tab.
I just made a try in a private tab, accepting the cookies this time… and it works!
Now, I’m having a look at Cookiebot. I just remarked that 3 cookies from Stripe (_mf, _ab and id) appears in fact as “unclassified”. I have to admin that I don’t know if it’s new or if it’s like this since a long time.
Could you please tell me which one is (or which ones are) actually necessary/functional and I’ll make the change to check if it solve the problem?

Thank you very much for your response!

• I just tried to add this constant on the cart page, thanks to PHP Code Snippets plugin > the problem is still there
• Yes, I’ve tried to reject the 2 pages (/cart/ and /order/) in the reject url setting a few days ago > the problem is still there

Yes, indead: the Network tab shows that stripe.min.js is loaded, and the problem (in the Console tab) is that Stripe is not found. But in the Source tab, js.stripe.com doesn’t appear (at the side of fonts.googleapis.com, ajax.googleapis.com, consent.cookiebot.com)… whereas js.stripe.com appears there when logged. The fact that js.stripe.com is missing there could explain why Stripe is not defined in the code.

Do you have some other ideas?

Hi,

Sorry to insist, but “early next week” is now two weeks ago. ?? Could you please give me an update on this topic, I really need a solution for my customer!

Thank you in advance for your time.

Regards,
Emma

Hi,
Do you have some news? ??
Regards,
Emma

Hi,

I’ve seen this article, but I can’t do it like it explains: my customer signs in to the newsletter when he’s buying a product (thanks to the optin setting). It means I don’t have any subscription form, it’s done thanks to the plugin. I just created the second part of the workflow, the “Double optin confirmation template”, and linked it thanks to the plugin (Woocommerce / Sendinblue / Subscription settings / Double optin template).
Do you see the point? That’s why I’m asking if there is a snippet to do this.

Emma

Hello Sarah,
Thank you for giving me some updates of the situation ??
Enjoy your weekend too!
Emma

Hello Alice,

Thank you very much for your answer!

On one side, I’m glad to hear that they reproduced it. It means I didn’t bother you and the support team for “nothing”: it doesn’t come from a wrong setting I could have done…
On the other side, I may have prefered that it’s just a mistake I did and I’m a bit worried. I hope it will be resolved soon, the launching date of the website of my customer depends now on when you will come back to me for this bug!

I look forward to hearing from you.

Regards,

Emma

Hi Alice, did you manage to reproduce the problem?

Thanks a lot Alice for your answer!

Concerning the “identified_contacts” list: I’ve read in some other comments that every customer is in this list (with just his email address as saved field) when he orders something on Woocommerce and that the Sendinblue plugin is activated. So it seams ok in my case because it’s the result that I have when I uncheck the optin checkbox.

If I buy a “normal” product (with Woocommerce and the Sendinblue plugin) and I click on the optin checkbox to subscribe to the newsletter before paying, everything works fine:
– all my informations (email address, name, phone number, address,… in fact, all the fields I parametered in the Sendinblue plugin to be synchronized with the parameters of my Sendinblue list) are saved in Sendinblue and I’m added to the “newsletter” list as well. Everything works fine.
The problem is when I do exactly the same, but with a digital product: this time, the fact that I check the box or not doesn’t change the behaviour of the plugin: only my email address is saved in both cases and I’m added to the “identified_contacts” list.
In both cases, I receive well the order confirmation email. But in the second case, I don’t receive the welcome email that people receive when they subscribe to the “newsletter” list (that is logic: the plugin didn’t add me to this list). I’d like to have the same result as with a “normal” product.

Here are the options of my downloadable+virtual product: “force download”, “grant access to downloadable products after payment” and “append a unique string to filename for security”.
In the Woocommerce account options, I authorize customers to buy without having an account, so it means no account is created.
Does it help you to understand the situation? Don’t hesitate to ask if you need some other technical details!

Did you already have this feedback? Is there a trick to solve it? Or are you investigating? Could I have an answer please?