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.
Filter the ‘comments_open’ check. It happens inside of the function with the same name, and that function is called in a theme usually like this: comments_open() and comment_form( array ( ‘comment_notes_after’ => ” ) ); This is how the filter works: add_filter( ‘comments_open’, ‘wpse_98775_comment_check’, 10, 2 ); function wpse_98775_comment_check( $open, $post_id ) { if ( … Read more
The “Contributor” role has very little access to anything on the back end but can created posts. delete_posts edit_posts read http://codex.wordpress.org/Roles_and_Capabilities#Contributor For comparison, an ordinary “Subscriber” has the last of the three, so “Contributor” has only two extra capabilities. I am not quite sure what “access to specific plugins” means exactly but I am nearly … Read more
Check this plugin. I’ve used it and it’s quite versatile regarding user roles and user capabilities. You can also add conditional statements in your php files, like this: if (!current_user_can(‘some_capability_you_added’)) { echo “You don’t have permission for it!”; return; } You can output that sentence or nothing at all.
I would start by looking into the set_user_role action hook. You would be passed 3 arguments to your callback function – the User ID, the new user role, and an array of the old user roles(that seems strange to me, that you can’t pass an array of roles, but oh well). So here’s an example … Read more
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 );
as s_ha_dum said in the comments you could do something remove_menu_page However, the problem with this is it doesn’t actually prevent the user from editing the plugin if they know the url. From the codex: Removing a menu does not replace the need to filter a user’s permissions as appropriate. When I run into this … Read more
Yes the better solution is to use add_role( $role, $display_name, $capabilities ); and make a distinct role for the front end. That way you have a separation of abilities that is easier to manage, the way you are doing it will lead to trouble.
You have to remove the previous role first, then add the new role like $u = new WP_User( $user_ID); $role_of_user= $u->roles[0]; $u->remove_role($role_of_user); $u->add_role(‘new_role’); If user has more than 1 role then $u = new WP_User( $user_ID); foreach($u->roles as $role){ $u->remove_role($role); } $u->add_role(‘new_role’);
Yes, I use the Members plugin on a few projects where I need to customize or specify certain permissions. Your workflow would be Create a new Role (named something like “Partial Admin” or whatever you’d like to name these people. Add those people to this role (removing them from the Administrator role). Edit the role … Read more