Please leave as plugin: Do NOT add to core

  • Please leave this as a plugin. Do NOT add to core.

    Don’t force millions of collective work hours on WP developers by removing core features like Meta Boxes, Custom Fields, etc. A content builder is NOT worth the massive effort that would be required by thousands of developers to refactor and rewrite their code.

    If users want Gutenberg, they can add it anytime as a plugin. Let the user decide IF they want this sort of functionality. And if they do, let them also decide which plugin is best. Forcing these important decisions on millions of users is a HUGE mistake, and is the wrong direction for WordPress.

    Leave Gutenberg as a PLUGIN !

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    First, thanks for leaving a review. Secondly, you will be pleased to know that metaboxes are coming in the new version of Gutenberg (within a few days). That said, as you point out the product is in early stages still. Each feedback matters and sees iteration.

    It’s a fine line between innovation and having to have people adjust existing code. The balance though is being found in many areas within Gutenberg. This is just the kind of thing that will be iterated on as feedback happens with more testing.

    Thread Starter Jeff Starr

    (@specialk)

    There should be no reason that you need to remove metaboxes, custom fields, or the plain text editor just to add a content builder. All of the other amazing content-building plugins have managed to do it, so maybe take a look at what they are doing and follow suit in that regard.

    To sum up my thoughts about adding Gutenberg to WP core, here are the four golden rules:

    • Don’t remove the plain-text editor
    • Don’t remove metaboxes
    • Don’t remove custom fields
    • Make Gutenberg optional

    If/when these four things happen, I will be happy to change my rating to 5-star all the way, and even support Gutenberg thru my various channels.

    Plugin Author Tammie Lister

    (@karmatosed)

    You’ll be pleased to hear we are not removing metaboxes or the plain text editor itself. Metaboxes are being shipped in the latest version as I said and also there is the classic text block for the editor.

    There will also be an option to turn off Gutenberg, this is going to be implemented soon through a MVP of a plugin.

    Thread Starter Jeff Starr

    (@specialk)

    That sounds encouraging. Thank you for the information. So I assume that Custom Fields also will be left intact, as they are a part of metaboxes, correct?

    Plugin Author Tammie Lister

    (@karmatosed)

    At this point you need to have your custom fields REST enabled but yes they will work if you have that.

    Thread Starter Jeff Starr

    (@specialk)

    What does that mean specifically?

    Would be super useful to know if any changes will need to be made to literally thousands of plugins that use Custom Fields.

    …you need to have your custom fields REST enabled…

    So are Custom Fields “REST enabled” by default (like when using add_post_meta(), get_post_meta(), et al)? Or will Gutenberg require changes in order to work properly?

    Thanks for your help, btw.

    Thread Starter Jeff Starr

    (@specialk)

    Any help on this? I’m about to post at DigWP.com.. would be great to understand what’s going on with your plugin.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Please leave as plugin: Do NOT add to core’ is closed to new replies.