Custom Fields
Support MB Custom Post Type Empty 'supports' gives unexpected results

  • Creator
  • #27245
    Resolved Adam M

    There's a place where I think the interplay between MetaBox and WordPress behaves counter-intuitively.

    When unchecking all features under 'Supports', like this:

    I expect no built-in fields to appear on the form.

    However, WordPress interprets this as "default to showing a title and editor field".

    But MetaBox knows that this wasn't the users intent. So, instead of issuing an output of

    'supports' => [],

    wouldn't it make more sense for MetaBox to output

    'supports' => false,

    which will indeed cause the expected result: don't display native fields?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Author
  • #27259
    Long Nguyen


    Thanks for your feedback.

    Yes, the default support of a CPT is title and editor. I will inform the development team to improve this case.


    Hi, I have the same problem.

    I want to create a CPT with pure metabox fields - no WP gutenburg nonsense.
    I want the Title value to be constructed from the contents of some other fields in the CPT - hence want the Title filed to appear at the bottom of the CPT.

    So I also expected unticking the Title in the Supports tab to remove the Gutenburg stuff.
    The other issue is that I can't see a field to replace the Title in the Metabox fields. ( Unlike Taxonomy which is there and works fine )


    Long Nguyen


    Please update MB Custom Post Type to the new version 2.1.1 to resolve this issue.


    MAny thanks. Waiting for the update to drop. 🙂


    Hi, Excuse my ignorance ... but how do I upgrade the CPT module?

    I have not seen an update at the WordPress level for the Metabox plugin.
    I can not see what the current version of any of the extensions is, so how to tell if it is upgraded?

    The free download still shows the 1.9.1 version so I can't upgrade manually.

    What am I missing here?


    Long Nguyen

    Hi Alan,

    You can download the plugin on and re-install it


    Ah many thanks, that works.
    I was using which is still showing the old version.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.