Release notes for Magnolia 4.4.5
This release contains a bug. See Pending workitems in inbox result in errors below.
- What has changed since Magnolia CMS 4.4.4
- How to update from Magnolia CMS 4.4.4, 4.4.3, 4.4.2, 4.4.1 or 4.4
- How to update from Magnolia 4.3.8
- Known issues
What has changed since Magnolia CMS 4.4.4
Magnolia CMS 4.4.5 fixes several multisite issues, improves the account lockout feature introduced in 4.4.3, and provides a whole lot of other fixes. It is now bundled with JackRabbit 1.6.4, and is a recommended update for all users of Magnolia CMS 4.4.x.
It also introduces the Synchronization module in the Enterprise Edition, which allows synchronizing newly created or previously disconnected public instances to the main author instance.
An aggregated change log can be found in our issue tracker; this release includes the following new module versions:
- Magnolia CMS 4.4.5
- Standard Templating Kit 1.4.5
- Extended Templating Kit 1.4.3
- Data 1.6.4
- Form 1.2.4
- LDAP 1.4.3
- Groovy 1.1.2
- Tools 1.1.4
- Backup 1.1.3
- Softlocking 1.0.2
- Packager 4.0.6
- CAS 1.0.1
- Synchronization 1.0
How to update from Magnolia CMS 4.4.4, 4.4.3, 4.4.2, 4.4.1 or 4.4Please 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
<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).
Pending workitems in inbox result in errors
The release introduces a bug that causes errors when the inbox is loaded. This only happens if workitems exist in the inbox prior to upgrade. Activating such a workitem also results in an error to be logged. To work around this issue, make sure to clear the inbox of any pending workitems before upgrading. This issue is tracked as MAGNOLIA-3837 and a fix will be provided shortly.
FormThe fix for MGNLFORM-82 introduced another issue: MGNLFORM-90. The fix for MGNLFORM-82 has been cancelled: for forms to work properly, you currently need to exclude them from the cache.
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.