Uploaded image for project: 'Magnolia DAM Module'
  1. Magnolia DAM Module
  2. MGNLDAM-804

AssetAndNodeBaseCachingStrategy considers only asset node last mod date even if the actual media was updated more recently

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Not an issue
    • Icon: Neutral Neutral
    • None
    • None
    • None
    • None
    • UI Framework 7

      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.

        Acceptance criteria

              apchelintcev Aleksandr Pchelintcev
              apchelintcev Aleksandr Pchelintcev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoR

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Time Spent - 52m Remaining Estimate - 1h
                    1h
                    Logged:
                    Time Spent - 52m Remaining Estimate - 1h
                    52m