- This topic has 7 replies, 3 voices, and was last updated 3 years, 8 months ago by
.
Viewing 8 posts - 1 through 8 (of 8 total)
-
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 8 posts - 1 through 8 (of 8 total)
- You must be logged in to reply to this topic.