Release notes for Magnolia 4.3.6
- What has changed since Magnolia CMS 4.3.5
- How to update from Magnolia CMS 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.5
Magnolia CMS 4.3.6 is a bug fix release, fixing a bug with certain Virtual URI patterns. It also introduces a mechanism to configure error handling in FreeMarker. For more details see the detailed change log. It is a recommended update for all users of Magnolia CMS 4.3.x.
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 CMS better. Special thanks go to Benjamin Cody for the precise bug report, including a test case !
How to update from Magnolia CMS 4.3.5, 4.3.4, 4.3.3, 4.3.2 or 4.3.1Please refer to the general update procedure page.
How to update from an earlier version of Magnolia CMSPlease 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).
JBoss 5There 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 command
zip -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.jarfile. See MAGNOLIA-2577 for technical details. If you get exception messages such as
org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parserand/or
java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration, this is the issue you're hitting.
Weblogic 10When deploying on Weblogic 10, there is a version conflict while using
commons-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.shof Weblogic and add
PRE_CLASSPATH. Since version 2.4 of
commons-langdoesn'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 9The imaging module doesn't function properly due to conflict with a
javax.imageioplugin 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.