Hallo List, I'm updating one of our projects from mgnl4.0.1 and stk1.1-m4 to mgnl4.1 and STK1.1 and would like to share some experiences.
We could remove most of our patched magnolia classes because the bugs have been fixed. Updating the stk module caused some problems with our project. Obviuosly the structure is not exactly as expected by the update tasks. 1. Task 'Update site configuration' failed. The UpdateSiteConfigurationTask failed because it could not load a node '/modoules/standard-templating-kit/config/site/templates/prototype'. The prototype-node should have been created before by the same task but this happans only if a node '/modoules/standard-templating-kit/config/site/layout' exists. For some reason this node was missing in our project. Adding this node fixed the problem and we could see the next. 2. Task 'New template definitions' failed. This happens because 'a node with uuid 324f5252-6dac-4ac4-8c37-39ad37a48121 already exists'. In our project this was /modules/standard-templating-kit/templates/stkSection.mainArea.paragraph s. We fixed it by removing this template. Since we provide a modified version of stkSection with our project we had to manually change the uuid in our bootstrap file too. Note, that before failour 2 the update process renamed the node '/modules/standard-templating-kit/config/site/style' to '.../theme'. If style is missing the UpdateSiteConfigurationTask fails. This is good luck because it allows us to restart magnolia and fix the 'uudi-already-exists-problem'. Just don'f forget to rename 'theme' back to 'style' if you want to restart magnolia update again. Now the stk update process completed without problems. However, our module is not OK now. I'll come back with more problems. Cheers Wolf ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
