The doc doesnt describe your current case: on a fresh install migrate your module.
Here you dont have to migrate the other modules like STK, Form (as they are already migrated...) So I suggest to update the main groovy script (or create yours) and add only the steps you need. if you follow this diagram http://wiki.magnolia-cms.com/display/DEV/Migration+process+of+module+configuration+and+websites#Migrationprocessofmoduleconfigurationandwebsites-STKbasedmodule 1. Move you modules templatesAndParagraphsToPagesAndComponents = new TemplatesAndParagraphsToPagesAndComponents(ctx: ctx) templatesAndParagraphsToPagesAndComponents.doModules(["your module name"]) 2. Id creation - HERE you need ids of all the templates you extend, Map dialogsIdMap = new BuildDialogIdMap(ctx: ctx).buildDialogIdMap(["your module", "and all the module you extend"]) Map pagesIdMap = MigrationUtil.buildPagesIdMapFromListOfModule(["your module", "and all the module you extend"], ctx) Map componentsIdMap = MigrationUtil.buildComponentsIdMapFromListOfModule(["your module", "and all the module you extend"], ctx) 3. Preprocess your module preProcessSTKTemplates = new PreProcessSTKTemplates(ctx: ctx) preProcessSTKTemplates.doPreProcess("your module", "your siteDef path") 4. Final transfomation transformSTKTemplates = new TransformSTKTemplates(ctx: ctx, componentsIdMap:componentsIdMap, pagesIdMap:pagesIdMap, dialogsIdMap:dialogsIdMap) transformSTKTemplates.migrateModulesAndSiteDef("your module", "your siteDef path") I think it should be enough. For the extends, we have other scripts, maybe Natasha could give your more detail on this point. Samuel _____ From: Will Scheidegger [mailto:[email protected]] To: Magnolia User-List [mailto:[email protected]] Sent: Tue, 13 Mar 2012 12:19:40 +0100 Subject: Re: [magnolia-user] CE 4.5.1: "No template definition registered for id: psHome" I'm starting to see more clearly. Thanks for the help. Here my further feedback: - The docs describe the process of upgrading an existing 4.4.6 installation to 4.5. But I'm currently trying to get my modules to run on a fresh 4.5.1 installation. I add my module names to the collection, did a fresh build of the migration module and had everything bootstrap. This however did not do the trick. So I had to call the scripts manually. Bootstrapping the scripts would work better for me, but that might just be me. - My templates extend stk templates. Unfortunately the migration script does not update the "extend"-Paths. - After a restart Magnolia shows me the "You are nearly there" screen, telling me that I should install some templates now. Things that make you go "hm…" Any more pointers still warmly appreciated. -will On 13.03.2012, at 11:34, Samuel Schmitt wrote: Thanks to your feedback I realize that I have to update several points in the documentation. But if you want to start the migration of your module, please follow these steps: - first update to 4.4.6 - then add the migration module and groovy module to your config and update to 4.5 - to execute the migration over your modules you have to update the main groovy script http://svn.magnolia-cms.com/view/community/modules/magnolia-4-5-migration/tags/magnolia-4-5-migration-1.0.1/src/main/resources/scripts/migration/from4_4To4_5/Migration.groovy In the migration docu I explain that you have to add the module names in different collections of the file Migration.groovy. So if we take the example of a STK-based module, you must add your module names to: modulesRelevantForIDCreation, stkBasedModules and your site def names to: siteDef Now the migration module is updated and ready, you can start Magnolia. Tu run this script you have two possibilities, either run it on startup (there is a flag in magnolia.properties) or run it from the groovy console by the command "run Path/To/Migration.groovy" To handle special case, you must add an extra task. But the main migration steps should handle most of the cases. And a lats important point, the migration can be only trigger one time and over all the modules at the same time. Hope that helps. If you need more explanations I'm here ;) Samuel _____ ---------------------------------------------------------------- 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: <[email protected]> ---------------------------------------------------------------- _____ ---------------------------------------------------------------- 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: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- 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: <[email protected]> ----------------------------------------------------------------
