Be careful: Update 8.5.2 crashed my site

I had to downgrade to 8.4.0 also, 8.5.x seems to be a total disaster and constant 500 and 504 errors due to the upgrade.

Hi @retepuang and @allmyhoney,

Sorry to hear that the site crashed after you updated to 8.5.2.

Can you please share more details on the error you encountered? We have merchants who are using WooCommerce 8.5.2 without any issues so I’d like to review the error and see if it’s reproducible.

Can you please share the below details?

• System Status Report: You’ll find it at the top of the page under WooCommerce > Status > Get system report > Download for support (after you scroll down a bit). Once you have the System Status Report file, please attach it to your reply. (Please remove any sensitive information from the System Status Report).
• The fatal error you encountered.

Looking forward to your reply!

My issue is outlined here https://developer.woo.com/2024/01/16/woocommerce-8-5-1-issues-with-web-application-firewalls-modsecurity/ and basically I am waiting on a fix as my host will not alter the Mod Security rules on their managed servers. So just waiting on the fix basically. I am using V8.4.0 for now but would like to use the latest version of course when a fix comes out.

We also have a similar issue with woo 8.5.2

8.5.2 produces error 404 on product categories.

Theme storefront version: 4.5.4

A reset to version 8.5.1 solved the problem.

The error is not documented in the Woo log.

Addendum: We had problems updating to Woo 8.5.0. These were related to the switch to HPOS. We had to remove some plugins that affect the ordering process. These plugins have not been maintained for a long time.

I confirm the problems.

1. Problem with editing: Storefront Wersja: 4.5.4.
2. Strange redirections to the home page from categories and products.
3. Clicking on some tabs shows: File not found.

The problems only occur in the browser Firefox.

Woo version 8.5.2 with new test without errors. The errors occurred in the cache. Recommendation: Always clean the cache in WP Super Cache after updating Woocommerce!

Hello

we got the same Problem after updating to 8.5.2. The further problem is that we can not downgrade to 8.4 even not to 8.3.1. When installing these zip file we get an 500 error.

Aktives Theme: Kinetika for WordPress (Version 6.6.1)
Aktuelles Plugin: WooCommerce (Version 8.5.2)
PHP-Version 8.0.30

Fehler-Details
==============
Ein Fehler vom Typ E_ERROR wurde in der Zeile 2009 der Datei /var/www/web30172/apps/fotohedwig/wp-content/plugins/woocommerce/includes/wc-core-functions.php verursacht. Fehlermeldung: Allowed memory size of 268435456 bytes exhausted (tried to allocate 68276871276 bytes)

Are there any propositions what do do? I do not believe the extension to 68276871276 bytes will be the resulution ….

Thanks woolie

• This reply was modified 9 months, 3 weeks ago by woolie4.

Hey @druideniggi, @maxwww, and @woolie4!

I’m sorry to hear each of you has been experiencing issues with updating WooCommerce.

Each of these sounds like a different issue. To keep the problems separate and to ensure you receive the help you need, please create a new support thread for your issue.

When you open the thread, please provide as much detail as possible, including the system status report, fatal error logs if they exist, and any screenshots that may help understand the problem. If you want to get a head start on troubleshooting, you can also consider running a full conflict test.

If you have a site that is using Avada and you’re running into problems with 8.5.x, please check out this comment on GitHub for details on a conflict our developers found with Avada.

Hello,

I deactivated 3th party combine in Avada (adviced by Avada Support) and the problem is gone.

Best,
Tom

@tom-van-m what do you mean you “deactivated 3rd party combine in Avada” ? I also use Avada, what is 3rd party combine? Is that a plugin or a setting or something? Thanks

You’ll find it under Avada > Options > Performance > Combine Third Party CSS Files. If you don’t see it, turn on CSS Compiling Method > File

@tom-van-m Thank you, I have done this now like so: https://share.zight.com/NQuBYvOO

Yes, with this setting the problem stopped here