Closed maxlaf closed 7 months ago
Hey @maxlaf! I'm unable to reproduce this on my local site or a JN site using the steps you've outlined.
Are there any additional details you can provide?
Edit: I think I can reproduce this only if I'm opting to save the payment method. I can also reproduce this if I am trying to add a new payment method via the My Account page.
However, the error is related to /wp-content/woocommerce-gateway-stripe/build/upe_classic.js
— which means this issue may be rooted in the Stripe plugin and not WooPayments.
Just in case... 7983612-zd-a8c
This case has to do with saving payment method, and the user reported that they could not save it on a normal web browser, but they can on incognito mode browser. Adding the case to this in case they are related.
A short investigation lead me to the issue, which is with the Stripe gateway. I've opened another issue there: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/3041
Closing this one, as it is not caused by WooPayments.
Describe the bug
If both WCPay and Stripe are installed, but Stripe is inactive as a gateway, Stripe JS throws an error on the Pay for Order page when trying to pay with WCPay.
This does not affect the regular checkout page.
To Reproduce
Actual behavior
Error is thrown on pay for order page:
can't access property "elements", b[r] is undefined
Screenshots
Expected behavior
WCPay and Stripe to not conflict with each other in a way that prevents purchases.
Additional context
SSR