[wp-trac] [WordPress Trac] #59718: Short-term (WP 6.4) hotfix to prevent fatal error in standalone Gutenberg (<16.5)

WordPress Trac noreply at wordpress.org
Tue Oct 24 18:17:22 UTC 2023


#59718: Short-term (WP 6.4) hotfix to prevent fatal error in standalone Gutenberg
(<16.5)
-------------------------------------+---------------------
 Reporter:  rebasaurus               |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.4
Component:  Upgrade/Install          |     Version:
 Severity:  critical                 |  Resolution:
 Keywords:  reporter-feedback close  |     Focuses:
-------------------------------------+---------------------
Changes (by jorbin):

 * keywords:  reporter-feedback => reporter-feedback close


Comment:

 This was discussed in the #core-upgrade-install room amongst myself,
 @hellofromTonya, @pbiron, @costdev, @icaleb, and others. The consensus
 that we came to is that the protections in core feel sufficient for 6.4,
 but that the Gutenberg plugins should be enhanced to help future versions.

 The Guteneberg Readme states:
 > Are you a tech-savvy early adopter who likes testing bleeding-edge and
 experimental features, and isn’t afraid to tinker with features that are
 still in active development? If so, this beta plugin gives you access to
 the latest Gutenberg features for block and full site editing, as well as
 a peek into what’s to come.

 When a user opts into using bleeding edge features that are still in
 active development, they are accepting a certain risk. In the Gutenberg
 plugin, some additional checks can be added so that future versions of WP
 will have less of an issue around compatibility. GB is designed to be an
 experimental platform and the desire isn't to reign in that
 experimentation by forcing strict backwards compatible guidelines on it. A
 [https://github.com/WordPress/gutenberg/pull/35194 PR] is being worked on
 that it is believed will help prevent fatal errors in future versions.

 @icaleb mentioned doing some research to see if reverting [56575] should
 be considered to prevent the fatal error. Going to leave this open for
 that.

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


More information about the wp-trac mailing list