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. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=0cc529a5-50d4-4bf2-8642-95f1bce48895 ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
