[JBoss JIRA] (GTNPORTAL-3337) User disables himself
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3337?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-3337:
---------------------------------------
I find that GTNPORTAL-3345 would impact to this change, so wait for it.
> User disables himself
> ---------------------
>
> Key: GTNPORTAL-3337
> URL: https://issues.jboss.org/browse/GTNPORTAL-3337
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Trong Tran
> Assignee: Tuyen Nguyen The
> Fix For: 3.7.0.Final
>
> Original Estimate: 2 hours
> Time Spent: 4 hours
> Remaining Estimate: 1 hour
>
> - Login by John
> - Go to User and Group management
> - Disable John himself
> => He still can do other action ( edit/delete user / Add page/Add/edit portal) but can't edit for him -> NOK
> Expectation:
> - Session should be invalidated immediately, like the delete action
> or
> - Show confirmation message, then disable
--
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
12 years, 3 months
[JBoss JIRA] (GTNPORTAL-3263) "Restricted" page editor
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3263?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3263:
----------------------------------------------------
Thomas Heute <theute(a)redhat.com> changed the Status of [bug 1038562|https://bugzilla.redhat.com/show_bug.cgi?id=1038562] from ASSIGNED to MODIFIED
> "Restricted" page editor
> ------------------------
>
> Key: GTNPORTAL-3263
> URL: https://issues.jboss.org/browse/GTNPORTAL-3263
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
>
> See https://community.jboss.org/wiki/RestrictedPageEditor
> A customer is willing to give the ability to many different users to edit pages. Those users would require a simplified page editor and be constrained to simple actions. In particular, users should not be able to compose complex pages and risk to break the layouts.
> The layouts should be restricted to what is available from the "Containers" tab of the editor.
> In particular the 2 following scenarios should not be possible:
> Scenario 1: User should not be able to put an application above/below the 2 column layout (As this break the pre-defined layouts, suddenly the user is able to have a single column representation while this may not have been provided):
> Scenario 2: User should not be able to put a layout within a layout (only above or below existing ones)
> Proposed solution
> Add an option in configuration.properties for a restricted page and layout editor. This would apply across the whole portal.
> gatein.portal.pageeditor.mode=full (default) | restricted
> gatein.portal.layouteditor.mode=full (default) | restricted
>
> Applications could only be added to predefined layouts (and not directly on a page).
> Containers could only be added to the root of a page (not inside another container).
--
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
12 years, 3 months