This documentation is still in progress. We are working hard to update all our screenshots to the new Magnolia 6 style. Please bear with us.

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

The latest cloud packs that are available on the INT, UAT and LIVE environments are 5.7.2 and 6.0. For the setup procedure, see the Setting up a new environment page.

Release notes for Magnolia CORE 5.7.2 and Magnolia CMS 6.0 are available. 

(warning) We recommend that Magnolia CORE 5.7.2 be used for your production environments until the release of Magnolia CMS 6.1. The supported modules page shows the modules supported in Magnolia 5.7.2.

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

  • Which modules are provided by the Magnolia cloud offer.
  • What custom modules can be added.
  • Known limitations.

Cloud bundle 

The standard Magnolia cloud offer bundles a selection of enterprise-level modules, including connectors enabling you to integrate third-party systems, tools and data sources.


About App module | Advanced cache modules | App Switcher module | Cache modules | Campaign Publisher module | Categorization module | Configuration app | Contacts module | Content Dependencies module | Content Editor module | Content Importer module | Content Translation Support module | Content Types module 0.6.x | Definitions App module | Diff module | Digital Asset Management module | External Forms module | Form module | Google Analytics Visualization module | Groovy module | High performance caching modules | Imaging module | JavaScript Models module | JCR Tools module | jsonfn | LDAP Connector module | Link Mapper moduleLog Tools module | Mail module | Marketing Tags module | Messages App module | MTE module | Multisite module | Observation module | Pages module | Password Manager module | Personalization module | Publishing module | Resources module | REST client module | REST module | RSS Aggregator module | Scheduler module | Security App module | Site module | SiteMesh module | Soft Locking module | Solr module | Synchronization module | Tools module | UI Admincentral module | UI Framework module | UI Media Editor module | Virtual URI module | Workflow module 


Amazon S3 Connector module | Cumulus DAM connector | IBM Marketing Cloud connector | Salesforce connector | SugarCRM connector

Headless cloud bundle modules

Magnolia's headless cloud offer bundles a lighter selection of enterprise-level modules enabling you to create content and use it in headless deployment scenarios.

About App module | Activation module |  App Switcher module | Cache modules | Categorization module | Configuration app | Content Dependencies module | Content Editor module | Content Importer module | Content Types module 0.6.x | Definitions App module | Digital Asset Management module | Groovy module | Imaging module | JavaScript Models module | JCR Tools module |  jsonfn | LDAP Connector module | Log Tools module | Mail module | Messages App module | Observation module | Password Manager module | Resources module | REST module | Scheduler module | Security App module | Synchronization module | Tools module | Transactional Activation module | UI Admincentral module | UI Framework module | UI Media Editor module | Workflow module 

Connector: Amazon S3 Connector module

Need more java modules?

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

  • You can neither add nor remove Maven modules or other .jar files.
  • It is not possible to add custom Java code.

If you rely on custom Java code and want to run it in the cloud, please contact Magnolia.

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

Custom connectors

In addition to the Magnolia Enterprise connectors provided in the bundles, 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 on-premises 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.
Multisite module

You must provide your domain names during the onboarding process for your Magnolia cloud subscription package.

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 or use jsonfn.

REST Tools (part of REST module)

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

Workflow moduleCustomization is not possible.

Light modules

We recommend you do not use a YAML-based module descriptor for light modules because the Magnolia instance would have to be restarted to take the module descriptor into account. In general you should avoid restarting. The cockpit does not provide an action for this.