-
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
White screen, no editor, 2 x errors in console #10315
Comments
Thank you for including error details from your browser console! I just tested installing Yoast 8.3 on a site running WordPress 4.9.8 and Gutenberg 3.9.0 and the editor loads normally for me so I may be missing a testing step or I may be missing a plugin or server config setting that you have that I do not. I tested from Firefox 62.0 on macOS 10.13.6 and the test site I used is hosted at WP Engine. First, to confirm whether or not this is a plugin conflict with Yoast and Gutenberg in your case, could you temporarily disable Yoast and then clear browser cache and try starting a new post to see if the same exact errors show up in the console? If the errors go away, we'll know it's a plugin conflict with Yoast. If the errors are still there, could you please provide a list of your active plugins and note where your website is hosted? In your screenshot, I see what looks like a lonely gray button at the bottom of the screen near the right side. What is that? |
Hi @tofumatt RE: the little button, that was my mouse hovering over an icon on the system tray on my MacBook :) |
Have also notified the guys at Yoast @CarolineGeven per the issue I've logged there: Yoast/wordpress-seo#11131 |
Awesome, much appreciated! I'll close this issue then, thanks for following up with us and filing with Yoast! |
Hello! What is the proof that Yoast causes the issue? |
As mentioned above:
|
@JohnGiddi - also worth seeing the comment here: https://wordpress.org/support/topic/white-screen-no-editor-2-x-errors-in-console/#post-10754009 further to the above |
+1 |
Describe the bug
Hi guys,
I’m seeing two errors in Chrome’s dev console when trying to create a new post in 3.9 (WP 4.9.8, PHP 7.2):
Uncaught TypeError: Cannot read property 'primaryShift' of undefined at Object.217 (index.js:12) at n (index.js:1) at wp.editPost.0 (index.js:1) at index.js:1 217 @ index.js:12 n @ index.js:1 wp.editPost.0 @ index.js:1 (anonymous) @ index.js:1
and
Uncaught TypeError: Cannot read property 'initializeEditor' of undefined at HTMLDocument.<anonymous> (post-new.php:2448) (anonymous) @ post-new.php:2448
This happens why I try to create a new Gutenberg post.
I’m unsure if it relates to the following error I have reported with Yoast: https://wordpress.org/support/topic/yoast-gutenberg-cannot-read-property-pluginsidebar-of-undefined/
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expecting to see the Gutenberg editor.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
N/A - haven't tried
The text was updated successfully, but these errors were encountered: