[Vladimir]

Hi,

“Content view restrictions” should do nothing with “topics” and “answers” until you apparently set them for them. Please re-check your settings for role and for the topics/answers, which are not available.
Does members see private forums if you deactivate “content view restrictions” add-on. As I remember ‘participant” role does not allow to read private forums by default. For example I had to add to it:
– read_private_forums;
– read_private_topics;
– read_private_replies;
– read_hidden_forums.

[Vladimir]

Go to the “Users->User Role Editor”. Select the role of your user. Click ‘Admin Menu” button and turn ON menu items which you wish to hide from this role.

[Vladimir]

Hi Luis,

You may block unneeded menu items, which protected by the necessary (you can not revoke them from the role) capabilities like ‘edit_posts’ using “Admin Menu Access” add-on:
https://www.role-editor.com/block-admin-menu-items
These restrictions are applied to the user role, not to the user.

[Vladimir]

I think some clarification is needed. “Edit restrictions” does not give/grunt to a user any additional capabilities. It does not depend from the model you select: ‘Allow’ or ‘Prohibit’. User should have posts edit capabilities already.
When you add ‘edit restrictions’ for user, User Role Editor make a less subset of posts available for edit for this user.

Bulk action “Edit Access” from the posts list has a purpose to automate the ‘edit access restrictions’ setup on the user level. You can modify this settings directly opening selected user profile.
So you should input IDs list of users, for which you wish to modify posts edit restrictions. If you do not input users ID list, and suppose that script will update data for all users, it’s a wrong assumption.
Some sites has tens of thousands users – update meta data for every user at such site is not the task which can be fulfilled within the limited time of 1 client-server update request.

For example, users 5,7,9 has role ‘editor’ and can edit all posts. After you set for them ‘Allow’ to edit posts with ID 4, 6, 8 those users will see and can edit just those 3 posts.
If you wish to remove such restriction and allow them to edit all posts back, you may do it opening those users profiles one by one and removing post IDs from ‘edit restrictions’ section.
Other way is to use bulk action ‘Edit Access’ at the posts page, select replace existing data, left posts list empty, input user IDs list (5, 7, 9). As the result post IDs will be removed from those users meta data and edit restrictions stop work for them.

If you wish to set/remove edit restrictions globally it’s more convenient to work with them at the role level – ‘Posts Edit’ button at the User Role Editor page.

[Vladimir]

Thanks for the information.

[Vladimir]

Hi,

Download URL was built incorrectly after I have modified update server yesterday. WordPress may take it from the internal cache (transients). So about 24 hours may take place before it will request a fresh (valid) value from role-editor.com.
You may wait until tomorrow or try to clear cached values from the database – these records:

SELECT * FROM wp_options where option_name like '%update_plugins%';
SELECT * FROM wp_options where option_name like '%external_updates-user-role-editor%';

[Vladimir]

Hi,

Assign to your users a ‘contributor’ role.

[Vladimir]

Thanks for this information. I fixed mistake in the updates server script. Please try to update again.

[Vladimir]

WooImporter uses ‘manage_options’ capability to protect its menu items. Try this variant:
1) add ‘manage_options’ to your VA role and
2) use Admin Menu Access add-on to block for that role “Settings” menu and any other menus which also are protected by the “manage_options” capability.

[Vladimir]

I need a WooImporter plugin copy to look to its code. Sometimes developers allows to replace needed capability for plugin menu on the fly. You may send a .zip or a link to it to support [at-sign] role-editor.com

[Vladimir]

Add “edit_theme_options” capability to the “editor” role:
1) Open “Users->User Role Editor”, select “Editor” role.
2) Turn ON checkbox for the “edit_theme_options” capability, click “Update”.

After that user with “Editor” role will receive access to the full “Appearance” menu, as all its submenu items are protected by the same “edit_theme_options” capability.
If you wish to allow to the ‘editor’ role to work just with “Menu” and “Widgets” items of the “Appearance” menu, you need to block other items with “Admin Menu Access” add-on.

[Vladimir]

I will publish stable Pro version 4.28.2 tomorrow.

[Vladimir]

Currently I can not recommend another workaround then that you use already.
But it’s a good point to extend User Role Editor Pro functionality. I will think on it. May be something similar to the “force custom taxonomies to use own capabilities” option will be possible to add. I will post here as I will find a decision.

[Vladimir]

Hi,

Try this recipe:

add_action('admin_init', 'remove_product_editor');
function remove_product_editor() {

  if (current_user_can('product-meta-editor')) {
    remove_post_type_support('product', 'editor');
  }
  
}

Replace role ID ‘product-meta-editor’ with your own as ‘sales-manager’. Add this code to the active theme functions.php file or setup it as a must use plugin.

[Vladimir]

Hi Urs,

Thanks for your help in finding this.
“Admin menu access” add-on works with this rule: if something is not directly allowed – it’s prohibited. I extended the list of allowed arguments for the ‘edit.php’ command to fix the issues your noted. Try development version 4.28.2.b8. It’s available after login from the download page as always.

[Author]

Posts