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 December 12, 2014

What has changed since Magnolia 5.3.5

Magnolia 5.3.6 delivers the following key fixes and enhancements:

  • Made sure that "Unpublish" action is only available for already published content.

  • Made sure variant icons are removed in pages app after deletion of the variants.
  • A title on a form page is only rendered if the formTitle has a value; otherwise nothing is displayed.
    If a user wants to display the PageTitle he must enter it into the field of the form.

  • Locale of the authoring context is exposed now to Freemarker and can be used in ftl scripts.
  • Retrieving all users or all groups is now significant faster if you have large group of users or groups.
  • Pulse doesn’t truncate messages anymore.
  • Fixed a bug on Assets app which forced the user to unexpectedly leave the application (for instance when downloading an .mp4 file with Firefox).
  • Fixed the download list component: When selecting a folder all direct descendant or all sub assets beneath are listed (selectable).
  • Enabled formSubmit component to add a Cancel button on the form template.
  • Added German translation for the workflow app.

An aggregated change log for 5.3.6 contains all the changes.

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

REST method RepositoryNode#getNodes doesn't return empty children node

Since REST Framework 1.0.5,  RepositoryNode #getNodes (with level=0, which is default) it won't return an empty node for the children nodes. (See MGNLREST-58).

Try it out on our demo instance:

Updated modules

This release includes the following new module versions:

  • Magnolia 5.3.6

  • UI 5.3.6
  • Enterprise Edition 5.3.6
  • Cache 5.3
  • Advanced Cache 1.6
  • Personalization 1.1
  • Workflow 5.4.3
  • Form 2.2.9
  • Categorization 2.3.2
  • RSS Aggregator 2.3.2
  • DAM 2.0.6
  • Marketing Tags Manager 1.0.2
  • REST Framework 1.0.5
  • Magnolia Standard Templating Kit 2.8.6
  • Data Module 2.3.3
  • Google Sitemap 2.2.2
  • Forum 3.4.5
  • Resources 2.3.3
  • In-place templating 2.3.1
  • Contacts 1.3.3
  • Groovy 2.3.2

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: Andreas Doebeli, Florian Fuchs, Diana Racho, Moritz Siuts, Rico Jansen, and Danilo Ghirardelli.

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