Page tree
Skip to end of metadata
Go to start of metadata

Magnolia CMS 6.1 will be available soon in your cloud subscription pack. The supported modules page already shows the modules supported in 6.1. See the Release notes for Magnolia CMS 6.1 for what is coming soon in the cloud. 

(warning) At the moment the cloud packs that are available on the INT, UAT and LIVE environments are 5.7.3 and 6.0. We recommend that Magnolia CORE 5.7.3 be used for your production environments until Magnolia CMS 6.1 is available.

This page describes the supported features of the Magnolia cloud-based platform.

Magnolia bundle 

The standard Magnolia cloud offer bundles DX Core modules enabling you to integrate third-party systems, tools and data sources.


for intro to bundle: as well as Connector Packs and Special Features

Connector Packs

Special Features

Need more java modules?

Magnolia software bundles are predefined sets that cannot be changed by a customer with a standard Magnolia cloud subscription package.

  • You can't add or remove Maven modules or other .jar files.
  • You can't add custom Java code.

If you rely on custom Java code and want to run it in the cloud, please contact us through the Cloud Helpdesk.

Custom modules

As the owner of a Magnolia subscription package, you can add your own modules. Custom modules must be light modules.

  Click to learn more about a light module
A Magnolia light module is a file and folder-based module. It can define every Magnolia item which can be configured in YAML – such as apps, content types, templates, dialogs, themes, and others. It can also contain a lightweight YAML-based module descriptor and web resources such as css and javascript files.

Light modules can be built with a simple text editor, with no special tools (such as Maven) required. A light module cannot incorporate java classes.

Your Magnolia light modules for the cloud are managed with Git. Every Magnolia cloud subscription package is connected to a Git code repository. This allows developers to check out code to local computers for custom feature and module development. See Developing for Magnolia in the cloud.

If you rely on custom Java code and want to run it in the cloud, please contact us through the Cloud Helpdesk.

Custom connectors

You can integrate other third-party web-services using JavaScript and FreeMarker code from templates or static webresources. In this case:

  • You must rely on HTTP(S) using standard ports (80, 443).
  • You cannot use Java classes.

Cloud offer limitations

Bundled Magnolia Maven modules

The Magnolia cloud offer includes the Configuration app that allows you to configure your modules.

Magnolia Client Hosted installations provide additional customization possibilities because you can add custom Java classes. 

Here is a list of known limitations for modules which are part of the Magnolia cloud software bundle:


Limitation in the cloud offer

Suggested workaround

Content Translation SupportContent from YAML-based dialogs cannot be translated.
Form module

No additional validators or form processors (which require Java).

Use Regexp and other default validators.
Personalization module

No Java-based custom traits.

Use cookie-based traits.

REST moduleNo custom (Java-based) endpoints.

Configure custom Delivery endpoints with YAML, use the default endpoints Nodes and Properties.

REST Tools (part of REST module)

Requires the configuration of the property apiBasePath and subsequent restart of the instance.

Workflow moduleCustomization is not possible.