[Plugin: Verve Meta Boxes] Requiring custom-fields "support" is inconvenient

I will probably automatically hide the custom post meta box on any post type that uses verve post meta. Coming soon to an upgrade near you! ??

You can easily hide the Custom Fields meta box using a plugin such as Adminimize.

Yeah, having Verve hide the default Custom Fields UI itself is just a convenience issue. Maybe also a slight performance benefit (to reduce memory usage) if that’s all you would have used Adminimize for.

// you can remove metaboxes of a especified post type

function my_remove_meta_boxes() {

remove_meta_box(‘postcustom’, ‘slide’, ‘normal’);

}

add_action( ‘admin_menu’, ‘my_remove_meta_boxes’ );

I agree KevinB, i don’t want the client to see the custom fields box and as a developer I can′t spend time enabling support for custom-fields, then create the meta boxes and finally remove support for custom-fields, so here’s what i do to solve this “issue”:

Edit the meta_boxes.php file so that custom post types show up in the context list:

if(function_exists('post_type_supports')){
    $post_types = get_post_types();
    //edit:
    $excluded_post_types = array('attachment', 'revision', 'nav_menu_item');
    // edit end;
    foreach($post_types as $key => $value){
	// edit:
	if (in_array($value, $excluded_post_types)) {
	    unset($post_types[$key]);
	}
	// edit end;

	// original code:
	/*if ( !post_type_supports($value, 'custom-fields') ){
	    unset($post_types[$key]);
	}*/
    }
}else{
    $post_types = array('post','page');
}

That is all there is to it, nothing gets broken and we developers can select our custom post types in the “context” list without enabling “custom-fields” for them (enabling custom-fields for a custom post type simply shows the user the custom-fields box on the write/edit admin panel but does not have any other consequences so this hack is safe, nothing will break). If I’m wrong correct me of course.