Page tree
Skip to end of metadata
Go to start of metadata
Released on September 9, 2015

What has changed

Magnolia 5.4.2 delivers the following key fixes and enhancements:

  • Improved: Imaging now supports TIFF images. Please see TwelveMonkeys third-party library about supported TIFF files.
  • Improved: Back-end forms with many tabs which do not fit in a dialog provide a popup now for the hidden tabs.
  • Improved: Tree views (for JCR data) can be sorted now. You need to enable this feature in configuration.
  • Improved: Added option to have Magnolia respond to configured extensions only, configurable in MIME type mapping.

  • Fixed: nodes endpoint in the REST API handles the depth argument correctly.
  • Fixed: ZIP file upload of assets works again on Windows.

  • Fixed: No more cache issues for items with special characters in the root path.

An aggregated change log for 5.4.2 contains all the changes.

This release is a recommended update for all users of Magnolia 5.

Updated modules

This release includes the following new module versions:

  • Cache 5.4.2
  • Content Dependencies 1.6
  • Demo Projects 0.7
  • Enterprise Edition 5.4.2
  • Form 2.3.1
  • Imaging 3.2.2
  • Language Bundles 1.0.1
  • Magnolia 5.4.2
  • Magnolia Templating Essentials 0.6
  • Rest 1.1.1
  • Rest client 1.0.6
  • Scheduler 2.2.2
  • Site 1.0.2
  • UI 5.4.2

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: Antoine Contal, Florian Fuchs, Kees De Koning, Frank Sommer, Marvin Kerkhoff, and Mathias Lin.

How to update from earlier versions

Important changes for Magnolia 5.2 and 5.3 users


CE bundle

Modules that are no longer bundled:

  • Standard Templating Kit (STK)
  • Form
  • Public User Registration (PUR)
  • Device detection
  • Data module

EE bundle

  • Personalization is now an EE Standard feature. Previously it was available only in EE Pro. See: Editions and licenses
  • Performance features Advanced cache and Dynamic caching are EE Pro features.

Data module is no longer included

Starting with Magnolia 5.4, the Data module is no longer included. The Data module was originally developed to manage structured data such as contacts or products. Content apps, introduced in Magnolia 5.0, effectively replace the Data module. Content apps provide a more modern approach for managing any structured content item.

We removed the Data module and its data workspace from the product in Magnolia 5.4. When you migrate from Magnolia 4.5 to Magnolia 5.x, replace custom data types with content apps.

If you had STK installed

Standard Templating Kit (STK) is not included in this release. Read MTE and STK to learn if the new Magnolia Templating Essentials (MTE) is an option for you.

To keep working with the STK:

  • Bring back latest STK (2.9.1) to your bundle, along with its dependencies: 
    • magnolia-module-standard-templating-kit 2.9.1 (download)
    • magnolia-theme-pop 2.9.1 (download)
    • magnolia-demo-project 2.9.1 (download)
    • magnolia-dam-compatibility 2.1.1 (download)
    • magnolia-module-device-detection 1.1 (download)
    • magnolia-module-form 2.3.1 (download)
    • magnolia-module-public-user-registration 2.5 (download)
    • magnolia-module-data 2.3.5 (download) (See: Data module is no longer included)

      STK Dependecies
  • Exclude the new travel demo (site-definition is unique on CE)
    • magnolia-travel-demo 0.7
    • magnolia-travel-tours 0.7
    • magnolia-travel-demo-marketing-tags 0.7

    • magnolia-travel-demo-multisite 0.7

    • magnolia-travel-demo-personalization 0.7

      Travel Demo Exclusions
        <!-- declare the exclusion here -->

Jackrabbit configuration

In order to enable getting an HTML excerpt in a query result, you should update the configuration files of your Jackrabbit instances. Add the two <param/> directives within your <SearchIndex> block.

  <!-- more params here -->

  <!-- needed to highlight the searched term -->
  <param name="supportHighlighting" value="true"/>
  <!-- custom provider for getting an HTML excerpt in a query result with rep:excerpt() -->
  <param name="excerptProviderClass" value="info.magnolia.jackrabbit.lucene.SearchHTMLExcerpt"/>
</SearchIndex> file

Add the following line:

magnolia.resources.dir = ${magnolia.home}

log4j.xml addition

Add the log configuration for org.reflections

 <category name="org.apache.jackrabbit">
    <priority value="WARN" />
 <!-- Reflections library spoils logs with hundreds of harmless warnings; tries to look into native libs but none of its DefaultUrlTypes can handle them. -->
  <category name="org.reflections">
    <priority value="ERROR" />
  <category name="com">
    <priority value="WARN" />

How to update from Magnolia 5.2 and earlier

To update your project, follow the standard update procedure, then make the following changes:

  1. Update your content apps with the content app upgrade task. It automatically takes care of the following:
    • Using the content connector.

    • Updating configuration of availability rules and default rule classes

    • Updating selected action definitions with node-type based availability

  2. If you used the DAM: 
    • Replace DamManager with AssetProviderRegistry.
    • See DAM and the STK and DAM templating on how to use assets in your templates.
    • The DAM changes have no impact on the STK. There is no need to modify Freemarker scripts because the new DAM API is abstracted from STK.
  3. If you have a custom jBPM workflow:
    • In the info.magnolia.module.workflow.jbpm.JbpmWorkflowManager#completeWorkItem method, checking for present parameters is obsolete and refers to publication related workitems. The method is no longer used for completing a workitem in the new human task context. It is still valid in the context of completing service tasks, however.
    • Stop using the info.magnolia.module.workflow.jbpm.JbpmWorkflowManager#getWorkItem method. It was used to complete a work item for human tasks. Furthermore, the wrapper we initialize only holds the mgnlData map.

    • The previously hardcoded mgnlData parameter is now configurable in /modules/workflow/commands/workflow/activate/activate/parameterMapName.

  4. If you have custom widgets or Vaadin add-ons:
    • Magnolia's default widgetset was relocated to info.magnolia.widgetset.MagnoliaWidgetSet.
    • Update your webapps's file.
    • Otherwise Magnolia will automatically fall back to the new widgetset but will issue warnings during upgrade, and whenever a user logs in to Magnolia.

How to update from Magnolia 4.5 and earlier

Are you running on Magnolia 4.5 or earlier? It’s time to move to 5. Contact us for migration support and look at the migration process.

Known issues

Allocate more JVM memory

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