Publish to Live is not properly configuring Page Permissions from Staging

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 5.1.0
• Fix Version/s: None
• Component/s: none
• Labels: None
• Similar Issues: Show 5 results ; ;

  LEP-5905	Using 'Link to Page' type with Stage turned on does not point to Live after 'Publish to Live' - still points to the page in Stage
  LEP-4238	Staging: support publishing to live a single page
  LEP-4996	Permissions for staging aren't always checked properly
  LEP-4555	Staging to Live issue
  LEP-6577	Permissions attached to User Groups are ignored on import/export and staging publish

In Staging when I create a first level page ("Admin") and removing "View" permission for "Guest", "User", "Power User" so that only the administrator can see, then run Publish to Live option in that page, permissions of Admin page are not properly configured and all users (Guest, User, Power User) can also view that page. Another important thing is that in Staging if it behaves correctly (hidden page) with non Administrator users.

[Dale Shan]

Yes, i can reproduce this problem with LIferay trunk. when a community's staging is active, even if you have defined permission in community but the permission has no effect after you publish the page.

[Jeff Wilson]

This is the same issue I reported as LEP-6657.

The underlying cause appears to be a failure to codify the "guest view" permission when exporting the available permissions. All other permissions appear to be exported properly, but the "guest view" permission's status does not appear to be included in the permission export list.

Consequently, the permission import facility has no information on whether this permission is marked as granted, and just assumes this permission should always be granted. Unfortunately this causes staging to be useless to any site containing any pages which are not guest viewable.

[Dana Oredson]

I apologize for the cross-posting with LEP 6657, but I don't know what issues are actually still live.

Still affects 5.2.2 I have been struggling with this for some time.

Note that ALGORITHM_5 works fine. ALGORITHM_2 exhibits the buggy behavior. I am more than willing to try out patches against relative to 5.2.2, if anyone has ideas.
Additionally, I would like to point out that the LayoutImporter.importUserPermissions method looks like it won't remove user permissions.

For example, if a user was assigned VIEW to a page on the live side; then in staging that user's VIEW permission is removed and the page is published, the for loop in importUserPermissions is only going to loop over the user-actions elements, which won't have an entry for that user anymore, so the permission can't be revoked.

It seems to me that what should instead be happening is remove all user permissions to the page, then do the normal import of permissions from xml

[Thomas Kellerer]

this still doesn't work with 6.0.3

[Tagnaouti Boubker]

This issue is being addressed as part of the 100 PaperCuts program. Please see http://liferay.com/community/100-papercuts

[Tagnaouti Boubker]

Hi all,

ALGORITHM_5 and 6 work fine in the trunk version 6.1.x but the buggy behavior still persist when using ALGORITHM_1_4.

[Tagnaouti Boubker]

This patch fixes the problem for exporting layout permissions from staging.

[Tagnaouti Boubker]

I found another bug (while working on this ticket) related to exporting permissions from staging environment when using ALGORITHM_1_4.
Portlets permissions are apparently not properly exported.

[Tagnaouti Boubker]

Hi Dana,

Can you try those solutions and let us know if it fixes the issue for you?

[Tagnaouti Boubker]

Another version of the patch including only the diffs for the bug fix.

[Cynthia Wilburn]

Thank you for the contribution. We ask that you click the "Contribute Solution" workflow step in the left-hand navigation of the ticket and accept the Contributor's Agreement. The reporter must then click "Accept Contribution" to change the state to "Community Resolved". Our engineering team will then review the contribution for potential inclusion into the source code.

[Vicki Tsang]

LPS ticket created. Need to retest issue to see if still present.

[James Falkner]

Dup of LPS-23543 (filed as a clone and no longer reproducible).