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

Page tree
Skip to end of metadata
Go to start of metadata
Released on January 5, 2016

What has changed

Java updates 1.6.0_105 and 1.7.0_85 introduced strict validation of HTTP header field values. Colon (:) is no longer an allowed character, as specified in HTTP 1.1. This change broke the publishing action in Magnolia since we pass a message header that contains mgnl:deleted.

Symptom: You see the following error when you publish content in Magnolia running on 1.6.0_105 and 1.7.0_85 or later.

ERROR dule.exchangetransactional.TransactionalSyndicator: Failed to activate content.
info.magnolia.cms.exchange.ExchangeException: java.lang.IllegalArgumentException: 
Illegal character(s) in message header field: mgnl:deleted

The issue was fixed by renaming the value to mgnl-deleted MAGNOLIA-6462 - Getting issue details... STATUS MGNLXAA-95 - Getting issue details... STATUS .

Upgrade to Magnolia 4.5.27 to fix the issue or downgrade your Java virtual machine as a temporary workaround.

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

(info) This is a maintenance release of a previous major version (4.5) of Magnolia, therefore available only to Enterprise clients. Read our maintenance policy for details. The released artifacts are in the magnolia.public.maintenance.releases repository (login required).

Updated modules

This release includes the following new module versions:

  • Magnolia 4.5.27
  • Enterprise Edition 4.5.27
  • XA Activation (exchange-transactional) 1.3.11

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: Andrei Muresanu.

How to update from Magnolia 4.5.x

Follow the standard update process.

How to update from Magnolia 4.4 and earlier

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

Known issues

See: Known issues.