-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.X EE, 7.0.0 M3
-
Fix Version/s: 6.2.4 CE GA5, 6.2.X EE, 7.0.0 M2
-
Component/s: Staging
-
Branch Version/s:6.2.x
-
Backported to Branch:Committed
-
Story Points:16
-
Fix Priority:5
-
Git Pull Request:
Steps:
1) set up local staging site
2) add a document to "staging"
3) publish to remote but do not check document library - make sure that publish is from "last publish date"
at this point LPS-50521 may be an issue. If it is, add an additional document at this point. also, LPS-48828 is an issue if the staging options are changed.
4) publish again with documents selected - also be sure to use "last publish date"
5) observe that only the document added after the publish in step 3 is staged instead of all the documents since the document library was published.
Important Note
This issue is only solved for local staging site. For remote staging see issue LPS-55458
- causes
-
LPS-69904 Staging publishes cannot create a "Last Publish" date if none exists in PortletPreferences
- Closed
-
LPS-51336 Last publish date option is ignored when publishing a portlet
- Closed
-
LPS-52271 Staging - Publish fails with NPE
- Closed
- is related to
-
LPS-50521 Staging publish screen doesn't show properly the amount of entities when "From last publish date" date range is selected
- Closed
-
LPS-55458 With Remote Staging, it is not possible to stage portlets independently, they do not remember their last publish date
- Closed
- relates
-
LPE-13128 Portlets do not remember their last publish date thus making it impossible to stage portlets independently
-
- Closed
-
-
LPE-13553 Unable to stage portlets independently because portlets do not remember their last publish date
-
- Closed
-