Stopped Working after Update (2 of 3 issues solved: plugin conflict, nginx config update)

[masterpulha]

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.

• Windows 10
• Google Chrome
• Version 69.0.3497.100 (Official Build) (64-bit)
• Gutenberg Version 3.9.0

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)`

[barrymichaeldoyle]

I'm also having issues since the update.

TypeError: wp.media is not a function
    at new t (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/build/edit-post/index.js?ver=1537904929:12:4466)
    at yh (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:97:111)
    at lg (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:88)
    at mg (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:386)
    at gc (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:127:202)
    at vb (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:230)
    at ub (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:65)
    at zd (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:124:449)
    at ra (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:123:319)
    at Object.enqueueSetState (https://www.barrymichaeldoyle.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:189:231)

[masterpulha]

Now I also disableable Yoast SEO and tested Gutenberg 3.8.0 - 3.7.0 and 3.6.2.
All will just show a blank page :-/
Really needed this solved today, was creating content and got used to Gutenberg.
Tried Elementor just to see if it worked and maybe get some work done, and it's working great.
Also tried WPBakery and all good, so I'm pretty sure its exclusively a Gutenberg problem.

The plugin is starting to get to the level of the other two so I hope it gets fixed soon.

[kudesa]

Not working. Gutenberg 3.8.0 and 3.9.0.

macOS 10.13.6
Chrome/69.0.3497.100
Gutenberg Version 3.9.0

TypeError: Cannot read property 'show_ui' of undefined
    at /wp-content/plugins/gutenberg/build/editor/index.js?ver=1537964740:50:237190
    at i (/wp-content/plugins/gutenberg/vendor/lodash.min.59550321.js:6:91)
    at An.filter (/wp-content/plugins/gutenberg/vendor/lodash.min.59550321.js:99:338)
    at /wp-content/plugins/gutenberg/build/editor/index.js?ver=1537964740:50:237155
    at yh (/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:95:430)
    at lg (/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:88)
    at mg (/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:386)
    at gc (/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:127:202)
    at vb (/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:230)
    at ub (/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:65)

[designsimply]

@masterpulha thanks for reporting this! I see that several of the notices in your console errors include wp-seo-structured-data-blocks-820.min.js and that may indicate a conflict with Yoast SEO. I did test the plugin with the Gutenberg 3.9.0-rc.2 release and it worked in my test, so there may be something specific to your server environment that is different compared to what I have been able to test so far. Also, Yoast SEO has just been updated to 8.3 so updating that first and then clearing cache and testing again would be a good step based on those specific errors.

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 wp-seo), can you confirm that? Do you see any different errors at that point?

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!

[designsimply]

@barrymichaeldoyle TypeError: wp.media is not a function is a different error. If you are using the Wordfence plugin, may I ask that you add a comment to #7643 noting the error there and whether you are using a multisite install or not? If you are not using Wordfence, may I ask that you create a new issue and note the error as well as a list of your plugins as a starting point for further help?

[designsimply]

@kudesa the error and screenshots you posted look similar to #9912. Would you mind adding your screenshots there and also note whether you are using nginx and also if you use a VPN?

[kudesa]

@designsimply I am using mamp with nginx

[designsimply]

@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)

[designsimply]

@twosg since I see references to wp-seo-structured-data-blocks-830.min.js in the error you posted, may I ask if the problem goes away if you temporarily deactivate the Yoast SEO plugin and then clear browser cache and try editing a post again?

[kudesa]

@designsimply wow!
I replaced the old rule nginx location
$uri $uri/ /index.php?q=$uri$args;
on new rule
$uri $uri/ /index.php?$args;
It's working.
Thank you!

[Lofesa]

Hi @kudesa @designsimply
Try better index.php$is_args$args ; from nginx docs:
$is_args
“?” if a request line has arguments, or an empty string otherwise
$args
arguments in the request line

[Lofesa]

Hi @masterpulha @designsimply
errors related to polifylll are from Yoast. Update the version and it is go

[twosg]

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.

[designsimply]

@twosg, ah! Good find! May I ask which plugin? Maybe we can contact them and let them know aobut the problem.

[designsimply]

I am closing this issue with the following notes:

1. @masterpulha's errors are related to the Yoast SEO plugin and should try updating.
2. @barrymichaeldoyle should move to #9912.
3. @kudesa solved by updating nginx location rules.

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!

[twosg]

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.

[designsimply]

Ace. Thank you for the follow-up @twosg !