[Vladimir]

I confirm a problem with add-ons data replication from the main site to the new created one. They were not replicated as automatic replication of add-ons data is switched off by default. You need to set custom filter in order to tell to URE what add-ons data to replicate. Filter is: ure_addons_to_copy_for_new_blog.
In order to replicate “Plugins access” add-on data this line is needed additionally:

$addons['plugins']->copy = true;

2nd possible issue: Current version of URE uses ‘wpmu_new_blog’ action to execute own function for roles data replication. Starting from WordPress 5.1 this action was deprecated and process of new site creation was rewritten.
I developed the fix. It’s currently available as the beta version 4.50.4.b1.

[Vladimir]

Hi,

Does, such user has a single role assigned? If you grants multiple roles to such user, is role with restrictions for plugins granted as primary one?

What plugin adds ‘Clone’ button for your pages? Does superadmin still sees “Clone” button?

[Vladimir]

You can restrict editing with Edit restrictions add-on.
Look what’s more suitable in your case:
– turn ON “Own data only” option. User will see and can edit just his own posts, where he is an author.
– use categories as the team list and restrict access to the post by unique category ID for every coach. Such restriction will allow to a coach to post just to that specific category and see at the backend just the posts inside that category.

[Vladimir]

Thanks for this report. I will re-test the code, which replicates add-ons data from the main site to the new registered site with roles together.

[Vladimir]

Got a role file from you. Role includes “ure_manage_options” capability. User Role Editor counts a user who has such capability a superadmin and does not apply to him any restrictions. Having this capability user can go to the “Settings->User Role Editor” and switch off “Admin menu access” add-on. What’s the sense to restrict such user some how via URE?

[Vladimir]

Hi,

Did you block any admin menu item for this role with “Admin menu access” add-on?
If Yes, pay attention on the tech. details part of the article.

[Vladimir]

Lukas,

I meant that I need to know role ID and the list of capabilities granted to it.
You can export it and send file to support [at-sign] role-editor.com in order do not spend time on screenshots.

[Vladimir]

Hi Lukas,

Clarify, for what role do you try to block other roles?

[Vladimir]

Hi,

My test showed that “Widget show access” part works as expected. Can you re-check you selection for mentioned widgets?
If you need further help, I’m ready to look at the issue on-line, just send site URL and admin credentials to support [at-sign] role-editor.com

[Vladimir]

Hi,
It’s possible to use [user_role_editor] shortcode in order to hide part of post/page from users with certain role on not logged-in users.

[Vladimir]

Done. You make take a new license key from your account page.

[Vladimir]

Changing license key for the account will require to replace it at all projects where it was used. I may do this by your request.

You can go to the “Settings->User Role Editor->General” and input any chars sequence to replace the actual license key. Project which you handover will not use your license key after that.

[Vladimir]

More correct to say:
“role with ‘manage_options’ capability granted will get access to any admin menu item protected by ‘manage_options’ capability. Be careful, as ‘manage_options’ allows access to some critical menu items like “Settings”.

[Vladimir]

You can go to “Users->User Role Editor”, select “editor” role and turn ON the “manage_options” checkbox for it. Yes, editor role will get access to the many menu items, including “Settings”. But you can block other menu items with “Admin menu access” add-on.

Yes, I meant that you can share .zip of TG plugin source code with me via DropBox or similar service. I use such code for the investigation purpose and install locally only.

[Vladimir]

Hi,

Share this TG plugin copy with support [at-sign] role-editor.com
I will look at its code to answer you, what is possible to do.

2nd, alternative way, is to grant ‘manage_options’ to editor role, but use Admin menu access add-on to block admin menu items (like ‘Settings’, etc.), which are not needed to ‘editor’ role.

[Author]

Posts