![]() |
|
|
|
|
Issue Type:
|
![Story]() Story
|
|
Assignee:
|
Unassigned |
|
Created:
|
22/Oct/13 3:20 PM
|
|
Description:
|
Similar to the following concept at http://wiki.magnolia-cms.com/display/DEV/Data+module+migration+step+1
What we do for 5.2
- We configure content-apps for all existing types in the data module
- We use detail subapps to create/edit new entries
- We also migrate data-module-based Company and RSS aggregator for fresh install
What we don't do for 5.2
- We don't move content to new workspaces
- We don't change ACLs consequently
- We don't have an app to manage custom types
|
|
Fix Versions:
|
2.1.x |
|
Project:
|
Magnolia Data Module
|
|
Labels:
|
migration
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Mikael Geljic
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
