Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.

Magnolia CORE 5.7.3 is a bug-fixing and security release that delivers the following:

Changes for authors

Content editor supports richText fields

In a custom content block, you can now use the richText  field type for more advanced text formatting. Previously, only basic text formatting functions were available through the special text block type.

With this Magnolia release, richText initializes correctly in a multivalue field.


Audit log correctly identifying requestor's user name

With the introduction of the Publishing module, audit log entries for publishing and unpublishing requests always mentioned superuser as the requestor. With Magnolia CORE 5.7.3, the audit log now correctly identifies the requestor's user name again.


Image editor: no black borders when rotating an image

The image editor in Magnolia's digital asset management no longer creates black borders when you rotate an image.


Scheduler working after configuration change

A bug has been fixed in the task-management module. The bug affected the Scheduler module, which stopped working after changing its configuration.


Changes for developers

Decorating dialogs with presenterClass possible

The system threw an exception every time you tried to launch a dialog decorated with a presenterClass property. With Magnolia CORE 5.7.3, you can now decorate and use dialogs with that property.


!with-type  renamed to !content-type

The !with-type directive referencing a content type in an app descriptor has been renamed to !content-type.


Error rendering macro 'code-pro'

Error 401 retrieving server data from URL. User is not authorized to perform the request.


Third-party library updates


Guava has been updated to version 24.1.1 to fix a security issue.



Tika has been updated to version 1.20 to fix some security vulnerabilities. The following Tika dependencies have been affected:

  • commons-compress-1.18
  • jempbox-1.8.16
  • pdfbox-2.0.13
  • poi-4.0.1
  • sentiment-analysis-parser-0.1
  • vorbis-java-tika-0.8
  • btf-1.2
  • checker-compat-qual-2.0.0
  • FastInfoset-1.2.15
  • istack-commons-runtime-3.0.7
  • msg-simple-1.1
  • stax-ex-1.8
  • txw2-2.3.1
  • javax.json.bind-api-1.0
  • jaxb-core-2.3.0
  • jaxb-impl-2.3.0
  • json-1.8
  • microprofile-config-api-1.1
  • microprofile-rest-client-api-1.0



Jackrabbit has been updated to version 2.18.1.

The artifacts and org.jetbrains:annotations have the same ID, but they are two different dependencies.



If you are upgrading from an earlier version, read Upgrading to Magnolia 5.7.x first and check the Known issues section on the page.


See the 5.7.3 changelog for all the changes.

Updated modules

  • Categorization 2.6.1
  • Community Edition 5.7.3
  • Content Translation Support 2.3
  • Enterprise Edition 5.7.3
  • Form 2.5.2
  • Magnolia 5.7.3
  • Mail 5.5.2
  • Password Manager 1.2.1
  • Public User Registration 2.7.2
  • Publishing 1.0.7
  • Publishing Transactional 1.0.1
  • Resources 2.6.3
  • RSS Aggregator 2.6.2
  • Scheduler 2.3.2
  • Task Management 1.2.6
  • UI 5.7.3
  • Vaadin Compatibility Addons 1.0.1


The Magnolia team would also like to thank everyone who reported issues, contributed patches or simply commented on issues for this release. Your continued interest helps us make Magnolia better. Special thanks go to Thomas Duffey, Michael Kaiser, Marvin Kerkhoff, Samuel Kohler, Vyacheslav Maksimov, Thomas Peintner, Frank Sommer, Bence Vass and Hugo Venancio.

  • No labels


  1. Building with 5.7.3 requires the following repo available only for enterprise customers:
    1. I've created an issue for that, since i'm also affected:  MAGNOLIA-7577 - Getting issue details... STATUS

  2. I second the issue that Joerg von Frantziusmentioned: one cannot build the project unless this repo was added to the project

    1. Hi Marty, thanks for reporting this issue. It is actually a valid one which we already tackled and solved with PUBLISHING-59 - Getting issue details... STATUS .
      A 5.7.4 release should be out soon (roughly in one or two weeks) and solve this. 


      Federico, for the Magnolia team