-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 when opening Categories & Tags #3953
Comments
Can this be reproduced with a non-premium plugin, or could you otherwise make said premium plugin available for me to test? |
Just confirming I can't replicate this with ACF or the free version of Yoast. |
Yeah I was hoping to have a free example too but I couldn't find one on short notice. Yoast SEO Premium includes the prominent words feature, which adds a private tag taxonomy, so that might be the difference (I tried it with Free too but indeed that one doesn't cause the problem). I'll arrange for a premium license for troubleshooting when I get to the office tomorrow. |
@hedgefield Thanks, I was able to reproduce and track down the issue. I'm inclined to call this a bug in Yoast, since the root cause is that the // Expected:
register_taxonomy(
'yst_prominent_words',
array( 'post', 'page', 'attachment' ),
array( /* ... */ )
);
// Actual:
register_taxonomy(
'yst_prominent_words',
array( 'post' => 'post', 'page' => 'page', 'attachment' => 'attachment' ),
array( /* ... */ )
); This is because the underlying The error occurs because Gutenberg expects the REST API taxonomy's † I might have expected the REST API to be a bit more strict about ensuring these schema types are rendered as promised. |
While I don't want to set a precedent of accommodating non-schema-conforming API results, we could alternatively use the more relaxed
|
Thanks a bunch for figuring out the problem @aduth. I'll bring your findings to the devs here and see if we can solve it from our end. |
Workaround proposed at #3972 |
I've got this error in Chrome and Firefox. Here's the error:
At first I was having error only in Chrome, but in Firefox when I switched from block tab to document it gave me this error and since then I can not go back to write a post. I don't have in SEO plugins install like Yoast SEO etc. |
Issue Overview
This seems to be caused by plugin metaboxes hooking into specific parts of Gutenberg. Related to #3929?
Chrome 62.0.3202.94
WP 4.9.1 vagrant
Gutenberg 1.9
Steps to Reproduce
Clicking
Attempt Recovery
does nothing. ALL other posts have the same error, even when selectingAdd New
(because the Categories & Tags section is technically still expanded).To 'fix':
Error message
TypeError: e.types.indexOf is not a function
at http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513096097:21:108874 at http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513096097:6:50595 at http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513096097:6:59929 at o (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513096097:6:19682) at http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513096097:6:60059 at o (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513096097:6:50575) at o (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513096097:6:15944) at o (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/editor/build/index.js?ver=1513096097:21:108835) at beginWork (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:133:69) at d (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:158:393) at f (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:159:214) at g (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:159:462) at t (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:167:3) at x (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:166:247) at batchedUpdates (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:169:173) at cc (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:26:56) at jc (http://src.wordpress-develop.dev/wp-content/plugins/gutenberg/vendor/react-dom.min.3583f8be.js:35:5)
The text was updated successfully, but these errors were encountered: