-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.X EE, 7.0.X EE, Master
-
Fix Version/s: 6.2.X EE, 7.0.0 DXP FP26, 7.0.X EE, 7.0.4 CE GA5, 7.1.X, Master
-
Component/s: Documents & Media, Staging
-
Branch Version/s:7.0.x, 6.2.x
-
Backported to Branch:Committed
-
Fix Priority:4
-
Sprint:Collab 5
-
Git Pull Request:
Steps to Reproduce:
- Create site
- Enable local live staging with Documents and Media selected
- Go to staging site
- Add document
- View document version (1.0)
- Publish to live
- Go to live site
- View document version on the live site (1.0)
- Go to staging site
- Edit document (version 1.1)
- Publish to live
- Go to live site
- View document version on the live site (1.1)
- Go to staging site
- Go to document
- Delete version 1.1
- View document version (1.0)
- Publish to live
- Go to live site
- View document version on the live site
Expected Result:
Document version matches staging site (1.0)
Actual Result:
Document version increased on the live site (1.3)
Reproduced on both local live and remote live configurations on:
Tomcat 8.0.32 + MySQL 5.7.17. Portal master GIT ID: f08886d834fd62d6422349a116834e6eef7a6708.
Tomcat 8.0.32 + MySQL 5.7.17. Portal ee-7.0.x GIT ID: 9496e46ec5a4c8d2e8656aebfb86e61e0723da8e.
- fixes
-
LPS-73950 Cannot export to live a reverted version of a document
- Closed
-
LPS-72662 Version number stays at 1.0 when a document with several versions is published to live on staging
- Closed
- is caused by
-
LPS-56374 Document version deletion isn't published
- Closed
- relates
-
LPE-16032 Document version increases on live site when a version is removed on staging
-
- Closed
-