Hi Gerd, [EMAIL PROTECTED] schrieb:
We use publication templating. I've created the root template-pubs by copying the "default" publication (source) and then changed manually anything publication specific (paths, pub-id etc.) that works very well (in 2.0). When using 2.0.2 (our pubs and modules are referenced in local.build.properties) the build succeeded but the pubs don't work as expected. For example:
- reference to org.apache.lenya.cms.cocoon.transformation.MetaDataTransformer in publication/sitemap.xmap is invalid (fixed by removing the transformer-declaration)
sorry for that. We should try to avoid including component declarations in sitemaps. By declaring them in xpatch files for the main sitemap.xmap, we reduce the risk of breaking things when class or package names change.
- Login-page shows no labels (fixed when I copy the files from pubs/default/lenya/resources/i18n/* to our pub)
We fixed an issue with missing namespaces in i18n catalogues files, maybe the error was due to this change. Catalogues without the correct namespace are not supported anymore.
- in Site-view the icon for the xhtml-resourcetype is missing in the tree (but in the 2.0.2-default pub it is)
I can't reproduce this - I just created an instance of the default publication, the icons are visible. Would you mind filing a bug with a guide how to reproduce the issue? TIA!
How could/should we proceed with the upgrade? Are Lenya 2.0 publications (publication-sitemaps) "incompatible" with 2.0.2?
Actually they are supposed to be compatible. 2.0 had some major issues, since it was the first release after a long development time. Some things had to be changed in the releases 2.0.1 and 2.0.2 to fix these issues. It was a tradeoff between reduced backwards comatibility and faulty behaviour. But in the last months the code has been consolidated, so I expect the next releases to cause less trouble.
-- Andreas -- Andreas Hartmann, CTO BeCompany GmbH http://www.becompany.ch Tel.: +41 (0) 43 818 57 01 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
