This page provides links to the release notes of the latest Magnolia releases as well as of older releases in the currently supported Magnolia branches. The page also provides a list of the most important Magnolia features released in the last two years.
Magnolia Cloud typically supports the most recent versions of Magnolia CORE branches as well as bringing in additional cloud-specific features. See the Magnolia Cloud changelog.
|6.0||Release notes for Magnolia CMS 6.0|
|5.7||Release notes for Magnolia CORE 5.7.1|
|5.6||Release notes for Magnolia CORE 5.6.8|
|5.5||Release notes for Magnolia CORE 5.5.12||The branch will reach the end of life on November 15, 2019.|
Recently released major features
The following is a list of selected major features delivered by Magnolia in the last two years. Click on the hyperlinks to go to the documentation pages for the Magnolia branch in which the features were released.
The Find Bar is the heart of the Magnolia user interface. If offers full-text search across all your content and provides a starting point for many tasks. Used together with the (EE) Periscope Result Ranker module, Magnolia suggests top hits and ranks all your search results based on what it has learned from previous search patterns and preferences on a given Magnolia instance.
Image recognition is a neural network-based feature which extends the Find bar by automatically recognizing and tagging the content of image assets. It comes with bootstrap configurations for two recognition services: a local image recognition service that uses the ImageNet image database; and the Amazon Rekognition Image service capable of generating a more refined set of image tags. You can integrate the feature with any other image recognition service.
Content Types (developer preview)
Magnolia Content Types allow you to define the content models of your projects in Magnolia, including the properties the types may contain and their relationships to other types of content. Content type items can be managed by a content app. You can define content types in light modules on a running Magnolia system without redeploying the WAR file of your Magnolia instances and without restarting the instance or a module. This makes it a perfect approach for Magnolia Cloud users.
May 2018 saw the introduction of new European regulations aiming to protect the online rights and data of European citizens. Magnolia introduced new data privacy features making us a GDPR-friendly CMS. We help you manage personal data, track website visitor consent, facilitate data portability and ensure your visitors' right to be forgotten.
The Content Tags module provides tagging functionality in Magnolia. Tags are keywords or terms assigned to a piece of content. They are free-form and can be defined by authors on the fly. Multiple tags can be applied to many content items. By using the tags it is easier and faster for authors to associate a content item with a specific context or interest area.
Easy REST with new delivery endpoint
BOM for third-party modules
Previously, dependency management information about third-party modules was defined in the parent POMs of
magnolia.ui. A software BOM (Bill of materials) project can now take care of this. The project can then be imported in all modules. Developers may no longer worry about the versions of the third-party modules.
Content editor for easy content creation
Content Editor is an editing interface that lets authors create content easily and publish it instantly. The Content editor brings
block, a component-like content element for the smallest piece of content in an implementation of the Content editor. Authors may use it for for long-form content where they need to mix structured form fields and free-flowing composition such as news articles, blog posts, product pages and press releases.
Stories app is a ready-to-use implementation of the Content editor. Use the app to write news articles, blog posts and press releases – anything that is a mix of structured form fields and free-flow composition. The Stories app is included in the Magnolia enterprise bundles, and as an author you can customize it to suit your needs, or use it as a blueprint to create your own content editor app.
View all definitions in the Definitions app
Magnolia has many kinds of definitions: template definitions, dialog definitions, site definitions, and so on. Definitions can come from various origins. Previously it was time consuming to find out where a definition resides and, if defined multiple times, which of them takes precedence. Developers now have a single place to view all definitions. The app displays registered definitions from all sources (JCR, YAML) and all origins (classpath, JCR, file system).
Bootstrap content in light modules
The new Content Importer module allows you to bootstrap content from the file system into the JCR. The module adds bootstrapping capabilities for light modules. Developers can import content during development, distribution and deployment of light modules. For example, a module that provides a new template can also import sample content that shows editors how to use the template.
Magnolia CLI is an npm package providing a command line interface (CLI) tool to set up Magnolia and help light development. Commands in Magnolia CLI help you get the Magnolia bundle, create a light module, create a page, define page availability, and create a component. The developers preferring light development now have a powerful tool to quickly set up a module and its elements.
Personalize any component and target it to a specific audience. Define the audience by individual traits or segment your visitors into meaningful groups. With component personalization and no additional skills to use it, editors can make small changes and increase the relevance of content in a scalable way. Combine personalization with Magnolia apps to create modular reusable pieces of content that you can reassemble to meet personalization needs, solving the content scalability problem at its source.
A mechanism which allows you to alter existing configured items, such as apps, dialogs, field types, templates and more using YAML files. Decoration is possible with Magnolia Maven modules and light modules. The same definition can be decorated multiple times. For developers definition decoration greatly reduces repetition of code, making the overall development process much faster.
Magnolia Templating Kit
The templates of the Magnolia Templating Essentials move to a new module called the Magnolia Templating Kit (MTK). MTK templates don't use model classes anymore. The separation is ideally suited for front-end developers since the MTK is available also as a light module.
Complete release history
- Release notes for Magnolia CORE 5.7.1 — July 27, 2018
- Release notes for Magnolia CORE 5.7 — June 25, 2018
- Release notes for Magnolia CORE 5.6.8 — July 26, 2018
- Release notes for Magnolia CORE 5.6.7 — June 29, 2018
- Release notes for Magnolia CORE 5.6.6 — May 8, 2018
- Release notes for Magnolia CORE 5.6.5 — April 9, 2018
- Release notes for Magnolia CORE 5.6.4 — April 6, 2018
- Release notes for Magnolia CORE 5.6.3 — February 21, 2018
- Release notes for Magnolia CORE 5.6.2 — February 16, 2018
- Release notes for Magnolia CORE 5.6.1 — December 22, 2017
- Release notes for Magnolia CORE 5.6 — November 15, 2017
- Release notes for Magnolia CORE 5.5.12 — July 26, 2018
- Release notes for Magnolia CORE 5.5.11 — June 29, 2018
- Release notes for Magnolia CORE 5.5.10 — May 7, 2018
- Release notes for Magnolia CORE 5.5.9 — February 2, 2018
- Release notes for Magnolia CORE 5.5.8 — December 22, 2017
- Release notes for Magnolia CORE 5.5.7 — October 19, 2017
- Release notes for Magnolia CORE 5.5.6 — August 29, 2017
- Release notes for Magnolia CORE 5.5.5 — July 5, 2017
- Release notes for Magnolia CORE 5.5.4 — May 12, 2017
- Release notes for Magnolia CORE 5.5.3 — March 31, 2017
- Release notes for Magnolia CORE 5.5.2 — February 17, 2017
- Release notes for Magnolia CORE 5.5.1 — January 16, 2017
- Release notes for Magnolia CORE 5.5 — November 15, 2016