_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.