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

[WordPress Trac]

#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 has-patch  |     Focuses:
-----------------------------------------------+---------------------

Comment (by jorbin):

 @rebasaurus The testing for that would need to make sure that no other
 versions of Gutenberg released since 16.5 have an issue due to the change.
 I believe this was the research Caleb mentioned doing. Is that the testing
 you did or was it just GB 16.4 and the patch vs trunk and/or 6.4? We also
 likely need to make sure that no public code is expecting the `protected`
 visibility. I've started
 [https://wpdirectory.net/search/01HDHPAKTMKWK9E01ETYWSMHKY a search of the
 plugins directory] to help with that.

 The change would also need to be made in Gutenberg and testing would need
 to be done to ensure trunk there has no issue.

 I also think @ramonopoly, @isabel_brison, and @spacedmonkey might want to
 chime in as [56575] is something they worked on.

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