[MGNLSYNC-34] Last version is everytime synchronize even when it wasn't approved Created: 13/Nov/17  Updated: 29/Mar/22  Resolved: 14/Dec/17

Status: Closed
Project: Magnolia Synchronization Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.7.1, 1.8.1

Type: Improvement Priority: Major
Reporter: Milan Divilek Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLACTIVATION-173 Set last activated version when publi... Closed
depends upon PUBLISHING-35 Set last activated version when publi... Closed
relation
is related to MAGNOLIA-7004 Restoring the first version of any no... Closed
is related to MGNLACTIVATION-175 multiple publishing leaves page in "m... Closed
is related to PUBLISHING-34 multiple publishing leaves page in "m... Closed
is related to MAGNOLIA-6766 Add LAST_ACTIVATED_VERSION_NAME prope... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Sprint: Kromeriz 122, Kromeriz 123, Kromeriz 124, Kromeriz 125, Kromeriz 126, Kromeriz 127
Story Points: 8
Team: Nucleus

 Description   

The above works as expected. But when I do the following:

1. create page X (v1) on author
2. publish page X (v1) approve workflow
3. modify page X (v2) on author
4. publish page X (v2) on author BUT DO NOT COMPLETE THE WORKFLOW (do nothing or assign but do not approve and publish)
5. use Synch app to synch website workspace from / recursively
6. page X (v1) should exist on public, but page X (v2) exists on the public after the sync.



 Comments   
Comment by Andrew Warinner [ 13/Nov/17 ]

Another related use case:

1. Modify page X (version n)
2. Publish page X (version n) at a scheduled date.
3. run Synchronization module before scheduled date for publication of page X
4. page X (version n) synced to public instance

There are probably other cases around multiple versions and publications too.

Comment by Jan Haderka [ 14/Nov/17 ]

This is the case also when running sync after the start of the workflow and before approval even w/o setting publication date. And was always the case.

Comment by Andrew Warinner [ 13/Dec/17 ]

Customers expecting a fix

Generated at Mon Feb 12 07:39:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.