[MAGNOLIA-6036] mgnl:lastModified not being updated on child nodes of a page Created: 08/Jan/15  Updated: 18/Aug/15  Resolved: 04/Feb/15

Status: Closed
Project: Magnolia
Component/s: page editor
Affects Version/s: 5.3.6
Fix Version/s: 5.3.8

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Mikaël Geljić
Resolution: Fixed Votes: 1
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-5351 Moved or deleted items (pages, compon... Closed
relates to PAGES-37 The "changed" marker is not removed f... Closed
causality
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:

 Description   

When a component is updated the mgnl:lastModified on the component node is not updated. As far as I can tell only the mgnl:lastModifed on the page node is updated. Whenever a node is updated on a page all ancestors of that node, up to the page level, should be updated. This was mentioned in MGNLUI-271.



 Comments   
Comment by Mikaël Geljić [ 22/Jan/15 ]

I ran precisely into that yesterday, so I dug a little bit

  • Looks like the behavior was correctly implemented in MGNLUI-271, but I had to go down to Magnolia 5.1 to find when it worked last!
  • I could relate it to the introduction of LastUpdateContentDecorator to handle lastModified dates, which we use since Magnolia 5.1.1 (MAGNOLIA-5351).
    • That code has been moved to MgnlPropertySettingContentDecorator since then.
  • For what it's worth, that's also the way 4.5 used to work
Generated at Mon Feb 12 04:10:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.