[wp-trac] [WordPress Trac] #45373: New reusable block creation returning blank white screen

[WordPress Trac]

#45373: New reusable block creation returning blank white screen
------------------------------+-----------------------
 Reporter:  umakantsharmamwb  |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  5.1
Component:  Editor            |     Version:  5.0
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  rest-api
------------------------------+-----------------------
Changes (by desrosj):

 * keywords:  needs-patch reporter-feedback => needs-patch
 * focuses:   => rest-api


Comment:

 Thanks for the details, @umakantsharmamwb. I am able to reproduce what you
 are detailing!

 So I did some digging on this. Looks like there is already an
 [https://github.com/WordPress/gutenberg/issues/12324 issue opened on the
 Gutenberg GitHub for this], but I am going to leave both open because I
 think there needs to be an update in both locations.

 The REST API request to the blocks endpoint is returning a 403 error. I
 believe that this is causing the error in `wp-polyfill` that you are
 seeing. This should be fixed upstream. A REST API error should not cause a
 white screen for the user. At a minimum, an error message should be
 displayed with a path forward.

 @designsimply also discovered a strange aspect of this. If the Gutenberg
 plugin is activated, the Add New Block page work and it continues to work
 even after the plugin is deactivated. This happens because the plugin
 block adds capabilities to the user roles, which are stored in the
 database. These are not cleaned up after the plugin is
 deactivated/removed, so they remain and the functionality continues to
 work.

 This second issue brings up a bug that could probably be fixed in both
 locations (Core and the Gutenberg Plugin) so that there is consistency
 moving forward. The bug in core causing the 403 permissions issue should
 be fixed, and then, potentially, the plugin should have its capabilities
 updated to match what is currently in core.

 A related issue is #45423, which could potentially fix this problem.

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