5.2 is a mess

Agree 100%.

I’ve never seen a Woo update as bad as this (and I’ve seen pretty much all of them).

same here I’ll give them some slack because It is actually quite rare they mess up like this but there is a serious glitch.

The worst thing though is that it’s still there for people to upgrade. They need to remove this from the repository

I do all my WP work from the command line with WP-CLI so I was fortunate enough to spot the problem fairly fast even before looking at the site. It wouldn’t even let me deactivate the plugin from the command line. A simple wp plugin list command would take forever to execute.
Ended up having to manually upload and unzip 5.1 over 5.2

• This reply was modified 3 years, 11 months ago by prospirity.

“I don’t even want to go into details” is a daft thing to say in a support forum. How are they supposed to resolve issues if you don’t tell them what problem’s you’re seeing?

@thewebatom I agree – that’s no help

I really did not have the time when I wrote this. My goal was simply to either warn people of the risk to upgrade and to roll back if too late.
After dealing with the problem I had it and I think that what I wrote is more helpful as prevention than if I had not said anything. There is nothing worst than going down a rabbit hole while the simplest solution is to revert back.

If I saved 1 person some trouble or hours of wondering what’s wrong I’m happy with that.

What I wrote after is the extend of my experience with the upgrade because I caught it before even looking at the website. There is nothing else I can offer.

I run a business not a website. I’ll leave it to the programmers to figure things.

Did they asked any questions…nope. I would have gladly volunteered. Works both ways

So I stand that it was still better to be “draft” than not saying anything at all. I just knew I could save some people some time and headaches that’s all. ??

• This reply was modified 3 years, 11 months ago by prospirity.

Well, for what’s it worth, we’ve updated 7 of our WooCommerce stores and haven’t run into a single issue in our usual testing process.

We always check the support forum for issues others are reporting in case we’ve missed something. At this point, we’re pleased to report that none of our sites are affected by the ~~serious glitch~~ described here.

Good to know. I never ran into a problem updating Woocommerce before and I have been doing this for a very long time. So it was easy to make WC the culprit since it was the only change I had made and removing it solved the problem.
It wasn’t as widespread as I thought obviously but I still wasn’t the only one.
I am still not updating to 5.2 though ??
In another thread, I mentioned that I have a LEMP/Ubuntu 20.04/PHP 7.4. Could be my specific setup. The update seems to have affected specifically the plugin folder.

Since I can roll back easily I will try again in the next few days when I have a moment and see if I can better pinpoint the conflict.

It was a serious glitch to me!

I’m sorry to hear that you are having trouble with your WooCommerce upgrade. It is most likely caused by a conflict on your site as we are not able to replicate this behavior on our end after running multiple tests with the latest WooCommerce version.

Please check the following documentation to understand how to do a conflict test:

https://docs.woocommerce.com/document/how-to-test-for-conflicts/

We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.