Released on April 23, 2014
What has changed since Magnolia 5.2.3
Magnolia 5.2.4 delivers the following fixes and enhancements:
- Added a new property
createAreaNodethat defines whether an area node should be created in the repository.
- Updated the default site definition to use the new createAreaNode property on several areas of the prototype.
- Added a warning in case a module version handler runs delta tasks that are intended for a future version of the module.
- Fixed an issue where recursive user groups caused a StackOverflowError.
- Fixed an issue where the system ignored the workspace configured in component definitions.
- Fixed host-based virtual URI mapping so that it selects the best-matching host name regardless of the order in which hosts are configured.
- Fixed dialogs in the Newsletter module that didn't work after migration to Magnolia 5.
Added a publishing status indicator in the page editor.
- Added the ability for a logged-in user to set their own preferences.
- Allowed execution of long-running actions in the background and in parallel, notifying the user if an action is already running.
An aggregated change log for 5.2.4 contains all the changes.
This release is a recommended update for all users of Magnolia 5.
This release includes the following new module versions:
- Activation 5.2.4
- AdminCentral Legacy 5.2.3
- DAM 1.2.4
- Enterprise Edition 5.2.4
- Magnolia 5.2.4
- Multisite 1.0.4
- Newsletter 2.0
- Resources 2.2.4
- Scheduler 2.1
- Standard Templating Kit 2.7.4
- UI 5.2.4
- Workflow 5.3.1
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: Rainer Blumenthal, Dean Pullen, Richard Unger, Matthias Müller, Tom Wespi, Nils Breunese, Marvin Kerkhoff, Dominik Kunz, Frank Sommer, Domenico Cianniello, Edgar Vonk, and Roland Polzer.
How to update from Magnolia 4.5 and earlier
How to update from Magnolia 5.x
Follow the standard update process.
If you have a site definition that extends from default be aware that the default site definition was reconfigured to use the new property createAreaNode. Several areas where reconfigured with this property set to false where previously it was always true. This could potentially introduce "missing content" on your website but not in the workspace. Meaning, the data exists in the JCR but because of the now reconfigured area node the data exists on the wrong level.
See: Known issues.