[wp-trac] [WordPress Trac] #45207: Meta-box compatibility warnings

WordPress Trac noreply at wordpress.org
Mon Oct 29 04:49:16 UTC 2018

#45207: Meta-box compatibility warnings
 Reporter:  johnjamesjacoby     |       Owner:  pento
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:  5.0
Component:  Options, Meta APIs  |     Version:  5.0
 Severity:  normal              |  Resolution:  fixed
 Keywords:                      |     Focuses:

Comment (by johnjamesjacoby):

 >The user can decide whether the plugin causing the fallback is really
 something they need, and either contact the plugin author to see if it
 will be updated, or choose to switch to a plugin that does offer block
 editor compatibility.

 I don’t believe this information or decision belongs in 5.0, when nobody
 will be ready.

 When core features are deprecated, they are done silently. See: Links. Why
 advertise out-of-date-but-not-out-of-date plugins against a new feature
 when the old one isn’t even being deprecated.

 Unless it is. If what you’re saying-not-saying is the classic editor is
 being deprecated, then doesn’t this message belong as a notice on the
 entire page, and not in the middle of eveyone’s own registered meta boxes?

 Frankly, this feels like plugin-shaming folks who aren’t onboard with
 Gutenberg yet, and that doesn’t feel right to me. It seems like asking for
 more problems. I think users would be more confused if their Give forms
 suddenly had a Gutenberg UI instead of the same old classic editor they
 are used to.

 Instead, the experience should be to offer some positive incentive for
 users to go through the painful process of tracking down plugin authors,
 and for plugin authors to finally get onboard.

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

More information about the wp-trac mailing list