-
Bug
-
Resolution: Fixed
-
Neutral
-
1.0
-
None
-
-
Empty show more show less
-
Kromeriz 132, Kromeriz 133, Kromeriz 134, Kromeriz 135
-
8
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
- Closed
- depends upon
-
MAGNOLIA-6766 Add LAST_ACTIVATED_VERSION_NAME property to NodeTypes.Activatable
- Closed
-
MAGNOLIA-7251 Determine activated state from last activated version if set
- Closed
- is cloned by
-
MGNLACTIVATION-175 multiple publishing leaves page in "modified" state
- Closed
- is related to
-
MAGNOLIA-6754 resource subnode not reflecting published changes
- Closed
-
MGNLSYNC-34 Last version is everytime synchronize even when it wasn't approved
- Closed
- mentioned in
-
Page Loading...