Woopayments broken with JS errors

  • Resolved Triweb Digital

    (@triwebdigital)


    4 months, 3 weeks ago

    Getting below errors on Woopayments page, cant use the gateway and unable to access the settings page etc.


    Woocommerce Version 10.4.3

    Woopayments Version 10.4.0

    at Cw (/wp-content/plugins/woocommerce-payments/dist/index.js?ver=10.4.0:2:578779) at Suspense at Pe (/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=311846ae4291f8628515:2:160195) at div at div at me (https:///wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=311846ae4291f8628515:2:158812) at div at a_ (https:///wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:221298) at c_ (/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:221939) at f_ (/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:222284) at w (/wp-content/plugins/woocommerce/assets/client/admin/admin-layout/index.js?ver=092d36684bd43b3c307d:1:1989) at Pn (https:///wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=311846ae4291f8628515:2:221657) at O (https:///wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=311846ae4291f8628515:2:127106) at P (https:///wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=311846ae4291f8628515:2:126547) at a (https:///wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=311846ae4291f8628515:2:121061) at https:///wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=311846ae4291f8628515:2:224303 at https:///wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:157128 at https:///wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:158205 at https:///wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:155018 at https:///wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:155018 at https:///wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:156243 at Rn (https:///wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=311846ae4291f8628515:2:229402)


    react-dom.min.js?ver=18.3.1.1:10 TypeError: Cannot read properties of undefined (reading ‘filter’)
    at index.js?ver=10.4.0:2:579647
    at Array.map ()
    at Cw (index.js?ver=10.4.0:2:579591)
    at ht (react-dom.min.js?ver=18.3.1.1:10:45677)
    at vr (react-dom.min.js?ver=18.3.1.1:10:56342)
    at Qs (react-dom.min.js?ver=18.3.1.1:10:121002)
    at wl (react-dom.min.js?ver=18.3.1.1:10:88341)
    at bl (react-dom.min.js?ver=18.3.1.1:10:88269)
    at yl (react-dom.min.js?ver=18.3.1.1:10:88132)
    at il (react-dom.min.js?ver=18.3.1.1:10:84984)
Viewing 4 replies - 1 through 4 (of 4 total)
  • LovingBro (woo-hc)

    (@lovingbro)

    4 months, 3 weeks ago

    Hi @triwebdigital,

    I can see how disruptive this is, especially when WooPayments pages are throwing JavaScript errors and blocking access to the gateway and settings. That kind of behavior can bring day to day store management to a halt, and I am keen to help get clarity on what is triggering it and guide you toward a fix.

    To narrow this down, could you let us know when you first noticed the issue, and whether it started after a recent update to WordPress, WooCommerce, WooPayments, or any other plugin or theme on the site. That timing often gives us a strong clue about the underlying cause.

    It would also help a lot if you could share a screenshot of the error page you are seeing, uploaded via https://snipboard.io, and your full WooCommerce System Status Report. You can find the report under WooCommerce, Status, then copy the report and share it using https://pastebin.com. With those details, we can review the environment more closely and advise on the next steps.

    Once you have those ready, feel free to drop them here and we will take it from there.

    Thread Starter Triweb Digital

    (@triwebdigital)

    4 months, 3 weeks ago

    Hello, the issue is there for a while, but we never noticed and our customers couldn’t pay for their orders and never get any error messages etc when they click on order button on checkout.

    We did a detailed review, and then we disabled the payments for now, but we cant access the settings page etc to troubleshoot further at all.

    https://prnt.sc/38N7P-iWh2Um

    https://pastebin.com/ThKvDr4j

    LovingBro (woo-hc)

    (@lovingbro)

    4 months, 3 weeks ago

    Hi @triwebdigital,

    Thanks for taking the time to share both the system status report and the screenshot, that really helps paint a clearer picture of what is happening on your end. I can see how disruptive this has been, especially with customers unable to complete payments and the WooPayments settings page being inaccessible, and I am keen to help you narrow this down.

    From what you have shared, the next best step is to run a plugin conflict test. This helps confirm whether another plugin is interfering with WooPayments and triggering the JavaScript error you are seeing. To do this safely, you can temporarily deactivate all plugins except WooCommerce and WooPayments, then check if the Payments page loads correctly. If it does, you can reactivate the other plugins one at a time until the issue reappears, which will point us to the conflicting plugin. You can follow the official guide here: https://woocommerce.com/document/how-to-test-for-conflicts/

    Alongside that, it would also be useful to temporarily switch to a default WordPress theme such as Twenty Twenty Four and test again, as themes can sometimes enqueue scripts that affect the admin experience. This is also covered in the same conflict testing guide above.

    Once you have a chance to run these tests, let us know what you observe. That information will help us decide the most effective next steps to get WooPayments fully accessible again.

    Plugin Support Ejay F – a11n

    (@ejayfernandes)

    4 months, 1 week ago

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

    If you have a few minutes, we’d love if you could leave us a review: https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.