[Vladimir]

Yes, it’s the same solution. I just changed a name of a custom function which returns FALSE in order to it would correspond to the what it really does. There is no bug in a code I offered above. I tested it before to send to you. Both version of code work. You can use anyone. Or even this 3rd version:

add_filter('ure_not_block_other_roles_for_local_admin','my_not_block_other_roles_for_local_admin');

function my_not_block_other_roles_for_local_admin($flag) {

  return false;
}

This custom filter included into Pro version code and will be there. The only thing which I can make for this point in future – add the checkbox to the URE Pro settings. But anyway its value will be sent to an existing filter 'ure_not_block_other_roles_for_local_admin' instead of default TRUE, which is sent currently.

I plan in future to add custom filters for all options of URE Settings in order URE Pro user can configure all URE functionality seting up a .php file as a must use plugin.

[Vladimir]

If you wish to change a default behavior of User Role Editor independently from a theme you can setup this code as a Must Use plugin.
Create a .php file, start it from < sign on the 1st row. Copy/paste a code there. Place that file to wp-content/mu-plugins folder. That’s it.

[Vladimir]

Thanks for all details which helped to reproduce an issue.
Sorry for delay with a solution. I re-tested a similar configuration, got the same result and reviewed my code after that. ‘Other roles access’ add-on restrictions are not applied for single site admins (administrator) role under multisite by default. But it’s possible to change this with a custom filter:

add_filter('ure_not_block_other_roles_for_local_admin','ure_not_block_other_roles_for_local_admin');

function ure_not_block_other_roles_for_local_admin($flag) {

  return false;
}

[Vladimir]

Thank you for details. One more thing to check, just to be sure:

Login as superadmin, go to “Network Admin -> Users” and check if your test user with ‘administrator’ role does not have ‘Superadmin’ privilege granted there.
It could be a reason why ‘Other roles access’ does not work for ‘Site admin (administrator)’ role.

[Vladimir]

Can you show the screeshots what critical role is available to users with ‘administrator’ role, but should not be?
What do you name ‘superadmin’ role?
Did you allow to single site admin access to the network admin like manage_network_options, manage_network_users?

[Vladimir]

WordPress built-in ‘administrator’ role is hidden from any drop-down list for single site administrators (without superadmin privilege) by default.

If you wish to exclude another role(s) from access of user with ‘list_users’, ‘edit_users’ capabilities you can use “Block other roles access” add-on.

[Vladimir]

Hi,

Does such user see an item uploaded by other user in Media Library but just do not have ‘edit’ link? Does such user have ‘edit_others_posts’ capability?

[Vladimir]

I confirm that all the user roles that you created will remain and show up in the pro version with the permissions still intact. You can create then new roles as usual with Pro version. Ads will be removed. When you activate add-on, like “Admin menu access” at “Settings->User Role Editor->Additonal Modules” tab you will see at toolbar a new button (e.g. “Admin Menu”) which belongs to that add-on.

[Vladimir]

Yes – in the both questions.

When I write about URE’s settings I mean only options available at the “Settings->User Role Editor” page.

Changes made to the user roles, or users permissions are not revertible. Any updates to the roles or users permissions you made with URE are permanent and do not depend from URE plugin activation/deactivation, deletion.

[Vladimir]

In case you have a free version of User Role Editor installed:
Pro version includes its own copy of a free version (or the core of a User Role Editor). So you should deactivate free version and can remove it before installing of a Pro version.
The only thing that you should remember is that both versions (free and Pro) use the same place to store their settings data.
So if you delete free version via WordPress Plugins Delete link, plugin will delete automatically its settings data.
You will have to configure User Role Editor Pro Settings again after that.
Right decision in this case is to delete free version folder (user-role-editor) via FTP, not via WordPress.

[Vladimir]

Hi Shweta,

This feature is not supported, but it’s interesting/useful enough to realize in a future.

When someone assign new role to a user via WordPress UI: add new user or edit user profile pages, WP_User::add_role() and WP_User::set_role() methods are used. These methods fire hooks:
– add_user_role;
– set_user_role.

User Role Editor does not fire any custom action when assigns to a user new roles. It uses the same WP_User::add_role() though, so it’s possible to use ‘add_user_role’ hook also.

[Vladimir]

OK. Good that you can find a solution for this problem. Yes, ‘not enough memory’ could be a problem.

[Vladimir]

This bug was fixed with core (free) version 4.35.1 release and Pro version 4.35.2.

[Vladimir]

Thank you for a patience and desire to help in resolving this issue.

I added “Duplicate Post” to the list of active plugins, but still did not get a described error.

We can proceed according to one of these variants:
1) you send me admin credentials for your site, I install backup plugin, create and download a copy of your site to install and work with it at my local development environment. It will be difficult to realize, if your data is too large (>100 Mb).

2) you create a copy of all files except wp-content/uploads folder and copy of database without wp_users, wp_usermeta, wp_posts, wp_postmeta tables and share them with me via DropBox or similar service. This way you will not open access to any critical or “copyrighted” information if you have any.

Of course I guarantee you a non disclosure of any information and use your files and data for the investigation purpose only.

[Vladimir]

Thanks. I confirm a bug. I will fix it.

[Author]

Posts