[Vladimir]

By default, URE looks to the user profile settings and to the user role both. There is no need to change something on the user level if it’s not the individual setting exactly for this user.

Go to the Users->User Role Editor. Select user role, like ‘Author’, click ‘Posts Edit’. You will see the “Own data only” checkbox at the opened window.

[Vladimir]

I suppose that with own images only it would be applicable to see own posts/pages only too.

Try ‘Own data only’ option at user profile or his role, after activation of this add-on

Allow user to edit selected posts and pages only

[Vladimir]

Thanks for your help.

I assume this beta release *could* be rolled out to a production site, in that reverting to an actual release will not cause an issue and that it is in the “upgrade path” so to speak?

Sure. There are no differences which could prevent to switch form one to another.

[Vladimir]

Hi Andy,
If you have time and development site copy to test beta version 4.65.b1, you may try it. It’s available from “Downloads” page.
Unfortunately, the ‘Import’ button under the “Network Admin->Users->User Role Editor” still waits update. Do not use it until the next beta.

[Vladimir]

Hi Andy,

Yes, work on this fix is almost finished. I update code according to miscelinouse security recomendations in addition.

I suppose to publish the updated version this week.

[Vladimir]

Thanks for patience, Andy. Yes, I confirm the final date of this update.

[Vladimir]

Hi,

Thanks for the detailed description.
Unfortunately, I can not repeat this issue. Is this happened with active URE Pro installed from the box? If not, share the settings you made in URE, which lead to the issue with application passwords. If you can share access to the site copy where I can repeat the issue, it would be helpful.

[Vladimir]

Can you setup development copy without critical data (for example, remove all users and content) where repeat the issue and provide access for the investigation then?

[Vladimir]

Thanks for the information. If it’s applicable, you may send user credentials with admin privileges to support [at] role-editor.com, in order I try isolate a reason.

[Vladimir]

It’s correct to uses this add-on for user role with ‘manage_options’ user capability.
Let me know, if you use “Admin menu editor” WordPress plugin? There is the known conflict between it and URE Pro “Admin menu access” add-on.

[Vladimir]

Let’s check, if you didn’t granted to this custom user role the ‘ure_manage_options’, ‘ure_admin_menu_access’ user capabilities.

[Vladimir]

Thanks for the quick feedback. “Update Network” is the “Network Admin->Users->User Role Editor->Update Network” button. “Apply to All sites” checkbox visible at the main (top level domain) site of the network historically was appeared at the free version of URE and doesn’t replicate the add-ons (Meta Boxes, Admin menu, etc.) data for role for other sites. I suppose it would be better to hide “Apply to All sites” checkbox for the Pro version at all in order do not confuse users.

[Vladimir]

Hi Jess,

Yes, send credentials for that to support [at] role-editor.com. I will try to provide your a solution. Send also WP user name who should work with LD notifications add-on. Screenshot with point on the admin menu item which should be available for user will be helpful.

[Vladimir]

Workaround: Do not use add-on related buttons ‘Meta Boxes’, ‘Other Roles’, ‘Post Edit’, ‘Plugins’ and ‘Import’ under ‘Network Admin->Users->User Role Editor’.

Under the main site of the multi-site network (top level domain site) these buttons work as expected, as under any other single site/subsite. The issue is related to the ‘Network Admin’ level only.

‘Update Network’ button works as expected, while you don’t wipe capabilities from user role(s) using add-on buttons from the list above.

Modules data update part should be refactored to get full compatibility with use under the Network admin. I will do it until April 9, 2026, to publish URE Pro updated version before WordPress 7.0 release.

[Vladimir]

Hi Jess,

Did you solve the described problem with MemberPress automatic redirection to front-end which blocks access to wp-admin for user with custom role and non-member? URE Pro can not solve this via existing functionality, but I could try to help with a piece of code.

[Author]

Posts