-
Bug
-
Resolution: Duplicate
-
Major
-
1.1.1, 1.1.2
-
None
-
None
-
Magnolia 4.4.6 project with already prepared repository and updated Maven dependencies for version 4.5.4, including the 1.1.3-SNAPSHOT version of the magnolia-4-5-migration module.
-
-
Empty show more show less
If you follow the migration path explained on http://wiki.magnolia-cms.com/display/DEV/How+to+migrate+your+project the problem occurs after running step 3B shown on this graphic: http://wiki.magnolia-cms.com/download/attachments/51285833/migration-process.jpg.
After configuring and enabling the Configuration.groovy script (see http://wiki.magnolia-cms.com/display/SERVICES/Migration+environment+-+run+the+migration+on+a+real+project) in Magnolia, the script ConfiguredMigration.groovy is executed and it reports that the migration successfully completed.
After restarting Magnolia, dialogs and trees are broken, e. g. the script editor dialog to edit the Groovy scripts in Magnolia or the tree displaying the Company data type in the data module.
The problem also occurs with earlier versions of the migration module (1.1.1, 1.1.2). We tested the scripts on the Coop internet project as reference (http://wiki.magnolia-cms.com/display/SERVICES/Migration+environment+-+run+the+migration+on+a+real+project).
- caused by
-
MAGNOLIA-4533 wrong extends configuration fails loading of dialogs or templates
- Closed