khoavo

Alight, Thanks.

@ckadenge – No need for a staging site. I updated to WC 8.6.0 and made sure the Order Attribution box is unchecked and all works fine.

@anastas10s or whoever with the plugin support:

I just saw WC v8.6.0 available for update. But there’s no Changelog shown for this version. This latest version contains a permanent fix for the issue that was brought up on this ticket? I had to uncheck the Order Attribution box under WC/Advanced/Features since this was checked by default which logs up all the CPU Memory on some shared web hosting. Just double checking before I do the update to WC 8.6.0. Lett us know please. Thanks!

@dinhtungdu – Looks like Midphase recently changed the names of their shared hosting packages. The Starter Plan is now called Essential Plan. The Personal Plan you got is on their same shared hosting server, just more features added and higher price, etc.

It was on my Client’s site. I simply duplicated their site and also activated the default TT3 theme to test as well. I disabled Order Attribution from WC and the issue went away, as the Order Attribution feature somehow overloads the server on some Hosting Providers and not others. And just so happen this site is hosted on the Midphase shared hosting.

I’ve already deleted the testing site and I rather not play around with my clients web hosting any more. It’s running smooth now with the Order Attribution disabled. Can’t afford to have their site to accidentally break again.

If your site runs fine with the WC’s Order Attribution feature activated, then your server has no issues with it. Because I have another client’s site hosted with Godaddy.com and it was never affected by this. Other than that, I have no idea why some hosting as are affected and not others by the Order Attribution feature. Hope this helps you.

@carolm29 – Yeah, a temporary fix is better than no fix. So we’ll wait for a permanent fix on the next WC update. You guys are the best, Thanks.

Yes, please close out this support ticket for now.

@josklever – I’m not an expert on web hosting servers bro. I shared my findings based on what I discovered on my end. You’ll need to discuss the technicalities with WC Support on this .

@josklever – I mentioned the issue is related to some hosting providers and not others meaning for some reason, the Order Attribution feature overloads the server on some servers and not others. It doesn’t matter if your server has sufficient CPU and Physical Memory RAM, etc. Because the Order Attribution from WC probably continues to load something over and over and over again, who knows! I have another website on the Godaddy.com shared hosting server and that site was not affected by this issue. And there’s limited physical RAM memory on my Godaddy web hosting plan too. So perhaps it’s how the server is configured on the backend or its incompatibility with the Order Attribution feature from WC? I have no idea.

You’ll need to discuss it further with WC support on why it’s affecting your web hosting server. I just checked my other website again this morning and after disabling the Order Attribution feature 8 hours ago, the site is still running smoothly.

@hastibe – Agreed 100%

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.

@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.

@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.

@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.

@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 9 months, 4 weeks ago by khoavo.

@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.

@gigitux – Your profile badge doesn’t show you’re with WC Support.

i had already posted my 2 private links to their Quickforget.com service yesterday. They include the data from my WC System Status.