WordPress: Disable “Add New” on Custom Post Type

5 Views

Is there any way to disable the option of adding a new post under a Custom Post Type in WordPress (3.0)? I’ve looked into labels and arguments but can’t find anything that would resemble such a feature.

Post Views: 5

Related posts

Leave a Reply

9 comments

  1. There is a meta capability create_posts that is documented here and is used by WordPress to check before inserting the various ‘Add New’ buttons and links. In your custom post type declaration, add capabilities (not to be confused with cap) and then set it to false as below.

    register_post_type( 'custom_post_type_name', array(
  'capability_type' => 'post',
  'capabilities' => array(
    'create_posts' => false, // Removes support for the "Add New" function ( use 'do_not_allow' instead of false for multisite set ups )
  ),
  'map_meta_cap' => true, // Set to `false`, if users are not allowed to edit/delete existing posts
));

    You’ll probably want to set map_meta_cap to true as well. Without it, you won’t be able to access the posts’ editing pages anymore.

  2. The combinations of the solutions above work in hiding the links (although someone could quite easily type the URL in directly.

    The solution mentioned @3pepe3 relies on get_post_type() which will only work if there is already a post in the listing. If there are no posts, the function will not return anything, and the “Add New” link will be available. An alternative method:

    function disable_new_posts() {
    // Hide sidebar link
    global $submenu;
    unset($submenu['edit.php?post_type=CUSTOM_POST_TYPE'][10]);

    // Hide link on listing page
    if (isset($_GET['post_type']) && $_GET['post_type'] == 'CUSTOM_POST_TYPE') {
        echo '<style type="text/css">
        #favorite-actions, .add-new-h2, .tablenav { display:none; }
        </style>';
    }
}
add_action('admin_menu', 'disable_new_posts');

    EDIT: To prevent direct access if someone types the URL in themselves: https://wordpress.stackexchange.com/a/58292/6003

  3. WordPress Networks: I found that Seamus Leahy’s answer doesn’t work if you are logged in as a super admin of the network, it doesn’t matter if the user doesn’t have the capability, mapped or otherwise, when current_user_can($cap) is called by the CMS. By digging into the core I found you can do the following.

    register_post_type( 'custom_post_type_name', array(
  'capability_type' => 'post',
  'capabilities' => array(
    'create_posts' => 'do_not_allow', // Removes support for the "Add New" function, including Super Admin's
  ),
  'map_meta_cap' => true, // Set to false, if users are not allowed to edit/delete existing posts
));

    The accepted answer hides the menu item, but the page is still accessible.

  4. In wordpress and for all the post types there is the capability create_posts. This capability is used in several core files :

    1. wp-adminedit-form-advanced.php
    2. wp-adminedit.php
    3. wp-adminincludespost.php
    4. wp-adminmenu.php
    5. wp-adminpost-new.php
    6. wp-adminpress-this.php
    7. wp-includesadmin-bar.php
    8. wp-includesclass-wp-xmlrpc-server.php
    9. wp-includespost.php

    So if you really want to disable this feautere you must do it per role and per post type.
    I use the great plugin “User Role Editor” to manage the capabilities per role.

    But what about the capability create_posts? Well this capability is not mapped and also create_posts is equal to create_posts so we should fix this and map the capability per post type.

    So you can add this piece of code in your functions.php and the you can manage this capability. 

    function fix_capability_create(){
    $post_types = get_post_types( array(),'objects' );
    foreach ( $post_types as $post_type ) {
        $cap = "create_".$post_type->name;
        $post_type->cap->create_posts = $cap;
        map_meta_cap( $cap, 1); 
    }
}
add_action( 'init', 'fix_capability_create',100);

    So here we are not hiding or removing menu elements… here we are removing the capability for users (including xmlrpc requests).

    The action was init and not admin_init or anything else because init at priority 100 prevents the display of “add new” on admin bar, sidebar, etc (in all the wp interface).

  5. Disable creating new post for registered post-types: (example for post and page)

    function disable_create_newpost() {
    global $wp_post_types;
    $wp_post_types['post']->cap->create_posts = 'do_not_allow';
    //$wp_post_types['page']->cap->create_posts = 'do_not_allow';
    //$wp_post_types['my-post-type']->cap->create_posts = 'do_not_allow';
}
add_action('init','disable_create_newpost');

  6. add_action("load-post-new.php", 'block_post');

function block_post()
{
    if($_GET["post_type"] == "custom_type") 
        wp_redirect("edit.php?post_type=custom_type");
}

  7. @ Staffan Estberg,

    This is best way to hide the Add New or Create New button in custom postypes

    'capability_type'    => 'post',

        'capabilities'       => array( 'create_posts' => false ),       

        'map_meta_cap'       => true,

    It disable to create new post in custom post types both side in admin menu and above the list of post type.

  8. I found this simplest way for this. Just ad this code into theme’s function.php.

    function hd_add_buttons() {
    global $pagenow;
    if (is_admin()) {
        if ($_GET['post_type'] == 'custom_post_type_name') {
            echo '<style>.add-new-h2{display: none !important;}</style>';
        }
    }
}
add_action('admin_head', 'hd_add_buttons');

  9. As the question is ‘how to disable add-new button on custom post type’, and not ‘how to restrict user editing custom post types’, in my opinion the answer should be purely hiding the buttons with css, by adding this to the functions.php file :

    add_action( 'admin_head', function(){
    ob_start(); ?>
    <style>
        #wp-admin-bar-new-content{
            display: none;
        }
        a.page-title-action{
            display: none !important;
        }
        #menu-posts-MY-CUSTOM-POST-TYPE > ul > li:nth-child(3) > a{
            display:none;
        }
    </style>
<?php ob_end_flush();
});