Forum Replies Created
-
AuthorPosts
-
Vladimir
KeymasterThanks for this note.
It seems something changed with one of bbPress updates. It influenced how role-editor.com private forum works too. That’s why you did not find your topic there.
I will let you know as I find a solution.
Vladimir
KeymasterThanks for the confirmation. I think the same way now. I will include this change into a next update.
Vladimir
KeymasterFix for this issue is available for testing starting from development version 4.32.b3. Development version is available after login from the same download page.
Vladimir
KeymasterThanks for your help. I repeated this issue. It will be fixed with a next update – this month.
The reason of a problem is that form edit URL has additional URL parameter ‘id’, which is not allowed as selected menu item URL does not contain it. I will extend the list of allowed URL parameters for Gravity Forms.
Quick workaround – change your “Admin menu” options from “Block not selected” to “Block selected” and then re-check menu items accordingly. You may swap them with ‘Shift’+Click on the top row checkbox.
Gravity Forms dashboard widget shows just forms which have unread entries. It does not show all existing forms.
Vladimir
KeymasterDo you really use so old WordPress version 3.6.1?
Vladimir
KeymasterHi,
Will it change if you turn off “Admin menu access” add-on at URE’s Settings? If ‘Yes’, show me a full screenshot of admin menu list for this user role.
Vladimir
KeymasterThanks for the feedback.
Vladimir
KeymasterI think that a better way to test how user sees menu is to visit site not under admin user. Currently ‘front-end menu access’ add-on does not fire for front-end menu view when admin user visit a site. So when you visit site front-end as admin user, URE does not hide from you any menu items which should be hidden according your settings.
Do you think this logic is incorrect, inconvenient?
And, Yes, admin user always sees full menu at the menu editing page at admin back-end.
Vladimir
KeymasterYes, I did not tested with pages somehow :), just with posts. Thank You for the update.
Vladimir
KeymasterYes, these restrictions are not applied for users who can edit them – additional menu item options are available only for administrator or user with ‘ure_front_end_menu_access’ capability. So ‘administrator’ and user with ‘ure_front_end_menu_access’ capability only should always see all menu items in spite of conditions applied to them.
Please let me know that it’s right for your installation. If ‘Yes’, then do you think that it will be more convenient for administrators to see the restricted (for logged-in / for logged-out users, etc.) menu under their own accounts too? I may add this as an option to change a default behavior.
Vladimir
KeymasterIn order to turn off URE’s front-end menu access add-on go to the “Settings -> User Role Editor -> Additional Modules” tab and turn off “Activate Front End Menu Access module” checkbox.
Vladimir
KeymasterOK. I’ve read your 2nd post.
Vladimir
KeymasterLicense key is for the full WP installation, not for the individual subsite. So even if you activated URE Pro not network wide, but for some subsite only, look at the URE’s Settings at the “Network admin -> Settings -> User Role Editor”.
Be aware that in case you will decide to network activate URE you need to deactivate it at subsites (where it was active) 1st.
Vladimir
KeymasterThis code is still actual to remove ‘Quick Edit’ link under a post line at the posts list. I re-tested it with theme 2017 functions.php, I just used the ‘editor’ role instead yours:
if (current_user_can('editor')) { add_filter('post_row_actions','remove_quick_edit',10,1); } function remove_quick_edit( $actions ) { unset($actions['inline hide-if-no-js']); return $actions; }
Check if you inserted code to the active theme’s functions.php, if your test user really has ‘page-editor’ role.
I’m ready to look at your site on-line if you send URL and admin login credentials to support [at-sign] role-editor.com
Vladimir
KeymasterUPS! Sorry, I have tested with ‘administrator’ incorrectly, I forgot that this add-on does not work for the users with ‘administrator’ role. It works as expected for other roles – ‘Log In’ is unavailable for logged-in users at my test site.
Try to deactivate all plugins except these 2. Will it change something? What if you try 2017 theme?
-
AuthorPosts