Release notes for Magnolia 5.3.7

What has changed since Magnolia 5.3.6

Magnolia 5.3.7 delivers the following key fixes and enhancements:

• Fixed: Comparing versions is now i18n-aware when you work in a multisite environment.

• Improved: The MarkNodeAsDeleted command does no longer attempt to version content when versioning is disabled or not available.
• Improved: A new method UserManager.getUsersWithGroup(String groupName, boolean transitive) returns also users that belong to the subgroups of the named group when transitive=true. This makes messaging faster when the system has many users.
• Fixed: Removed a hardcoded .html extension from internal links in the CKEditor. This fixes the issue where links to PDF documents in the DAM failed.

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

• Activation 5.3.2
• Categorization 2.3.3
• DAM 2.0.7
• Diff 1.6.2
• Form 2.2.10
• Imaging 3.1.3
• Magnolia 5.3.7
• Multisite 1.1.3
• Public User Registration 2.4.2
• RSS Aggregator 2.3.3
• Standard Templating Kit 2.8.7
• UI 5.3.7
• Workflow 5.4.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:  YMC AG, Stefan Baur, Rainer Blumenthal, Jennifer Brehm, Jozef Chocholacek, Florian Fuchs,  Zarko Ivanoski, Stefan Jahn, Diana Racho, Frank Sommer, Ricardo Ulate, Richard Unger and Samuel Zihlmann.

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