Magnolia 5.3 reached end of life on June 30, 2017. 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 5.0.1

Magnolia 5.0.2 prepares the product for a 5-series enterprise edition release, coming in 5.1. The release delivers the following fixes and enhancements.

  • Make JSR 250 annotation support configurable. Magnolia uses the @PostConstruct annotation but JSR 250 has a performance impact. You can enable it in Magnolia properties.
  • Make the population of request parameters configurable for all templates or for a specific template.
  • Integrate the MailChangePasswordLinkStrategy password retrieval strategy with STK. Make it the default strategy.
  • Changes to actions:
    • Introduce onPreExecute method in AbstractCommandAction.
    • Introduce new configurable ConfirmationAction to intercept an actual action execution. If you want to have a confirmation message when doing an action, you can now use the ConfirmationAction and define callback actions.
    • Introduce localization to actions.
  • Update Tika parser libraries to 1.4.
  • Use Maven's import dependency scope in Magnolia webapps and bundles. It allows you to import dependencies from Magnolia POMs
  • Keep the order of apps the same in the App Launcher. Use optional module dependency instead of setup tasks to reliably set the order.
  • Escape HTML code in Pulse messages.
  • Fix a cross-site scripting (XSS) vulnerability in the Contact Preview component.
  • Set field widths to 100% of the containing form. This way they accommodate long values better. To be improved further in Magnolia 5.1 by making field widths configurable.
  • Fix an out of memory error caused by asset export.
  • Fix a permissions issue where an editor was able to publish a page while in preview mode.
  • Fix an issue where cmsfn.isPreviewMode() always returned false
  • Check that an upload directory exists. This prevents failed uploads.
  • Move the X-UA-Compatible meta tag to the start of the head element. This ensures that the tag works on the author instances and in Internet Explorer.
  • Fix a layout issue in the Next Events teaser.
  • Look for area messages first in the area's own message bundle, then fall back to the parent element's bundle.

An aggregated change log for 5.0.2 contains all the changes.

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

Updated modules

This release includes the following new module versions:

  • Magnolia 5.0.2
  • Magnolia UI 5.0.2
  • Magnolia Standard Templating Kit 2.5.2
  • Magnolia Categorization Module 2.0.2
  • Magnolia DAM Module 1.0.2
  • Contacts app 1.0.2

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: Andreas Antener, Jörg Schaible, Maik Jablonski, Kevin Coshic, Stefan Baur, Will Scheidegger, Rebecca Heinen and Adrien Berthou.

How to update from Magnolia 4.5

We recommend that you wait until release 5.2, which is due later in 2013, before updating your project. The 5.2 release will include migration scripts, migration support and migration documentation.

How to migrate from Magnolia 4.4

Updating from 4.4 is a three-step process:

  1. Update your project first to the latest 4.4 series release. At minimum, update to Magnolia 4.4.6, not older.
  2. Migrate your project to 4.5. Understand that migration is not a simple update but an effort that needs to be planned ahead. Follow the procedures described in Migration.
  3. Wait for the 5.2 release later this year. Then update your project to 5.2

Known issues

Java 7 on Mac OS X

Java 7 crashes on Mac OS X. This is not a Magnolia specific issue. Java 7 on OS X is not in our certified stack. We recommend that you use Java 6.

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