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

WordPress Trac noreply at wordpress.org
Sat Oct 27 13:38:13 UTC 2018


#45207: Meta-box compatibility warnings
--------------------------------+------------------------------
 Reporter:  johnjamesjacoby     |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Options, Meta APIs  |     Version:  5.0
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:
--------------------------------+------------------------------

Comment (by johnjamesjacoby):

 In the above screenshots, for these plugins, if they ''never'' support a
 block-based editor interface, that would probably be totally OK.

 None of the text in these areas is so complicated, or requires to much
 thoughtful design, to warrant a block-based editor.

 The only way forward is to have the Visual Editor (TinyMCE) and Block
 Editor (Gutenberg) be treated as just another available UI element, like
 meta boxes always have been, and like textareas and inputs and buttons and
 links.

 There is no reason to migrate ''everyone'' in the entire WordPress
 ecosystem away from the original meta box API. Not everything that uses
 TinyMCE needs Blocks. I bet most things don’t. It will be confusing to
 users to force it.

 Also, these warnings will trigger an insane amount of support burden, from
 developers of sites, to developers of plugins.

 It’s one thing to want Blocks someplace they aren’t. It’s another to
 inject HTML into the markup of plugins that will never need Blocks.

 Thinking about this overnight, it is my opinion these warnings need to be
 removed entirely.

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


More information about the wp-trac mailing list