Release notes for Magnolia 4.3.8
- What has changed since Magnolia CMS 4.3.7
- How to update from Magnolia CMS 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2 or 4.3.1
- How to update from an earlier version of Magnolia CMS
- Known issues
What has changed since Magnolia CMS 4.3.7
Magnolia CMS 4.3.8 is a bug fix release which fixes important issues with virtual URI mapping and image rendering. It also bundles updated translations for AdminCentral and dialogs. It is a recommended update for all users of Magnolia CMS 4.3.x.
A new version of the Imaging module has also been made available and bundled with this release. Detailed change logs can be found in our issue tracker:
The Magnolia team would also like to thank everyone who reported issues, contributed patches, or simply commented on issues for this release. Your continued interest helps us make Magnolia better. Special thanks go to: Ernst Bunders and Fabrizio Giustina.How to update from Magnolia CMS 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2 or 4.3.1
Please refer to the general update procedure page.How to update from an earlier version of Magnolia CMS
Please refer to the release notes for Magnolia CMS 4.3. The procedure is identical.Please see the release notes pages for update instructions specific to each version following the version you are updating from; if you're updating from a fictional 1.2.3 to 1.2.6, for example, please read all release notes concerning the versions you are skipping (1.2.4 and 1.2.5 in this example).
Known issues
JBoss 5
There is an unfortunate issue, specifically when deploying under JBoss 5: you will need to remove the Xerces jar from the Magnolia CMS webapps: if deploying using WAR files, you can remove it from the archive, or with the following Unix commandzip -d path-to-magnolia.war WEB-INF/lib/xercesImpl-2.8.1.jar. If deploying using an exploded directory, simply remove the WEB-INF/lib/xercesImpl-2.8.1.jar file. See MAGNOLIA-2577 for technical details.
If you get exception messages such as org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser and/or java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration, this is the issue you're hitting.
Weblogic 10
When deploying on Weblogic 10, there is a version conflict while usingcommons-lang. While Weblogic-10 is distributed with commons-lang-2.3.jar, JackRabbit and Magnolia CMS need at least commons-lang-2.4.jar. To resolve this issue, modify setDomainEnv.sh of Weblogic and add commons-lang-2.4.jar to the PRE_CLASSPATH. Since version 2.4 of commons-lang doesn't remove any methods, but only adds new API and fixes known bugs, there is no adverse effect from this change to the Weblogic installation.
Weblogic 9
The imaging module doesn't function properly due to conflict with ajavax.imageio plugin bundled with this version of Weblogic. There is currently no known workaround for the issue.
Please see the list of known issues in the administration section for more details.