Hi there!
Thanks for reaching out and letting us know about this I understand how confusing that “Oops, something went wrong” message can be, especially when it doesn’t give any details.
As a first step, could you please try clearing both your site cache and your browser cache, then attempt to access the Analytics page again? Sometimes cached data can cause this type of issue.
If the problem persists after clearing the caches, 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.
I cleared the cache and no change. This is the pastebin link https://pastebin.com/BMVehGcw
Hi there,
Thanks for sharing the error details and system status report. I’ve checked the System Status Report, and I can see that the WordPress memory limit is currently set to 40MB, which is very low.
This error “CRITICAL Allowed memory size of 268435456 bytes exhausted” indicates that the site is running out of memory when trying to load the Analytics page. WooCommerce Analytics can be memory-intensive, and with such a low memory limit, the request fails and results in the generic “Oops, something went wrong” message.
To resolve this, I recommend contacting your hosting provider and asking them to increase the WordPress / PHP memory limit to at least 512MB. Once that’s done, please clear any site cache and try accessing WooCommerce → Analytics again.
If the issue persists after increasing the memory limit, please let us know and share any updated error messages so we can take a closer look.
Done that and still the same just the same errormessage
Hi there!
Thank you for the update. Could you please share the new System Status Report again?
In the meantime, please try to run a conflict test. Here is a guide to help you with the steps:
https://woo.com/document/how-to-test-for-conflicts/
Let us know what you find.
The conflict test will be a challenge due to issues with our host and the fact they screwed up our site last time we did anything like this
https://pastebin.com/fkSmMsLP
Hi there!
Thank you for sharing the System Status Report. I can see that the memory limit is not set to 512MB.
If increasing the memory does not help, it’s possible that a plugin or custom code on your site is causing this issue. I have seen a similar issue before here: https://ww.wp.xz.cn/support/topic/error-oops-something-went-wrong-5/, where a plugin conflict was the cause. That is why we suggest running a conflict test.
However, before running a conflict test, please go to WooCommerce → Status and do the following:
- Clear analytics cache
- WooCommerce transients – Clear
- Expired transients – Clear
- Clear template cache – Clear
Next, please clear your browser cache and then check again.
If that does not work, please create a staging site. You can use the following plugin to create a staging site: https://ww.wp.xz.cn/plugins/wp-staging/. Then run the conflict test on the staging site so that your live site remains unaffected.
No change after deleting cache’s
WP Staging failed to create a development site so I will have to do it manually
Hi @colinsp,
I can see how cautious you are being here, especially given the past issues with your host, and that makes complete sense. We want to make sure this is tested safely without putting the live site at risk, and a staging environment is the right approach.
Once you have the staging site created and the tests completed, please let us know the outcome so we can take the next step with you. Many hosting providers offer a built in staging feature directly within cPanel or their hosting dashboard, so it is worth checking there first before setting it up manually.
If you need guidance on running the conflict test once the staging site is ready, this guide walks through the process in detail https://woo.com/document/how-to-test-for-conflicts/.
Looking forward to your update, and we will take it from there together.
I found the issue the plugin causing issues was PublishPress Capabilities
Hi there!
I’m glad you were able to identify PublishPress Capabilities as the plugin causing the issue. That definitely helps explain the behavior you were seeing.
If you’re happy with the support you received today, would you consider leaving us a quick review? It really helps us out: https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/#new-post
Thank you
