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 November 4, 2014

What has changed since Magnolia 5.3.4

Magnolia 5.3.5 delivers the following key fixes and enhancements:

  • Improved login and work performance in Magnolia 5.x series for sites with many users (> 10k).

  • Added support for multiline scripts and autocompletion in the Groovy console.
  • Made complex fields i18n aware. This allows multilanguage content entry composite and multivalue  fields.
  • Deprecated the ValidateExpression  class. Use the replacement class RegexValidator . The new class does not extend  NoHTMLValidator . This change allows HTML characters (<, >, &) in passwords.
  • Disabled multiselection in choose dialogs. This fixes an inconsistency where a workbench in a choose dialog allowed choosing many items but the system only took one. 
  • Removed Standard Templating Kit's dependency on the Contacts module.
  • Updated to Freemarker 2.3.21.

An aggregated change log for 5.3.5 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:

  • Commenting 2.2.4
  • Content Translation Support 2.0.3
  • DAM 2.0.5
  • Enterprise Edition 5.3.5
  • Form 2.2.8
  • Google Sitemap 2.2.1
  • Groovy 2.3.1
  • Magnolia 5.3.5
  • Public User Registration 2.4.1
  • Standard Templating Kit 2.8.5
  • UI 5.3.5

Updated libraries

  • freemarker-2.3.21.jar

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, Rainer Blumenthal, Andreas Doebeli, Florian Fuchs, Wojciech Rydzewski, Richard Unger, Will Scheidegger, Karel Nedoma, Frank Sommer, Samuel Zihlmann, and Edgar Vonk.

How to update from Magnolia 5.3.4 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

Freemarker 2.3.21 does not work with jRebel

See the comment below for a workaround.

See also: Known issues.