prospirity

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 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, 7 months ago by prospirity.

For WOO team if that helps I’m on a LEMP stack Ubuntu 20.04 PHP 7.4

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, 7 months ago by prospirity.

the problems it creates are completely random depending on what people are running. So no point in fixing anything on our side. ROLLBACK don’t waste any time.

I actually found which one was creating the problem by installing each individual plugin and activating one by one. It is

Inline Styles.

So then my next question is why then this line in wp-config
define(‘INLINE_STYLES’, ‘false’);

not really disable the function?

Same here

Normally I wouldn’t repost my request but considering your history I guess my hope for an answer are slim.

First a while back I sent you the same question through your contact us page on your website. Never got a reply

Second I see no answer on this forum to any of these requests.

Hard to comprehend coming from a commercial plugin developper that claims to beat the competition. Hard to know if I can’t even install it

If that can be of any help i found the problem. A plugin called Follow-up email wrote “action_sheduler” and logged it in the comment table. I was able to delete and disable that feature and those records were successfully removed from the table.

sorry forget this, resolved

and how would this look like if I may ask
thanks

Thanks, smart idea. Haven’t thought about that.

Just checked in my cpanel and I thought I had enabled hotlinking but to my surprised it was disabled. Where else can I have enabled this…throught a plugin/htaccess?

I’ll check around but if you have a precise idea please share with me ??
Best

Hi Clayton

Just when I received the email for your post I was launching CCleaner. Cleared everything and was hopeful it was the issue. Unfortunately the issue is still there.

Had the idea to to check in other browsers Google Chrome and IE7 and the problem was there too.

Now I am trying to think where else could it be on this computer. I’ll check in my file directories

…still looking

Hmm! thanks I will investigate that. Both are on the same VPS server and I made some changes last week that might have triggered then….this forum is great fast and knowlegeable answers

Awesome, thanks…I thought I had done that but obviousl not as high as 777 and it is working. reverting back to 755 now