Magnolia 5.3 reached end of life on June 30, 2017. This branch is no longer supported, see End-of-life policy.

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

Magnolia 5.3.17 improves overall system performance and access to JCR version storage, brings a new way to navigate to a node, and fixes a bug connected with asynchronous actions.

What has changed?

An aggregated changelog for 5.3.17 contains all the changes.

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

Searching for a node by the absolute path

You can now search for a node in the workbench also by entering the absolute path in the search box. The absolute path is case-sensitive.
MGNLUI-3464

Improved access to JCR version storage

Version history of a content node is accessed only once per request. This is an interim solution to mitigate excessive access to JCR version storage while browsing through content.
MGNLUI-4020

The old constructor for CommandActionTriggerListener is deprecated

The old constructor for CommandActionTriggerListener is deprecated and kept for binary backward compatibility reasons only. Users who subclass or directly use CommandActionTriggerListener should switch to the new constructor:

CommandActionTriggerListener(String name, String successMessageTitle, String successMessage, String errorMessageTitle, String errorMessage, String errorComment, String userName, boolean notifyUser) 

(Constructor detail)

MGNLUI-4004

Updated modules

This release includes the following new module versions: 

  • Community Edition 5.3.17

  • Enterprise Edition 5.3.17

  • Magnolia 5.3.17

  • UI 5.3.17

How to update from earlier versions 

Important changes for Magnolia 5.2 and 5.3 users

If you had STK installed

If you continue to work with STK, use the new magnolia-enterprise-pro-stk-bundle as a basis for your project. It includes Enterprise Pro, STK and the old demo project. You get all STK functionality out of the box. Exclude the demo-project if it's in your way.

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.

<SearchIndex>
  <!-- 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>

log4j.xml addition

Add the log configuration for org.reflections

...
 <category name="org.apache.jackrabbit">
    <priority value="WARN" />
  </category>
 <!-- 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>
  <category name="com">
    <priority value="WARN" />
  </category>
...

How to update from Magnolia 5.2 and earlier

Unable to render {include} The included page could not be found.

How to update from Magnolia 4.5 and earlier

Unable to render {include} The included page could not be found.

Known issues

Memory consumption

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

This release – and the imaging module in particular – is know to have some issues with image generation depending on the java version used (e.g. Mac OS X and Java 8 or Linux and OpenJDK 1.7). We therefore provide version 3.1.5-java7 of the imaging module with this release. As it is not binary compatible to previous versions it is not bundled by default.  

Imaging module version incompatibilities with some OS / Java version combinations

Magnolia 5.3.17 contains Imaging module version 3.1.5. This module version has known issues in certain OS and Java environments. For example, if you use it on OSX with Java 8 the module creates images with wrong colors.

Use a special version of the Imaging module: 3.1.5-java7 if you are on:

  • Java 8 on OS X
  • Java 7 OpenJDK on Linux. (Java 7 from Oracle on Linux can use the regular imaging-module)

For further information please see:

Installing magnolia-module-imaging 3.1.5-java7

magnolia-module-imaging 3.1.5-java7 is not bundled by default. You have to install it manually.

Option 1: Maven

Maven is the easiest way to install the module. Add the following dependency to your bundle:

<dependency>
  <groupId>info.magnolia</groupId>
  <artifactId>magnolia-module-imaging</artifactId>
  <version>3.1.5-java7</version>
</dependency>

Option 2: Download and install the files

Pre-built jars are also available for download. 

For further information please see installing a module.

  • No labels