Vladimir Garagulya

Capabilities granted through the role are shown at the User’s capabilities page as disabled by design. You can not revoke them at the user level.
If you need user with the less permissions you have to grant him another role, not ‘administrator’ one.

If some plugin uses ‘administrator’ role directly, it should not. It should use user capability, not a role when define its admin menu.
WordPress built-in current_user_can() function is made for work with capabilities, not the roles.

Hi Eva,

‘edit_theme_options’ capability protects all items under ‘Appearance’ menu, including the ‘Menus’ one.

Hi,

Not registered user can not have any user capability by definition. It’s better to ask support from the ‘Listing plugin’ developer.

Hi,

These db tables belong to “TI WooCommerce Wishlist” plugin. If you don’t use this plugin no more, then you can be sure to delete them from the database.

• This reply was modified 5 years, 10 months ago by Vladimir Garagulya.

Hi,

At Word Balloon plugin Settings page I see the option:
“Permissions of user required to use Word Balloon when posting” with the dropdown list of WordPress built-in roles:
‘administrator’, ‘editor’, ‘author’, ‘contributor’.
This is a reason, why user with other role, who can add new posts can not use Word Balloon – no permissions. Word Balloon does not support custom roles. More, it does not support multiple roles.
Currently it realizes this logic – replaces role ID saved at the plugin settings page with user capability this way:

function word_balloon_capability($capability){
	if('administrator' === $capability ){
		return 'manage_options';
	}elseif('editor' === $capability ){
		return 'moderate_comments';
	}elseif('author' === $capability ){
		return 'edit_published_posts';
	}elseif('contributor' === $capability ){
		return 'edit_posts';
	}

	return 'manage_options';
}

Ask Word Balloon plugin developer to replace user roles in the dropdown list directly with corresponded capabilities. This solution will be more universal and work for those who use custom user roles.

@zenixnet:

The issue was related to the plugin with a lot (thousands) of files. Server generated the timeout error when PGC went through that plugin in a queue.

So I helped @playbasfa to isolate that plugin and add it to the skip-list as a workaround. You may contact me directly if you need a similar help.

Hi,

‘edit_posts’ is the base permission. It protects menu ‘Posts’, allows to see the posts lists and edit own not published posts. All the rest ‘edit_’ permissions for posts are additional levels of control.
If you can edit_posts but post is published, WP will check if you can ‘edit_published_posts’.
If you can edit_posts but post was created by other user, WP will check if you can ‘edit_others_posts’.
If you can edit_posts but post is private, WP will check if you can ‘edit_private_posts’.

The most of times custom post type are defined with the default capability type ‘post’, and thus WP checks for all such CPT the same list of permissions as for WP built-in posts: edit_posts, edit_others_posts, etc. Read more about permissions for custom post types here.