[MGNLCT-1] Load content-types and register workspace and node-types Created: 14/Feb/17  Updated: 23/May/17  Resolved: 24/Feb/17

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: 0.5

Type: New Feature Priority: Neutral
Reporter: Espen Jervidalo Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: selected-for-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File event.ctd     File event.yaml    
Issue Links:
Relates
supersession
Template:
Acceptance criteria:
Empty
Sprint: Basel 85
Story Points: 5

 Description   
  1. Introduce a new key in magnolia.properties file pointing to the content-type directory.
  2. Load all files in that directory during content-types' module startup-phase
  3. Create workspace and register nodetypes for the defined content-type.

Minimal requirement for now is to have the name and the namespace of the content-type read from the content-type file.

Example listing of the directory:

$ tree content-types/
content-types/
├── contact.ctd
├── event.ctd
└── my_file.ctd

For now we leave the files under the root-type directory and the filename is arbitrary. I don't want the namespace (e.g. 'mgnl') to be extracted from the filename.

$ cat contact.ctd
namspace 'mgnl'
entity 'contact'


 Comments   
Comment by Espen Jervidalo [ 21/Feb/17 ]

Add the following property to magnolia.properties:

magnolia.content.type.dir=/path/to/content-types/directory

Add the attached event.ctd to the directory.

A working app-configuration event.yaml needs to be loaded.

Until MCTP-3 is resolved you still need to manually add permissions to the events workspace for e.g. superuser.

Generated at Mon Feb 12 00:36:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.