-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Gutenberg crashes on Block validation failed for core/image
(browser extension conflict with "JavaScript Errors Notifier" in Chrome)
#10490
Comments
I tried testing this after upgrading to 4.0.0-rc.1 and opening a demo post published using a past version of Gutenberg and I didn't see a fatal exception or a total crash. I also tried opening a post with an image block made with a past Gutenberg version separate from the demo post, and that post opened normally for me as well. I tested using WordPress 4.9.8 and Gutenberg 4.0.0-rc.1 with Firefox 62.0.3 and Chrome 69.0.3497.92 on macOS 10.13.6. Are my testing steps exactly the same as yours or am I missing a step for testing? By fatal exception, do you mean the block was marked as invalid or do you mean the whole editor crashed or did something in between happen? Out of curiosity, does clearing browser cache make the problem go away? Would you be okay to try testing with 4.0.0-rc.1? You can download it at https://github.com/WordPress/gutenberg/releases/tag/v4.0.0-rc.1 Thank you for including console errors! I don't recognize the ones you've listed but I see several results for the 2nd line in a search at https://www.google.com/search?q=%22TypeError%3A+Converting+circular+structure+to+JSON%22. I am just not sure why you might be seeing that error while I am not. May I ask if you have added any additional custom blocks yourself or do you have any plugins installed that have added custom blocks? |
Your steps are exactly what I'm doing - open demo post created with older gutenberg (IIRC I made no changes to the original content). fatal exception = white page with empty gutenberg block, ie.
Cache is not involved (I just checked in the browser that never visited the site). Below you can see full trace for 2 additional errors:
|
I just tested on Firefox and the behavior is a bit different - the editor opens but images are not there. The console shows block validation errors for core/image, core-embed/vimeo, and core/pullquote - but no other exceptions
|
It seems that opening it in FF fixed old demo page (saved draft opens properly in Chrome). Upgrading gutenberg to 4.0.0-rc1 didn't fix the problem (I have other posts that are still "broken" - the cause errors in Chrome). |
Ok, I found the original cause - it's incompatibility with "JavaScript Errors Notifier" chrome extension: |
Notified upstream on barbushin/javascript-errors-notifier#79 |
Nice find!! Thank you for reporting and referencing that report. |
core/image
core/image
(browser extension conflict with "JavaScript Errors Notifier" in Chrome)
The commit e8f6bb0
from pull request #7721 referencing #5292 changes definition of image adding div around figure.
This seems to cause fatal exception when trying to edit post created before the change.
(currently I'm using Gutenberg 3.9.0 on WP 4.9.8).
The exception (from gutenberg demo article):
Expected behavior
I don't know, but total crash is not something expected. And I guess change in block definition isn't something rare - is there any migration function that didn't work? Should I fix the content manually to get past the problem?
Note
There are also two other exceptions on console, not sure if they're important.
The text was updated successfully, but these errors were encountered: