-
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
Gutenberg crashes on 9.2.0 when clicking on a block or inserting a block #26381
Comments
@arjendejong12 A patch, 9.2.1, was released for the plugin, does that help with your issue? |
@talldan Unfortunately it still happens with 9.2.1. |
Similar problem |
@arjendejong12 @fotovat Would you be able to share the plugins and theme do you have active? Not saying it isn't a Gutenberg bug, but it seems like it must be triggered by something specific to your WordPress environments, as it's not happening in the vanilla Gutenberg dev environment and there don't seem to have been any other reports of the issue. |
WordPress 5.5.1 I tested on staging site in local environment by MAMP Pro PHP 7.3 and there is no problem. |
@arjendejong12 @fotovat This looks like it could be the fix for your issue - #26484 I tested an empty reusable block and the console error message matched yours. If you can check your Reusable blocks ( |
@talldan This PR fixes my issue. I had an empty reusable block and when I deleted that, the bug didn't occur. With an empty block and this fix, the bug also doesn't occur. |
Great, glad we tracked that down 👍 |
Describe the bug
Clicking on blocks or trying to add a block via de inserter causes Gutenberg to crash with the following error stack trace:
This only happens on 9.2.0. Downgrading to 9.1.0 fixes the issue. It happens on every block, not a specific one.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Clicking a block or inserting one should just work.
Editor version (please complete the following information):
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: