![]() |
|
|
|
|
Change By:
|
Tobias Mattsson
(13/May/13 1:46 PM)
|
|
Description:
|
Outlined in http://wiki.magnolia-cms.com/display/DEV/Concept+-+Action+availability+and+access+control
* Change the term restrictions to availability for actions
* Move roles configuration to a sub node permissions and use the existing class from core for it
** Node types stays where it is
* Change the term restrictions to availability as well for actionbar
** Should use the same configuration object as for actions
** This means we'll also have permissions on sections and we should evaluate these as well
* Definitions should have evaluation logic in themselves to allow for custom classes with custom evaluation logic
The existing classes mentioned were introduced in MAGNOLIA-4989
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
