Details

    • Team:
      Team A
    • Sprint:
      Team A Sprint 54
    • Technical tasks:
      Hide

      In de SPIKE INTERN-1330 is beschreven hoe het moet worden geïmplementeerd. Op basis van dit issue kan de documentatie geschreven worden.

      Show
      In de SPIKE INTERN-1330 is beschreven hoe het moet worden geïmplementeerd. Op basis van dit issue kan de documentatie geschreven worden.
    • Max. hours:
      9
    • Story Points:
      2

      Description

      Background

      Content types used in code, should always be present. This issue should solve the problems when code is based on content types which are not available.

      Requirements

      The XML file for specific project content types can be placed into the `app/config/resources/integrated` directory, named like `content_types.xml`, see example.

      The XML should contain the content types which are required within the application. The only properties off the content type need to be defined in the XML are:

      • id (unique identifier)
        o There is no prefix for `content types`. There should always be a check if the unique id is already available within the collection. When the content type already exists, nothing will happen with the one from the XML.
      • class ( Class document)
      • name (for displaying in listings)
        o This property can be left out, it’s not really required. However it’s easy and more readable.
        The content types are stored into the database, in the collection `content_types`.

      Examples

      Project XML directory:

      • `app/config/integrated/content_types.xml`
      • `app/config/integrated/pages.xml` (future)
      • `app/config/integrated/blocks.xml` (future)

      Bundle XML directories:
      The other structures within the Integrated bundles should be for example:

      • `integrated/content-bundle/Resources/config/integrated/content_types.xml`
      • `integrated/content-bundle/Resources/config/integrated/blocks.xml` (future)
      • `integrated/content-bundle/Resources/config/integrated/pages.xml` (future)

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                Michael Jongman (Inactive)
                Client:
                Integrated Marijn
                Product owner:
                Marijn Otte
                Developer:
                Koen Prins
                Code reviewer:
                Jeroen van Leeuwen
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  OTM