Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Guttenberg Blog Post can't be edited with Yoast 8.2-3 enabled #10986

Closed
3 of 8 tasks
crazybadger opened this issue Sep 12, 2018 · 16 comments
Closed
3 of 8 tasks

Guttenberg Blog Post can't be edited with Yoast 8.2-3 enabled #10986

crazybadger opened this issue Sep 12, 2018 · 16 comments
Labels
wait for feedback

Comments

@crazybadger
Copy link

crazybadger commented Sep 12, 2018 •
edited

  • [x ] I've read and understood the contribution guidelines.
  • [x ] I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened.

With Yoast enabled, any blog posts I have created using the Guttenberg editor fail to open and display this error:

Error Message

I was following this issue 'Gutenberg editor crashes if the Classic Editor Plugin is enabled #10850' which seemed to be very similar, although this was supposedly resolved with 8.2 and I still have the issue

If I edit the Post using the classic editor, it opens, but none of the Yoast settings are available and I just see this:

Error Message 2

Please describe what you expected to happen and why.

I expect the post to open and for me to edit it.

How can we reproduce this behavior?

  1. Enable Yoast Plugin
  2. Edit Guttenberg Post
  3. Error message is displayed

Technical info

  • WordPress version: 4.9.8
  • Yoast SEO version: 8.2
  • If relevant, which editor is affected (or editors):
  • Classic Editor
  • Gutenberg
  • Classic Editor plugin
  • Which browser is affected (or browsers):
  • IE11
  • Edge
  • Chrome
  • Firefox
  • Safari
  • Relevant plugins in case of a bug: Yoast, Guttenberg
  • Tested with theme: Site is using Divi, but tested with Twenty Seventeen
@damadorPL
Copy link

its not only in gutenberg - it hits many themes ( DIvi , Divi-Extra The 7 ... ) without gutenberg enabled

@CarolineGeven CarolineGeven self-assigned this Sep 13, 2018
@CarolineGeven
Copy link
Contributor

Thanks for reporting this issue. Unfortunately, we were not able to reproduce this problem.

I have tested with Divi + Yoast + Gutenberg and Yoast + Gutenberg. The last screenshot you sent me, usually means there's a JavaScript console error. Could you please check your browser's console for errors? If you're unsure how to do so, please read this knowledge base article we've written about this: https://kb.yoast.com/kb/how-to-find-javascript-errors-with-your-browsers-console/

Could you please inform me of the results?

Could you please also confirm the following:

  • Are you running on the latest versions of the Divi theme and Gutenberg?
  • Have you only tested with Yoast and Twenty Seventeen and all other plugins inactive?

@CarolineGeven CarolineGeven removed their assignment Sep 13, 2018
@crazybadger
Copy link
Author

crazybadger commented Sep 13, 2018 •
edited by abotteram

Wordpress and plugins are all up to date. I checked opening the post with Yoast disabled, and it opened correctly. Enabled the Yoast plugin and tried to open the post and this is output from the Developer console:

commons-820.min.js?ver=8.2:1 Uncaught Error: only one instance of babel-polyfill is allowed
    at Object.<anonymous> (commons-820.min.js?ver=8.2:1)
    at Object.<anonymous> (commons-820.min.js?ver=8.2:1)
    at e (commons-820.min.js?ver=8.2:1)
    at Object.<anonymous> (commons-820.min.js?ver=8.2:6)
    at e (commons-820.min.js?ver=8.2:1)
    at commons-820.min.js?ver=8.2:1
    at commons-820.min.js?ver=8.2:1
(anonymous) @ commons-820.min.js?ver=8.2:1
(anonymous) @ commons-820.min.js?ver=8.2:1
e @ commons-820.min.js?ver=8.2:1
(anonymous) @ commons-820.min.js?ver=8.2:6
e @ commons-820.min.js?ver=8.2:1
(anonymous) @ commons-820.min.js?ver=8.2:1
(anonymous) @ commons-820.min.js?ver=8.2:1
index.js?ver=1536788033:5 


Jed localization error: 
Error: No locale meta information provided.
o @ index.js?ver=1536788033:5
(anonymous) @ index.js?ver=1536788033:5
o @ index.js?ver=1536788033:5
d @ index.js?ver=1536788033:5
value @ components-820.min.js?ver=8.2:59
f @ commons-820.min.js?ver=8.2:14
beginWork @ commons-820.min.js?ver=8.2:14
i @ commons-820.min.js?ver=8.2:14
u @ commons-820.min.js?ver=8.2:14
w @ commons-820.min.js?ver=8.2:14
m @ commons-820.min.js?ver=8.2:14
g @ commons-820.min.js?ver=8.2:14
h @ commons-820.min.js?ver=8.2:14
s @ commons-820.min.js?ver=8.2:14
e @ commons-820.min.js?ver=8.2:14
updateContainer @ commons-820.min.js?ver=8.2:14
nn.render @ commons-820.min.js?ver=8.2:22
(anonymous) @ commons-820.min.js?ver=8.2:14
unbatchedUpdates @ commons-820.min.js?ver=8.2:14
an @ commons-820.min.js?ver=8.2:14
render @ commons-820.min.js?ver=8.2:22
1419 @ wp-seo-help-center-820.min.js?ver=8.2:1
e @ commons-820.min.js?ver=8.2:1
window.yoastWebpackJsonp @ commons-820.min.js?ver=8.2:1
(anonymous) @ wp-seo-help-center-820.min.js?ver=8.2:1
wp-seo-post-scraper-820.min.js?ver=8.2:1 


Uncaught TypeError: Cannot set property 'domain' of undefined
    at o (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at h (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at HTMLDocument.C (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at i (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-tabs,jquery-form,wp-a11y,moxiejs,plupload&ver=4.9.8:2)
    at Object.fireWith [as resolveWith] (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-tabs,jquery-form,wp-a11y,moxiejs,plupload&ver=4.9.8:2)
    at Function.ready (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-tabs,jquery-form,wp-a11y,moxiejs,plupload&ver=4.9.8:2)
    at HTMLDocument.K (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-tabs,jquery-form,wp-a11y,moxiejs,plupload&ver=4.9.8:2)
o @ wp-seo-post-scraper-820.min.js?ver=8.2:1
h @ wp-seo-post-scraper-820.min.js?ver=8.2:1
C @ wp-seo-post-scraper-820.min.js?ver=8.2:1
i @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-tabs,jquery-form,wp-a11y,moxiejs,plupload&ver=4.9.8:2
fireWith @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-tabs,jquery-form,wp-a11y,moxiejs,plupload&ver=4.9.8:2
ready @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-tabs,jquery-form,wp-a11y,moxiejs,plupload&ver=4.9.8:2
K @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-tabs,jquery-form,wp-a11y,moxiejs,plupload&ver=4.9.8:2
index.js?ver=1536788033:2 

Block validation: Block validation failed for `core/more` ({name: "core/more", title: "More", description: "Want to show only part of this post on your blog’s…? Insert a "More" block where you want the split.", icon: {…}, category: "layout", …}).

Expected:

`<!--more-->`

Actual:

`<p><!--more--></p>`
(anonymous) @ index.js?ver=1536788033:2
et @ index.js?ver=1536788033:2
pt @ index.js?ver=1536788033:2
(anonymous) @ index.js?ver=1536788033:2
(anonymous) @ index.js?ver=1536788033:2
SETUP_EDITOR @ index.js?ver=1536788033:12
(anonymous) @ index.js?ver=1536788033:12
(anonymous) @ index.js?ver=1536788033:1
value @ index.js?ver=1536788033:1
t @ index.js?ver=1536788033:12
yh @ react-dom.min.82e21c65.js:97
lg @ react-dom.min.82e21c65.js:120
mg @ react-dom.min.82e21c65.js:120
gc @ react-dom.min.82e21c65.js:127
vb @ react-dom.min.82e21c65.js:126
ub @ react-dom.min.82e21c65.js:126
zd @ react-dom.min.82e21c65.js:124
ra @ react-dom.min.82e21c65.js:123
enqueueSetState @ react-dom.min.82e21c65.js:189
q.setState @ react.min.ab6b06d4.js:18
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
h @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
tryCatch @ wp-polyfill-ecmascript.min.2ae96136.js:3
invoke @ wp-polyfill-ecmascript.min.2ae96136.js:3
t.(anonymous function) @ wp-polyfill-ecmascript.min.2ae96136.js:3
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
d @ index.js?ver=1536788033:1
y @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:12
r @ index.js?ver=1536788033:1
n @ index.js?ver=1536788033:1
yh @ react-dom.min.82e21c65.js:97
lg @ react-dom.min.82e21c65.js:120
mg @ react-dom.min.82e21c65.js:120
gc @ react-dom.min.82e21c65.js:127
vb @ react-dom.min.82e21c65.js:126
ub @ react-dom.min.82e21c65.js:126
zd @ react-dom.min.82e21c65.js:124
ra @ react-dom.min.82e21c65.js:123
Id @ react-dom.min.82e21c65.js:138
kc @ react-dom.min.82e21c65.js:138
Sa.render @ react-dom.min.82e21c65.js:194
(anonymous) @ react-dom.min.82e21c65.js:141
Hd @ react-dom.min.82e21c65.js:136
mc @ react-dom.min.82e21c65.js:141
render @ react-dom.min.82e21c65.js:196
Rn @ index.js?ver=1536788033:12
(anonymous) @ post.php?post=22464&action=edit:2738
react-dom.min.82e21c65.js:110 


ReferenceError: YoastSEO is not defined
    at f (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at o (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at t.value (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at Xf (react-dom.min.82e21c65.js:91)
    at yh (react-dom.min.82e21c65.js:102)
    at lg (react-dom.min.82e21c65.js:120)
    at mg (react-dom.min.82e21c65.js:120)
    at gc (react-dom.min.82e21c65.js:127)
    at vb (react-dom.min.82e21c65.js:126)
    at ub (react-dom.min.82e21c65.js:126)
bg @ react-dom.min.82e21c65.js:110
d.function.d.componentDidCatch.c.callback @ react-dom.min.82e21c65.js:116
Jf @ react-dom.min.82e21c65.js:73
Kf @ react-dom.min.82e21c65.js:74
jc @ react-dom.min.82e21c65.js:134
gc @ react-dom.min.82e21c65.js:127
vb @ react-dom.min.82e21c65.js:126
ub @ react-dom.min.82e21c65.js:126
zd @ react-dom.min.82e21c65.js:124
ra @ react-dom.min.82e21c65.js:123
enqueueSetState @ react-dom.min.82e21c65.js:189
q.setState @ react.min.ab6b06d4.js:18
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
h @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
tryCatch @ wp-polyfill-ecmascript.min.2ae96136.js:3
invoke @ wp-polyfill-ecmascript.min.2ae96136.js:3
t.(anonymous function) @ wp-polyfill-ecmascript.min.2ae96136.js:3
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
d @ index.js?ver=1536788033:1
y @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:12
r @ index.js?ver=1536788033:1
n @ index.js?ver=1536788033:1
yh @ react-dom.min.82e21c65.js:97
lg @ react-dom.min.82e21c65.js:120
mg @ react-dom.min.82e21c65.js:120
gc @ react-dom.min.82e21c65.js:127
vb @ react-dom.min.82e21c65.js:126
ub @ react-dom.min.82e21c65.js:126
zd @ react-dom.min.82e21c65.js:124
ra @ react-dom.min.82e21c65.js:123
Id @ react-dom.min.82e21c65.js:138
kc @ react-dom.min.82e21c65.js:138
Sa.render @ react-dom.min.82e21c65.js:194
(anonymous) @ react-dom.min.82e21c65.js:141
Hd @ react-dom.min.82e21c65.js:136
mc @ react-dom.min.82e21c65.js:141
render @ react-dom.min.82e21c65.js:196
Rn @ index.js?ver=1536788033:12
(anonymous) @ post.php?post=22464&action=edit:2738
react-dom.min.82e21c65.js:110 


ReferenceError: YoastSEO is not defined
    at f (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at o (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at t.value (wp-seo-post-scraper-820.min.js?ver=8.2:1)
    at Xf (react-dom.min.82e21c65.js:91)
    at yh (react-dom.min.82e21c65.js:102)
    at lg (react-dom.min.82e21c65.js:120)
    at mg (react-dom.min.82e21c65.js:120)
    at gc (react-dom.min.82e21c65.js:127)
    at vb (react-dom.min.82e21c65.js:126)
    at ub (react-dom.min.82e21c65.js:126)
bg @ react-dom.min.82e21c65.js:110
d.function.d.componentDidCatch.c.callback @ react-dom.min.82e21c65.js:116
Jf @ react-dom.min.82e21c65.js:73
Kf @ react-dom.min.82e21c65.js:74
jc @ react-dom.min.82e21c65.js:134
gc @ react-dom.min.82e21c65.js:127
vb @ react-dom.min.82e21c65.js:126
ub @ react-dom.min.82e21c65.js:126
zd @ react-dom.min.82e21c65.js:124
ra @ react-dom.min.82e21c65.js:123
enqueueSetState @ react-dom.min.82e21c65.js:189
q.setState @ react.min.ab6b06d4.js:18
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
h @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
tryCatch @ wp-polyfill-ecmascript.min.2ae96136.js:3
invoke @ wp-polyfill-ecmascript.min.2ae96136.js:3
t.(anonymous function) @ wp-polyfill-ecmascript.min.2ae96136.js:3
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
Promise.then (async)
r @ index.js?ver=1536788033:1
c @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
d @ index.js?ver=1536788033:1
y @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:1
(anonymous) @ index.js?ver=1536788033:12
r @ index.js?ver=1536788033:1
n @ index.js?ver=1536788033:1
yh @ react-dom.min.82e21c65.js:97
lg @ react-dom.min.82e21c65.js:120
mg @ react-dom.min.82e21c65.js:120
gc @ react-dom.min.82e21c65.js:127
vb @ react-dom.min.82e21c65.js:126
ub @ react-dom.min.82e21c65.js:126
zd @ react-dom.min.82e21c65.js:124
ra @ react-dom.min.82e21c65.js:123
Id @ react-dom.min.82e21c65.js:138
kc @ react-dom.min.82e21c65.js:138
Sa.render @ react-dom.min.82e21c65.js:194
(anonymous) @ react-dom.min.82e21c65.js:141
Hd @ react-dom.min.82e21c65.js:136
mc @ react-dom.min.82e21c65.js:141
render @ react-dom.min.82e21c65.js:196
Rn @ index.js?ver=1536788033:12
(anonymous) @ post.php?post=22464&action=edit:2738

@CarolineGeven
Copy link
Contributor

Thanks for replying. We've looked at the errors and saw there are a couple.

The first one about Babel-polyfill will be fixed in 8.3, but this is not what is currently breaking your website. For more information, please see: #10953

The issue you have with yoastSEO is not defined, could be due to browser caching. Could you please clear your browser's cache? If you're unsure how to do so, please see this article: https://kb.yoast.com/kb/how-to-clear-my-browsers-cache/

Can you notify us of the results?

@crazybadger
Copy link
Author

I've cleared the browser cache but it doesn't make any difference.

If I disable the Guttenberg plugin, I can open the blog with the Yoast plugin active, although the Yoast settings section is blank as per the screenshot I posted above.

If I enable the Guttenberg plugin, I can't even open the blog.

@CarolineGeven
Copy link
Contributor

Could you please let me know which language you have selected as your site language and your profile language? Additionally, do you have any tabs in the sidebar open while writing?
And to clarify: is this still with Divi on or also without Divi?

@crazybadger
Copy link
Author

Site language is English (UK) and profile language is Site Default.

I've normally got the Settings sidebar open on the righthand side when editing posts, and yes, this is still with the Divi theme enabled.

@marcosdipaolo
Copy link

marcosdipaolo commented Sep 15, 2018 •
edited

is this related with this?
I also have Uncaught Error: only one instance of babel-polyfill is allowedand I get Updating failed and Publishing faIled when Yoast SEO enabled. The post updates though.
Uncaught Error: only one instance of babel-polyfill is allowed at Object.<anonymous> (commons-820.min.js?ver=8.2:1) at Object.<anonymous> (commons-820.min.js?ver=8.2:1) at e (commons-820.min.js?ver=8.2:1) at Object.<anonymous> (commons-820.min.js?ver=8.2:6) at e (commons-820.min.js?ver=8.2:1) at commons-820.min.js?ver=8.2:1 at commons-820.min.js?ver=8.2:1

Edit: Actually it also hapens outside Gutenberg editor (in plugin list).

@crazybadger
Copy link
Author

This is still broken in 8.3. Time to find a new SEO plugin?

react-dom.min.82e21c65.js:110 ReferenceError: YoastSEO is not defined at f (wp-seo-post-scraper-830.min.js:1) at o (wp-seo-post-scraper-830.min.js:1) at t.value (wp-seo-post-scraper-830.min.js:1) at Xf (react-dom.min.82e21c65.js:91) at yh (react-dom.min.82e21c65.js:102) at lg (react-dom.min.82e21c65.js:120) at mg (react-dom.min.82e21c65.js:120) at gc (react-dom.min.82e21c65.js:127) at vb (react-dom.min.82e21c65.js:126) at ub (react-dom.min.82e21c65.js:126) bg @ react-dom.min.82e21c65.js:110 react-dom.min.82e21c65.js:110 ReferenceError: YoastSEO is not defined at f (wp-seo-post-scraper-830.min.js:1) at o (wp-seo-post-scraper-830.min.js:1) at t.value (wp-seo-post-scraper-830.min.js:1) at Xf (react-dom.min.82e21c65.js:91) at yh (react-dom.min.82e21c65.js:102) at lg (react-dom.min.82e21c65.js:120) at mg (react-dom.min.82e21c65.js:120) at gc (react-dom.min.82e21c65.js:127) at vb (react-dom.min.82e21c65.js:126) at ub (react-dom.min.82e21c65.js:126) bg @ react-dom.min.82e21c65.js:110 react-dom.min.82e21c65.js:110 ReferenceError: YoastSEO is not defined at f (wp-seo-post-scraper-830.min.js:1) at o (wp-seo-post-scraper-830.min.js:1) at t.value (wp-seo-post-scraper-830.min.js:1) at Xf (react-dom.min.82e21c65.js:91) at yh (react-dom.min.82e21c65.js:102) at lg (react-dom.min.82e21c65.js:120) at mg (react-dom.min.82e21c65.js:120) at gc (react-dom.min.82e21c65.js:127) at vb (react-dom.min.82e21c65.js:126) at ub (react-dom.min.82e21c65.js:126) bg @ react-dom.min.82e21c65.js:110 react-dom.min.82e21c65.js:110 ReferenceError: YoastSEO is not defined at f (wp-seo-post-scraper-830.min.js:1) at o (wp-seo-post-scraper-830.min.js:1) at t.value (wp-seo-post-scraper-830.min.js:1) at Xf (react-dom.min.82e21c65.js:91) at yh (react-dom.min.82e21c65.js:102) at lg (react-dom.min.82e21c65.js:120) at mg (react-dom.min.82e21c65.js:120) at gc (react-dom.min.82e21c65.js:127) at vb (react-dom.min.82e21c65.js:126) at ub (react-dom.min.82e21c65.js:126) bg @ react-dom.min.82e21c65.js:110

@crazybadger crazybadger changed the title Guttenberg Blog Post can't be edited with Yoast 8.2 enabled Guttenberg Blog Post can't be edited with Yoast 8.2-3 enabled Sep 26, 2018
@andreascreten
Copy link

We are also still experiencing this issue with Yoast 8.3 and Gutenberg 3.9.0.

@crazybadger
Copy link
Author

I've disabled all plugins and switched to the twentyseventeen theme and with the latest Guttenberg and Yoast plugins activated I still get this error. If I disable Guttenberg I don't get the error, but no Yoast details appear in the Yoast section and I can't run the Yoast setup.

Can someone please change this from 'waiting feedback' and investigate?

@CarolineGeven
Copy link
Contributor

@crazybadger Unfortunately we haven't been able to reproduce this issue with the latest version of Gutenberg, Divi Theme and Yoast SEO. Could you please let us know the following:

  • Which blocks are you using?
  • When and how are you adding the 'more' Gutenberg blocks?
  • Is this happening with all posts? And if so, do the posts have anything in common?
  • Does this also happen when creating a new post or only when editing an older one?
  • Which version of PHP are you running?
  • Which OS are you running? I am assuming it's Mac as you said you tested it on Safari.

Please understand we do our best to reproduce each and every issue that is posted on GitHub. This may not always be within 24 hours.

@crazybadger
Copy link
Author

After playing with this for far too long, I finally stumbled across the Healthcheck plugin which highlighted that I didn't have the php-json modules installed. I added this and from an initial test, everything now appears to work.

If you're having a similar problem, add the json module and see if that helps. I'm going to close this thread now.

@designsimply designsimply mentioned this issue Oct 18, 2018
Closed
@yaroslavkozak
Copy link

TEMPORARY SOLUTION

Issue is still present with gutenberg 4.0.0 and yoast 8.4
I have two websites with latest yoast (8.4) and gutenberg (4.0.0)

There was the same issue as discribed above.
Tested with other plugins disadbled and no result.

SOLVED: by switching admin language to English (initially it was Ukrainian)
I suggest there might be an issue around there (localization or some files responsible for it) that crash gutenberg.

Reverse tested the hypothesis and it is indeed the reason causing gutenberg to crash.

Yoast team, please, check with your code and gutenberg team on the possible solution here. Many people might not be able to work with English and need some natives. This might lead to crashes in other languages too.

Looking forward for the fix.
If I can help in any way - let me know.

All the best!

@dnkhack
Copy link

dnkhack commented Oct 20, 2018 •
edited

I have this problem to. yoast 8.4 Wordpress 4.9.8–ru_RU standart editor.
sprinter lt crafter wordpress - google chrome
sprinter lt crafter wordpress - google chrome1

image
image
image

@dnkhack
Copy link

dnkhack commented Oct 20, 2018

I solved the problem. Hosting provider disabled php module "GD"

@Djennez Djennez mentioned this issue Apr 9, 2019
Closed
2 tasks
@cvanderlinden cvanderlinden mentioned this issue Nov 25, 2019
Closed
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wait for feedback
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@andreascreten @crazybadger @CarolineGeven @damadorPL @yaroslavkozak @marcosdipaolo @dnkhack