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 won't work at all (plugin conflict Yoast SEO 8.1 and Gutenberg 3.7, fixed in Yoast SEO 8.1.1) #9506
Comments
Hey @jalexander4444 |
@Soean Thanks so much for letting me know! |
Sorry for the issue, yes there's a pending fix in the Yoast plugin that will be hopefully released on Monday. The bug happens when trying to open the "Categories" panel in the Gutenberg sidebar. As a temporary workaround I would suggest: temporary disable Yoast SEO, then edit a post in Gutenberg and close the Categories panel. Then you can safely re-activate Yoast SEO and edit posts, as long as you don't re-open the Categories panel 🙂 |
@afercia Thank you for the workaround! |
Thank you so much for reporting the conflict! Here is the related issue at Yoast SEO for reference: Yoast/wordpress-seo#10850 |
A temporary workaround plugin file was posted at Yoast/wordpress-seo#10867 (comment) |
This was fixed in our 8.1.1 release we did just now. |
Yoast 8.1.1 has been released. Please update and activate your Yoast plugin, and (if applicable) deactivate and uninstall the workaround, and confirm the issue is addressed. |
Describe the bug
When I try to edit a post or add a new post, I get a message that says "The editor has encountered an unexpected error." This has been happening since I updated the Gutenberg plugin earlier today. Clicking "Attempt Recovery" has not fixed the issue.
To Reproduce
Steps to reproduce the behavior:
OR
Expected behavior
I should be able to add a new post or edit an existing post.
Screenshots
Desktop (please complete the following information):
Additional context
TypeError: Cannot read property 'getCollectionByRoute' of undefined
at t.value (https://blog.workful.com/wp-content/plugins/wordpress-seo/js/dist/wp-seo-post-scraper-810.min.js?ver=8.1:1:145344)
at t.value (https://blog.workful.com/wp-content/plugins/wordpress-seo/js/dist/wp-seo-post-scraper-810.min.js?ver=8.1:1:144551)
at jc (https://blog.workful.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:134:123)
at gc (https://blog.workful.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:127:223)
at vb (https://blog.workful.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:230)
at ub (https://blog.workful.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:65)
at zd (https://blog.workful.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:124:449)
at ra (https://blog.workful.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:123:319)
at Object.enqueueSetState (https://blog.workful.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:189:231)
at r.q.setState (https://blog.workful.com/wp-content/plugins/gutenberg/vendor/react.min.ab6b06d4.js:18:441)
The text was updated successfully, but these errors were encountered: