This release supersedes Magnolia 5.6.4. The previous release contained a reference to a snapshot version by mistake.
You can now request a specific language to return. For a content item that references other items, you can now get direct URLs to them. If the referenced item is an asset, you can get the URL to the asset in the size that you need via the asset renditions.
The new Tour Finder in the travel demo uses the REST delivery endpoint to demonstrate a single-page app in Magnolia.
This release also expands on the problem reporting introduced in 5.6.3 to help developers maintain clean projects. Now any missing or deprecated page templates or themes referenced by a site are reported. A new Deprecated level in the Definitions app Problems view helps developers find and review deprecated items easily.
Changes for developers
destinations). In response to the visitor's choices, it instantly refreshes a list of tours without reloading the web page.
Requesting a localized variant of an item
When sending a REST request to the delivery endpoint v2, you can use the
lang parameter to specify which language variant you want returned in the response. Sending
lang=all fetches all language variants available in the JCR repository.
In parallel to the
lang parameter, you can also request a specific language version by setting and sending the
Accept-Language header with the request. For more information, see Requesting localized content with the delivery endpoint.
Referencing assets, creating links to items and to asset renditions
Another improvement to the delivery endpoint v2 is that you can create relative links to any referenced item and you can also reference assets. If a referenced asset resides in the Magnolia DAM, the asset resolver can generate links to asset renditions (variations).
Multiple REST endpoints
In the delivery endpoint v2
JcrDeliveryEndpointDefinition class you can configure not just one but several endpoints. For more information, see Delivery endpoint API v2 configuration.
REST results are unsorted by default
Until now the results provided by the delivery endpoint were sorted alphabetically on node names (same as with the
ORDER BY LOWER(NAME(t)) statement in the JCR-SQL2 query) even though no
orderBy parameter was set in the request URL.
With delivery endpoint v2, the results are returned unsorted. This however does not mean "in natural order" since many other aspects may be involved, such as the setting of the
respectDocumentOrder property or index consistency. For more information, see Apache Jackrabbit Search and Rebuilding the Index.
orderBy parameter works without the direction attribute
Previously, setting the
orderBy parameter in a REST request without specifying the sort direction produced an error. This has been fixed in this release. If no direction is specified (
desc), the system applies
Reloading file system resources referenced with symlinks
This Magnolia release also comes with an important bugfix for developers of light modules. The existing contents of a directory linked via a symbolic link is now reloaded by Magnolia when you add the link to a running Magnolia instance.
Reporting of deprecated and non-existing definitions from site definitions
The Definitions app now reports references to non-existing and deprecated page template and theme definitions referenced from site definitions.
Even though the Definitions app shows the
sites registry, you cannot define or decorate a site via YAML.
Fixed full text search of documents
Indexing and full text search of documents works again as expected after we upgraded third-party dependencies for Apache POI and Apache Commons Compress.
See the 5.6.5 changelog for all the changes.
Please be aware that the version numbers for the Magnolia main and UI projects are not in sync with the version number of this release.
If you are updating from an earlier version:
Projects based on an older maven archetype may not build correctly starting with Magnolia 5.6.3 - because the version of the Magnolia main modules is not the same as the Magnolia bundle anymore. If you experience a problem, please update your project parent pom.
- Community Edition 5.6.5
- Content Editor 1.1.4
- Content Tags 1.0.2
- Definitions app 1.1.2
- Demo Projects 1.2.3
- Enterprise Edition 5.6.5
- Form 2.4.1
- Groovy 2.6.2
- Jackrabbit Backup 2.2.2
- LDAP support 1.10
- Magnolia 5.6.4
- Multisite 1.3.3
- Pages 5.6.3
- Personalization 1.5.2
- Publishing 1.0.3
- REST Client 1.5.2
- REST Framework 2.1
- Site 1.2.2
- Synchronization 1.8.2
- Templating Essentials 1.2.1
- Third-party library BOM 5.6.3
- UI 5.6.3
- UI 5.6.4
- Weblogic 2.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: Espen Jervidalo, Bret Lederle, Pietro Pagani, Christophe Rodriguez, Frank Sommer and Tom Wespi.