[MGNLMIGRATION-44] Running the migration script on a project breaks basic Magnolia configurations (dialogs/trees/...) Created: 14/Sep/12 Updated: 29/Mar/13 Resolved: 20/Sep/12 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | 1.1.1, 1.1.2 |
| Fix Version/s: | 1.1.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Lars Fischer | Assignee: | Jan Haderka |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
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. |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Description |
|
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). |
| Comments |
| Comment by Lars Fischer [ 14/Sep/12 ] |
|
The two files are exports of the complete modules configuration with the following content: 2-config-modules.xml contains the config when all the standard stuff (dialogs, trees) is still working. |
| Comment by Lars Fischer [ 14/Sep/12 ] |
|
This is when you try to open a script edit dialog: 2012-09-14 10:09:05,409 ERROR fo.magnolia.module.admininterface.DialogMVCServlet: no dialog registered for name: scriptsEdit |
| Comment by Lars Fischer [ 14/Sep/12 ] |
|
Tree handler exception for the "Company" data type: java.lang.RuntimeException: info.magnolia.module.admininterface.InvalidTreeHandlerException: Unable to instantiate a tree handler for [company] due to a info.magnolia.content2bean.Content2BeanException exception |
| Comment by Lars Fischer [ 14/Sep/12 ] |
|
Included the error log. |
| Comment by Lars Fischer [ 14/Sep/12 ] |
|
Collected debug logs. |
| Comment by Lars Fischer [ 17/Sep/12 ] |
|
At the moment it looks like the problem exists in version 4.5.4 of Magnolia: The method "isExists" in the class "ExtendingContentWrapper" has a bug that prevents all dialogs at Magnolia startup from being registered if only one of the dialogs has an error. Instead of private boolean isExists(String extendedNode, Content parent) throws RepositoryException { return parent.hasContent(extendedNode); it should be private boolean isExists(String extendedNode, Content parent) throws RepositoryException { else { return parent.hasContent(extendedNode); }} This will be fixed in the next release, at the moment you have to use the snapshot version. |
| Comment by Lars Fischer [ 20/Sep/12 ] |
|
Philipp found the problem in Magnolia Core and opened a separate issue ( |