• elisalopez

    (@elisalopez)


    Hi team,

    I’m having an issue with the WooCommerce Home/Analysis dashboard (WooCommerce Admin). When I open WooCommerce → Home / Analysis, the page crashes and shows an error screen. In the browser console I consistently get:

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

    and the stack trace points to WooCommerce Admin / WordPress core scripts, for example:

    at ll (https://aoralife.com/wp-content/plugins/woocommerce/assets/client/admin/components/index.js?ver=aaab180e037e84550a39:2:600773)
    at https://aoralife.com/wp-includes/js/dist/viewport.min.js?ver=f07b4909c08cfe9de4e2:2:1394
    at WithViewportMatch(ll) (https://aoralife.com/wp-includes/js/dist/compose.min.js?ver=7a9b375d8c19cf9d3d9b:9:13904)
    at v (https://aoralife.com/wp-content/plugins/woocommerce/assets/client/admin/chunks/dashboard-charts.js?ver=f5522d7a910eb9fa154d:1:775)
    at https://aoralife.com/wp-includes/js/dist/data.min.js?ver=f940198280891b0b6318:9:3361
    ...
    at D (https://aoralife.com/wp-content/plugins/woocommerce/assets/client/admin/chunks/customizable-dashboard.js?ver=f76e89c4d8f4e59ce880:1:6906)
    ...
    at G (https://aoralife.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=0cd23dbb9aaf179ae6e6:2:523670)
    

    What I’ve tried so far (no fix):

    • Switched site language to English and back.
    • Disabled JS/CSS minify/combine/defer and fully disabled WP Fastest Cache.
    • Purged all caches (plugin + CDN/hosting where possible).
    • Ran WooCommerce Status → Tools (cleared analytics cache, transients, regenerated analytics tables, updated inbox notifications, etc.).
    • Reinstalled WooCommerce.
    • Removed any custom code/snippets I had added.
    • Created a brand-new admin user and tested — same issue.

    So the problem seems global to wc-admin (not user-specific) and likely a plugin conflict or a compatibility issue with the current WordPress/WooCommerce versions. Could you advise on next steps or confirm if this is a known issue?

    Thanks!

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    Hi @elisalopez,

    I can see how disruptive it is when the WooCommerce Home or Analytics dashboard crashes, especially since it is such an important part of managing your store. Thank you for walking through so many troubleshooting steps already and for sharing detailed information about the error you are seeing. This really helps narrow things down and shows how thorough you have been in trying to isolate the cause.

    To understand this better, can you clarify when you first started noticing this behaviour on your site. Did it begin after a recent update of WordPress, WooCommerce or any other plugins or your theme. Any change in that timeframe can help point us in the right direction.

    When you can, please share a screenshot of the error you see on your end using https://snipboard.io
    Also, kindly share your full WooCommerce system status report. You can generate it by going to WooCommerce, Status, Get system report and then copy it into a service like https://pastebin.com or https://quickforget.com and send the link here.

    Once we have this extra information, we can continue digging into the cause and help get your dashboard loading smoothly again. Looking forward to your update.

    Mattia Merlin

    (@mattiamerlin)

    Hello,
    I am experiencing the same issue on my website.
    The Analytics page appears to load, but then the background remains gray without responding.
    Everything in the network seems to be returning a 200 status code, so there do not appear to be any errors.

    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    Hi @mattiamerlin, it is good to hear from you and I can see you are experiencing the same issue. I want to make sure your case gets proper attention so we can look into it correctly for your setup.

    Per the forum guidelines, each user should create their own support topic so we can troubleshoot separately without mixing different site configurations. You can check the guideline here https://ww.wp.xz.cn/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too

    Please create a new topic here https://ww.wp.xz.cn/support/plugin/woocommerce/#new-topic-0 and include the details you already shared so we can assist you directly.

    Thanks for your understanding.

    I have seen a couple of people report this exact error and I am seeing the same thing. It doesn’t make sense that each of us post a new forum post for the exact same error. Was this ever resolved. This isn’t a plugin issue as I haven’t changed / updated any plugins and this error just appeared today for me.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @fonderco

    I understand your concern, especially since you’re seeing similar reports from other users.

    That said, we’ve tried to replicate this issue on our end but haven’t been able to reproduce it. This usually indicates that something specific to the individual site is triggering the behavior. Each site can have a different combination of plugins, custom code, themes, server settings, or caching layers, any of which could cause this kind of issue—even if no recent updates were made.

    Because of these differences, troubleshooting needs to be done on a case-by-case basis, which is why we recommend creating a separate support ticket. This allows us to look at your specific setup and provide more targeted guidance.

    Please create a new topic here https://ww.wp.xz.cn/support/plugin/woocommerce/#new-topic-0 and include the details of the issue so we can assist you directly.

    Hi, same here, same error!

    Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    Thanks for pointing that out @hpablo!

    Please open a new topic as @shahzeenfarooq mentioned, so we can look into it.

    Hi guys! I am also having the same error.

    Here is the error message for your reference:

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

    at Xs (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/components/index.js?ver=d47f50445b4993d55e83:2:600652) at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/viewport.min.js?ver=f07b4909c08cfe9de4e2:2:1394 at WithViewportMatch(Xs) (https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/compose.min.js?ver=7a9b375d8c19cf9d3d9b:9:13904) at v (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/chunks/dashboard-charts.js?ver=618f630c1b2d98e05076:1:775) at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/data.min.js?ver=f940198280891b0b6318:9:3361 at WithSelect(v) (https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/compose.min.js?ver=7a9b375d8c19cf9d3d9b:9:13904) at div at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:15659 at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:25289 at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:332853 at div at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:15659 at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:25289 at div at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:15659 at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:25289 at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:500 at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:331055 at div at g (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/chunks/dashboard-charts.js?ver=618f630c1b2d98e05076:1:24125) at div at div at I (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/chunks/dashboard-charts.js?ver=618f630c1b2d98e05076:1:27961) at Suspense at component at div at A (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/chunks/customizable-dashboard.js?ver=79752f18523658232e66:1:6925) at https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/chunks/customizable-dashboard.js?ver=79752f18523658232e66:1:7994 at https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/data.min.js?ver=f940198280891b0b6318:9:3361 at WithSelect(Component) (https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/compose.min.js?ver=7a9b375d8c19cf9d3d9b:9:13904) at Suspense at u (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/chunks/dashboard.js?ver=094a07ae1860b94da525:1:287) at Suspense at Ie (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=c80895686cf15fe5df09:2:158990) at div at div at me (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=c80895686cf15fe5df09:2:153131) at div at a_ (https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:221298) at c_ (https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:221939) at f_ (https://checkout.advancedcosmeceuticals.com.au/wp-includes/js/dist/components.min.js?ver=ad5cb4227f07a3d422ad:26:222284) at w (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/admin-layout/index.js?ver=092d36684bd43b3c307d:1:1989) at Oo (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=c80895686cf15fe5df09:2:212223) at I (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=c80895686cf15fe5df09:2:120633) at N (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=c80895686cf15fe5df09:2:120064) at s (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=c80895686cf15fe5df09:2:114807) at https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=c80895686cf15fe5df09:2:214813 at https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=411c9de47bbcc5579cf6:2:145748 at https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=411c9de47bbcc5579cf6:2:146825 at https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=411c9de47bbcc5579cf6:2:143638 at https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=411c9de47bbcc5579cf6:2:143638 at https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=411c9de47bbcc5579cf6:2:144863 at Lo (https://checkout.advancedcosmeceuticals.com.au/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=c80895686cf15fe5df09:2:215737)
    • This reply was modified 3 months, 2 weeks ago by dannielibor.

    Here is what I did in the short term to fix the issue.

    in the file: \wp-content\plugins\woocommerce\assets\client\admin\components\index.js

    Find this part of the code:

    totalLabel:(0,y.sprintf)(b,N.length)

    Change to:

    totalLabel:(0,y.sprintf)(b ?? ”,N.length)

    This will stop the error from crashing the page.

    I know this is NOT a long term solution.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @fonderco

    Thank you for sharing the solution. However, we were not able to replicate the issue. I’ve escalated this internally with the team and will get back to you if we’re able to reproduce the issue.

    @fonderco many thanks, it solved the problem, today I have another error (TypeError: Cannot read properties of undefined (reading ‘Spinner’)) but cleaning cloudflare’s cache brought first error again, and now with your fix its working OK! many thanks! Have almost 100 sites I didnt check all but was happening with only 1 site by now.

    Hi @hpablo ,

    I’m glad you found @fonderco’s response helpful and were able to resolve the issue on your end—great work!

    @elisalopez, it looks like we haven’t received a response from you yet. You might also want to try @fonderco’s suggestion to see if it works for your situation temporarily.

    Looking forward to your update.

    This has also just appeared on my site as well

    Hi @uncle-chenzo,

    Thanks for reporting this. To keep things organized and make sure we can look into your setup properly, could you please open a new support thread for your site and share the details there?

    Per forum best practices, each site should have its own topic since configurations can differ. Once you open the new thread, please include:

    • When you first noticed the issue
    • Your WordPress & WooCommerce versions
    • The full error message / console output
    • A copy of your WooCommerce System Status (via pastebin/quickforget)

    You can open a new topic here:
    https://ww.wp.xz.cn/support/plugin/woocommerce/#new-topic-0

    We’ll be happy to help once that’s done

    gillavry

    (@gillavry)

    Like many others, I have the same issue. Will you come with an update fixing it? I can open a new support thread like you suggest, but it saves everyone time by just waiting for the update?

Viewing 15 replies - 1 through 15 (of 18 total)

You must be logged in to reply to this topic.