- February 25, 2015 at 4:53 am #5160
we have an issue with changing the admin menu items (based on user roles and capabilities). This feature was our main incentive for buying the pro version.
Now, can you please direct me how to accomplish this:
All editors should be granted access to the menu and widgets control screens. All the other menu items under “Design” should not be accessible (or at least not visible) to editors.
What we did was this (for role “editor”):
– set “edit_theme_options” capability, leave out all other caps for “Themes”
– only check “Widgets” and “Menus” Items on Menu Editor
But the “Customize” and “Header” options are still displayed.
“Header” can be disabled in the Mneu Editor but after saving is checked again.
“Customize” is orange (no capability) but still checked.
Do you have any hint what might go wrong here?
Thanks in advance!February 25, 2015 at 10:08 am #5171
I’ll do a test myself and let you know.
SyamFebruary 25, 2015 at 6:40 pm #5209
It looks like those menus creates their slug dynamically, it depends on the page slug where the menu object is loaded. I’m using the menu slug to identify each menu, but since these menus uses different slugs based on the page, the code just skips over them. Also one of the menus uses a “customize” non-standard capability. I believe it translates to a standard capability dynamically, but since none of the roles have the customize capability that check box never gets enabled. I’m working on a solutions.
SyamFebruary 26, 2015 at 1:07 am #5216
again: thanks for having a look at this.
I’m glad you could reproduce this behaviour.
The topic ‘Role based Menu Item Control’ is closed to new replies.