[MGNLMIGRATION-24] STK Migration script can fail if a module has components but no dialogs Created: 25/Feb/12  Updated: 25/Jul/12  Resolved: 25/Jul/12

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

Type: Bug Priority: Neutral
Reporter: Matt Dertinger Assignee: Jan Haderka
Resolution: Duplicate Votes: 0
Labels: installation, migration, stk2, update
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLMIGRATION-1 Check if a node exist before operatin... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Visible to:
Tony McCrary, Yun Qian

 Description   

Hi,

If a module (that contains components but does not have any dialogs) is added to the modulesRelevantForIDCreation collection, the Magnolia Standard Templating Kit (Migration) module fails to install. The following message is given on the Install/Update screen:

Could not install or update standard-templating-kit-migration module. Task 'Trigger migration scripts' failed. (PathNotFoundException: modules/MY_MODULE_NAME/dialogs)

Let me know if you need any more info.

Cheers,
Matt



 Comments   
Comment by Espen Jervidalo [ 14/Mar/12 ]

After a quick look at BuildDialogIdMap.groovy I would say that this issue is still relevant:

dialogPath = modulePath + "/dialogs"

and a direct call to def dialogContent = hm.getContent(dialogPath)

Comment by Jan Haderka [ 25/Jul/12 ]

This issue have been fixed by changes made for MGNLMIGRATION-1.

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