Uploaded image for project: 'CMS'
  1. CMS
  2. CMS-7630

Privacy metadata should not be stored as version nor beeing store in the metadata holder

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 4.10.0
    • None
    • None
    • None
    • 4.10 M3
    • 1 - Middle term
    • 3 - Complex
    • Oui

      Currently, ametys:privacy is stored as a metadata.

      It should be managed using the getUnversionnedMetadataHolder.

      If it is too difficult to handle, it should at least be declared as non-versionned in the custom_nodetypes.xml. If so, plz open another enhancement ticket to hold it with getUnversionnedMetadataHolder.

      Once done it can be removed from SynchronizeComponent#synchronizeContent exception list.

        1. CMS-7630 - revert privacy metadata.js
          1 kB
        2. image-2025-12-08-15-59-57-696.png
          image-2025-12-08-15-59-57-696.png
          28 kB
        3. image-2025-12-08-16-00-59-141.png
          image-2025-12-08-16-00-59-141.png
          13 kB
        4. image-2025-12-15-15-51-03-730.png
          image-2025-12-15-15-51-03-730.png
          91 kB
        5. image-2025-12-15-15-51-56-308.png
          image-2025-12-15-15-51-56-308.png
          41 kB
        6. image-2025-12-15-15-53-41-317.png
          image-2025-12-15-15-53-41-317.png
          31 kB

            cbayle Caroline Bayle
            raphael Raphaël Franchet
            Caroline Bayle Caroline Bayle
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: