Bug 1090875 - Permissions Move Apps, Move Containers are not inherited to a newly created page
Summary: Permissions Move Apps, Move Containers are not inherited to a newly created page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER02
: 6.2.0
Assignee: Peter Palaga
QA Contact: Tomas Kyjovsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-24 10:45 UTC by mgottval
Modified: 2014-09-15 00:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-05 07:57:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-3459 0 Major Resolved Permissions Move Apps, Move Containers are not inherited to a newly created page 2014-06-12 00:52:19 UTC

Description mgottval 2014-04-24 10:45:26 UTC
When creating new portal site, there are 4 permissions to set - Access, Edit, Move Apps, Move Containers. When I create new portal and set some permissions, then create new page in this portal, the owner of the new page is the newly created portal, and Access and Edit permissions are inherited or "copied" into the permissions of the new page. But Move Apps, Move Containers permissions are set to "Everyone". This permissions should probably also inherit the permissions from the owning portal. 

Steps to reproduce:
1. Create new portal site, set some permissions
2. Go to this new portal site, create new page. On the 3rd step of creating the page, in View Page Properties, Permissions tab are inherited only Access and Edit permissions.

Comment 2 Peter Palaga 2014-05-05 07:57:21 UTC
This cannot be fixed as suggested in the description because there already are defaults applied from the selected page template. I have created Bug 1094154 to fix some small inconsistencies in page creation forms.


Note You need to log in before you can comment on or make changes to this bug.