Title: Editor Crashed Last modified: September 1, 2018 --- # Editor Crashed * Resolved [ellenmgregg](https://wordpress.org/support/users/ellenmgregg/) * (@ellenmgregg) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/) * As I was finishing up drafting a post, Gutenberg stopped working. This is what I copied: TypeError: Cannot read property ‘getCollectionByRoute’ of undefined at t.value ([https://ellenmgregg.com/wp-content/plugins/wordpress-seo/js/dist/wp-seo-post-scraper-810.min.js?ver=8.1:1:145344](https://ellenmgregg.com/wp-content/plugins/wordpress-seo/js/dist/wp-seo-post-scraper-810.min.js?ver=8.1:1:145344)) at t.value ([https://ellenmgregg.com/wp-content/plugins/wordpress-seo/js/dist/wp-seo-post-scraper-810.min.js?ver=8.1:1:144551](https://ellenmgregg.com/wp-content/plugins/wordpress-seo/js/dist/wp-seo-post-scraper-810.min.js?ver=8.1:1:144551)) at jc ([https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:134:123](https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:134:123)) at gc ([https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:127:223](https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:127:223)) at vb ([https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:230](https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:230)) at ub ([https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:65](https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:65)) at zd ([https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:124:449](https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:124:449)) at ra ([https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:123:319](https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:123:319)) at Object.enqueueSetState ([https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:189:231](https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:189:231)) at r.q.setState ([https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react.min.ab6b06d4.js:18:441](https://ellenmgregg.com/wp-content/plugins/gutenberg/vendor/react.min.ab6b06d4.js:18:441)) Viewing 9 replies - 1 through 9 (of 9 total) * [merlinjk](https://wordpress.org/support/users/merlinjk/) * (@merlinjk) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10646908) * exactly the same here. went edit a page and got a blank screen with error message. * First time I tried to use it after updating today. * Not sure if to add error here or not as its public and contains URLs. * [dilusionz](https://wordpress.org/support/users/dilusionz/) * (@dilusionz) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10647328) * Came here to see this, experiencing the same issue. Imagine if this crash occurred while it was core. * I see this particular issue was “caused by Yoast”. When it really is just straight up evidence of how fragile the new-to-be “core” editor is. I’ve never had tinyMCE crash like this, not once – in many years of developing & editing. * Gun well aimed at foot WordPress, I know you want to pull that trigger. * [mrshft](https://wordpress.org/support/users/mrshft/) * (@mrshft) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10647515) * I just experienced the same exact issue, though I don’t know if it was caused by Yoast. Did anyone find any sort of resolution? Or temporary workaround? I was unable to make any progress sadly.. * Edit: Welp! I deactivated Yoast and, boom, everything was working dandy again. My apologies for doubting that Yoast was the cause! I read in another thread that Yoast is going to release an update on Monday (source: [https://wordpress.org/support/topic/after-update-no-editor-shows-up/](https://wordpress.org/support/topic/after-update-no-editor-shows-up/)) * Anyway, hopefully this gets resolved with the Yoast update on Monday. - This reply was modified 7 years, 11 months ago by [mrshft](https://wordpress.org/support/users/mrshft/). Reason: Added more relevant info * [merlinjk](https://wordpress.org/support/users/merlinjk/) * (@merlinjk) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10647846) * Yap, deactivating Yoast did the trick. Hope it’s fixed soon as I have converted all posts to Gutenberg and I depend on Yoast. * Thread Starter [ellenmgregg](https://wordpress.org/support/users/ellenmgregg/) * (@ellenmgregg) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10648199) * [@merlinjk](https://wordpress.org/support/users/merlinjk/) Glad that worked. Will give it a go. Fingers crossed a quick fix is on the way for us. * [Joost de Valk](https://wordpress.org/support/users/joostdevalk/) * (@joostdevalk) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10650036) * We’ve just released Yoast SEO 8.1.1 that fixes this. * Background: Gutenberg 3.7 removed a dependency that we also relied on. The bug was on our side (we should have registered our dependency ourselves) but the testing process needs improvement on both sides, we’re talking about that right now 🙂 * [merlinjk](https://wordpress.org/support/users/merlinjk/) * (@merlinjk) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10650093) * Cool. * [merlinjk](https://wordpress.org/support/users/merlinjk/) * (@merlinjk) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10650252) * Yap. All working good now. Tell you one thing. First time posting without Yoast yesterday since installing earlier this year, and just checked with Yoast and I haven’t done half bad. So definitely using Yoast does actually teach you SEO. * Thread Starter [ellenmgregg](https://wordpress.org/support/users/ellenmgregg/) * (@ellenmgregg) * [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10652346) * [@joostdevalk](https://wordpress.org/support/users/joostdevalk/) Thank you so much! We’re very grateful. All is well. Peace. Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Editor Crashed’ is closed to new replies. * ![](https://ps.w.org/gutenberg/assets/icon-256x256.jpg?rev=1776042) * [Gutenberg](https://wordpress.org/plugins/gutenberg/) * [Frequently Asked Questions](https://wordpress.org/plugins/gutenberg/#faq) * [Support Threads](https://wordpress.org/support/plugin/gutenberg/) * [Active Topics](https://wordpress.org/support/plugin/gutenberg/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/gutenberg/unresolved/) * [Reviews](https://wordpress.org/support/plugin/gutenberg/reviews/) ## Tags * [Crash](https://wordpress.org/support/topic-tag/crash/) * 9 replies * 5 participants * Last reply from: [ellenmgregg](https://wordpress.org/support/users/ellenmgregg/) * Last activity: [7 years, 11 months ago](https://wordpress.org/support/topic/editor-crashed/#post-10652346) * Status: resolved