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 18, 2015

What has changed since Magnolia 5.3.10

Magnolia 5.3.11 delivers the following key fixes and enhancements:

  • Improved: Added option to have Magnolia respond to configured extensions only, configurable in MIME type mapping.
  • Improved: Personalization specific workspace wide observers having better performance now.
  • Improved: Backend forms with many tabs (which do not fit in width) provide a "popup" now for the hidden tabs.
  • Improved: Tree views (for JCR data) can be sorted now. You need to enable this feature in configuration.
  • Improved: When trying to delete a group or a role, the Security app checks whether the item has dependencies to other security items and lists them. If confirmed, the dependencies to the other items are removed.
  • Fixed: nodes endpoint in the REST API handles the depth argument correctly.

  • Fixed: Audit logging for login events works again.
  • Fixed: ZIP file upload for assets on Windows works again.
  • Fixed: I18nNodeWrapper properly handles array-Properties from multi value fields.


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

  • Content Dependencies 1.4.3
  • DAM 2.0.11
  • Enterprise Edition 5.3.11
  • Magnolia 5.3.11
  • Personalization 1.1.3
  • Rest 1.1.1
  • Standard Templating Kit 2.8.10
  • UI 5.3.11
  • Workflow 5.4.8 

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: Adrian Andermatt, Antoine Contal, Florian Fuchs, Rico Jansen, Marvin Kerkhoff, Kees De Koning, Adi De Masi, Robert Mikoda, Diana Racho, Christian Schroeder, Frank Sommer,Bence Vass, Duy Vo and Edgar Vonk.

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

If you update from Magnolia 4.5 to 5.3.11 - Magnolia logs an error during startup phase due to a NoSuchNodeTypeException.
You can ignore this exception when it is thrown during startup. After start up all the node types are registered properly.
The only "issue" here is the wrong error message. We are aware of and try to get rid of it as soon as possible. (See  MAGNOLIA-6375 - Getting issue details... STATUS .)

Magnolia 5.3.11 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.


  1. Imaging should be 3.1.4


    1. True. Thanks for reading carefully. Imaging was not released. Magnolia 5.3.11 indeed still contains imaging 3.1.4 - same version as was already used on Magnolia 5.3.10.