[wp-trac] [WordPress Trac] #45073: Upgrading to 5.0 and handling the Gutenberg plugin
WordPress Trac
noreply at wordpress.org
Wed Nov 14 21:53: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: 5.0
Component: Upgrade/Install | Version: trunk
Severity: normal | Resolution:
Keywords: ux-feedback | Focuses:
-----------------------------+-----------------------
Comment (by mrwweb):
''I'm coming to this late, so my apologies for restating anyone's earlier
ideas or unintentionally reopening discussions.''
Replying to [comment:39 azaozz]:
> Generally users that have installed Classic Editor **-know-** that they
have installed it :)
I would add to that: "...or someone else installed it for them for a
specific reason."
I wonder if some slightly more explanatory language that relies a little
less on understanding the plugin name might work better for users with the
Classic Editor installed. Here's a first attempt that isn't quite right
but heads in the direction I'm thinking:
**"You are currently using the WordPress legacy content editor because the
[# Classic Editor plugin] is activated. [# Try out the new editor] and
have your site administrator deactivate the plugin when you're ready for
the new experience."**
I also think that text might go really nicely in the "Try the New Editor"
section of the Welcome dashboard widget.
Finally, should there be any attempt to add or suppress messaging for
other Gutenberg disabling plugins (especially
[https://wordpress.org/plugins/gutenberg-ramp/ Ramp]) or simply detecting
if `add_filter('use_block_editor_for_post', '__return_false');` is set?
Especially in that last case, it becomes a pretty darn good assumption
that either the person knows what they're doing or doesn't know how to
change it even if they know what's happening [and might be better off not
knowing?].
--
Ticket URL: <https://core.trac.wordpress.org/ticket/45073#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list