WooCommerce v8.5.1 – Broke My Website

The WordPress site that I have issues with while running WC v8.51 is on the Midphase.com shared web hosting server. Perhaps you can find out the type of server Midphase.com is using?

@khoavo can you please share with us the exact hosting plan you’re using at Midphase.com that has this issue?

@dinhtungdu – One of the site we are using that is affected by WC 8.5.1 is also hosted with Midphase.com on their Starter Web Hosting Plan. It’s one on their Shared Hosting Server. But I believe this issue affects any of their shared hosting plans.

I already had Midphase senior technicians troubleshoot on this issue and they concluded it’s due to WC 8.5.1 when activated, somehow overloads the CPU & Physical Memory, causing the site to crash, with internal server error, etc.

On the other hand, we have another site on the Godaddy.com shared web hosting server and that site has no issues with WC 8.5.1.

Hi there @khoavo,

As the majority of us are unable to replicate the issues on our test sites, do you mind performing an update on a test site to see if the same issue persists on the latest WooCommerce V 8.5.2?

Let us know how it goes.

@ckadenge – Once again, I did another test by updating WC to v8.5.2: https://prnt.sc/cq9p9oAo48Pw on a test site and the same issue persist. WC 8.5.1 and 8.5.2 overloads the server, hogging the entire CPU and Memory RAM usage, causing Internal Server Error & breaks all websites on the server: https://prnt.sc/ypg30QDoobUy – Even when I activated only the default TT3 theme and with all other plugins deactivated and with only WC activated…FYI.

You guys need to contact some of the Hosting Providers and are being affected by your latest WC v8.5.1, etc. The one hosting provider I know for sure is affected by this is: Midphase.com – Perhaps you contact their support dept. and get details on their share hosting server.

The other web hosting provider that’s not affected by WC 8.5.1 or 8.5.2 is Godaddy.com – Because I have another Client’s website on their shared hosting server and the site runs fine with WC 8.5.1 or 8.5.2

The other users on this thread that’s also having the same server issue with WC 8.5.1 or 8.5.2, you should find out their Hosting Providers and contact those hosting companies as well for their server info to compare.

I’v already sent your team my WooCommerce System Status for both the sites that’s not affected and for one that is affected. It was paste and sent on your QuickForget.com portal, did you not review that? I’ve spent a lot of time doing these site tests for you guys. Come on, let’s fix this. Thanks!

• This reply was modified 10 months ago by khoavo.

@khoavo, this doesn’t seem to be related to certain hostingproviders. I have multiple WooCommerce sites on my server and only one is affected by this bug. The server also has more than enough resources, so it’s not a limited shared hosting package that’s too small for the site. It must be caused by something on the website and as it’s not related to the theme, it must be something in the settings or data that’s handled by WooCommerce.

The developers should reverse engineer how the calls to all the CSS files (mentioned earlier and in other topics on this forum as well) are made in an endless loop and step back to figure out where it happens and in what conditions. Then we can check these circumstances on the affected websites and try to find a solution.

@josklever – I activated the default TT3 theme and deactivated all other plugins except WC 8.5.1 but the same issue persist. From testing on my end, this issue appears to affect some Hosting Providers and not others.

Yes, whatever they did on the WC 8.5.1 update ain’t compatible with some hostings and the Shared hosting level does not matter.

It would only be related to certain hosting providers if every WC site with that provider would have the same issue. I’ve got clients with all kinds of providers and 19 of them on my own server. Only 1 site is affected on that server. So it’s not related to the server or the hosting provider. It’s something in the site, but the big question remains: what?

@josklever – You should send some of your site’s WooCommerce System Status data to the WC support team so they can investigate further. Even the bare minimum Twenty Twenty 3 theme is affected by the WC 8.5.1 update. So I have no idea on the cause of this issue. Still waiting for WC to respond.

That would only be a system status of the site running 8.4.0, because with 8.5.x the server overloads. That’s why I mentioned that the devs should inspect the code to see where all the CSS files are getting loaded. Then we can investigate these steps and the related data.

I’m waiting until one of the many support people are taking this serious and get the devs involved, because this isn’t a bug that the first responders can fix.

I’ve just found the GitHub ticket, where I’ll respond: https://github.com/woocommerce/woocommerce/issues/44093

@josklever – Once you update to WC 8.5.1 it takes about 5 seconds for it to overload and freezes the server.. So you would need to navigate to WC settings to Copy the System Status data quickly. That’s what I did and have already sent them this data for review.

But so far they have no fix for this issue. I’m exhausted on this, let me know if they respond to your inquiry on this matter. Thanks bro.

I’m not getting my server overloaded again for a status report, causing downtime for 130+ clients. But you can have a look at that ticket and subscribe to follow it. And of course I’ll keep an eye on many other topics on this forum. Hopefully we’ll have some devs involved soon. Until then, WooCommerce 8.4 is still running fine.

Hello @khoavo and @josklever,

Have you had a chance to disable the Order Attribution feature? You can find it under WooCommerce > Settings > Advanced > Features. After disabling it, check if it resolves the issue.

We introduced this new feature, which loads additional resources on the front end. This could be the reason behind the loading and high CPU issues you’re experiencing.

Let us know how that goes. Looking forward to hearing from you!

Looks like @shameemreza is our hero! I updated WC from v8.40 to v8.5.2, then unchecked the box: https://prnt.sc/IywV4jPiIcUN – to disable Order Attribution and the overloading of the CPU on the server no longer occurs. I’ve been refreshing my site and monitoring my CPU and Physical Memory Usage % for the past 40 minutes since the WC update and so far so good on the front and backend of my site.

I suggest on the next WC update, your team either REMOVE the Order Attribution option (since this feature doesn’t seem useful) OR at least have it DISABLED BY DEFAULT so it won’t automatically overload some of the web hosting servers that are being affected by this.

To my fellow members:
First update WC to v8.5.2. Once the update is finished, QUICKLY navigate to WooCommerce / Settings / Advanced / Features and unchecked the box next to Order Attribution to disable it, then Save Changes. BECAUSE AS SOON AS YOU UPDATE TO WC 8.5.2, within about 10 seconds it will overload the CPU & Physical Memory on the server since the Order Attribution is enabled by default after the WC update is completed.

I’ll let WC Support mark this ticket resolved as soon as they see other members confirm this fix, by disabling the Order Attribution feature.

@khoavo — want to echo that Order Attribution should be disabled by default with the prompt to enable it explaining that it “loads additional resources on the front end,” and you should test that your hosting plan can handle it on a staging site, first.