As a system administrator, I can migrate my custom types from the data module to content apps (MGNLDATA-201)

[MGNLDATA-218] Update to new bootstrap files Created: 31/Oct/13  Updated: 14/Nov/13  Resolved: 13/Nov/13

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 2.2
Fix Version/s: 2.2

Type: Sub-task Priority: Major
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Date of First Response:
Sprint: 5.2-rc2

 Description   

Once generated auto-migration of company dataType is complete, we should also make sure to bootstrap its app configuration for 5.2 fresh installs



 Comments   
Comment by Mikaël Geljić [ 06/Nov/13 ]

Updated dialogs
Company app + subapps sample bootstrap

Comment by Roman Kovařík [ 08/Nov/13 ]
  • DataTypeToContentAppTask was changed recently and this should be reflect into bootstrap files.
    We should update the bootstrap files when Data migration will be finished so we don't need to change files after each small change.
  • dataType dialog is not in migrated in its bootstrap file:
    -> dialog is not migrated on fresh install

Diff report:
http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.data.html

Comment by Mikaël Geljić [ 11/Nov/13 ]

You're right, from then on we have to propagate updates in migration to new bootstraps consistently.
As for dataType dialog, we should just remove it.

Comment by Philip Mundt [ 13/Nov/13 ]

App launcher group should be bootstrapped in mgnl-bootstrap, the companyApp app launcher in mgnl-bootstrap-samples.

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