Oops, something went wrong

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    2 days, 1 hour ago

    Hi @brthmrk!

    Thanks for reporting this. I understand that WooCommerce Analytics is not loading and is showing the following JavaScript error:

    TypeError: Cannot read properties of undefined (reading 'store')

    In short, this indicates that WooCommerce’s Analytics/admin JavaScript is trying to access data that isn’t available as expected. This can sometimes be caused by a plugin/theme conflict or another change affecting the WooCommerce admin.

    To help us investigate further, could you please:

    1. Share your WooCommerce → Status → System Status Report with us via Pastebin. Please enable Burn After Read when creating the paste so the report is not publicly available.
    2. Any relevant error logs from WooCommerce → Status → Logs. Please select the latest log entries that appeared around the time the Analytics issue occurred and share them with us.
    3. Let us know if you made any changes to the site shortly before the Analytics issue started, such as updating/installing a plugin or theme, changing settings, or updating WordPress/WooCommerce.

    Once we have these details, we can take a closer look and advise on the next steps.

    Thread Starter brthmrk

    (@brthmrk)

    2 days ago

    1. https://pastebin.com/CtTtq8H0
    2. There are no relevant logs
    3. No nothing changed
    Zahid Ul Islam

    (@zahidui)

    1 day, 13 hours ago

    Thanks for sharing the System Status Report. Since the error is thrown by WooCommerce’s bundled Analytics/admin JavaScript, could you try these checks on a staging copy (or during a maintenance window)?

    1. Go to WooCommerce → Status → Tools and run Clear Analytics Cache, then reload Analytics in a private browser window.
    2. Check WooCommerce → Analytics → Settings for failed historical imports. If the import reports failures, open the related log and retry the import after the cache is cleared.
    3. Temporarily disable JavaScript optimization/combining and run a conflict test: leave only WooCommerce active and switch to a default WordPress theme. If Analytics loads, re-enable the other plugins/theme one at a time to identify the conflict.
    4. With the error reproduced, open the browser Network panel and reload Analytics. Please share the status and response body of any failed wc-analytics REST requests, together with the WordPress and WooCommerce versions. Redact domains, emails, tokens, and customer data.

    If the error still occurs with a default theme, only WooCommerce active, caches disabled, and a clean Analytics cache, that would be useful evidence for a WooCommerce bug report. The WooCommerce JavaScript troubleshooting guide recommends the cache/optimization and full conflict checks above.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    1 day, 2 hours ago

    Hi @brthmrk!

    Thanks for sharing the System Status Report. I’ve reviewed it, and I can see that your site has a number of plugins installed, along with several outdated WooCommerce templates. These can potentially contribute to the issue you’re experiencing.

    To help us narrow this down, could you please run a conflict test by temporarily deactivating all plugins except WooCommerce and switching to a default WordPress theme, such as Twenty Twenty-Five or Storefront? Then, please check whether you still experience the same issue.

    I recommend performing this test on a staging site so your live site remains unaffected. You can use the WP Staging plugin to create a staging environment.

    You can also follow our guide for detailed instructions on performing a conflict test:

    How to test for conflicts

    Once you’ve completed the test, please let us know whether the issue still occurs with only WooCommerce active and a default theme enabled.

    Thank you!

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

You must be logged in to reply to this topic.