Oops, something went wrong – TypeError: Fe(…) is not a function
-
Hi, my website frontend works fine. But the backend is having some issues. Its taking a long time to load and I’m quite sure it is due to woocommerce. I’m unable to change prices as well and do anything on woocommerce on the backend. Please see the error that I got on my analytics page.
Upload and share screenshots and images – print screen online | Snipboard.io
-
Hi there!
Thank you for sharing the details. I understand that your website frontend is working fine, but the backend is loading slowly and WooCommerce actions like changing prices aren’t functioning properly.
To help us narrow this down, could you let us know if you made any changes on your site (plugins, themes, updates, etc.) after which this issue started appearing?
Also, 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.
Hi, updating prices is working fine. Is just that the backend is very slow and analytics and others are unable to be viewed.
I also had an issue with woo-commerce cart page recently where it gave an error only for the cart page. When I included only the woo commerce cart short code, it worked fine. Previously there was some theme file’s code.
However this slowness issue came after that. Only other change was that the Pro plugin of the Woo-delivery plugin had expired a month ago. But as per the plugin developers that won’t cause an issue, I will only be unable to change the initially setup settings.
Woocommerce Status – Status wc – Pastebin.com
I don’t see any fatal error mentioned in the logs
Thanks
Hi there!
Thank you for providing more information about the issue. I’ve checked the report, and I can see that you’re using multiple plugins on your site, which could be causing this issue.
To help us narrow this down, could you please deactivate all plugins except WooCommerce and activate a default theme such as Storefront to see if the issue still occurs? I recommend running this test on a staging site so your live site remains unaffected. You can use the following plugin to create a staging site:
https://ww.wp.xz.cn/plugins/wp-staging/Please let us know what you find.
Hi
I created the staging website. The admin dashboard is fine in the staging website but in the live website it is slow. This is even without making any changes to the plugins as you suggested.
The analytics page is also working fine without any error in the staging website
Hi there!
Thanks for the update. Since the issue only affects the live site, the next step would be to clear all caches.
To assist you further, please first try clearing your site cache. Once that’s done, go to WooCommerce → Status → Tools and perform the following actions:
- Clear WooCommerce transients
- Clear expired transients
- Clear template cache
- Reset capabilities
- Clear customer sessions
After completing these steps, please contact your hosting provider and ask them to clear the server-side cache, then check if this resolves the issue.
Let us know what you find
Hi
I tried all of the above and still facing the same issue. My cart page is also not working now.
Hi there!
For testing purposes, could you please disable the W3 Total Cache plugin and see if you still experience the same issue?
Regarding the cart page, could you please provide more information about the exact issue you are facing there?
I have disabled the W3 Total Cache plugin and still issue is there.
Time to time I’m getting and error code 522 error. Now the error is gone.The error code 522 I was referring to is for the cart page.
However the analytics page issue and the admin dashboard slowness issue is there. This is not there for the products page though. It is there for the customers, payments, analytics and extensions pages.
Hi there!
Thank you for the update. I suspect there may be a plugin on your live site that’s causing this issue.To help isolate the cause, could you please try the following on the live site:
- Temporarily deactivate all plugins except WooCommerce
- Then check whether the slowness and issues still occur on the Customers, Payments, Analytics, and Extensions pages
If the issue no longer occurs after doing this, it would confirm that one of the plugins is causing the conflict. You can then reactivate the plugins one by one to identify which one is responsible.
Let us know how it goes, and we’ll be happy to help you further.
Hi
I tried deactivating all the plugins and also changed the theme to twenty twenty five and still it is slow. The errors in the woocommerce pages are also still the same.
The staging website works fine though when checking after reactivating all the plugins.Hi @zakir123,
Since the issue persists on the live site even with all plugins disabled and a default theme active, and does not reproduce on staging, this strongly points to a server level or environment specific difference between live and staging. At this stage, the next practical step is to involve your hosting provider directly. Please ask them to check server resources, PHP error logs, slow query logs, and any security or firewall rules, especially since you mentioned seeing a 522 error earlier, which often indicates a server timeout or connection issue. It would also be worth confirming whether any server side caching, CDN, or security layer is active only on the live site and not on staging.
From the WooCommerce side, you can also enable WordPress debug logging temporarily on the live site to capture any PHP or JavaScript errors when loading Analytics or other affected admin pages. This guide walks through enabling debug logging safely, https://ww.wp.xz.cn/support/article/debugging-in-wordpress/. Once logs are generated, you can share the relevant entries using https://pastebin.com or https://gist.github.com so we can review them.
If your host confirms there are no server side issues and the logs do not reveal anything conclusive, the next step would be for the host to compare the live and staging environments closely, including PHP version, memory limits, database configuration, and any active server modules, as even small differences can cause this kind of behaviour.
Please keep us posted on what your host finds or share any logs you are able to collect, and we will continue working with you on this until we get clarity.
It’s been a while since we heard back from you for this reason we are closing this thread.
If WooCommerce has been useful for your store and you appreciate the support you’ve received, we’d truly appreciate it if you could leave us a quick review here:
https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/#new-post
Feel free to open a new forum topic if you run into any other problem.
You must be logged in to reply to this topic.