Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

What has changed since Magnolia 4.1.1

This is a bugfix release, fixing visual artefacts with tree manipulation in AdminCentral, activation issues for users with restricted write access on public instances and issues with usability of EditBar tag.

It is bundled with an updated version of the DMS and Newsletter modules (latter included in the Enterprise Edition).

It is a recommended update for all users of Magnolia 4.1.

As usual, the complete list of changes can be found on our Jira.

The Magnolia team would like to thank everyone who reported issues or contributed patches to this release. Your continuous interest helps us make Magnolia better.

How to update from Magnolia 4.1.1

Please refer to the general update procedure page.

If you want to take advantage of Jackrabbit's new “DataStore” feature, you will have to migrate your repository; modifying your existing repository configuration to add the DataStore feature, without migrating it, will result in the loss of blobs.

How to update from an earlier version of Magnolia

Please refer to the release notes for Magnolia 4.1. The procedure is identical.

Please see the release notes pages for update instructions specific to the version you are updating to. If you're skipping versions (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're skipping too.

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