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

Prepare migration to the new model API with no type of view

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • 4.3.0
    • None
    • None
    • None
    • 4.3 M4

      The new model API does not support type of view (rendering or edition).

      The "main" view with "edition" type, will be removed or renamed if usefull.

      For content types which edition view is different from rendering view (ex: ODF contents), the default metadata set for edition should be "default-edition".
      For legacy purpose and waiting for the migration of all content type, we need to introduce a "fallback" metadata to fallback to "main" view when the initial requested view does not exists.

      Edit button will required by default "defaut-edition" view and a "main" fallback view.

      This issue is required to be able to sax the content type model with the new API.

            Unassigned Unassigned
            laurence Laurence Aumeunier
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: