[wp-trac] [WordPress Trac] #45073: Upgrading to 5.0 and handling the Gutenberg plugin

[WordPress Trac]

#45073: Upgrading to 5.0 and handling the Gutenberg plugin
-----------------------------+-----------------------
 Reporter:  mcsf             |       Owner:  mcsf
     Type:  defect (bug)     |      Status:  assigned
 Priority:  normal           |   Milestone:  5.0
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  ux-feedback      |     Focuses:
-----------------------------+-----------------------

Comment (by azaozz):

 I'm pretty much with everything @dd32 said above. Just one (technical)
 exception: it would be better if core would include any warnings about the
 Classic Editor plugin being active (and preventing the Block editor from
 loading). The reason is simple: if that text is in core, it will get
 translated. If it is in the plugin, there would be only few translations,
 at most.

 Also things may be a bit over-complicated in the discussion so far. It is
 important to tell people why the "Major New Feature" (Block editor)
 doesn't work on their site: because they have installed a plugin to
 disable it. Best place for this is right on the post-install (What's New)
 screen. The same place would be great to notify the users that the
 Gutenberg plugin has been deactivated, and offer to reactivate it.

 IMHO showing additional admin notices seems excessive. Generally users
 that have installed Classic Editor **-know-** that they have installed it
 :) If we keep telling them, it would be super annoying. Also keep in mind
 that the admin notices are sometimes (often?) overused by plugins. It's
 not unusual to see several of them popping up everywhere after an upgrade.
 That, of course, has the exact opposite effect, most users just ignore
 them.

 The tl;dr:
 1. The post-install (What's New) screen is the best place to warn the
 users if the Classic Editor plugin is preventing use of the Block editor,
 or if Gutenberg was deactivated.
 2. Any such warnings should be in core as they will be translated.
 3. Admin notices and/or additional tabs will probably be a lot less
 effective. The same is true for Screen Options or the Help tab.
 Unfortunately these are used by a very small percentage of users.

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