5.7.1 – Analytics crashing

EDIT: This solution does work just make sure when you copy and paste the code you need to redo the apostrophes as they format incorrectly.

// temporarily dosables WOO Analytics info on dashboard – disables all Woo Analytics!
add_filter( 'woocommerce_admin_disabled', '__return_true' );

• This reply was modified 3 years, 2 months ago by clownguts. Reason: Solution does work corrected for mistake

@clownguts Thank you for your comment! Am i doing something completely wrong? I added the code in the function.php. I even made a screenshot:

View post on imgur.com

But when im activating Woocommerce the backend will just freeze again and is not accessible.

• This reply was modified 3 years, 2 months ago by Naturaldude.

Want to give an update for my temporarily fix. I have downgraded WordPress to 5.6.2 and Woocommerce isn’t giving any problems anymore.

HI @markout

Good to hear your temporary solution is working. Since that functions.php fix didn’t work, it does sound slightly different from the problem I’m having.

Hopefully we’ll get a solution for the problem soon.

@markout I’d say your issue must be slightly different as you have that functions line correct. Glad the downgrade sorted it out however there is a security vulnerability in versions under 5.7.0 so just be mindful of that https://developer.woocommerce.com/2021/09/22/important-security-patch-released-in-woocommerce/

Hi guys to confirm 5.6.1 version didn’t work for me. At the moment my client is logging in & then choosing to use the report area for sales data. I’m back on 5.7.1 for now hopefully fix in the next update? currently when selecting the WP Dashboard the site CPU hits the ceiling & gives a 500 Error..

Sale are still coming through the store at least & this is def a Woocommerce dashboard Analytics issue..

Good luck guys!

Also just received the error from WP:
An error of type E_ERROR was caused in line 321 of the file: /wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Reports/TimeInterval.php. Error message: Maximum execution time of 30 seconds exceeded

• This reply was modified 3 years, 1 month ago by sipdesign.

@clownguts @sipdesign

Sorry maybe I was a bit unclear. I downgraded WordPress to 5.6.1. My woocommerce plug-in is still version 5.7.1 (currently the latest available). I also tried downgrading the woocommerce plug-in earlier but that had no effect. My only temporarily solution was to downgrade WordPress. Really interested if that also helps for you.

Hey guys, I had exactly the same issue. I am in NSW and I assumed it had to do with daylight savings starting on Sunday.

I think maybe they got the day wrong from when daylight savings starts so I changed my timezone in settings to Brisbane and it resolved the issue for me.

I will change my TimeZone back to Sydney on Monday after daylight savings started to see if the issue “disappeared”

• This reply was modified 3 years, 1 month ago by ozbraai.
• This reply was modified 3 years, 1 month ago by ozbraai.

Experiencing the same error issue here too, 1 hour ago I received the error from WP:
An error of type E_ERROR was caused in line 321 of the file: /wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Reports/TimeInterval.php. Error message: Maximum execution time of 30 seconds exceeded

Changing the time zone as suggested by ozbraai also worked for us being located in NSW Australia.

We hope this is resolved in a future update of Woocommerce

hey guys i hope this solves your issue. it worked for me ??

That issue is happening recently with the GoDaddy hosting. To fix it, please add the following to your .htaccess file

# BEGIN Line too long fix
<IfModule mod_substitute.c>
SubstituteMaxLineLength 10M
</IfModule>
# END Line too long fix

Hi

I am also facing the same issue I can’t login into the wordrpess admin area getting a 504 error. The issue is due to the latest version of woocommerce.

@big00ballz The above code is for Apache servers anybody knows the equivalent of NGINX code that could be used NGINX server then I can try that. My site hosted on Kinsta

Thanks

Reverting to WooCommerce 5.7.0 will fix the issue.

Hi there,

Thank you all for your reports.

I’ve not been able to reproduce the issue by upgrading WooCommerce to version 5.7.1. In this case, I recommend that you get more insights directly from WooCommerce developers and open a bug report here:

https://github.com/woocommerce/woocommerce/issues/new/choose

Doing that will bring it straight to the attention of the core developers, and they can check the issue directly.

Cheers.

I can confirm having this issue also now on atleast 3 sites. One on
PHP 7.35 two on 7.4.24.

All sites have latest updated plugins.

Today’s 2.7.1 update to “woocommerce admin” has resolved this issue for us and we no longer need “add_filter(‘woocommerce_admin_disabled’,’__return_true’);” in our theme’s functions.php file.