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
Released on August 13, 2014

What has changed since Magnolia 5.3.1

Magnolia 5.3.2 delivers the following key fixes and enhancements:

  • Added the possibility to validate fields in workflow dialogs.

  • Theme can install two identically named images that have different extensions such as icon.jpg and icon.gif.
  • Re-enabled the ability to define Freemarker shared variables in /server/rendering/freemarker/sharedVariables.
  • Custom i18n settings used in multisite are now resolved and properly displayed in page editor.
  • Fixed issues in migration from 4.5.x to 5.3.x.
  • Favorites are saved now properly also when using HTTPS.
  • InstallBinaryResourcesTask doesn't overwrite existing resources.
  • Errors in apps won't stall AdminCentral anymore.
  • The problematic environments issue is resolved with JDK 7u65 and 8u11.

An aggregated change log for 5.3.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.3.2
  • Backup 1.5.3
  • Contacts 1.3.2
  • Content Dependencies 1.4.1
  • Content Translation Support 2.0.1
  • DAM 2.0.2
  • Enterprise Edition 5.3.2
  • Forum 3.4.2
  • Imaging 3.1.1
  • Multisite 1.1.1
  • Resources 2.3.1
  • Standard Templating Kit 2.8.2
  • Tools 1.6.1
  • Transactional Activation 2.1.4
  • UI 5.3.2
  • WebDAV 2.1
  • Workflow 5.4.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, Bence Vass, Jan Christian Haddorp, Marcus Büttner, Chris Jennings, Tom Wespi, Nils Breunese, Brad Kazazes, Frank Sommer, Karel Nedoma, Rory Gibson, Peter Phillips, and Markus Koller.

How to update from Magnolia 5.3.1 and earlier

Follow the standard update procedure.

How to update from Magnolia 5.2 and earlier

To update your project, follow the standard update procedure, then make the following changes:

  1. Update your content apps with the content app upgrade task. It automatically takes care of the following:
    • Using the content connector.

    • Updating configuration of availability rules and default rule classes

    • Updating selected action definitions with node-type based availability

  2. If you used the DAM: 
    • Replace DamManager with AssetProviderRegistry.
    • See DAM and the STK and DAM templating on how to use assets in your templates.
    • The DAM changes have no impact on the STK. There is no need to modify Freemarker scripts because the new DAM API is abstracted from STK.
  3. If you have a custom jBPM workflow:
    • In the info.magnolia.module.workflow.jbpm.JbpmWorkflowManager#completeWorkItem method, checking for present parameters is obsolete and refers to publication related workitems. The method is no longer used for completing a workitem in the new human task context. It is still valid in the context of completing service tasks, however.
    • Stop using the info.magnolia.module.workflow.jbpm.JbpmWorkflowManager#getWorkItem method. It was used to complete a work item for human tasks. Furthermore, the wrapper we initialize only holds the mgnlData map.

    • The previously hardcoded mgnlData parameter is now configurable in /modules/workflow/commands/workflow/activate/activate/parameterMapName.

  4. If you have custom widgets or Vaadin add-ons:
    • Magnolia's default widgetset was relocated to info.magnolia.widgetset.MagnoliaWidgetSet.
    • Update your webapps's magnolia.properties file.
    • Otherwise Magnolia will automatically fall back to the new widgetset but will issue warnings during upgrade, and whenever a user logs in to Magnolia.

How to update from Magnolia 4.5 and earlier

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

Known issues

See: Known issues.