Migrate module configuration and websites with magnolia-standard-templating-kit-migration

[Armin Wurmser]

Hi everyone

I am running into some troubles when trying to migrate my stk project from Magnolia 4.4.6 to Magnolia 4.5.4.
The stk itself was migrated properly, but when trying to use the migration module with my own project I get following error in Groovy script:


MissingMethodExceptionNoStack: No signature of method: scripts.migration.from4_4To4_5.Configuration.main() is applicable for argument types: ([Ljava.lang.String;) values: [[]]
Possible solutions: wait(), wait(long), any(), wait(long, int), print(java.lang.Object), any(groovy.lang.Closure)

I couldn't find this main method and I didn't find any when searching for it on the web.

Did I miss something in the migration config file?
Following my configuration file.

package scripts.migration.from4_4To4_5;

import scripts.migration.from4_4To4_5.*;


class Configuration{

def config = [
// Enter your modules to migrate
//
// name:Give the name of the module
// migrationType: Set migrationType to STK if your module is based on STK templating, otherwise choose BASIC
// templatingDependency: if your project references templates, paragraphs or dialogs form another modules, please list their names.
// This will allows your template definition for example to point to the new
// stk ID's.
modules : [
"module1" :[
"name":"magnolia-module-testproject",
"migrationType":"STK",
"templatingDependency":["standard-templating-kit", "form"]
]
//
// "module2" :[
// "name":"TheName2",
// "migrationType":"BASIC"
// ]
], // End of Modules config

//Enter the site definition to migrate
siteDef : [
"/modules/simplemultisite/config/sites/testproject"
// "SiteDefPath2"
],

//Enter your websites to migrate (only STK Based)
websites : ["/testproject"],

// Magnolia Module to migrate
// Any magnolia module that is not yet migrated has to be set to true
migrateSTK : true,

migrateDemoProject : true,

magnoliaModulesToMigrate : [
"commenting" : true,
"public-user-registration": true,
"form": true,
"rssaggregator": true,
"categorization": true,
"forum": true,
"shop": true,
"dms": true,
"resources": true
],

// When you think that the config is ready set this flag to true.
isConfigReady : true,

// Intermediate save
intermediateSave : false,

// Deactivate node Listener (in order to avoid WARN log during migration process.)
deactivateNodeListener : false
]
///// END CONFIG

Thanks for any help
Armin

----------------------------------------------------------------
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: <user-list-***@magnolia-cms.com>
----------------------------------------------------------------

[Samuel Schmitt (via Magnolia Forums)]

Hi Armin,

you ran the migration on STK and in your config I can see that in your second try MigrateSTK is still true. Maybe this cause the issue.

But in general, it's mandatory to run the migration of your modules and of Magnolia modules in the same run.
The reason is that the migration of STK renames paragraphs and these renaming references are not kept. So in your modules if you have references to these renamed paragraphs the migration wont be able to update the id of the paragraph/components.

These are the steps are recommend for a successful migration:
1. In order to prevent an out ouf memory error increase the heap size of the server.
2. Update security, configurations files (and set migration to false)
3. Start your instance and perform the install. You must see some issues on update, but dont worry it's normal. Modules try to perform task on a not-yet existing configuration.
4. In adminCentral, open Tools / Scripts. Open the script /scripts/migration/from4_4To4_5/Configuration. Here you must adapt the config with your configuration.
Enable the script and save.
5. Run the migration. Open the script /scripts/migration/from4_4To4_5/ConfiguredMigration. Click on RUN... and wait until it's done
6. Restart, it must trigger the install of STK and ETK.

Migration must be done.

HTH,
Sam

PS: We are currently updating the documentation.