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

WordPress Trac noreply at wordpress.org
Thu Oct 25 18:58:32 UTC 2018

#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 JoshuaWold):

 Sharing a new version of this based on feedback in the #design Slack
 channel during our previous Bug Scrub.

 1. Added the option to re-activate Gutenberg on path 4
 2. Added an option to install the Classic Editor on the update page if
 you're on Path 1.
 ''Note:'' I think this is enough, it was suggested by @postphotos to
 potentially group together the ability to install the plugin and update at
 the same time, but that seems like an unnecessary complication. \\
 ''Additional note:'' @joyreynolds brought up a great point regarding 4.9.3
 users having an update and not seeing anything about Gutenberg until this
 update hits. The minor change above for Path 1 may be enough for them to
 learn more about Gutenberg and activate the Classic Editor if need be.
 Welcome feedback on this point!
 3. Removed the checkmark to validate that you want to update. It was
 discussed as adding unnecessary complication to the update process.
 4. Simplified the text on the WordPress updates page. It should now be
 easier to read and easier to translate.
 5. Re-arranged the paths so they're shown sequentially.

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

More information about the wp-trac mailing list