Hi @thedenizen,
Thanks for the detailed report and for already running through health check.
I see the issue is related to Google for WooCommerce, so I would recommend opening a thread on its support forum. I know it’s a hassle having to post in the wrong channel the second time, so I’ll go ahead and explain what’s happening so you can reply in the right forum.
Looking at the console error in your screenshot, the crash is happening inside @wordpress/data‘s internal store subscription machinery, triggered by Google for WooCommerce’s settings.js when the Merchant Center setup page loads. The error pattern suggests a JS package version mismatch, specifically, the way Google for WooCommerce’s settings script is interacting with the @wordpress/data store registry appears incompatible with what WooCommerce 10.6.1 currently ships with. This would explain why it persists even with only those two plugins active.
Before we dig deeper, could you try a couple of things:
- Hard clear your browser cache. Not just a normal refresh, but a full cache wipe (in Chrome: Settings → Clear browsing data → Cached images and files). Then try loading the Merchant Center setup page again. This rules out a stale
commons.js being served from cache, which can cause exactly this type of mismatch.
- Try in a different browser (Firefox, Edge, etc.) with no extensions (or incognito) just to confirm whether it’s browser/cache specific.
- Share your System Status Report at WooCommerce → Status → Get system report, pasted at https://gist.github.com. Particularly interested in your PHP version, server environment, and any other active plugins.
I hope that helps. I’ll go ahead and close this thread, but please let us know how the cache clear goes in the new thread! Be sure to add a link to this one.
Hi frank sorry for posting in the wrong threads, ive been panicking because off the issues with the product feed that have occured because of my stupidity in trying to fix it even though it was technically still working.
This is the thread: https://wordpress.org/support/topic/typeerror-ne-is-not-a-function-2/
No worries @thedenizen!
That happens and we completely understand. We’ll continue troubleshooting in the other thread.
Take care.