[MGNLDAM-804] AssetAndNodeBaseCachingStrategy considers only asset node last mod date even if the actual media was updated more recently Created: 26/Sep/19  Updated: 07/Oct/19  Resolved: 07/Oct/19

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: 1h
Time Spent: 52m
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLDAM-664 Thumbnail preview doesn't refresh aft... Closed
caused by MAGNOLIA-7641 Consider bubbling modification status... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: UI Framework 7

 Description   

Uncovered with the updated ui framework forms:

Previously whenever an asset is edited, its last mod date would be updated because of how the form logic worked. In updated forms we only update the last mod date if actual changes occurs. This lead to the situation in which the user updates the asset media, but the renditions aren't updated: the root asset node stays intact!

There's a point in the existing logic though: when one restores the old version - it is the root node that was updated the last and should indicate that the variations need to be purged from cache.

Proposed solution: consider the latest of the two dates.



 Comments   
Comment by Aleksandr Pchelintcev [ 07/Oct/19 ]

The related issue in main ensures that whenever the related media is modified, the mgnl:asset node is also marked as modified. Current proposed solution for this ticket would only hide the problem solved in main (and also would not be sufficient for the consequent publishing problems).

Generated at Mon Feb 12 05:03:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.