[MGNLMIGRATION-27] Migration cannot be proceed only on the website / content Created: 19/Jun/12  Updated: 03/Sep/12  Resolved: 03/Sep/12

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: 1.1.3

Type: Improvement Priority: Major
Reporter: Samuel Schmitt Assignee: Samuel Schmitt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

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.



 Comments   
Comment by Jan Haderka [ 23/Aug/12 ]

Should this not be solved by using Robert's scripts?

Generated at Mon Feb 12 10:16:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.