[gatein-issues] [JBoss JIRA] (GTNPORTAL-3470) Make permission defaults in page creation forms consistent

[Peter Palaga (JIRA)]

     [ https://issues.jboss.org/browse/GTNPORTAL-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga updated GTNPORTAL-3470:
------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/850


> Make permission defaults in page creation forms consistent
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-3470
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3470
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
> The page creation forms for which this applies:
> I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page 
> II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
> III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
> For each of them, the defaults should be set as follows: 
> (1) For portal pages the access and edit permissions should be taken from the parent site.
> (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.
> (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.
> In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)