[Vladimir]

Thanks.
It seems some redirects took place before you get the URE’s page and it does not get needed POST parameters, similar to the initial opening.

What will be if you try temporally update the available role ‘subscriber’? Turn on some uncritical capability, like ‘read_private_pages’ and click ‘Update’ button. Will you see the same ‘array()’ output?

[Vladimir]

1) Did you try to change current role to one from the WordPress built-in set, like ‘author’?

2) What plugin do you use for the domain mapping?
At this plugin
https://wordpress.org/plugins/wordpress-mu-domain-mapping/
description I found:

The login page will almost always redirect back to the blog’s original domain for login to ensure the user is logged in on the original network as well as the domain mapped one

So it seems that it’s not the real reason of a problem.

3) Could you add this line

print_r($_POST);

to the begin to of ‘editor()’ function at user-role-editor-pro/includes/class-ure-lib.php, line #252?

So it will be seen as:

public function editor() {

        print_r($_POST);
        
        if (!$this->editor_init0()) {

When plugin works correct you should see this output after role change:
Array ( [action] => role-change [object] => role [user_role] => test_copy [ure_nonce] => c82168f082 )

[Vladimir]

Hi,

Check the browser JavaScript console for the error messages (Shift+Ctrl+J at Google Chrome).

[Vladimir]

I installed both virtue premium and its child you sent to me and added code for the premium theme to the child theme’s functions.php file for testing.

Did you changed role ID at the code for your own one?

[Vladimir]

Hi,

I updated the post for the Virtue Premium, which differs from a free one.

[Vladimir]

This recipe will help you to restrict access to the selected sections of the Virtue them options page:

Hide Virtue theme options page sections

[Vladimir]

You discovered the real bug. Old feature was lost due to use of the hard coded path inside the code. Version 4.21 includes a fix for this bug:
Fix: Removed hard coded folder name (user-role-editor) from the used paths. User Role Editor Pro is hidden now from a user without permissions (administrator or ure_edit_roles), even if a user has access to the ‘activate_plugins’ capability.

You may restrict plugins available for the activation/deactivation at the user level:

Could you please test plugins access related part with the development version 4.21.b7?
It’s available after login from the Downloads page.

I look at the free version of the theme to understand if it’s possible to change something with access to the tabs at its options page.

[Vladimir]

Hi Francis,

I’m looking on the described issues currently. I will answer you today definitely.

[Vladimir]

Hello,

There are some rare issues when a client discovers specific product incompatible with User Role Editor Pro. I hope it’s not your case.
Could you give more details about to what plugin do you wish to provide access? May be a hint, which follows below, will be helpful.

How can I give access only to some plugins and not to the rest?

If plugin provides its own user capabilities use theme 1st. If plugin does not provide its own permissions or there is not enough them, use “Admin menu access” add-on with ‘Block not selected’ option:
https://www.role-editor.com/block-admin-menu-items

What theme do you use? What do you try to block/hide? If it’s a commercial product, could you send its copy to [email protected] for the research?

[Vladimir]

If you used “Content view restrictions” add-on – it is for the front-end only.

If you wish that a user have ‘read only’ access to the list of posts or pages at the back-end, give him ‘edit_posts’ capability, but do not give ‘create_posts’ capability (it should be activated at the URE’s Settings ‘Additional modules’ tab. This way a user will see only ‘View’ link under the posts created by other authors and can not create any post himself.

[Vladimir]

– Check if valid role was really assigned to the user. Try to assign to him some other role, then needed role back again. Sometimes it helps.
– Check related theme’s settings, compare them with those were set at dev. environment.

[Vladimir]

Is it possible that your theme setup the different menus for the different roles?
Try to test admin menu access with the WordPress default 2015 theme.

[Vladimir]

Yes, use ‘Admin menu access’ add-on for this purpose:
https://www.role-editor.com/block-admin-menu-items

[Vladimir]

OK. I see now that admin menus are really different and user can edit posts but does not see ‘Posts’ menu.

Are you sure that all WordPress customizing plugins are disabled at your site when you get this picture?

[Vladimir]

Thanks.
1st, to be sure that there is no other code preventing needed access, could you deactivate all plugins?
2nd, what menu item is unavailable for other (non-admin) user?

[Author]

Posts