Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.2.X, 7.3.X, Master
-
7.3.x, 7.2.x
-
Committed
-
5
-
Regression Bug
Description
Step-by-Step:
# Start from a pristine 7.2.x instance.
# Enable local staging.
# Create a content page.
# Edit it, add an experience e1 and publish.
# Publish to live.
# Edit the page again, move e1 at the top and publish.
# Publish to live.
# Edit again, add a new experience e2 and publish.
# Publish to live.
# Edit again, move e2 to the top and publish.
# Publish to live.
# Edit again, add a new experience e3 and publish.
# Publish to live.
# Edit again, move e3 to the top and publish.
# Publish to live.
# Edit again, move e1 to the top and publish.
# Publish to live.
Actual result:
The publish to Live fails with the message:
_"An unexpected error occurred with the publish process. Please check your portal and publishing configuration.
The Segments Experience <?xml version='1.0' encoding='UTF-8'?><root available-locales="en_US" default-locale="en_US"><Name language-id="en_US">Signed in</Name></root> could not be imported because of the following error: could not update: com.liferay.segments.model.impl.SegmentsExperienceImpl#41018."_
Expected:
The reorder of the experiences changes are applied in Live.
NOTE:
The behaviour for master and 7.2.x branches is different:
- MASTER: Described in the Step-by-Step.
- 7.2.x: The error message does not appear and it says that the Publish to Live is successful. However, when the different users lands on the Content Page, they all see the Default experience. If you go back to Staging again, all the experiences but Default are being deleted. Segments cannot be deleted because it says that an experience is using the segment. Please check the videos attached.
Environment: localhost
Github: https://github.com/liferay/liferay-portal.git
Branch: master
Bundle: Liferay DXP
Last Commit: 05d615c76689c47990c3a2e64eb4c3bb4b8cbb1c
Evidence:
- 7.2.x (The 7.2.x part 1 video describes the creation of all the needed segments, users, page and experiences, which is almos the same in 7.2.x and master. The 7.2.x part 1 is where the bug can be seen)
7.2.x Part 1.webm7.2.x Part 2.webm
- Master:
Master.webm
Browsers:
- Chrome Latest
Attachments
Issue Links
- fixes
-
LPS-140510 Changes after reordering experiences with Staging are not applied in life using Org and Session segments
- Closed
- Testing discovered
-
LPS-128146 Exploratory testing in 7.2.x involving Experiences/Segments + Staging
-
- Closed
-