Hi Barry,
Sorry you’ve run into this error, can you let us know what specific error you’d seen in the console?
I’m not sure if we can recreate this, but what I would try is perhaps seeing if some conflict troubleshooting might help show the error on the front end.
The best way to determine if the issue is being caused by a theme and/or plugin is to temporarily switch your theme to Storefront (https://woocommerce.com/storefront/) and disable all plugins except for WooCommerce. Finally, test to see if the issue is resolved by
To figure out which plugin is causing the problem, continue to the next step – reactivate your other plugins one by one, testing after each, until you find the one causing conflict.
Here’s a more extensive explanation in our docs: https://docs.woocommerce.com/document/how-to-test-for-conflicts/
—–
Tools to help you troubleshoot:
Meks Quick Plugin Disabler is a plugin you can install which will remember what plugins you currently have active so it’s easy to switch them back on. Link: https://ww.wp.xz.cn/plugins/meks-quick-plugin-disabler/
You can clone your site to a staging environment and perform tests without modifying your live site or impacting customers. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin. Link: https://ww.wp.xz.cn/plugins/wp-staging/
PS – Could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status.
Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
Hi Ryan,
Thank you for your reply. I really wanted to highlight that sometimes when an error occurs the error banner may be blank. Wouldn’t it be better if some message could be displayed rather than the blank error banner?
Reflecting on this further, perhaps I should have raised the issue with WooCommerce, rather than specifically the WooCommerce Stripe Payments Gateway, because I guess the timeout occurred early in the AJAX sequence. And looking at the Stripe Log for the relevant time there is just ‘POST /v1/sources’ and no following log entries at that time.
Perhaps I will pursue this further by looking at how WC handles AJAX timeout errors. It would appear not to be exhausting possibilities with a default case.
Thank you,
Barry
Hi @datastream,
I really wanted to highlight that sometimes when an error occurs the error banner may be blank. Wouldn’t it be better if some message could be displayed rather than the blank error banner?
Absolutely, I wanted to do some of that basic conflict testing to rule out a plugin or theme causing the empty error notice.
Once any sort of conflict could be ruled out, we can look at the next potential causes. Does that make sense?
Hi Ryan,
It might only makes sense if the issue was reliably repeatable, which it is not. For me, it’s now own the back burner, only to be dealt with should it recur.
However, I would have thought WooCommerce (and I’m using Storefront theme) could catch a default case where the screen refreshes with no message content. Then at least maybe saying ‘Failed with unknown error’. or some such. Indeed there may well be an error code available if the AJAX ‘error:’return were being handled, which it would appear it’s not. But as I say, this is more Woo than Stripe Gateway, so not your problem?
Regards,
Barry
Hi @datastream,
For me, it’s now own the back burner, only to be dealt with should it recur.
Sounds a-ok, if you do wanna dig into this at some point on a staging environment we can try to figure out if the error notice is being blocked or if there was truly some blank output. 🙂
Thanks!
Plugin Support
Hannah S.L.
(@fernashes)
Automattic Happiness Engineer
We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.
