[MGNLACTIVATION-175] multiple publishing leaves page in "modified" state - Magnolia - Issue tracker

To reproduce this issue:

Create a new test page in the travel demo using the basic template.
Add an image component to the page and select an image from the dam.
Start publication on the page so a task makes it into the pulse.
Change the image on the test page and publish it again so that 2 tasks appear in the pulse.
Approve the test page for publication in the same order. First version first, second version second.
Go back to the pages app and observe the page remains in a modified (yellow) instead of the published (green), even though the page is in the same state on both author and public.

caused by

MAGNOLIA-3230 incorrect indication of status after edit during activation workflow

clones

PUBLISHING-34 multiple publishing leaves page in "modified" state

depends upon

MAGNOLIA-6766 Add LAST_ACTIVATED_VERSION_NAME property to NodeTypes.Activatable

MAGNOLIA-7251 Determine activated state from last activated version if set

is related to

MAGNOLIA-6754 resource subnode not reflecting published changes

MGNLSYNC-34 Last version is everytime synchronize even when it wasn't approved

supersedes

MGNLACTIVATION-177 Publication status not updated in scheduled publications at the same time

(1 is related to, 1 supersedes, 1 mentioned in)