[Vladimir]

To what post type post with ID=1601 really belongs: post, page or custom post type (CPT)? You need to know this to be clear what capabilities are in use for item with ID=1601: posts, pages or special for that CPT.

User should be capable to edit this CPT item before you apply edit restrictions with URE. So if item ID=1601 was created by other author, user should have ‘edit_others_pages’ for pages, ‘edit_others_posts’ for posts or CPT which uses the same capabilities as posts do, or ‘edit_others_cptname’ for that CPT, e.g. ‘edit_others_videos’ for videos CPT.

You may look at ‘Admin Menu’ at this CPT menu for administrator role to be sure what capabilities CPT uses.

“Look at Roles” is related to the “What to do” (restriction type) field only: prohibit or allow or look 1st not empty value from roles assigned to this user.

So if you need to add a special restriction just for this user make it at this user profile without reference to the roles, assigned to this user.

You may set edit restrictions at the role level and use them for the group of users.

[Vladimir]

Thanks for the additional information. I reproduced a problem. I will develop a fix.

[Vladimir]

Did you set ‘block not selected’ restrictions with ‘Admin menu access’ module for this role?
Could you show a screenshot?

[Vladimir]

You have to understand what plugin removes ‘Logout’ menu. Did you set “Admin menu” restrictions for that role? What will be with ‘Logout’ if you deactivate URE’s “Admin menu” add-on?

If URE is not a source of a problem, try to deactivate plugins one by one to isolate it.

[Vladimir]

Is top menu bar available for such user at the back-end?

[Vladimir]

Hi,

Thanks again. The issue was confirmed and fixed.
bbPress requires to add additional capabilities to the “Participant” role in order user with this role may see the private topics and replies.

[Vladimir]

Thanks for your help with testing.

Yes, It’s safe to use at the live site. I applied just the only change to it – allowed the sorting parameters for posts list page.
I will publish 4.26.1 as a stable one in a couple of days, just in case some other quick bug will be discovered in version 4.26.

[Vladimir]

Hi Rick,

Thanks for your help. I confirm this bug. It occurs when you restrict role with “Admin Menu” and use “block not selected” model.
I made available a fix with development version 4.26.1.b1. You may get it after login from the download page.

I wait a result of your test.

[Vladimir]

Thanks for the information. Good that this issue was resolved finally.

[Vladimir]

Hi,

Thanks for your help. I added a “Logout” link to the “Account” page.

Forums are managed by bbPress here. “Private” means that topic is not available for not logged-in users and, that is, for the search engines. Any logged-in user may read such topic of course.

I tested – site returns 404 error for the private topic if you did not login.

[Vladimir]

Hi,

In short, WooCommerce redirects to front-end any user without edit_posts capability.
This post will give more details on the problem and workaround for it:

WooCommerce admin bar and dashboard access

[Vladimir]

Hi Jawad,

It’s a bug of that plugin, which shows its empty menu to any user without ‘manage_options’ capability. Until it’s not fixed by developer you may remove this menu item for all users without ‘manage_options’ capability by adding this code into the active theme functions.php file or setup it as a must use plugin:

add_action('admin_menu', 'yit_menu_fix', 100);

function yit_menu_fix() {
  
  if (!current_user_can('manage_options')) {
    remove_menu_page('yit_plugin_panel');
  }
  
}

[Vladimir]

Yes. I work on it.

[Vladimir]

Hi Jawad,

‘Yith Plugins’ menu is protected by ‘manage_options’ capability. This menu is not shown in ‘Admin menu’ dialog in case a role does not have ‘manage_options’ capability.

[Vladimir]

Yes, you are right. I supposed that you have active WPML plugin, when found a ‘lang’ parameter in URL.

[Author]

Posts