Details
-
Type:
Story
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects versions: None
-
Fix versions: integrated-0.9
-
Components: None
-
Epic Link:
-
Team:Team A
-
Sprint:Team A Sprint 54
-
Technical tasks:
-
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
- blocks
-
INTEGRATED-1336 Write documentation about how to implement a XML for Content Types
-
- Closed
-
-
INTEGRATED-1338 Change the content type manager to work with the XML files
-
- Closed
-