-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editor Has Encountered an Unexpected Error....Not Yoast Plugin #9885
Comments
In the report you filed a few weeks ago at #9095 you mentioned the problem was happening for drafts. Can you provide a little bit more detail about that? Is the problem now happening only for drafts or for all posts and pages? I also noticed in your report at #9095 you said that clearing browser cache solved the problem in that case, may I confirm with you that you have also tried that step for this case as well? Do you have other plugins installed which you think might be causing a conflict or are you using any other custom blocks that you know of such as in a theme? Here is a copy of the error message from the first link for reference:
I searched for past reports of the same error and I found a few cases where the problem was traced back to problems with how some of the custom code was written: It may not be the same in your case, and the first thing to check will be to look for a plugin or theme conflict if that is something you are able to do. |
Related #9866, where re-saving permalink structure fixed the problem. |
Several other reports of this on the forums: https://wordpress.org/support/topic/nvariant-violation-minified-react-error-130/ |
Try re setting the permalinks Go to permalinks in settings, change your structure to something other than your default, then save. Then select your usual default permalink again and save. Return to your problem pages and check status. |
With Gutenberg 3.9.0 there is a JS Error, and of course saving permalink changes not resolve it.
|
Closing as stale, if we have more detailed informations about the errors ( |
Describe the bug
Same error as a few weeks ago, but this time I disabled the Yoast Plugin and it still comes up with this error.
The text was updated successfully, but these errors were encountered: