Release notes for Magnolia 4.4.1
- What has changed since Magnolia CMS 4.4
- How to update from Magnolia CMS 4.4
- How to update from Magnolia 4.3.8
- Known issues
What has changed since Magnolia CMS 4.4
Magnolia CMS 4.4.1 is a bug fix release which fixes a few cache and activation related issues; it also brings back a working installer, and fixes a couple of cosmetic issues. It comes bundled with a new version of STK as well as a few other modules. It is a recommended update for all users of Magnolia CMS 4.4.
Detailed change logs can be found in our issue tracker:
- Magnolia CMS 4.4.1
- Standard templating kit 1.4.1
- Diff 1.0.2
- Content translation support 1.0.1
- Content dependencies 1.0.1
How to update from Magnolia CMS 4.4Please refer to the general update procedure page.
How to update from Magnolia 4.3.8
Since Magnolia 4.4, we are dispatching the main filter on includes (MAGNOLIA-3338): you have to update your
<filter-mapping> <filter-name>magnoliaFilterChain</filter-name> <url-pattern>/*</url-pattern> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <!-- add the following line: --> <dispatcher>INCLUDE</dispatcher> <dispatcher>ERROR</dispatcher> </filter-mapping>
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).
Fresh CE installWhen installing fresh Magnolia CE instance you may run into MAGNOLIA-3447. This issue doesn't affect functionality of Magnolia and will be solved in next release. For manual fix please remove content node
Configurationworkspace. Instances with Commenting module installed are not affected by this issue.
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.