[MGNLDATA-20] bootstrapping data via XML Created: 26/Feb/08 Updated: 16/Sep/15 Resolved: 17/Mar/09 |
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.1 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Patrick Aebischer | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
It would be nice if defined items for the data module can be exported and later loaded automatically during bootstrap. We need this feature to be able to have the same basic items on several environments. |
| Comments |
| Comment by Philipp Bracher [ 10/Mar/08 ] |
|
The main problem is that you have to register the nodetypes first. Otherwise the import will fail. The data module does this in its start method. If the nodetypes are registered properly the import files can be placed in the 'normal' bootstrap folders. In your module you could register the nodetypes you need by providing a specific extra install task. |
| Comment by Jan Haderka [ 17/Mar/09 ] |
|
Such a task have been introduced in |
| Comment by Michael Mühlebach [ 16/Sep/15 ] |
|
This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again. |