Yoast SEO breaks Gutenberg/Block Editor

Hi,

We’re sorry to hear that the Yoast SEO plugin is causing a disruption to your editor.

Can you confirm that you are using the latest version of WordPress 5.7.1, Yoast SEO for WordPress 16.1.1, and the latest version of the rest of your plugins and themes?

Would it be possible for you to provide a screenshot and more details on the specific error messages you are having when editing a post or page?

We would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

As we can imagine that you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process:?How to check for plugin conflicts.

Performing a conflict check (starting with a default WP theme and only having Yoast SEO as the plugin active, and then turning on the plugins one-by-one) will help us determine which plugins are in conflict and how to reproduce it, and what the specific error message/issue is.

• This reply was modified 3 years, 11 months ago by Michael Ti?a.

Here is how I know what the problem is…

I had numerous phone conversations today with WP live support AND Hostgator. WP Live had me disable my plugins one by one and test. It was only after I disabled Yoast that Block editor opened. I can also replicate it… reactivate Yoast and the problem returns. I cleared my cache, had Hostgator clear theirs, checked pHp Memory and version, yada yada yada. Everything is up to date, everything else is working. It is Yoast. I downloaded another SEO plugin today and I can finally edit again in Block Editor. I must say, the Hostgator guy was pretty blown away that I had this big of a problem from Yoast…

How do I send a screenshot?

Hi @ladyvet15

We understand there is a problem on your website. Each website has a totally unique combination of themes, plugins, and custom code, and other factors, so we really would need a screenshot and more details of the specific error message that is appearing.

You can use something like snipboard.io to upload images and share a link with us here.

If there are any JavaScript errors appearing in your browser’s console when editing a post or page, it is most likely a conflict with another plugin or theme, which is why we are requesting for a conflict check so we can identify where the conflict might be — https://yoast.com/help/how-to-check-for-plugin-conflicts/

I understand that each website is unique. After I posted my original message, I got the problem resolved, and the problem was resolved when I disabled Yoast. I understand you’d like all the parameters to figure out the problem. But I spent a lot of hours today that I didn’t have to spend getting things working again. I’m sorry, but the ROI for me to go through all of that just isn’t there…

Hi,

When the problem was resolved when you disabled the Yoast SEO plugin, it’s most likely indeed a conflict with Yoast SEO and one of the plugins on your site.

Unfortunately, it’s hard for us to say exactly where the issue or conflict is coming from without trying to replicate it with a conflict check and starting from a default WP theme such as TwentyTwenty and starting with only the Yoast SEO plugin, and going from there. It’d also be difficult to troubleshoot without any screenshots of visible JavaScript errors in the browser’s console or any visible error message or notification. Perhaps you might be interested in troubleshooting this further in the future — https://yoast.com/help/how-to-check-for-plugin-conflicts/

I decided to figure out what the conflict was… so I reached out again this morning to WP live to have them walk me through it. We installed TwentyTwenty (I was using Astra, and the WPL gal said Astra is always up to date and she would be shocked if Astra was the conflict.) With TwentyTwenty installed, and ALL OTHER PLUGINS DEACTIVATED except Yoast, THE PROBLEM PERSISTED. The WPL gal audibly gasped when she (and I) realized that YOAST is the problem. The error message that appears says this: “The Editor has encountered an unexpected error.” It then gives me three options: Attempt recovery, copy post text, or copy error. Nothing worked…

I sent the lengthy error message I got to WPL but I can’t find it now. If it is super critical I suppose I could look again. But at any rate, I think I have proven, at least to my satisfaction and the WPL gal’s satisfaction, that the issue resides in the YOAST plugin.

Before I upgraded to Live WP Support, I had email support. I just received this email from a WP Live Support tech:

“I have also seen reports of the same error tied to the Yoast plugin so I want to run some tests and make sure there’s no plugin/theme conflict happening.”

This was the first time anyone had pointed a finger at Yoast…

As I mentioned above, I DID do the tests to determine if it was a conflict with another plugin and it is not…

Thanks for sharing all the relevant information here with us. We understand that you are having an issue specific to Yoast SEO and it’s must be frustrating for you.

Due to the nature of the issue, we’ll need to take a look at your setup. However, we are unable to do it here as this is a public forum.

So, if you have an active Yoast SEO Premium subscription or if you can consider buying one, we can investigate the issue further directly on your setup privately through email.

However, if you don’t wish to get the Yoast SEO Premium subscription, that’s completely fine. In this case, you’ll need to troubleshoot the issue further on your setup as we are literally out of any clue at this moment without taking a look at the setup. So, someone from the community might step forward as well who has experienced or familiar with the issue.

Thanks for your understanding!`

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

ROFL. You basically said to her – “you have to pay for our plugin that doesn’t work for us to try and fix this error with our plugin that we may not be able to fix anyway or we aren’t going to bother to look into it any further”!! and you wonder why you got no reply!

For what its worth I have the exact same problem and its yoast causing it. its been weeks now and still not fixed. I would happily chuck yoast in the bin but my client likes it for some reason – although not enough to get the paid version like in the past

Firecastdan, thanks for your response! You nailed it! I am quite happy not messing with Yoast! And yes, they wanted to make it MY problem. God forbid anyone thinks there was a problem with Yoast!

I’ve also had the exact same problem. I’ve done a conflict check and it occurs with the default theme and only Yoast enabled. I upgraded to Premium in an effort to get better support, but the issue has still not been resolved.

Update: Upon troubleshooting a separate issue with Sucuri, I discovered that I had forgotten to remove the server IP from my “hosts” file. After I did this, the problem was resolved.