[Vladimir]

Hi,

Thanks for this report. I confirm the bug. I will post here as the fix will be ready for testing.

[Vladimir]

Hi,

Do you use “Admin menu access” add-on to restrict this role and user? If Yes, then I suppose that you use “Block: Not Selected” model. Read carefully the “Block Not Selected” part of the article.
If you selected “Forms->Entries” menu item, it has /wp-admin/admin.php?page=gf_entries link, with the single argument/parameter ‘page’, but when you click ‘View’, URL has at least 9 new parameters /wp-admin/admin.php?page=gf_entries&view=entry&id=8&lid=18&order=ASC&filter=&paged=1&pos=0&field_id=&operator=) and URE blocks it redirecting user to the 1st allowed URL – dashboard. Add those parameters to ‘White List‘ for this menu item/URL.

[Vladimir]

Confirm that required capabilities (create_pages, edit_pages, publish_pages, edit_published_pages) are still granted to this user. If Yes, try to deactivate all plugins. If it will return ability to work with pages, activate plugins back one by one to isolate a reason.

[Vladimir]

Thanks for the additional information. I can not repeat the issue with similar settings.

FYI, I rewrote some part of edit restrictions add-on to fix the discovered issue with cache. Just in case it would be involved you can test the 4.59.2.b1. It’s available after login from the “Download” page.

If that will not help and if this applicable, you can send to my email the site URL and admin credentials. I will make a copy of your files (themes, plugins) and data and test them locally with debugger to catch what is going wrong.

[Vladimir]

Hi,

I fixed the linked article. Code is available now. Just replace ‘post’ with your custom post type slug.

Yes, you can place it to functions.php file.

[Vladimir]

Try to block unneeded admin menu items using “Admin menu blocking” add-on.

Btw., I work on add custom taxonomies to the code executed for the URE’s option
“Force custom post types to use their own capabilities”. This will replace ‘edit_posts’ for such taxonomies with ‘assign__terms’ capability. So you will not need to add ‘edit_posts’ for custom post types. I plan to add this to the next udpate.

[Vladimir]

Your reply have waited moderation due to the 2 link included. Thanks for the notification about this.

I see that individual capabilities don’t work for your taxonomies. What about to try ‘edit_posts’ and if it will not help, ‘manage_categories’?

[Vladimir]

Hi,

1st, look for the assign__terms user capability. If you don’t see it and it does not work if you try manually add it, then I can suppose that custom taxonomy is defined with default capability type. Try to add to a role ‘edit_posts’ and/or ‘manage_categories’ capability.

[Vladimir]

Hi,

Thanks for this note. I repeated and confirm this issue with hiding meta boxes in Gutenberg. I will inform you as prepare a fix.

[Vladimir]

Hi,

Is user restricted with ‘edit post/page restrictions‘ add-on?
If Yes, show(via external URL) or send to email the screenshot with edit restrictions settings for this user and/or his role.

[Vladimir]

Learndash->Overview is protected by ‘manage_options’ capability. So you 1st, grant to a role ‘manage_options’ capability. Then open for this role the ‘Admin menu’ and block menu items, which use the same ‘manage_options’ (like “Settings”, but are not needed for your role/user.

[Vladimir]

“URL Parameters White List…” allows to inform URE about URL parameters which you allow to use for not blocked links/menu items. It’s useful when you use “Block not selected” model blocking access to admin menu items.

[Vladimir]

Hi,

Beta version 4.59.2.b1 contains the required fix. It’s available after login from the same Download page, where you take a stable version.

Could you please test it and share the results?

[Vladimir]

E.g. mentioned by you “Learndash->Reports, and Learndash->Settings” menu items, which also are protected by ‘manage_options’ capability. So you 1st, grant to a role ‘manage_options’ capability. Then open for it ‘Admin menu’ and block menu items, which use the same ‘manage_options’, but are not needed for your role/user.

[Vladimir]

1st, “Activate per plugin user access management for plugins activation” add-on has another purpose. It’s designed when you prepare the site for a client, installed and activated some plugins and do not wish that client see them and can deactivate, but at the same time you wish to allow for client to activate/deactivate some other pre-installed plugins. It’s all not about access to the some specific items at the admin menu.

2nd, you have “Admin menu access” add-on. Which you can use:
1) to get information about what capability protects what admin menu item. Just open “Admin menu” for the ‘Administrator’ role, which has access to the all admin menu items by default.
2) In case you can not block/hide unneeded menu items revoking related user capability from user role, like ‘manage_options’ for example, you can block the “Settings” menu item here, but user still will have access to the menu, which is also protected by ‘manage_options’.

It’s possible to include screenshots here if use external links. Be aware that message which contains > 2 links, automatically gets ‘pending for moderation’ status. (If I missed and did not approved it, it’s better to send the remind).

[Author]

Posts