[wp-trac] [WordPress Trac] #59038: WordPress 6.3 Gutenberg Editor Bug - Editor Unusable

[WordPress Trac]

#59038: WordPress 6.3 Gutenberg Editor Bug - Editor Unusable
--------------------------+-------------------------
 Reporter:  sarahh1997    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.3.1
Component:  Editor        |     Version:  6.3
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:  javascript
--------------------------+-------------------------

Comment (by leehodson):

 Replying to [comment:19 glendaviesnz]:

 I have more info for you.

 I've taken a longer look into the issue. I think the issue is greater than
 just one or two plugins being incompatible with the new Gutenberg version
 shipped with WP 6.3.

 The error shown below no longer happens when I disabled the plugin Grow
 Social by Mediavine (nee 'Social Pug'). The editor area works more
 smoothly when this plugin is disabled but other errors seem to be present;
 these other errors disappear as more editor affecting plugins are
 disabled.

 I'm not sure why the errors previously failed to disappear when I disabled
 all plugins and used a default theme but I will guess that I was lead to
 believe that because the non rendered blocks still showed errors when the
 editor pages were reloaded e.g. they had the message 'Click to Restore
 Block' or whatever the error wording is. I probably judged too quickly out
 of frustration that I had a huge number of non working sites caused by the
 upgrade to WP 6.3.

 So, reloading the page editor with the Console open using Ctrl+R to
 encourage files to be freshly downloaded and after disabling plugins one-
 by-one before each reload I see that

 1. the errors reduce in number with each editor affecting plugin disabled;
 2. the editor gradually restores to being as responsive as it was prior to
 WP 6.3 being installed; and
 3. Improperly rendered blocks (those with the 'fix errors' message button
 above them) remain non rendered until the 'fix it' button is pressed.

 I think it is a mixture of pure luck that fewer people have reported the
 issue than would otherwise notice the fault because A) some people still
 use the Classic Editor (I and my clients prefer Gutenberg, by the way;
 despite hiccups you are doing a great job with GB) and B) the errors that
 are accumulating in the editor area are too few in many sites to cause the
 editor to break.

 The error message shown below is not shown when Grow Social is disabled.
 The length of the error message when Grow Social is enabled decreases with
 each other plugin that is disabled i.e fewer of these lines in the
 message: ''at B (element.min.js:9:6431)''.

 {{{
 blocks.min.js:10 Uncaught RangeError: Maximum call stack size exceeded
     at Function.zr [as save] (blocks.min.js:10:4273)
     at Wg.Content (block-editor.min.js:26:308655)
     at B (element.min.js:9:6433)
     at B (element.min.js:9:6431)
     at B (element.min.js:9:6431)
     at B (element.min.js:9:6431)
     at B (element.min.js:9:6431)
     at B (element.min.js:9:6431)
     at B (element.min.js:9:6431)
     at B (element.min.js:9:6431)
     ...
     ...
 }}}

 Other sites without Grow Social installed experience the same or similar
 Gutenberg related issue(s): editor won't save, edits can't be made, blocks
 fail to render, editor experience is slow.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59038#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform