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 October 10, 2014

What has changed since Magnolia 5.3.3

Magnolia 5.3.4 delivers the following key fixes and enhancements:

  • Fixed a role renaming issue in the Security app. ACLs are updated when a role name is changed.

  • Added search functionality in the Security app.
  • When a node tree is closed, any selected child items inside the tree are automatically deselected.
  • Added edition and license information in the About app.
  • Added a new property  expand in the BoundedResize image operation. The property defines whether upsampling of images is allowed.
  • Added recursive restore functionality that can recover a deleted subtree. Recursive restore is default behavior in the Pages app only.
  • Provided an example CKEditor configuration file config-magnolia.js that contains Magnolia defaults. Use it as your customization starting point.
  • Provided a utility method Release notes for Magnolia 5.3.4#stkfn.getImageVariationLinkFromBinary() for creating variations of non-DAM images.
  • Added a new property  modifiedOnly  to action definitions. When true, Magnolia excludes already-published nodes from the publish action.
  • Fixed an ampersand (&) encoding issue in the stkRedirect template. Now you can pass query parameters in the target path such as
  • Fixed an issue where the system converted a date to a string when you edited a date in the JCR Browser, resulting always in the current date.
  • DefaultFormDataBinder.bindAndValidateFields() will read the underlying template configuration for the current form field and check for the value of a new boolean property escapeHtml . Default value is true which escapes HTML entered into the field, in keeping with previous system behavior. The only exception is /modules/form/templates/components/formPassword which has escapeHtml=false and therefore will not escape HTML characters.

  • Updated to aceeditor-0.8.11.jar

An aggregated change log for 5.3.4 contains all the changes.

This release is a recommended update for all users of Magnolia 5.

Recursive restore

MGNLUI-2754 - Getting issue details... STATUS

A new recursive restore action allows you to recover quickly if you delete a page and its children by accident. This is default behavior in the Pages ap. You can also enable it for other apps with configuration.

New action classes:


Old deprecated classes:


The class used in the Pages app breaks the previous API. The new class is a subclass of RestoreItemPreviousVersionAction  instead of AbstractAction . Note that the new classes are in a different package.

You can configure which node types are restored with using parentNodeTypeOnly property.


STKTemplatingFunctions  has a new utility method getImageVariationLinkFromBinary() which provides image variations for binary nodes in any workspace.

The method resolves an issue that occurs when a content app uses the DAM upload field in its editor. The uploaded image is typically not stored in the dam workspace but directly on the content node. The Contacts app is such an example where contact photos are stored in the contacts workspace, under the contact node (mgnl:resource child node). You cannot retrieve the image with an image variation link. This means you cannot create image variations through the STK imaging generator to provide different sizes, for example.

In order for the image/binary to be resolved, the workspace has to be added to URI2RepositoryMapping in server configuration:

Node nameValue













To use the method in a template script:

Example 1
[#assign link = stkfn.getImageVariationLinkFromBinary(binaryNode, model)]
<img src=${link!}>
Example 2
[#assign variationName = stkfn.resolveImageVariationName(model)]
[#assign link2 = stkfn.getImageVariationLinkFromBinary(binaryNode, variationName)]
<img src=${link2!}>

Updated modules

This release includes the following new module versions:

  • Activation 5.3.1
  • Commenting 2.2.3
  • Content Translation Support 2.0.2
  • DAM 2.0.4
  • Device Detection 1.1
  • Diff 1.6.1
  • Enterprise Edition 5.3.4
  • Form 2.2.7
  • Forum 3.4.4
  • Imaging 3.1.2
  • Magnolia 5.3.4
  • Multisite 1.1.2
  • Standard Templating Kit 2.8.4
  • Transactional Activation 2.2.1
  • UI 5.3.4
  • Workflow 5.4.2

Updated libraries

  • aceeditor-0.8.11.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, Anton Borisov, Samuli Penttilä, Per Andersson, Richard Unger, Frank Sommer, Marcel Stör, Jozef Chocholacek, Edgar Vonk, and Raju Subramaniam.

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

See: Known issues.