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 June 9, 2015

What has changed since Magnolia 5.3.8

Magnolia 5.3.9 delivers the following key fixes and enhancements:

  • Updated: jBPM 6.2 ensures compatibility with Java 8.

  • Fixed: The Vaadin filteringMode property now works correctly in SelectFieldDefinition . See also Select field.
  • Improved: Enabled server-side validation for the upload field. A new  FileUploadValidator  allows you to set a maximum file size (default is 10MB) and allowed mime types. The default types are application/pdf, image/gif, image/jpg, image/jpeg and image/png. (See Field validation.)
  • Improved: Ability to display remaining characters in input fields. The indicator is displayed when you configure maxLength  in the TextFieldDefinition .
  • Improved: The Pulse message hub performs and scales now much better with a huge number of messages.
  • Improved: Disabled the possibility to deactivate nodes on the config workspace on level 1 and 2.

An aggregated change log for 5.3.9 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.9
  • UI 5.3.9
  • Enterprise Edition 5.3.9
  • Workflow 5.4.6
  • Admininterface Legacy Module  5.2.4
  • Form Module 2.2.13
  • DAM 2.0.9
  • Magnolia Standard Templating Kit 2.8.9
  • WebDAV Module 2.1.2
  • Activation Module 5.3.3
  • Content Translation Support 2.0.4
  • XA Activation (exchange-transactional) 2.2.2
  • Task Management 1.0.2
  • Mail Module 5.2.2
  • Backup 1.5.4 

 

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: Stefan Baur, Ravish Bhagdev, Piotr Bojdoł, Marco Collovati, Grubii Dmitry, Hugo Ferreira, Joerg von Frantzius, Stephan Helas, Sang Ngo Huu, Stefan Jahn, Rico Jansen, Chris Jennings, Kristiaan De Jongh, Adi De Masi, Steven McDermott, Benoit Olbrechts, Benoit Poncelet, Gavin Purnell, Felix Rabe, Diana Racho, Erich Ruf, Luke Shilson-Josling, Frank Sommer, Vivian Steller, Trang Truong, Richard Unger, Edgar Vonk and Tom Wespi.

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

Magnolia 5.3.8 ee-bundle may require you to allocate more memory the Java Virtual Machine (JVM). If you see a java.lang.OutOfMemoryError in the startup log or the system stops responding during installation, increase the Java heap size. The default maximum heap size is 512M. Try a higher amount such as 1024M. We are working on uncovering the root cause for the increased memory need.

See: Java out of memory