[ http://jira.magnolia.info/browse/MAGNOLIA-1164?page=all ]
Grégory Joseph resolved MAGNOLIA-1164.
--------------------------------------
Resolution: Fixed
Ok, so here's how I "fixed" this. Let me know what you think + if it solves
your issues.
Sample module now has
- users
- bob
- joe
- melinda
- groups
- developers
- employees
- roles
- base
- developer
- editor
- securitymanager
Workflow module has
- groups
- editors
- publishers
Joe and Melinda are assigned to the editors and publishers groups respectively
upon installation of the workflow module, if the sample module is present in
the system. (installed previously or being installed at the same time)
The defaut activation workflow definition was adapted to match the new group
names. (plural form)
> Clean up default users/groups/roles
> -----------------------------------
>
> Key: MAGNOLIA-1164
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1164
> Project: Magnolia
> Issue Type: Improvement
> Components: samples
> Reporter: Grégory Joseph
> Assigned To: Grégory Joseph
> Fix For: 3.1
>
>
> * some groups have irrelevant roles (for instance group "editor" currently
> has the "superuser" role !!)
> * most names could be improved :
> ** avoid duplicate names (for instance there currently is a user, a group
> AND a user called "editor")
> ** group names could be of the plural form, to make it more obvious they're
> groups of users
> ** users might have "real" names (joe, ...) to avoid confusion with
> groups/roles
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
