Uploaded image for project: 'Magnolia Synchronization Module'
  1. Magnolia Synchronization Module
  2. MGNLSYNC-36

Add support for configuration of synchronization source (version vs current content)

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None

    Description

      There are cases like when version store is corrupted or when versioning scheme is different than the default one which might make sync module take wrong content and activate it. E.g. in DAM versioning strategy is on modification, not on activation hence latest version of the content, might not be the one we want to activate, but current one might be better match when activated. Thus it would be beneficial to optionally configure whether to activate latest activated version, current content or use custom to-be-synchroned-content-selection-strategy.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              had Jan Haderka
              Nucleus
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Task DoD