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.9 delivers the following fixes and enhancements:
dmsworkspaces could be previewed.
jaas.config) before migration to 4.5.
idwas not considered when configuring template availability.
An aggregated change log for 4.5.9 contains all the changes. This release is a recommended update for all users of Magnolia 4.5.
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: Bence Vass, Marvin Kerkhoff, Michiel Meeuwissen, Mike Wilson, Ralf Hirning, and Wolf Bubenik.
Do this before installing Magnolia. This is an additional task when updating to Magnolia 4.5.9 and to Data module 1.7.5. It fixes an issue where a JCRAdminTree does not show the correct activation status for subnodes. The activation status is incorrect because metadata nodes are missing.
You can perform the update in two ways:
A) Manual update
Edit the node types in
B) Scripted update
updateDataItemNodeDefinition.py Python script. The script is in the Data module bundle in Nexus.
To run the script:
Migration is your starting point. You should understand that migration is not a simple update but an effort that needs to be planned ahead.
Updating from a version prior to 4.4.6 directly to 4.5.9 does not work. You need to first update to 4.4.6, then follow the procedure described in Migration. Finally, follow How to update from Magnolia 4.5.8 above.
We recommend that you update to Form module 1.4.7 which fixes a cross-site scripting (XSS) vulnerability.
Starting with Form 1.4.5, confirmation email messages that are sent to users when they submit a form are composed using a
editCode control. The messages were previously composed with an
edit control. This changes the way the confirmation message HTML body is stored in the repository and how it is retrieved. You need to update your custom forms and existing message bodies accordingly. See an example in
UpdatePurConfirmationEmailTypeTask. If you don't update the control type and message nodes you will not be able to read or update existing messages and you run the risk of losing the messages altogether when a user saves the dialog.
Getting issue details...
See other known issues.