Page History

This page contains the information you should be aware of when upgrading to Magnolia 5.6.x from any previous and currently supported version, see the End-of-Life policy.

Before starting the upgrade, please read the release notes for the version you are updating to and all intermediate versions, the general upgrade procedure and the specific aspects. If migrating from Magnolia 4.4/4.5, please read migration documentation first. You can also contact us for migration support. 

...

1. Stop the application server.
2. Extract the new Magnolia bundle.
3. Replace JAR files in the WEB-INF/lib folder of your old Magnolia instances with new JARs from the bundle.
4. Remove any module JARs you had previously removed from your instances. Add any modules you might have added.
5. Optional: Delete all indexes to give them a little boost. Delete the index folder under each workspace directory: repositories/magnolia/workspaces/<workspace>/index. Indexes are recreated on startup, which might take a while depending on the size of your repository.
6. If you customized magnolia.properties files, compare the changes to the file in the new bundle. Properties may have been added and removed.
7. Read release notes for all intermediary versions for any additional update tasks.
8. Restart the application server.
9. Using your browser, go to the Magnolia instances and run the Web update.

...

The BOM feature was made available for the first time in Magnolia 5.5.7. For further information on how to use a BOM in your project, please see the BOM for third-party modules page.

Using the Standard Templating Kit (STK)?

...

Since the release of Magnolia 5.6 we no longer produce preconfigured bundles and webapps with the STK based demo. If you still rely on the STK, see how to add STK to your bundle.

Publishing vs Activation and custom commands

The 5.6 branch brings the Publishing module pack (see  publishing on Git) which replaces the Activation module ( /modules/activation ) and the Transactional Activation module ( /modules/exchange-transactional ). Besides giving a more logical ordering to the publishing functions in Magnolia, the new module pack also sets all workspaces as publishable by default. For an overview and comparison please see Publishing and activation.

 The publishing and activation modules cannot be used side-by-side in Magnolia.

...

For further information about configuring the new publishing-core module see the Publishing module page.  

Continue using activation

...

• Remove all the publishing JARs from the ../WEB-INF/lib folders of your author and public instances. Add the activation JAR files in their place.
• Exclude the publishing dependencies from the POM and add the old activation dependencies.

See also Publishing and activation.

Tags vs marketing tags

The introduction of content tagging in Magnolia 5.6 has had an effect on node type and workspace names:

• Any marketing tag, used by the Marketing Tags app, is a marketing-tag node type and is stored in the marketing-tags workspace.
• Any content tag, used by the Tags app, is a tag node type and is stored in the tags workspace.

...

Check your magnolia.properties file for the presence of the following lines which configure a directory for loading file system resources and the file types Magnolia should observe in the classpath and reload on-change:

...

Since ClientErrorInterceptor does not exist in RESTeasy 3, its capabilities were removed from our client implementation, the REST client module. If you have been relying on such objects, you have to handle it in a different way.

...

Magnolia 5.6 ee-bundle may require you to allocate more memory the Java Virtual Machine (JVM). If you see a java.lang.OutOfMemoryError in the startup log or the system stops responding during installation, increase the Java heap size. The default maximum heap size is 512M. Try a higher amount such as 1024M. We are working on uncovering the root cause for the increased memory need.

See: Java out of memory

The Show action in the Configuration app doesn't open the correct location

...

For other known issues please see the Known issues page.

Further reading

• Migration from Vaadin Framework 7 to Vaadin Framework 8
• Upgrading to Vaadin Framework 8 (Part 1 of 2) 
• Upgrading to Vaadin Framework 8 (Part 2 of 2)