Elasticsearch 8.15.x has been tested and added to the compatibility matrix to the corresponding Liferay versions.

Note: Compatibility with newer Elasticsearch minor versions is tested in two ways:

1. Latest-Latest: Testing the latest Liferay version with the latest available minor version of Elasticsearch → e.g. Master/2024.Q3 + Elasticsearch 8.15

2. Minimum-Latest: Testing the minimum Liferay version where Elasticsearch 8 compatibility was first made available with the latest minor version of Elasticsearch → DXP 7.4 U81/DXP 7.3 U31 + Elasticsearch 8.15

This way Liferay can allow a broader deployment base to operate their stack with an up-to-date search engine version.

As Elasticsearch is usually releases a new Minor version roughly every two months, this is a recurring process and a planed activity in each quarter.

The /search and /suggestions APIs comes with the following enhancements:

• New, optional scope parameter supporting Site (Group) IDs and External Reference Codes (ERCs) in /search. The scope parameter of /suggestions has also been updated to have the same semantics.

• /search now is in RELEASE status.

• The APIs now are available under the /o/search/v1.0/ endpoint with backward compatibility for current /o/portal-search-rest/v1.0 calls through server-side forward.

Refer to the documentation for more details.

Clause Contributors configuration is now stored within the blueprint’s JSON with a smaller footprint, reducing the size of a blueprint by more than 90% when using the default setting (all contributors enabled → Enable All) or the new Disable All option.

The behavior of the different options is as follows:

• with Enable All, all current and future query clause contributors introduced to the platform will be enabled automatically. Disable All behaves the opposite way,

• with Customize, the configuration is locked to the specified contributor list.

Allow users to map Repeatable fields of a Web Content Structure already defined in Fragments and Collection Displays.

Users can select and reorder categories for a blog’s friendly URL, so they can preview the order of the categories in the friendly URL.

The configuration settings for "Autogenerate Structure Key" and "Autogenerate Template Key" have been moved from their previous location in System Settings > System Scope > Administration to a more instance-specific location under System Settings > Web Content > Virtual Instance Scope > Web Content, appearing as the first options after "Custom Token values." These options allow instance admins to control whether structure and template keys are automatically generated at the instance level.
 

External reference codes are now generated for Blogs Images and Document Shortcuts.

ERC can now also be used to update and delete these entities via their headless APIs.

Smoother Workflow for Publication Editors

The new toolbar offers real-time insights to help editors stay focused and efficient. We have improved the toolbar to provide essential context, including current publications, potential conflicts, and change history.

Enhanced User Safety and Transparency in Publications

We have implemented safeguards to guide users through complex interactions and provided clearer information about changes in the Review Changes screen. 

Boost Liferay’s platform with drag-and-drop, multi-selection, and cut/copy/paste features for easier field and fragment organization.

The upcoming Marketplace release of the Liferay Connector to OpenSearch 2.x will provide an alternative to Elasticsearch for Self-Hosted Liferay deployments.

IMPORTANT: Please note that the Liferay Enterprise Search Learning to Rank, Cross-Cluster Replication, and Monitoring applications are not compatible, and thus not supported with OpenSearch.

Enable JavaScript Client Extensions within SaaS environments to enhance customization and flexibility for administrative tasks, allowing tailored solutions directly within the platform.

Enabling users to be notified externally by allowing email notifications when a new user is assigned to a publication.

The Database Upgrade Report is now enabled by default and offers expanded information compared to previous releases.

After running a database upgrade, check the reports/ directory for reports about what occurred in the system during the upgrade. The new upgrade_report_diagnostics file includes further details to diagnose any possible issues.

Feature Status change:

Tracking events related to non-default asset types and visualizing this data on a dashboard

A pack of improvements to the usability of the logs page. Clients now can troubleshoot more effectively, be it by better handling multiple filters or by selecting/copying logs without the use of the log inspector.

Feature Status Change

The Commerce Search Results widget is going into maintenance.