Version 8.9.0 breaks the settings page and no options are present

  • Hi, Woo.

    The plugin’s latest version completely breaks Stripe’s payment gateway settings.

    Rolling back to v8.8.2 does not solve the issue.

    A screenshot of the settings page and console errors can be viewed.

    A copy of the console errors is also below:

    Uncaught TypeError: Cannot read properties of undefined (reading 'unstable_scheduleCallback')
    at n (react-dom.min.js?ver=18.3.1:10:105894)
    at react-dom.min.js?ver=18.3.1:10:129073
    at react-dom.min.js?ver=18.3.1:10:129108Understand this errorAI
    upe_settings.js?ver=f63af19c5e5a5d5f1a8fef3d276afb75:17 Uncaught TypeError: n.a.render is not a function
    at Module. (upe_settings.js?ver=f63af19c5e5a5d5f1a8fef3d276afb75:17:2982)
    at l (upe_settings.js?ver=f63af19c5e5a5d5f1a8fef3d276afb75:1:110)
    at upe_settings.js?ver=f63af19c5e5a5d5f1a8fef3d276afb75:1:902
    at upe_settings.js?ver=f63af19c5e5a5d5f1a8fef3d276afb75:1:913Understand this errorAI
    data.min.js?ver=7c62e39de0308c73d50c:2 Store "core/interface" is already registered.
    c @ data.min.js?ver=7c62e39de0308c73d50c:2Understand this errorAI
    index.js?ver=f6b99809c4bcabe8b8ec:2 Uncaught TypeError: (0 , e.createRoot) is not a function
    at index.js?ver=f6b99809c4bcabe8b8ec:2:561489
    at index.js?ver=f6b99809c4bcabe8b8ec:2:564195
    at index.js?ver=f6b99809c4bcabe8b8ec:2:564231

    Deactivating and re-activating the plugin also does not restore the settings page. It remains blank with the same errors.

    Kind regards,

    Simon

    • This topic was modified 6 days, 20 hours ago by harpo1984.
    • This topic was modified 6 days, 20 hours ago by harpo1984.
    • This topic was modified 6 days, 20 hours ago by harpo1984.
Viewing 12 replies - 1 through 12 (of 12 total)

  • ouch.

    yes having the same, cart and checkout pages blank.

    nothing appears in stripe settings page.

    gonna try rolling back….

    Dear oh dear. Lol breakage with every update ??

    • This reply was modified 6 days, 16 hours ago by itsmefti.
    Thread Starter harpo1984

    (@harpo1984)

    Hi, @itsmefti.

    Sorry to hear you are experiencing the same issue with the Stripe settings pages being completely blank.

    We aren’t experiencing a blank cart or checkout, however.

    Good luck,

    Simon

    Thanks @harpo1984

    Also noticed there seems to be no mention of Stripe in API and Webhooks section?

    Does this mean its “disconnected”? Rather confused now its all gone very wayward!

    Lol Shopify is creeping into my thoughts now… can’t deal with such chaotic breakages every 3 months!

    Same issue with blank settings dashboard

    Same here!

    Plugin Support Jonayed Hosen (woo-hc)

    (@jonayedhosen)

    Hi @harpo1984 ,

    I’m really sorry to hear that the WooCommerce Stripe Payment Gateway plugin stopped working after updating to version 8.9.0, and that rolling back didn’t help resolve the issue. The errors you’re seeing, especially those related to react-dom.min.js and upe_settings.js, indicate there might be a conflict between the plugin and your site’s JavaScript.

    To help troubleshoot, could you try the following steps?

    • If you’re using caching plugins, clear all caches and also clear your browser cache to make sure you’re loading the latest scripts.
    • Deactivate all plugins except WooCommerce and the Stripe Payment Gateway. Then, check if the Stripe settings page loads correctly. If it does, reactivate the plugins one by one to identify any conflicts.
    • Switch to a default WordPress theme (like Storefront) and see if the issue persists.
    • Ensure WordPress, WooCommerce, and all plugins are updated to their latest versions.
    • Try deactivating and deleting the current Stripe plugin, then reinstalling and activating it again.

    If none of that works, it would be helpful for us to take a look at your System Status Report to better understand your setup. You can find this by going to WooCommerce > Status in your dashboard, selecting Get system report, and then copying it for support.

    Also, if there are any fatal error logs, it would be great if you could share those as well. You can find them under WooCommerce > Status > Logs.

    Once you’ve gathered this information, please paste it into a code block in your reply, or use pastebin.com and share the link with us.

    I hope this helps, and we’ll be happy to assist further once we have more details!

    i have disabled all plugins and theme, same issue

    Resolved for me

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @pipoulito,

    Mind sharing the steps you took to help resolve this issue. This way, @harpo1984 can also follow the steps to see if it helps solve their issue.

    Cheers!

    sorry but i don’t understand how it has worked again…

    Thread Starter harpo1984

    (@harpo1984)

    Hi, @ckadenge.

    I can confirm that like @pipoulito one of the sites has resolved the issue seemingly on its own.

    However the other site which is also impacted is still facing the same issue.

    @jonayedhosen, you can’t perform all those changes on a live website (only some of them), so I will need to spin up a staging website to investigate further, but I can confirm:

    • All caches have been cleared (and caching plugins disabled).
    • All plugins and WordPress are up to date.

    Kind regards,

    Simon

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi Simon @harpo1984,

    so I will need to spin up a staging website to investigate further, but I can confirm:

    • All caches have been cleared (and caching plugins disabled).
    • All plugins and WordPress are up to date.

    In some cases, updates can cause conflicts with other plugins. However, it is a best practice to make tests on a staging site to avoid messing with your live store. Once you are done running the conflict tests from your staging site, you can reach out with your findings so that we can assist you further.

    Looking forward to hearing back from you.

Viewing 12 replies - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.