When choosing pages to stage over the selection will be inconsistent

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.0.12 EE, 6.0.X EE
• Fix Version/s: 6.0.X EE, 6.1.X EE, 6.2.0 CE B1
• Component/s: Frontend Infrastructure, Staging
• Labels:
  • QA-R
  • QA-TP
• Environment: LIFERAY VERSION: 6.0 SP2 ; OPERATING SYSTEM: Windows Server 2008; APPLICATION SERVER: JBoss 5.1 ; JAVA VIRTUAL MACHINE: Java 6; DATABASE: SQL Server 2008
• Branch Version/s:
  6.1.x, 6.0.x
• Backported to Branch:
  Committed
• Story Points: 3

Summary:
change selection pages results in different pages will be chosen

Steps to reproduce:
1) Grab a brand new 6012 bundle
2) Go to Control Panel -> Pages -> Settings -> Staging -> Enable "Local Live" Staging
3) Add pages as following :
.p1
----s11
----s12
.p2
----s21
----s22
.p3
----s31
----s32
4) Publish to Live -> Change Selection -> i.e. select all pages -> Select

Result : Inconsistent pages were chosen.

Note:
6.0.x and trunk also have the similar issue, which after clicking on "change selection", the selected page and the page tree are not consistent.

[Michael Chen (Inactive)]

Hi guys, just wanted to check is there any new progress available on this issue? Thanks.

[Michael Chen (Inactive)]

Hi guys,

I just noticed that this LPS(LPS-37405) has been resolved as Fixed. And I updated the 6.0.x to Rev. 158990, which includes the fix of LPS-37405 that committed on Rev. 158987. Looks now on latest 6.0.x, LPS-37405 can no longer be reproduced, however there's no "Load more results" button showing.

Before we gave the patches of customer's original issue - http://issues.liferay.com/browse/LPP-6329, the "Load more results" button does exist and work well. So customer will expect the new fix will not take the "Load more results" button away from portal.

Also the regression issue that after applying the patches of LPP-6329 is LPS-34256, "Manage Pages - Cannot drag and drop to change child page display order if these pages were hidden", which requires the "Load more results" button. If we just explain customer the button is being taken away instead of fixing it, they might not accept it.

To sum up, the customer should expect that the original issue gets fixed and other functionality(i.e. "Load more results" button) can still work as before.

Would the final resolution be the behavior in latest 6.0.x now?

Thanks

[Pani Gui (Inactive)]

PASSED Manual Testing following the steps in the description.

Reproduced on:
Tomcat 6.0 + MySQL 5. Portal 6.0.12 EE.

Selection pages doesn't work properly in staging.

Fixed on:
Tomcat 6.0 + MySQL 5. Portal 6.0.x GIT ID: 65697e56d2246620c75225f12764889af68fc03d.
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 620c0de576e60ceacbc24f1c34eaa368157d54f6.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 249e0a08b30b1280488abec5009b1a48424e03ba.

Selection pages works correctly in staging.