[PUBLISHING-34] multiple publishing leaves page in "modified" state Created: 25/Jul/16  Updated: 29/Mar/22  Resolved: 20/Feb/18

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.0.2

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 5h
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLACTIVATION-175 multiple publishing leaves page in "m... Closed
Relates
causality
caused by MAGNOLIA-3230 incorrect indication of status after ... Closed
dependency
depends upon MAGNOLIA-6766 Add LAST_ACTIVATED_VERSION_NAME prope... Closed
depends upon MAGNOLIA-7251 Determine activated state from last a... Closed
relation
is related to MAGNOLIA-6754 resource subnode not reflecting publi... Closed
is related to MGNLSYNC-34 Last version is everytime synchronize... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Kromeriz 132, Kromeriz 133, Kromeriz 134, Kromeriz 135
Story Points: 8
Team: Nucleus

 Description   

To reproduce this issue:

  1. Create a new test page in the travel demo using the basic template.
  2. Add an image component to the page and select an image from the dam.
  3. Start publication on the page so a task makes it into the pulse.
  4. Change the image on the test page and publish it again so that 2 tasks appear in the pulse.
  5. Approve the test page for publication in the same order. First version first, second version second.
  6. 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.


 Comments   
Comment by Evzen Fochr [ 18/Aug/16 ]

It's not doable without complete rework of how we get node activation status.

Comment by Espen Jervidalo [ 25/Aug/16 ]

https://wiki.magnolia-cms.com/display/DEV/Storing+of+activation+status

Comment by Roman Kovařík [ 10/Jan/18 ]

Unblocked: try to use mgnl:lastActivatedVersion.

Generated at Mon Feb 12 10:34:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.