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

Released on February 11, 2014

What has changed since Magnolia 4.5.15

Magnolia 4.5.16 delivers the following fixes and enhancements:

  • Remove support for request attributes and parameters in PageMVCServlet and implement a strict URL pattern.
  • Upgrade to jackrabbit 2.4.5
  • Create an activation timestamp right after a temp file is prepared. This makes sure the time difference between author and public is as short as possible.
  • Write a temporary file once per activation. Writing redundant temp files for each subscriber caused unnecessary disk activity.
  • Allow entering a license key even if the license node was deleted by accident.

An aggregated change log for 4.5.16 contains all the changes.

This release is a recommended update for all users of Magnolia 4.5.

(info) This is a maintenance release of a previous major version (4.5) of Magnolia, therefore available only to Enterprise clients. Read our maintenance policy for details. The released artifacts are in the magnolia.public.maintenance.releases repository (login required).

Updated modules

This release includes the following new module versions:

  • Magnolia 4.5.16
  • Commenting 1.2.6
  • Enterprise Edition 4.5.16
  • Extended Templating Kit 2.0.17
  • License 1.3.4
  • Migration 1.2.8
  • Standard Templating Kit 2.0.17
  • Transactional Activation 1.3.10
  • WebDAV 1.1.4

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: Joerg Von Frantzius, Ricardo Ulate, Nils Breunese, Jean-Charles and Charles Jones.

How to update from Magnolia 4.5.x

Follow the standard update process.

How to update from Magnolia 4.4 and earlier

Are you running on Magnolia 4.4 or earlier? It’s time to move to 4.5 and then to 5. Contact us for migration support and look at the migration process.

Known issues

See: Known issues.