-
Notifications
You must be signed in to change notification settings - Fork 0
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
Block inserter - The editor has encountered an unexpected error - Chrome problem #28
Comments
Reverted to WordPress 5.1 and got the same problem. |
Looking at Local storage for https://blocks.wp.a2z I see whereas for https://blocks.wp-a2z.org it's I don't understand what this data is but I'll delete the local storage in my development server and see if the problem goes away. |
I was initially unable to reproduce the problem using Chrome on my iPad. |
I'm going to leave this open until - retested on 15th Jan
Incidentally, while looking at a problem with the Divi theme I came across a plugin that I could possibly use to fix the issues on my iPad. https://github.com/jonathanbossenger/clear-divi-page-builder-cache |
I updated the previous comment. Closing issue now. |
I'm raising this here while I figure out if this is a bug with WordPress 5.1 or something else.
Having upgraded to WordPress 5.1.1, I now get problems with Add new.
Almost immediately the message box saying "The editor has encountered an unexpected error." appears.
The console log reveals...
where prefix/block_name is the name of the Most Used registered block.
Sometimes it's oik-block/github, but when I deactivate the plugin that registers it, it's core/paragraph.
The problem is only a problem for one subdomain, in a local installation of wp-a2z.org.
The local domain is blocks.wp.a2z
The problem occurs on Chrome Version 73.0.3683.86 (Official Build) (64-bit)
It does not happen with Firefox or Edge.
Problem appeared to be resolved after clearing the cache but came back very quickly when I reactivated my own plugin. The block name appearing in the message changed back to "oik-block/github". Previously, when the only routine registering blocks was WordPress core the block name was "core/paragraph".
The text was updated successfully, but these errors were encountered: