Forum Replies Created
-
Posts
-
I include links to the documentation from the very 1st answer. But it seems that you ignore them for some reason. Please open this thread on site in a browser and go to the documentation links provided. Then ask questions if you will still have them.
Searching/filtering adds new arguments/parameters to URL. When you use “Block not selected” model, only apparently selected menu links are allowed. The same link with additional argument(s) is counted as not selected, and thus, blocked. Take into account that “Block not selected” model is more restrictive comparing to the “Block Selected”, where URE block only links which you selected and does not decide itself what to block.
This screenshot just confirms my assumption. It is exactly the case addressed here. Try to follow to this recommendations:
1)You can change model from “block not selected” to “block selected” and invert menu items selection by pressing ‘Shift’ and click on the top checkbox.
or
2) You can add URL arguments added by search in the Media Library to the admin menu “URL Parameters White List” for this menu item.Hi Max,
URE works with the single (current) network at this point of time. When URE is network activated its settings are saved for the main site of the current network.
Let me know if you will find any issue during your milti-network tests.
I suppose the issue is related to the “Admin menu” restrictions made to this custom role. This part of the “Admin menu access” documentation page may help.
If ‘General’ is a kind of WordPress categories/taxonomies supported by “Plants” custom post type, “< a href="https://www.role-editor.com/allow-user-edit-selected-posts/">Users access restriction for editing selected posts and pages only by category/taxonomy ID list” add-on should help you.
You need to activate this add-on at “Settings->User Role Editor->Additional Modules” tab. Open every editor user profile and input there the list of ‘Genera’ IDs to the edit restrictions section:
Custom post type definition includes a capability type parameter. If capability type is omitted, WordPress uses a default value ‘post’, the same as for the WP built-in post type ‘posts’. All such custom post types are protected by the same user capabilities set as WordPress uses for the ‘Posts’: edit_posts, delete_posts, etc.
If you use some plugin to define custom post type you can input a unique capability type there.
User Role Editor Pro has an option which forces all custom post type to use own capabilities set (Settings->User Role Editor->Additional Modules). Related capabilities are added to the administrator role automatically, but should be granted to other roles manually.
Hi Bill,
You can add an option “Prohibit Admin” for the roles as at this article and turn it ON for the selected role. User will be redirected to front-end automatically after try to access wp-admin.
Thanks for the additional information. OK. There was misunderstanding from my side here.
I will develop this feature for post/page edit restrictions.‘Page attributes’ section at the page editor should be unavailable for restrictions users, right? Other way user may change page template for a page and make it unavailable for him.
Can you please test version 4.44.b1? It’s available after login as the development version from the same download page.
Role should have required capabilities in order you can see the related menu items in “Admin menu” – at least the ‘edit_posts’.
