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

Magnolia 4.4.11 is an optimization release for Enterprise Edition only. This release:

  • Fixes a recursive activation issue when running Magnolia on Java 7.
  • Fixes a JavaScript error that prevents assigning permissions to roles.
  • Fixes a JavaScript issue with the Packager module.
  • Fixes Firefox layout and templating issues
  • Updates translations.
  • Allows changing of passwords without sending them as plain text.

Version 4.4.11 includes Jackrabbit 2.4, the latest version of the JCR repository implementation. Jackrabbit 1.6 is no longer supported by the Apache Software Foundation. Jackrabbit 2.4 brings some fixes that benefit larger Magnolia installations. To reflect this change, Maven artifacts use version 4.4.11-jr24.

An aggregated change log can be found in our issue tracker. For recently fixed Jackrabbit issues, see 2.0.5, 2.2.12 and 2.4 release notes.

Updated modules

This release includes the following new module versions:

  • Magnolia 4.4.11 (CE)
  • Magnolia DMS Module 1.5.5 (CE)
  • Magnolia Public User Registration 1.3.2 (CE)
  • Magnolia Resources Module 1.4.3 (CE)
  • Magnolia Standard Templating Kit 1.4.9 (CE)
  • Magnolia Content Dependencies Module 1.0.7 (EE)
  • Magnolia Enterprise Edition 4.4.11 (EE)
  • Magnolia LDAP support 1.4.5 (EE)
  • Magnolia Packager 4.0.8 (EE)
  • Magnolia XA Activation (exchange-transactional) 1.2.6 (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: Bence Vass, Frank Sommer, Matt Dertinger, Mike Wilson, Nils Breunese, Ralf Hirning, and Richard Unger.

Should you upgrade?

When we release a new major version we continue to support the previous major version for another two years. This means that you don't have to upgrade Magnolia or the Jackrabbit repository every time we release. However, if you run into problems with an unsupported version of Jackrabbit we may ask you to upgrade to a newer version.

Reasons to upgrade to Jackrabbit 2.4:

  • If your website has high load and multiple threads request the same piece of content at the same time, you might run into a situation where the threads get interlocked. Any future requests for that same content will get locked as well. In Jackrabbit 1.6 the only way to resolve the lock and release the threads is to restart the server. In Jackrabbit 2.0 this issue is solved by allowing multiple threads to fetch the same content into the cache and override the cached entry. The probability that you will run into this issue is low. However, if the problem on your site is caused by infrastructure rather than the number of incoming requests, you are likely to run into it over and over again. If your server stops responding, you do a thread dump, and discover that threads are blocked in the shared item cache then consider upgrading.
  • If you have a Magnolia cluster, you may see cluster configuration issues similar to thread locking. These were fixed between Jackrabbit 1.6 and 2.4.
  • If you have a lot of binary content (PDF, Word) that needs to be indexed for search, consider upgrading. With Jackrabbit 1.6 the search index can get corrupted when you upload a corrupted PDF file into the DMS workspace. Indexing of binary content was greatly improved in Jackrabbit 2.4.

Please note that Magnolia 4.4.11 is currently the last update of the 4.4.x series we are planning. Consider upgrading to Magnolia 4.5.

How to update from Magnolia 4.4.10

Unable to render {include} The included page could not be found.

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.

    <!-- add the following line: -->

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

See: Known issues.