[PUBLISHING-244] mgnl:lastActivated is irrelevant-confusing on public instances Created: 02/Mar/23  Updated: 23/Aug/23  Resolved: 11/Jul/23

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

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Antonín Juran
Resolution: Done Votes: 6
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue Links:
causality
is causing PUBLISHING-248 Don't pass the mgnl:lastActivated pro... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PUBLISHING-245 DOC: first draft Sub-task Completed Adrian Brooks  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Maintenance of Publishing module
Sprint: Nucleus 40
Story Points: 2
Team: Nucleus
Work Started:
Approved:
Yes

 Description   

Steps to reproduce

  1. Perform any modification on an already published page.
  2. Proceed to publish such page
  3. Check from the JCR app the value for mgnl:lastActivated both in Author & Public

Expected results

mgnl:lastActivated parameter has the same value on both author and public instances.

Actual results

mgnl:lastActivated is only correct on author. Public retains the previous version values.

Also, lastActivatedVersion is one version behind author's.

Workaround

Development notes


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