[Vladimir]

Hi Jakub,

You can develop locally with User Role Editor Pro. Just do not input/activate a license key there. URE Pro will provide a full functionality except the automatic update via WordPress.

[Vladimir]

Yes, it’s possible:

SELECT user_login, user_email, user_registered FROM wp_users

[Vladimir]

Hi,

User Role Editor exports just a user roles with capabilities. It’s a serialized PHP array additionally encoded.

You can use PhpMyAdmin to export needed data. Use this command at SQL tab:

SELECT user_login, user_email FROM wp_users

replace ‘wp_’ with your own database prefix, if needed.
Then click ‘Export’. Select an option “CSV for MS Excel” and that’s it. You will get a file with data formatted this way:

"user1";"[email protected]"
"user2";"[email protected]"

[Vladimir]

Editor is a power user. He can edit any attribute of a published post. It means that he can change its status (as you mentioned), he can change its permalink, he can just remove/replace full content of the post.
So 1st, I would think about stronger selecting of and more trust to so powerful users.

There is no built in functionality in WordPress to filter posts statuses list or prevent post status change at the post edit page. If user can publish post he can change its status to one of hard coded at wp-admin/includes/meta-boxes.php, function post_submit_meta_box().

It’s possible to write some code which will make any unpublished post back to the ‘published’ state. But I think that you will not wish to remove from editor this ability in case if he publish some post by mistake and wish return it back to a ‘draft’ or ‘pending’ status.

An example of changing post status after post saving is available here. You can use it as a starting point.

[Vladimir]

Hi,
Revoke from an editor’s role just a ‘delete_publish_posts’, but still grant to it the rest:
‘delete_posts’, ‘delete_others_posts’. This way editor role should be capable to delete draft and pending posts.

‘delete_posts’ granted to a ‘contributor’ role allows contributors to delete their own drafts.

[Vladimir]

It seems some PHP error takes place.

Try to deactivate all plugins and re-test. If problem will go away, activate plugins back one by one to isolate a problematic one.

It’s possible to turn ON temporally debugging information in order to see what error prevent normal post creation: https://codex.wordpress.org/Debugging_in_WordPress

[Vladimir]

Hi,

Give me more details about what do you try to achieve. Screenshots will be very helpful.

[Vladimir]

Hi Shweta,

Try to deactivate temporally all plugins at the main(root) site except URE and test if role will be assigned correctly and will be in place after user login. I suppose that some plugin can reassign subscriber to this user at the root site.

[Vladimir]

Hi Caroline,

If you did not register new account, but upgraded your older account, the license key is still the same. Update server caches responses for 6 hours. I cleared its cache. Try again. You should receive a response according to the actual state of your license key.

[Vladimir]

In case you work with single site WordPress installation role should include ‘unfiltered_html’ capability. You can find it at the ‘All’ or ‘Core’ capabilities groups.

In case you work with multisite WordPress then ‘unfiltered_html’ capability does not active by default for security reasons. It’s possible to enable it back using special option at ‘Settings->User Role Editor->Multisite’ tab.

Thanks for your help. I discovered that ‘unfiltered_html’ was not included into the ‘Core->General’ group, but it should. This fix will be published with a next update.

[Vladimir]

Hi,

Thanks for letting me know that your issue was resolved.
I will think, it would have sense to replace this constant with a direct admin_url() call through all code.

[Vladimir]

I can’t use “Block Not Selected” if I’m working with custom post types – as these are always edited with a URL similar to “wp-admin/post.php?post=nn&action=edit’. Is that correct?

No, in general, it’s possible to use “block not selected” option with custom post types. I suppose, that a possible source of a problem in your case is that the link like ‘wp-admin/post.php?post=nn&action=edit’ would be associated with one of the existed (but not selected and thus blocked) admin menu item, created by a theme or plugin. URE does not block any link except selected, just not selected links included into admin menu should be blocked.

Try to look for similar URL at the list of URLs shown at the dialog window when you click ‘Admin menu’ for the role. Is there such URL? To what plugin does it belong?

[Vladimir]

Hi Donal,

When you select a menu item to be blocked, URE does not simply hides it. URE blocks the URL assigned to the hidden menu item. Any try to use blocked URL leads to the redirection to URL, assigned to the 1st available (not blocked) menu item.

When we work with ‘block not selected’ model – all URLs from the main admin menu except apparently selected become blocked. So I suppose that you have some menu item with similar URL, like ‘wp-admin/post.php?post=nn&action=edit’ and it’s counted as blocked.

I can not repeat described situation at my development environment though, as I don’t have supposed menu item.

All selected URLs under “block selected’ model should be really blocked. Can you show an example when you turn ON some checkbox but still can access that URL typing it directly at a browser address bar?

Combining “Admin menu access” data from multiple roles assigned to the same user, you have to take into account this logic:
– assigned restrictions take effect in the assigned roles order. Admin menu blocking data from the 1st (primary) role takes effect always;
– data from the rest roles are taking into account only if they use the same blocking model. For example, if the 1st role has ‘block selected’ model, but the 2nd role has ‘block not selected’ model, the 2nd role ‘admin menu access’ data is ignored.
– ‘admin menu access’ data from other roles with the same blocking model are added to the data from the 1st role.

If you have an example when the rules described above don’t work, let’s discuss it. I will try to repeat the situation and fix the bug if we discover it.

[Vladimir]

Thanks for letting me know that problem was resolved.

User Role Editor includes control of input characters for role ID and does not allow spaces inside it. I did not suppose that you created new roles beyond User Role Editor.

[Vladimir]

1) Try with default WordPress 2017 theme, as theme code may be involved too.
If it will not isolate conflict,
2) Setup development copy of your site to which you can give me admin access. I will search a reason of this problem myself.

[Author]

Posts