• Ruben

    (@rubenecho)


    Hi team,

    We are trying to access the Woocommerce Analytics page but its not working and showing a fatal error

    Error information here – https://pastebin.com/9c1uKw2g

    Can you please with what is causing this?

    Kind Regards
    Ruben

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    Hi @rubenecho,

    Thanks for sharing the error details!

    I checked for similar reports and this matches a known pattern: the TypeError: n[e] is not a function error in WooCommerce’s Analytics admin JS has appeared in a few recent threads, and the strongest lead right now is a JavaScript dependency conflict involving Pinterest for WooCommerce on WooCommerce 10.9.x, where a regenerator-runtime bundled by Pinterest collides with WooCommerce’s admin module registry and causes this exact crash across WooCommerce admin pages.

    Could you confirm a few things:

    1. Which WooCommerce version are you currently running?
    2. Did this start after a recent WooCommerce, WordPress, theme, or plugin update?
    3. Do you have Pinterest for WooCommerce active on the site?
    4. Is this limited to Analytics, or do other WooCommerce admin pages also fail to load?

    If Pinterest for WooCommerce is active, please temporarily deactivate it and check whether Analytics loads again. That’s the quickest way to confirm or rule out that conflict.

    If that doesn’t help, also try clearing any server, CDN, or browser cache and reload Analytics in a private/incognito window.

    And please share your System Status Report at WooCommerce → Status → Get system report → Copy for support, then paste into pastebin.com or gist.github.com and share the link here.

    Let us know how it goes!

    Thread Starter Ruben

    (@rubenecho)

    Hi there,

    We are not using pinterest and we have the latest version of woocommerce installed. I clear the website cache and cloudflare cache and this is working again.

    Do you know why this would be the case?

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @rubenecho!

    Thanks for the update. I’m glad to hear that clearing your website and Cloudflare caches resolved the issue.

    It’s difficult to determine the exact cause now that the issue is no longer occurring. A stale cache can sometimes continue serving outdated files after an update, and clearing the cache forces fresh files to be loaded, which can resolve unexpected errors.

    If the issue does happen again, please let us know and we’ll be happy to investigate further.

    Thread Starter Ruben

    (@rubenecho)

    Hi there,

    Had my colleague in a different office and network try it and he is saying its not working for him.

    Here is the system status – https://pastebin.com/nhbh6bwS

    Hope this helps

    Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    Hi @rubenecho,

    Thanks for sharing the system report, and for having your colleague test this too.

    Analytics itself is enabled, and Action Scheduler isn’t backed up, so this looks more like the admin JavaScript app getting interrupted while loading, not a data import issue.

    A few things stand out as worth testing: WP Rocket, Object Cache Pro, Freesoul Deactivate Plugins (active as a must-use plugin), and the number of active plugins/extensions overall.

    Two quick things first:

    1. Could you get the exact browser console error your colleague sees? If it matches your original TypeError: n[e] is not a function, we’re likely looking at one issue across two networks. If it’s different, we may have two separate causes.
    2. Was his test done with only WooCommerce active and a default theme (Storefront), using the Health Check & Troubleshooting plugin? That lets you test cleanly on your admin account without affecting visitors.

    If the error still happens in that clean test, please share a console screenshot (via snipboard.io), any fatal errors from WooCommerce → Status → Logs, and whether it persists in incognito after clearing site, WP Rocket, and Object Cache Pro caches.

    If it doesn’t happen in the clean test, we’ll re-enable plugins one by one (starting with WP Rocket, Object Cache Pro, and Freesoul Deactivate Plugins) until it returns.

    One note: I wouldn’t attribute this to the outdated theme templates as those are frontend-only and unlikely to affect the Analytics admin screen.

    The stack trace should help identify whether this is coming from WooCommerce Admin itself or a plugin/theme conflict. It may be worth testing with non-WooCommerce plugins temporarily disabled and confirming that WooCommerce, WordPress, and PHP versions are fully compatible.

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

You must be logged in to reply to this topic.