Hi Natascha We have the "standard setup" for bigger projects (website module, theme module and webapp in separate maven modules). We did upgrade the website module according to the migration guidelines and (after a "few hickups" that we already bothered you with) things seemed to have worked fine.
Since you need to pass in the site definition in the migration tasks, we kind of expected this to be all we needed. Was this a bad assumption? Do we need to migrate the theme module also specifically? If so, we must have missed this in the manual. Also I did not expect that we would have to migrate the demo-project site, but most of those errors mentioned above came from js scripts in the pop theme. Anyways, I wrote a small groovy script now, which searches the resources for any items with the mgnl:template = "css", "js", "processedCss" or "processedJs" and replaces them with the new template types "resorces:css", "resources:js", "resources:processedCss" and "resources:processedJs". Easy script, works well. In fact, the migration module could do the same "globaly" without the need for further configuration. Again: Thanks for the help, Natascha! -will -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=98fa688c-68a4-41c4-a6af-78225debb124 ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
