-
☆ A M B ☆
- 2,475 Posts
I’ve tried to document some of the stuff for CMPs, but I’m hitting a wall here... when you create a new menu item, how the heck do you make use of the following fields:
* Icon
* Parameters
* Handler
* Permissions
I thought permissions were handled by the ACLs... so what does this Permissions field do? Does anyone have any examples of this stuff?
Thanks!
-
☆ A M B ☆
- 2,475 Posts
Right, I understand the ACL way of allowing access to a certain action... but what does this little box in the menu creation screen have to do with it?
You can specify a permission that is required to have to view the menu item there.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
-
☆ A M B ☆
- 2,475 Posts
Sorry, I need examples for how this is supposed to work. Are there some 3rd party components that have implemented this stuff? And what is the purpose of having permissions in the ACLs (sorta external to this) and having permissions in here (sorta internal to this). I’m confused.
The permission (or permissions -- it can be a comma-separated list) specified in the Menu item is the permission necessary to see that particular Menu item in the Top menu. User’s without that permission don’t see the menu item.
User’s are *granted* that permission in the policy specified in a Context Access ACL entry (or not).
-
☆ A M B ☆
- 2,475 Posts
Thanks, Bob. I think I understand that now... I was looking at some of the built in menu items.
But the icon? Is that even used?
Icon is not used currently.
Parameters are any REQUEST params you want attached to the menu item click, in querystring format.
Handler is optional javascript code to do onclick instead of loading a page. Think the clear cache menu item.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com