-
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
"Updating failed" error and cannot change permalink and preview is not working (solved by an update from Cloudflare) #8412
Comments
Could you please share with us where and when did you get this error? |
Today, I got an update for WordPress 4.9.8 after updating the WordPress it suggested me to install Gutenberg editor plugin. And when I tried the editor I got this error. |
Thank you for the details, @topkhoj! The Yoast team are currently working on their full Gutenberg support, so there may be some features that aren't quite available yet. I'd suggest contacting Yoast support for more info. For editing the permalink/slug, if you click on the post title, you'll see the current permalink and an edit button you can use. |
We should also improve the handling of custom taxonomies to ensure they don't impact Gutenberg itself. This is where we can do much better:
|
Thanks for your suggestions @pento, but I'm not getting the option for editing the permalink/slug. Another error is the post preview is also not working. |
To be able to edit the permalink, you'll need to select a permalink structure other than "Default", there should be a link to the permalink settings page when you click on the title. For post preview, the "Updating Failed" message you're seeing suggests that Gutenberg wasn't able to talk to the REST API properly. Do you have any security plugins that might be disabling the REST API? Also, if you use CloudFlare, there's a problem with the CloudFlare WAF that they're working on a fix for. There's a workaround here that you can use. |
TypeError: Cannot read property 'show_ui' of undefined
at https://topkhoj.com/wp-content/plugins/gutenberg/build/editor/index.js?ver=1533269593:12:302843
at i (https://topkhoj.com/wp-content/plugins/gutenberg/vendor/lodash.min.59550321.js:6:91)
at An.filter (https://topkhoj.com/wp-content/plugins/gutenberg/vendor/lodash.min.59550321.js:99:338)
at https://topkhoj.com/wp-content/plugins/gutenberg/build/editor/index.js?ver=1533269593:12:302808
at yh (https://topkhoj.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:96:396)
at lg (https://topkhoj.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:88)
at mg (https://topkhoj.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:386)
at gc (https://topkhoj.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:127:202)
at vb (https://topkhoj.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:230)
at ub (https://topkhoj.com/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:65)
The text was updated successfully, but these errors were encountered: