Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-7641

Consider bubbling modification status to parent nodes [at least for the assets]

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Neutral
    • 6.2
    • None
    • None
    • None
    • UI Framework 7

    Description

      Whenever we change something under the page node - it is automatically marked as modified as well.
      Assets store content in separate node and -> should logically follow the same logic, but they don't, which leads to issues like the linked one.

      We need to make sure that the pattern we have for pages (and also for users) spreads on the assets. All that has to be done is that the node wrapper responsible for the last mod update would know how far to propagate it up the parent tree (MgnlPropertySettingContentDecorator that is). In case of pages - it is always mgnl:page, in case of users - mgnl:user.., in case of assets - should be mgnl:asset. The former two are hardcoded, the last belongs to a different module (dam), but we can at least custom string mapping.

      In the best case scenario the strategy should be injectable, just like the TODO in MgnlPropertySettingContentDecorator.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR