@shameemreza I haven’t tested it myself, but if disabling that option makes it work, then that functionality is still broken. Why would a site with enough resources kill the server with a new default option, when that hasn’t been used before? What does it do with existing settings/data on the site that leads to this issue? That’s what the developers need to find out. Just disabling it, would only be a temporary workaround until the client wants/needs that option enabled in the future.
So I’m still keeping WooCommerce on version 8.4.0 until the issue is actually solved and I should not have to risk my server to get overloaded again.
@khoavo, you keep mentioning a relation with certain hosting providers, when we already know it’s not related to the hosting/server. It’s related to settings or data on the website.
Thread Starter
khoavo
(@khoavo)
@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.
I’m managing 50+ webshops, 19 on my server and only 1 is having this issue. Overload can probably happen on every environment, but it only happens in rare cases that involve particular settings or data on the specific website. If it was related to a hosting environment, why does it affect only 1 of the 19 sites on my server? The environment is the same (or at least very similar) for every site.
Disabling a new default option is not a solution. It’s a temporary workaround until the issue is really fixed.
Thread Starter
khoavo
(@khoavo)
@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 .
Hey, @khoavo @hastibe @josklever!
I’m glad the issue was solved for now.
I understand this is only a workaround and we are looking into the issues with the Order Attribution feature.
Thank you for your feedback. User feedback is very important to us and always appreciated.
I’ll close this now, okay? Let us know if there’s anything else we can do to help!
Thread Starter
khoavo
(@khoavo)
@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.
Plugin Contributor
Tung Du
(@dinhtungdu)
@khoavo I can’t find the Starter plan on midphase.com, so I purchased a Personal plan on https://www.midphase.com/website-hosting/ to test. But I still can’t reproduce the issue with WooCommerce 8.5.1 and Twenty Twenty-Four.
- Is that the same hosting type/plan you had issue with?
- Can you share a test/staging site that can reproduce the issue? I know that you fixed issue temporarily by disabling Order Attribution. But since we’re still having trouble reproducing the issue, a staging/test site having the issue will help a lot to find the root cause. If yes, you can drop me an email at tung.du@automattic.com. Thanks in advanced!
Thread Starter
khoavo
(@khoavo)
@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.
@dinhtungdu As I explained a couple of times now, this is NOT related to a specific hosting package/provider. It can happen everywhere, but ONLY if there a certain SITE SPECIFIC settings or data. So it probably can’t be reproduced by creating a new site as that site doesn’t have the old (buggy) setting or data.
And giving access to an existing site is not allowed, even if it’s a copy of that site. You would still get access to data you are not allowed to access and it could get you banned from this forum. See the forum guidelines.
That’s why you are wasting resources by focussing on individual cases, while the devs should investigate the changes in the code to determine how the current symptoms can be caused. The thing you can do is monitor the forum topics and bundle all the information to the problem that’s being investigated in the GitHub post.
Plugin Contributor
Tung Du
(@dinhtungdu)
@khoavo thank you so much!
@josklever Yep I read your comments as well.
And giving access to an existing site is not allowed, even if it’s a copy of that site. You would still get access to data you are not allowed to access and it could get you banned from this forum. See the forum guidelines.
I’m sorry about that! And thanks for the guidelines link.
That’s why you are wasting resources by focussing on individual cases, while the devs should investigate the changes in the code to determine how the current symptoms can be caused.
We’re still investigating this issue on our end. I agree that it could be some site setting that causes the issue. The reason I spent time reproducing the issue in parallel is that it could help us find that specific issue earlier. I’m trying to gather as many clues as possible.
Again, thanks you so much for your status report and info you shared with us here and on GH issue.
A couple of your support colleagues have tried the same, so that’s the reason I have to share my information over and over again. Start reading all the support topics about this issue (there are quite a few already). Check within your team if there are already developers working on this issue and ask them for an update. That would actually help, because we have been waiting almost 2 weeks and no real progress seems to be made, because nobody is looking at the bigger picture. So I hope you can change that. 😊
Thread Starter
khoavo
(@khoavo)
@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!
Hi there @khoavo,
But there’s no Changelog shown for this version
You can find the changelog for the version 8.6.0 here.
This latest version contains a permanent fix for the issue that was brought up on this ticket?
Depending on your site setup, different site setups behave differently. I suggest creating a staging site and updating your staging site to the latest version and observing for any errors before updating your live site. This will help avoid any unnecessary hiccups.
Cheers.
Thread Starter
khoavo
(@khoavo)
@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.
