Release notes for Magnolia 4.4.8

What has changed since Magnolia CMS 4.4.7

Magnolia CMS 4.4.8 fixes issues related to concurrent activation, recursive activation and content locking. It is a recommended update for all users of Magnolia CMS 4.4.x.

Please note that this is currently the last update of the 4.4.x series we're planning; please consider upgrading to 4.5.x.

An aggregated change log can be found in our issue tracker; this release includes the following new module versions:

This release includes the following new module versions:

  • Magnolia 4.4.8 (CE)
  • Magnolia Content Dependencies Module 1.0.5 (EE)
  • Magnolia Diff Module 1.0.5 (EE)
  • Magnolia XA Activation (exchange-transactional) 1.2.3 (EE)
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: Richard Unger and Rory Gibson.

How to update from Magnolia CMS 4.4.7, 4.4.6, 4.4.5, 4.4.4, 4.4.3, 4.4.2, 4.4.1 or 4.4

Please refer to the general update procedure page.

How to update from Magnolia 4.3.8

Since Magnolia 4.4, requests are dispatched to the main filter also on includes (MAGNOLIA-3338): you have to update your web.xml file.

<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>

Warning

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 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.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 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.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 a javax.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.