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

What has changed since Magnolia 5.0.2

Magnolia 5.0.3 is the first enterprise release in the 5-series. It adds some some enterprise modules such as workflow and multisite and brings the 5-series closer to the 4-series in terms of feature completeness. See 5.x Modules Migration for module status.

This release also includes fixes and enhancements to the Community Edition.

Changes in Community Edition

The release delivers the following CE fixes and enhancements:

  • Fix an issue that caused the action definition parameters to not be correctly set.
  • Fixes an issue where cmsfn.isEditMode() returned true when a page was accessed outside of the Page Editor.
  • Pulse now preserves the latest message state when you navigate away from the message. For example, a workflow message is still displayed in pulse if you go see the page and come back to Pulse.
  • Fix an issue where template variations could not override the renderType of their parent element.

Changes in Enterprise Edition

The release delivers the following EE fixes and enhancements:

  • Add enterprise modules such as multisite, transactional activation, LDAP, advanced cache, diff and content dependencies.
  • New jBPM workflow engine.
  • New license key:
  • Change the groupId of EE bundle artifacts from info.magnolia to info.magnolia.ee-bundle.
  • Rename the Extended Templating Kit module to Multisite module since multisite was the only feature left in the module.
  • Use Maven's import dependency scope in Magnolia webapps and bundles. It allows you to import dependencies from Magnolia POMs.
  • Put only a single copy of the Magnolia webapp in the bundle and have the startup script to copy it on first start.

An aggregated change log for 5.0.3 contains all the changes.

Updated modules

Community Edition modules:

  • Magnolia 5.0.3
  • Magnolia UI 5.0.3
  • Magnolia Standard Templating Kit 2.5.3
  • Magnolia Data Module 2.0.2

Enterprise Edition modules:

  • Magnolia Enterprise Edition 5.0
  • Magnolia Workflow Module 5.0
  • Magnolia Blossom Module 3.0
  • Magnolia Transactional Activation 2.0
  • Magnolia Extended Templating Kit 2.5
  • Magnolia License 1.4
  • Magnolia Diff Module 1.3
  • Magnolia Content Dependencies Module 1.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.

Is it ready for production?

You can start a new project with the 5.0.3 release. Bear in mind that not all modules that worked in 4.5 are yet available in 5.0.3. Try the new release and see if it already has the functionality you require.

The first minor release is 5.1 which will be out at the Magnolia Conference in September. It will close the gap between 4.5 and 5 further.

Missing functionality includes enterprise features such as:

  • Multisite support
  • Approval workflow using inbox notifications. Activation of content works.
  • Diff view for comparing changes between versions
  • Soft locking
  • Forum

How to update from Magnolia 4.5

We recommend that you wait until release 5.2, which is due later in 2013, before updating your project. The 5.2 release will include migration scripts, migration support and migration documentation.

How to migrate from Magnolia 4.4

Updating from 4.4 is a three-step process:

  1. Update your project first to the latest 4.4 series release. At minimum, update to Magnolia 4.4.6, not older.
  2. Migrate your project to 4.5. Understand that migration is not a simple update but an effort that needs to be planned ahead. Follow the procedures described in Migration.
  3. Wait for the 5.2 release later this year. Then update your project to 5.2

Known issues

Java 7 on Mac OS X

Java 7 crashes on Mac OS X. This is not a Magnolia specific issue. Java 7 on OS X is not in our certified stack. We recommend that you use Java 6.

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