[PUBLISHING-129] mgnl:lastModified Metadata Property Is Being Updated Incorrectly Upon Publish Created: 23/Sep/21  Updated: 29/Mar/22  Resolved: 07/Dec/21

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.3.1
Fix Version/s: 1.1.14, 1.3.3

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: VN-Maintenance, cm-team-support, maintenance
Remaining Estimate: Not Specified
Time Spent: 1d 5.25h
Original Estimate: Not Specified

Attachments: PNG File lastmodified_author.PNG     PNG File lastmodified_public.PNG    
Issue Links:
Problem/Incident
causality
caused by PUBLISHING-82 Wrong order of nodes after publishing... Closed
relation
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:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: Order of nodes after publishing
Sprint: Content Mngmnt 16 / Maintenace, Pages Maintenance 1, Pages Maintenance 2
Story Points: 3
Team: Nucleus

 Description   

Upon publishing some content, either in pages app or any content app, the published content on the author instance does not display the correct mgnl:lastModified date or time. Further, the published content on the public instance has the correct mgnl:lastModified value, but this property also gets updated for content that has not been modified (the sibilings).

Steps:

  • Open some content app, i.e. Contacts
  • Publish a contact
  • Observe the mgnl:lastModified property on Author and Public

Actual Results
You will see that the published content in Author has the incorrect mgnl:lastModified value. You will also see that the published content on Public along with other content on the same app, has the mgnl:lastModified value updated.

Expected Results
the mgnl:lastModified property will display the proper date and time for only the content that has been published and no other content would have this property updated.

Other Notes
This is reproduceable in the demo.
Please see screenshots for examples:

Workaround

Set orderSiblings=false https://demo.magnolia-cms.com/.magnolia/admincentral#app:configuration;/modules/publishing-core/config:treeview:

Developments nodes

  • why the metadata are updated if siblings are already in correct positions?
  • if this really needs to happen, can we unwrap from MgnlPropertySettingNodeWrapper when ordering is in progress*?*


 Comments   
Comment by Saskia Friedrich [ 19/Nov/21 ]

Hello,

In our case, it seems, the mgnl:lastModified is correct on author instance, but (after publication of one node) is incorrect for all unchanged siblings (and the parent node) on pubilc instance.

We´ve tried the workaround, the result of our tests is the following:
We noticed that while not all siblings are updated, the second to last sibling gets the same modification date. If there are no siblings, then the parent node is also changed, if the second to last sibling is updated, then it happens to be correct because no other node is updated.

Kind regards,
Saskia

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