[wp-trac] [WordPress Trac] #53410: Provide better guidance for users looking to test FSE themes

[WordPress Trac]

#53410: Provide better guidance for users looking to test FSE themes
---------------------------------------+-----------------------
 Reporter:  desrosj                    |       Owner:  desrosj
     Type:  defect (bug)               |      Status:  assigned
 Priority:  normal                     |   Milestone:  5.8
Component:  Themes                     |     Version:  trunk
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:
---------------------------------------+-----------------------
Changes (by desrosj):

 * keywords:  has-screenshots => has-screenshots has-patch


Comment:

 [attachment:"53410.diff"] is a proof of concept that adds a check for the
 `full-site-editing` tag in the theme's `style.css` file. With this patch:
 - A user can preview the theme in the Customizer, but they are not allowed
 to activate it unless Gutenberg is active.
 - Clicking activate in the admin throws a `WP_Error` displays on a
 `wp_die()` screen.

 The error message displayed is very basic right now, but I envisioned an
 "Activate anyway" button, and potentially linking out to a page on .org
 explaining traditional themes vs. FSE themes.

 [attachment:"plugin-screen.png"] shows what I have in mind for the plugin
 screen. Deactivating Gutenberg will not be blocked, but a notice can be
 added to point out that the plugin is required for the current theme. This
 could and should probably be added to the plugin itself (the action hooks
 needed are already present in Core).

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