Hi there,
Thank you for reporting this and for sharing the screenshot I understand how concerning this can be after updating WooCommerce.
The error message:
“TypeError: t(…)(…).tz is not a function”
usually indicates a JavaScript conflict affecting the WooCommerce Analytics interface. In most cases, this happens when another plugin or the active theme loads a script that conflicts with WooCommerce’s admin analytics scripts after an update, rather than being caused by Analytics itself.
I’m not currently seeing a widespread core issue reported for WooCommerce 10.6.0, so the next step is to narrow down what may be causing the conflict on your site.
Could you please try the following checks?
Head over to WooCommerce → Status → Tools, and do the following:
- WooCommerce transients – Clear
- Expired transients – Clear
- Clear template cache – Clear
- Capabilities – Reset Capabilities
- Clear customer sessions -Clear
Next, please clear your browser cache and then check again.
If that does not work, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:
- System Status Report which you can find via WooCommerce > Status
- Fatal error logs (if any) under WooCommerce > Status > Logs.
Please use https://pastebin.com/ or https://gist.github.com/ and share a link to that paste in reply here. Once we have more information, we’ll be able to assist you further.
Thank you for your assistance. Unfortunately that didn’t seem to work. I don’t have any folders called fatal-errors in the log, so I don’t think there are any.
But here is the system status:
https://gist.github.com/alwayssomething2026/e0acbcde0a0088a7998ac466ee563061
In the error portion of the initial screenshot I posted, it only mentions .js files, so I think you are correct about javascript being the issue somehow.
Hi there!
Thank you for sharing the system status and additional details. I can see you are using many plugins on your site, and I suspect that one of them may be causing the issue.
In that case, The next step I recommend is to run a conflict test on a staging site. This will help identify if a plugin or theme is causing the problem. You can follow the guide here for detailed steps: How to Test for Conflicts.
Once the conflict test is complete, you should be able to pinpoint the source and take the appropriate action.
Let us know what you find, and we can help guide you further from there.
Since there’s been no recent activity on this thread, I’m marking it as resolved. Don’t hesitate to start a new thread if you need help in the future.
Your feedback helps others – please consider leaving a review: https://wordpress.org/support/plugin/woocommerce/reviews/#new-post
