criticalmash

Actually, I can’t acknowledge that. Because facts are facts. I deleted three other plugins last week. None of them previously caused a bevy of 500 errors while active or being deactivated. This one, however, is the only thing – in my six years of managing this site – that has caused that type of mess – both while active and while being deleted.

Yes, I’ll admit that another action could trigger the same result. But I won’t say that this plugin was ever useful. Unless the goal is to render it totally inaccessible. Any simple Google search for “Yoast 500 error” will show you that it leaves a lot to be desired. Like – the ability to use your own website.

And I wouldn’t call Bluehost thoroughly inept. It’s true – the guy wasn’t completely forthcoming with me. But he couldn’t be. Because I’m not the keeper of the pin so he could only tell me so much while I hustled to try to get in touch with the guy who does have that pin.

It’s resolved now and I won’t make the same mistake again. Working on the memory issue, too. ??

Thank you! I was on my way here to report back!

That’s exactly what it turned out to be. Increasing the memory gave us a chance to remove the plugin.

I am SO appreciative of the helpful suggestions all around. You guys are great. I am part of a larger team and although I have access to those things for other sites I manage, I don’t have access to those things for this one so I had to lean on the host for some assistance but we got it done.

Much thanks. Officially resolved. ??

Jos: I wish I could remember but it’s been a very long time. IIRC, my host was able to determine that the plugin was doing two things – one issue had something to do with the sitemap and the other was the addition of htaccess files that were problematic. They were able to resolve those two long enough for me to disable the plugin. And things worked fine until I (irrationally) decided to delete the plugin today.

Jos and Jon: Apparently when you try to delete the plugin, something is triggered along the way that causes the memory overload. There was nothing else going on, no other users, no site visitors, no other load on the memory. Only one event happened – me removing the plugin – and the result was this. Yes, I realize that a disabled plugin doesn’t seem to be doing any harm but there’s something about the act of deleting it that causes mayhem.

I’m waiting for my host to get back to me to see if we can somehow modify the memory long enough to get this back up and running.

I’m sorry but your condescension and defensiveness are getting in the way of being a solutions-oriented commenter and developer.

I’ve been dealing with this for seven months. No one even bothered to reply to
my original post asking for help. This issue has been acknowledged in other threads. My hosting provider validated that it’s an issue with this plugin and I find it impossible to believe, given the speed with which you respond, that you’ve done little to work on the issue other than achieve a high level of competency at defending it against its detractors.

I am happy to rebuild my site if it means I can be rid of the complications of dealing with this.

Just the act of deleting it caused a string of 500 errors. It didn’t work when it was active and you can’t even delete it. At what point are they going to address all of the users whose sites are compromised by this plugin that generates issues so badly that entire websites are lost forever? It’s not really a great product if it renders a website totally useless.