Yoast crash visual editor

Please delete your browser’s cache. It is said that it would solve most issues of that kind.

Its not make changes. Adding keyword to YOAST freezing visual editor and can not edit normally article.

Some people reccomend to do:

If you use Adblock on Firefox, you can install the Element Hiding Helper for Adbblock Plus plugin, press Ctrl+Shift+F3 and block the element “wpseo-dismiss-recalculate”

I don’t use AdBlock plugin, yet I have a crashed editor and have to deactivate Yoast SEO, edit the contents, reactivate Yoast SEO and come back to add some keywords… It’s really annoying when you post several items in daily basis.

I have the same problem. I think, the “realtime content analysis” is the problem. But I don′t find a possibility to deactivate this feature.

same problem here on multiple websites. Cleaning cache was working a few days ago but now the backend is freezed. Script is running error messages.

Editor is totally hanging, can’t edit articles.

Downgraded to version 2.3.5 and everything is running smooth again.

Hmm okay, I’ll stay on 2.3.5 until this is fixed then.

I have two clients that are experiencing the same issue. Post editor (whether visual or test) hangs as you try to type. It’s not even an annoyance, it’s unusable. Clearing the cache isn’t a fix.

Same problem with the editor hanging (both visual and text). I tracked it down with the debugger to the real-time content analyzer. I took out the keyword, and the page doesn’t hang any more, but that defeats the purpose of the plugin.

I have the same problem. Anyone know if this is planned to be corrected?

We’ve been also experiencing issues with Visual Composer and the latest version of Yoast. We got hundreds of “Failed to load resource: the server responded with a status of 414 (Request-URI Too Large)”

This seems to be directly related to the wp-seo-post-scraper-302.min.js file since we often have the following error right after/before dozens of the previous error : Uncaught TypeError: Cannot read property ‘match’ of undefined

Hopefully a fix for this will be out soon!

I’ve tested version 3.0.4 just released and nope, it is not fixing this in my case ??
I will downgrade to 2.3.5…

If 3.0.4 doesn’t solve your specific problem, please create a detailed bug report on GitHub, so our development team can investigate and fix it.