I personally don’t use Yoast plugin, I have my own SEO solution that is fine for my needs. But, in the past week or so, there have been so many complaints against the Yoast SEO plugin, that it is very likely that problems you have are caused by the Yoast SEO plugin. If you must use Yoast SEO plugin, you must wait for them to fix bugs.

1) I was using the Classic Editor plugin so that I could keep using the Classic Editor. Unfortunately, recently Yoast started having conflicts with Classic Editor so all of my metadata info disappeared, and evrything in editor was a complete mess and got worse every day until I had to remove the Yoast plugin completely. After more and more research I realized that it was the Classic Editor that had had the conflict with Yoast. So, I deactiated the Classic Editor so I could reactivate Yoast (because without it my site started appearing as if it had hundreds of pages of duplicate content, lost all of it’s meta data descriptions, etc. because Yoast was providing all of this).

NOW I’m being forced to use the block editor so I can keep yoast active but even with this I’m still having issues iwth the editor that I think are due to Yoast! It’s constantly ‘thinking’, it has delays and shuts down, can’t show previews, won’t let me enter key terms in SEO bar, etc. So now I have to figure out which plugin has an issue with the block editor (even though this isn’t even a plugin and I DO NOT UNDERSTAND). Do you have any suggestions for how to get my site back to being able to run yoast safely and successfully? What a nightmare. I just want my classic editor back. But I also need Yoast.

> One of the reasons against the option is to avoid confusing users.

Huh. Are we not users of WordPress? And aren’t us users asking for the option? Only thing confusing is how condescending that decision is!

Thanks for the comment! Yes, that would be best, and a lot of WordPress professionals asked that such options were included, but WordPress core developers decided against it, and that was it. One of the reasons against the option is to avoid confusing users.

Sorry, I have never used Types plugin. But, my code to disable Gutenberg is simple and straightforward, so most likely Types detects the version of WordPress to do somethings differently, regardless of Gutenberg being active or not.

Hi, Disable Gutenberg plugin has options for selective disabling of Gutenberg. Or you can modify my example code to use conditional check for page ID instead of the post type.

You saved my morning.

Big thanks.