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

What has changed since Magnolia 5.3

Magnolia 5.3.1 delivers the following key fixes and enhancements:

  • Fixed garbage collection in the Repository tools app which broke with the upgrade to Jackrabbit 2.8.
  • Fixed an issue where versioning failed if a subnode was created with same name as existing node.
  • Fixed the ACL choose dialogs in the Security app.

  • Fixed an issue where AdminCentral became unusable if its servlet mappings were missing.
  • Changed the structure of sub app mapping for EditDataActionDefinition to handle node types with prefixes.
  • Restored compatibility with Blossom 3.x regarding the FormDialogPresenter.

  • Serve DAM images via Imaging module.
  • Fixed registration of external CKEditor plugins.
  • Fine-tuned action availability in apps regarding write permissions (set writePermissionRequired  property in configuration) 

An aggregated change log for 5.3.1 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.1
  • Activation 5.2.6
  • Cache 5.2.5
  • Categorization 2.3.1
  • Contacts 1.3.1
  • DAM 2.0.1
  • Data 2.3.1
  • Form 2.2.5
  • Forum 3.4.1
  • Google Sitemap 2.2
  • Mail 5.2
  • Marketing Tags Manager 1.0.1
  • Public Users Management 2.3.1
  • RSS Aggregator 2.3.1
  • Standard Templating Kit 2.8.1
  • Task Management 1.0.1
  • Tools 1.6
  • Transactional Activation 2.1.3
  • UI 5.3.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: Nils Breunese, Joey Bartram, Ruth Stocks, Richard Unger, Stefan Baur, Frank Sommer, Johannes Selig, Jozef Chocholacek and Erich Ruf.

How to update from Magnolia 5.3

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.