Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-7070

Store additional mixins added through the DocumentType Editor in a separate (new) mixins property instead of the supertypes property

    XMLWordPrintable

Details

    • Improvement
    • Status: Open
    • Normal
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Currently additional mixins like taxonomy:classifiable are also saved as a 'supertype' in the supertypes property of a hipposysedit:nodetype.
      However the behavior and semantics of such mixins is different from 'real' supertypes which are actually stored and defined in the explicit JCR nodetype definition as supertypes.
      Such additional mixins are only applied/added to prototypes, as mixin, and therefore not part of the type system for the document primary type.
      The ContentTypesService (CMS7-7024) must separate these semantically and model-wise, so it would be better and easier to also store such additional mixins separately (e.g. separate property hipposysedit:mixins) in the hipposysedit:nodetype.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              adouma Ate Douma (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: