-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.X EE
-
Fix Version/s: 6.1.X EE, 6.2.2 CE GA3 , 6.2.X EE
-
Component/s: Staging
-
Branch Version/s:6.2.x, 6.1.x
-
Backported to Branch:Committed
-
Flagged:Impediment
-
Story Points:16
-
Fix Priority:3
-
Git Pull Request:
QA found this issue during the automatic tests:
Steps to reproduce from QA:
- Go to control panel, add a blank site, called local.
- On local, add a page called Staging Test Page.
- Add another blank site: Remote Site, remember the Site ID.
- On local, click staging, click remote live, check Enabled On Public Pages and Enabled On Private Pages, check Blogs checkbox and save.
- Go to local, on Staging Test Page, add blog portlet, add a blog.
- Under staging drop down menu, click mark as ready for publish, so this page is ready for publish.
- Click Publish to Remote Live, click publish, you will see the success status.
- Click My Sites, go to Remote Site, the blog portlet is blank.
Expect behavior:
The blog entry should be displayed on remote
Actual behavior:
The blog portlet is blank.
The problem is that when you selected the Blogs content from #4 the Staged Content configuration wasn't saved.
The backport of LPS-44722 caused this regression bug.
- is caused by
-
LPS-44722 Last published version of layouts/contents are lost when turning off remote staging with page versioning
- Closed
- relates
-
LPE-12781 Options not saved when setting up remote staging
-
- Closed
-
- Testing discovered
-
LPS-52379 Staged portlets doesn't show as checked when publishing to remote live
- Closed