Migration cannot be proceed only on the website
-----------------------------------------------
Key: MGNLMIGRATION-27
URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-27
Project: Magnolia Migration
Issue Type: Improvement
Affects Versions: 1.1.1
Reporter: Samuel Schmitt
Priority: Major
Fix For: 1.1.x
Right now if you want to first migrate your configuration and in a second run
your websites it's not possible.
Why?
Because in your second run, you will set in {{Configuration.groovy}} all the
modules to migrate to {{false}} and you will provide no "custom" module to
migrate.
And then {{Configuration.getModulesForIDCreation}} will return an empty list.
This list is needed by the migration of your websites.
In {{ConfiguredMigration.groovy}}, this list is needed to create the list of
pages ID and components ID used by your website. So if this this is empty, the
templates information wont be updated in the content of your websites.
How to solve that:
{{Configuration}} must be improved. As for the {{modules}}, we must define the
{{templatingDependency}} of a website, and then according to that update the
method {{Configuration.getModulesForIDCreation}}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
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: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
