-
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
Stopped Working after Update (2 of 3 issues solved: plugin conflict, nginx config update) #10162
Comments
I'm also having issues since the update.
|
Now I also disableable Yoast SEO and tested Gutenberg 3.8.0 - 3.7.0 and 3.6.2. The plugin is starting to get to the level of the other two so I hope it gets fixed soon. |
Not working. Gutenberg 3.8.0 and 3.9.0. macOS 10.13.6
|
@masterpulha thanks for reporting this! I see that several of the notices in your console errors include To confirm, the problem still happens when you have installed Gutenberg 3.9.0 and have also temporarily disabled Cloudflare and Yoast SEO 8.2? In that state, if you clear local browser cache and then load the editor and check your browser developer tools for errors, you shouldn't see the same errors any more with the plugin disabled (the ones that start with If the problem is with Cloudflare, then a good troubleshooting step will be to check the Cloudflare WAF log to see if it indicates which rule is causing requests to be blocked. Is this something you can check? Based on the errors showing in your screenshot, it looks like a plugin conflict, but based on what you have mentioned testing (thanks for those details btw!) it sounds like there could be something additional going on and the more information we can get about the specifics the better! |
@barrymichaeldoyle |
@designsimply I am using mamp with nginx |
@kudesa cool, could you note that on #9912 and also mention if it's a plain vanilla install or if you have made any server configuration changes such as for Content-Security-Policy or to rewrite rules? Or you think it should be a separate issue, could you open a new one with all of the related details you can think of? For reference, here is another similar error reported where updating rewrite rules on the server solved the problem: #8802 (comment) |
@twosg since I see references to |
@designsimply wow! |
Hi @kudesa @designsimply |
Hi @masterpulha @designsimply |
Just to let you know, I had similar errors and the problem was a plugin which disabled all embeds in Wordpress. Seems Gutenbergs needs them. |
@twosg, ah! Good find! May I ask which plugin? Maybe we can contact them and let them know aobut the problem. |
I am closing this issue with the following notes:
I also wanted to note that I really appreciate everyone here who is testing Gutenberg at this early stage and taking the time to understand the details. Thank you so much! |
Plugin called Clearfy: https://wordpress.org/plugins/clearfy/ - its not a fault of the plugin directly. It allowes to remove a lot of unneeded stuff from WP, depending on the project. |
Ace. Thank you for the follow-up @twosg ! |
I have been using Gutenberg for a few weeks without any issue with my theme or plugins.
Had Cloudflare and WP Fastest Cache from start. Decided to upgrade and now it only gives me a White Screen.
Tried Cloudflare Developer Mode, and stop caching the site, removed the plugin and installed again but the same result.
https://imgur.com/Kz6YbCM
`Uncaught Error: only one instance of babel-polyfill is allowed
at Object. (commons-820.min.js:1)
at Object. (commons-820.min.js:1)
at e (commons-820.min.js:1)
at Object. (commons-820.min.js:6)
at e (commons-820.min.js:1)
at commons-820.min.js:1
at commons-820.min.js:1
Uncaught TypeError: Cannot read property 'InspectorControls' of undefined
at Object. (index.js:1)
at t (index.js:1)
at Object. (index.js:1)
at t (index.js:1)
at Object. (index.js:1)
at t (index.js:1)
at index.js:1
at index.js:1
Uncaught TypeError: Cannot read property 'Content' of undefined
at Object.1439 (wp-seo-structured-data-blocks-820.min.js:1)
at e (commons-820.min.js:1)
at Object.1438 (wp-seo-structured-data-blocks-820.min.js:1)
at e (commons-820.min.js:1)
at Object.1437 (wp-seo-structured-data-blocks-820.min.js:1)
at e (commons-820.min.js:1)
at Object.1436 (wp-seo-structured-data-blocks-820.min.js:1)
at e (commons-820.min.js:1)
at window.yoastWebpackJsonp (commons-820.min.js:1)
at wp-seo-structured-data-blocks-820.min.js:1
Uncaught TypeError: Cannot set property 'cssText' of undefined
at content.index.js:9150
at content.index.js:9189
at Object.defineProperty.value (content.index.js:1029)
at Object.defineProperty.value (content.index.js:1041)
at webpack_require (content.index.js:20)
at Object.webpack_exports.a (content.index.js:12790)
at webpack_require (content.index.js:20)
at Object. (content.index.js:12043)
at webpack_require (content.index.js:20)
at Object. (content.index.js:12030)`
The text was updated successfully, but these errors were encountered: