[wp-trac] [WordPress Trac] #45073: Upgrading to 5.0 and handling the Gutenberg plugin
WordPress Trac
noreply at wordpress.org
Wed Oct 10 20:24:39 UTC 2018
#45073: Upgrading to 5.0 and handling the Gutenberg plugin
-----------------------------+-----------------------------
Reporter: mcsf | Owner: mcsf
Type: defect (bug) | Status: assigned
Priority: normal | Milestone: Awaiting Review
Component: Upgrade/Install | Version: trunk
Severity: normal | Keywords:
Focuses: |
-----------------------------+-----------------------------
Once 5.0 lands, a process will be needed through which users running 4.9.*
with the Gutenberg plugin activated can have the plugin automatically
deactivate upon upgrading to 5.0. As is expected.
As a feature plugin, Gutenberg differs slightly in a couple of ways:
- Gutenberg development — phase 2 and beyond — will continue via the
plugin. A small subset of users may be interested in remaining on the
faster-iterating cycle of the plugin.
- The feature being merged, i.e. the new editor, can be disabled by way of
a second plugin: Classic Editor. Although everything is being done to
eschew its need, it will nevertheless be sought by many.
These beg a few of questions:
- How much information should be offloaded to the “Welcome to 5.0” post-
upgrade page and what should we handle separately?
- Should we account for the prospective intent of some users to keep using
the Gutenberg plugin?
- Should the message conveyed vary depending on a user’s installed plugins
(Gutenberg, Classic Editor)?
The overarching goal for the entire process should be to **minimize the
user’s burden** of choice, especially upfront choice (e.g. requiring a
decision before trying the changes), and the anxiety that comes with it.
Thus a tentative flow could be:
1. User requests 5.0 upgrade.
2. Upgrade is carried through.
3. In the process, the Gutenberg plugin is deactivated. No user action is
required (nor is any explicit notice of this deactivation necessary).
And that’s it in terms of flow. After the upgrade, the 5.0 Welcome page
should present Gutenberg as a highlight of the release. Perhaps this page
is enough.
If not, should a [https://make.wordpress.org/core/2018/08/02/try-
gutenberg-callout-in-wordpress-4-9-8/ callout-like] header appear in WP-
Admin, letting users know about the Gutenberg plugin and/or Classic
Editor?
cc @pento
--
Ticket URL: <https://core.trac.wordpress.org/ticket/45073>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list