Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Magnolia 4.5.1 introduces several new features and changes the API and templating mechanism significantly. It is mandatory to update to Magnolia 4.4.6 before upgrading to 4.5.1. You also need to migrate your projects to comply with the new configuration and templating features.
In addition to all "core" modules released with version number 4.5.1, this release includes the following new module versions:
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: Arjan Van Bentem, Bert Leunis, Brad Kazazes, Brian Bowman, Christian Strappazzon, Craig Blake, Danilo Ghirardelli, David Pronk, Diana Racho, Diego Schivo, Fabrizio Giustina, Frank Bosma, Frank Sommer, Giancarlo Berner, Harold Capitaine, Hay Kranen, Igor Klimchynski, Jörg Schaible, Kimmo Björnsson, Luca Boati, Manuel Molaschi, Marco Glur, Matt Dertinger, Mingfai, Nickolaus Wing, Nils Breunese, Orlando Warren, Richard Unger, Rico Jansen, Rory Gibson, Ruth Stocks, Sean McMains, Stefan Baur, Steve Pugh, Sven Damm, Thomas Kalmar, Thomas Martin, Tomas Brimor, Vincent Gombert, Vit Kroutil, Vivian Steller, Vychtrle, Will Scheidegger, Wolfgang Habicht, and Zam6ak.
Migration is your starting point. Understand that migration is not a simple update but an effort that needs to be planned ahead.
LDAP Connector module requires configuration changes:
ldap.propertiesfile must be configured in a new property
java.naming.security.principalas the identity of the principal to be authenticated is no longer mandatory.
adminUserPassworddefine an admin user who has permissions to perform an initial search against the LDAP server.
jdni.ldap.configwhen adding the LDAP authentication module as a requisite login module is no longer needed.
realmNameand set its value to
See LDAP Connector documentation for details.
You will need to add a
magnolia.author.key.location in your
magnolia.properties file(s), with a value pointing to a file that can be created/written by the process running your Magnolia instance.
A few new properties have been added:
magnolia.home- not mandatory, but can be useful. By default, its value is that of the the
magnolia.app.rootdirproperty, which is the root of where the webapp is deployed. Typically, you'll set this single property to a folder of your choice, to store repositories, caches, logs, temp files, etc outside of the webapp.
magnolia.author.key.location- a new property which indicates where Magnolia should store the key pair file. See details above.
magnolia.service.contact- an optional property that lets you set a contact string which will be displayed on login pages, so users who can't login to their Magnolia instance know what to do and who to contact.
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.
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.
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.