Just download an old version from https://wordpress.org/plugins/woocommerce/developers/ and upload via FTP.
You may want to look into plugin conflicts/make sure plugins are compatible before upgrading again. There are no known performance issues with 2.6 specifically.
Thread Starter
johson
(@johson)
Hi Mike,
Thanks! Everything still very slow, so I might be forced to. No plugin conflicts as far as I can see.
I have downloaded 2.55. But how do I proceed. If I completely deactivate and remove this woocommerce, and the add the downgraded 2.55, won’t all my settings, products, orders etc. be gone?
You won’t lose your data when switching.
The only way WooCommerce will delete data from the database is if you uninstall the plugin while this option is checked at WooCommerce > System Status > Tools: http://cld.wthms.co/10EtK/2TNOQOSo
If you switch out the plugins via FTP though, the uninstall hooks will also never be triggered – so this won’t be a concern.
Thread Starter
johson
(@johson)
Ah, thank you! Normally, when you delete a plugin after disabeling that plugin, you get the question “are you sure you want to delete this plugin and all of it’s data?”. I assume this setting will make sure that only the plugin gets deleted and none of it’s data like products, orders etc.?
Ah, thank you! Normally, when you delete a plugin after disabeling that plugin, you get the question “are you sure you want to delete this plugin and all of it’s data?”. I assume this setting will make sure that only the plugin gets deleted and none of it’s data like products, orders etc.?
Just to stress, if you use the delete button you will lose data.
If you upload your plugin via FTP, no data is lost because it is not uninstalled first.
Be careful!
Thread Starter
johson
(@johson)
Ok, so, just to make sure:
– I do NOT disable the woocommerce via dashboard and do NOT delete woocommerce via dashboard
– I do NOT delete the woocommerce folder through FTP
– I just OVERWRITE the woocommerce plugin folder with the woocommerce plugin folder contained in version 2.55 (unzipped)?
Correct me if I’m wrong.
I’m sorry, I have never done this before…
Thread Starter
johson
(@johson)
Thank you so much! I will do that and I will let you know if I still have the problem.
One question in advance. Assuming, this will solve my problem, how should I proceed then? At some point I am gonna have to try to upgrade again…
Just wait for 2.6.2 and hope it works then again?
The cause of why this problem occurs has been discovered. Each time a visitor comes to the site, something since the update triggers an apache service and causes it in some sort of loop and server load goes to 100%. The first hour or so when somebody visits an uncached page, like when clicking add to cart or remove from cart, it still handles it pretty fast. 1 – 2 seconds.
But as time progresses and the services in apache stay in an loop, it takes longer and longer to load those uncached pages. After 10 hours, time to add to cart increases to more then 80 seconds…
Thread Starter
johson
(@johson)
It worked, thank you so much!
But now I have another problem. I use YITH WooCommerce Ajax Product Filter to filter colors, subcategories etc.
After the downgrade, the filters are not working anymore…
Any suggestions?
Were you using wordfence plugin? I had this same problem and it was due to wordfence.
Thread Starter
johson
(@johson)
Ah, just fixed it. I did the same as you suggested for woocommerce and downgraded to a version before woocommerce 2.6. So all is working for now again.
Thank you soooo much for all your help!
How should I proceed now? At some point I am gonna have to to upgrade again…
I’d wait for your extensions to support it fully. Maybe get a staging/test site to test the update beforehand,
Thread Starter
johson
(@johson)
Thanks.
Yith does support 2.6 fully. They released a major update simultaniously.
However, after I downgraded, the most recent version of Yith, built for woocommerce 2.6, did not function correctly. Afterdowngrading that one also, all was ok. So I know when I will upgrade again, Yith will be ok again.
As for your suggestion for a test site. I did. It all seemed to be working ok at first. The problem with the Apache ending up in a loop was discovered much later, once it took up 100% server load and many website visitors. Of course, that cannot be tested in a dev. site. Since there is no traffic.
But placing orders and all other stuff was working correctly in the dev. site, so I thought it safe to upgrade.
I will wait for the next update to 2.6.2 and see if there is a fix there. If not, I can always go back again to 2.5.5 like I did earlier this afternoon.
Thanks again for all your help!
