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 September 11, 2014

What has changed since Magnolia 5.3.2

Magnolia 5.3.3 delivers the following key fixes and enhancements:

  • Added support for multiple validators per form field. (warning) Change validation to a multivalue property.

  • Added tasks for migrating FCKEditor links that reference DAM assets.

  • Fixed an issue where links to DAM images contained a context path, making such links instance specific. The issue was introduced in DAM API 2.x.
  • Set Vaadin heartbeat interval to 90 seconds. This is how often a Vaadin client UI tells the server it is still alive.
  • Resolved a memory leak on the author instance.
  • Fixed an issue in personalization variant resolving. Previewing the original (non-variant) version of a page was broken.
  • Fixed role assignment for registered public users. The issue prevented a logged-in user from viewing protected pages. 

An aggregated change log for 5.3.3 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.3
  • Activation 5.3
  • Commenting 2.2.2
  • DAM 2.0.3
  • Enterprise Edition 5.3.3
  • Form 2.2.6
  • Forum 3.4.3
  • Mail 5.2.1
  • Observation 2.0.3
  • Personalization 1.0.1
  • Public User Registration 2.4
  • Resources 2.3.2
  • Standard Templating Kit 2.8.3
  • Transactional Activation 2.2
  • UI 5.3.3
  • WebDAV 2.1.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: Thomas Koerner, Samuli Penttilä, Moritz Siuts, Matteo Pelucco, Cedric Reichenbach, Bharath, Stefan Baur, Vivian Steller, Adi De Masi, Joerg Von Frantzius, Nils Breunese, Frank Sommer, and Rico Jansen.

How to update from Magnolia 5.3.2 and earlier

Follow the standard update procedure, then make the following changes.

Change validation to a multivalue property

MGNLFORM-235 added support for multiple validators per form field. Validators are now stored in the JCR using a property that accepts multiple values. If you use multiple validators on a form field, change the validation  property to allow multiple values.

Before: validation is a single-value property
<sv:property sv:name="validation" sv:type="String">
   <sv:value>email</sv:value>
</sv:property>
After: validation is a multivalue property
<sv:property sv:name="validation" sv:type="String" sv:multiple="true">
   <sv:value>email</sv:value>
   <sv:value>noHTML</sv:value>
</sv:property>

Add the  ChangeValidationToMultiValuedPropertyTask  update task to your module version handler. As an argument, pass a list of template definitions used for form fields that may have multiple validators. The task will update the validation property in fields that use the templates.

ChangeValidationToMultiValuedPropertyTask in a version handler
.addTask(new ChangeValidationToMultiValuedPropertyTask("Change validation property to a multivalue property", Arrays.asList("myModule:components/myTemplate1,myModule:components/myTemplate2")))

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.