WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was hoping if someone could help me better understand WordPress' post type support.

remove_post_type_support( 'post', 'author' );

Above in example doesn't seem to actually remove the support, just hide things like (post) meta boxes and (edit) columns more globally compared to this example:

remove_meta_box( 'authordiv', 'post', 'normal' );
// unset( $columns['author'] );

Guessing because of this some modifications will be made to add_post_type_support sooner or later.

For future compatibility, which out of the above would you suggest for simply hiding things? (removing the author post type support could really mess up your site if remove_post_type_support would actually drop the support)

share|improve this question

When you register post type, you can choose what support you need. For Example:

function codex_custom_init() {
    $args = array( 'public' => true, 'label' => 'Books', 'supports' => array( 'title', 'editor' ) );
    register_post_type( 'book', $args );
add_action( 'init', 'codex_custom_init' )

In this way you will create post type Books only with Title Option and Editor

share|improve this answer
Thank you for your quick reply, but this doesn't exactly answers my question, mainly about remove_post_type_support 's exact functionality. – Cor van Noorloos Jan 6 '13 at 13:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.