Okay, so the code above does work, but not for super admins, you must explicitly remove permissions from super admins, like this: // restrict super admin capabilites add_filter(‘map_meta_cap’, ‘restrict_super_admins’, 10, 4); function restrict_super_admins($caps, $cap, $user_id, $args){ $super = array( ‘add_users’, ‘create_users’, ); if( in_array($cap, $super) ) { $caps[] = ‘do_not_allow’; } return $caps; }
These are actually two questions. The second question – how to add categories to attachments – is already answered. How to restrict uploading attachment to a specific role? The capability to do that is named upload_files in WordPress. Some roles have this capability by default: authors, editors, administrators. I would restrict it to editors and … Read more
According to register_post_type() documentation capability_type argument is used to construct capabilities. I think since you are customizing it for the post type, its capabilities requirements won’t be formed like read_post but like read_an_group.
You should use WP_User class (http://codex.wordpress.org/Class_Reference/WP_User) It has methods: set_role, add_role, remove_role. Example: $uid = wp_insert_user($userdata); $u = new WP_User( $uid ); add_role( $role, $display_name, $capabilities ); // I assume $role, $display_name, $caps are already set before $u->set_role( $role );
‘capability_type’ is an argument that must be a valid post type. So, or you use one of default post types (post, page) or once you have defined your own capabilities array you have to use your own post type. So, using: …. ‘capability_type’ => ‘career’ …. your code should work. However, once you defined all … Read more
In WordPress is pretty simple create custom roles and also assign specific capabilities to specific user roles (no matter if from core or custom). In my plugins I often create an user role that has all the capabilities required by my plugin, and then I attach some of thos capabilities to existing roles. I’ll give … Read more
The capability is delete_post, you can see it in source here.
If you want to specifically deny a capability from a user (not a role), you need to use the add_cap() method and specify that the $grant parameter is false. $user = new WP_User( ‘Y’ ); $user->add_cap( ‘edit_plugins’, false );
This line in your wpo_add_caps() function is incorrect: $admin->add_cap( ‘administrator’, $admin_cap ); It should simply read: $admin->add_cap( $admin_cap ); Source: WP_Role::add_cap().
I find the solution, that’s a WordPress 4 year’s bug. Here is the Summary from DrewAPicture changed from manually created user roles not showing in author dropdown irregardless of assigned capabilities to Manually created user roles not showing in author dropdown regardless of assigned capabilities Please see ticket 16841 for more details. The only simple … Read more