Feature Status Change

The "Featured Content" contributed fragment set is being deprecated and it will be removed in the future.

Feature Status Change

The widget pages are going into maintenance.

Feature Status Change

The Asset Publisher widget is going into maintenance.

Feature Status Change

Users can easily identify components that may cause performance issues in their Pages. We have added a new tab on the Page Audit to show the users the back-end render times of the different components, as well as warnings to help identify specific components configurations that may lead to performance issues. Those warnings also appear on the Edit mode, so the user is aware of possible issues during the page creation.

The AI Assistant is a versatile and powerful tool designed specifically for content creators to enhance their productivity and streamline workflows. By centralizing AI-driven content creation into a single, easy-to-use application, the AI Assistant simplifies the process of generating and managing diverse types of content. Whether you're working on blogs, Knowledge Base articles, or page layouts, the AI Assistant offers the tools and flexibility to help you work smarter and faster—all in one place.

Availability: The AI Assistant is a cloud-based application readily accessible on the Marketplace, making it easy to integrate into your existing digital ecosystem. Its cloud infrastructure ensures reliable performance and scalability, providing users with consistent and seamless access to its capabilities.

Due to the upcoming migration to Jakarta EE, we are deprecating all the current versions of our application servers to prepare for the release of the new versions that are Jakarta EE 10 compatible. This is a breaking change and so new app server versions will replace the old versions.

Deprecated:
Apache Tomcat 9
Wildfly 26.1
Jboss EAP 7.4
Weblogic 14

In 2025.Q3 we are adding support for the following application servers:
Apache Tomcat 10.1
Wildfly 30
Jboss EAP 8.0
Weblogic 15 (Pending release from Oracle)

When filtering a set of items on a Data Set, sometimes we will be interested in filtering for a field that is part of a relationship.
With this new capability, we enable users to choose to filter by children of complex objects.

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.

The Centralized Products Eligibility and Configuration Management feature empowers catalog managers to efficiently manage individual products through multiple configuration pages containing all catalog’s products. With tools for manual configuration, eligibility-based visibility, and some bulk editing, this feature ensures streamlined operations and enhanced control over product offerings. Additionally, it enables faster and smarter management of product eligibility for channels, order types and accounts.

Key benefits:

1. Improved Catalog Management Efficiency:

• Simplified product configuration editing via a centralized, flat table view.

• Streamlined workflows for managing product attributes like visibility, minimum/maximum quantities, eligibility and much more.

• Avoid duplicating products to manage specific configurations by modifying targeted configurations instead.

• Perform batch updates on visibility, eligibility, and other product attributes for multiple products, whilst inheriting base setting from the Master catalog configuration

• Leverage pre-filled default master configurations to ensure consistency and simplify product setup when adding new products in a catalog.

2. Enhanced Control over Product Eligibility and Visibility:

• Define and manage eligibility rules tailored to specific customer groups, channels, and accounts

• Quickly adjust product availability and settings for various markets and segments (e.g. B2B vs B2C).

• Streamline the management of seasonal items or time-sensitive offerings using configuration scheduling.

Enhance the user experience by allowing users to directly provision cloud applications from marketplace platform, simplifying application deployment.

Key benefits:

1. Streamlining Application Provisioning: Enable users to provision cloud applications directly from the Marketplace platform, eliminating the need for complex manual processes and without leaving the platform.

2. Intuitive User Interface: Provide an easy-to-use interface for installing and uninstalling cloud applications directly from the marketplace, including an intuitive form for inputting necessary information.

3. Efficient License Management: Offer a clear and intuitive interface for managing application licenses, ensuring compliance and optimizing resource utilization.

This release introduces a new Multishipping feature to the storefront, allowing customers to ship parts the same order to multiple addresses with a single checkout. Whether customers are sending gifts to different recipients or shipping products to various locations, the Multishipping feature offers a seamless and flexible shopping experience.

Administrators can allow multishipping in their site through a new configuration in the site’s Channel details page. The customers can access a new “Multishipping” tab in the Open Order Details page to easily manage the Delivery Groups and customize the quantity of each order item for every Delivery Group for the order before the checkout.

Please note that this feature is available through the existing “Commerce Classic Site Initializer” Beta feature flag. To enable it, open the Applications Menu → Control Panel → Instance Settings → Feature Flags → Beta.

Key benefits:

1. Easy to Setup: Multishipping can be activated for your site by enabling “Allow Multishipping” in your site’s Channel Details page.

2. Flexible Address and Delivery Management: Customers can easily set different shipping addresses or different delivery dates for the same address in the context of the same order.

This feature focuses on rigorously aligning the User Management headless APIs with the established standards and best practices. This includes:

• Comprehensive Functionality Testing: Verifying that all API endpoints (PATCH/POST/PUT) correctly update the expected fields in user records.

• Custom Field Support: Ensuring seamless integration and proper functioning of custom fields within the API interactions.

• Error Handling: Thoroughly testing error handling mechanisms and verifying that informative and user-friendly error messages are returned in all relevant scenarios.

• Data Manipulation Capabilities: Confirming the correct and efficient functioning of sorting, filtering, and other data manipulation operations within the API.

Key benefits:

• Enhanced User Experience: By ensuring the reliability and accuracy of the User Management headless APIs, we provide a seamless and efficient user experience for developers and integrators.

• Increased Developer Productivity: Well-defined and documented APIs empower developers to build integrations quickly and confidently, reducing development time and effort.

• Improved System Stability: Rigorous testing and alignment with standards minimize the risk of unexpected errors and system disruptions, leading to a more stable and reliable user management system.

• Enhanced Data Integrity: By ensuring accurate data updates and consistent API behavior, we maintain the integrity and consistency of user data across the system.

Provided an option to turn the “Out-of-date” feature on/off. When turned on (the default behavior before this release), ongoing publications created in previous Liferay versions were labeled as “Out-of-date” after the upgrade and could not be modified or published. This feature is now off by default, and users can publish these publications without Liferay support.

Key benefit:

Increase manageability over publications and the ability to publish any previous modification, including after Liferay upgrades.

The two separate option menus currently displayed in the Web Content Display widget have been merged into a single, consolidated dropdown menu for content creators. This new menu will improve the user experience by reducing confusion and unnecessary clicks, ensuring all relevant widget actions (e.g., Hide Widget, Duplicate, Export/Import, etc.) are easily accessible.

Previously, when managing complex data models, users must create scripts or code in order to make changes to multiple related objects. Now users are able to configure multiple objects as if they are one object. Related child objects now inherit permissions and account restrictions and more from the top level parent, making object management more convenient.

Key benefits:

Simplifies the management of multiple objects through a configuration on the relationship between objects

• Permissions and Account Restrictions for the child objects are inherited from the Top level parent

• API endpoints are nested under the same namespace of the top level parent

Allow users to move display pages containing Object or Form widgets across environments

Key benefit:
Addresses a feature gap when moving content pages across environments
 

Liferay Cloud now provides CI/CD support for Client Extensions on Liferay PaaS. Developers can integrate Client Extensions into their Git-based CI/CD pipelines, ensuring automatic builds and deployments alongside core Liferay services. This update enables automated validation, independent deployments, and faster release cycles for Client Extensions.

Highlights:

• Dedicated CI/CD Pipeline: Separate build pipeline for Client Extensions to prevent conflicts with core Liferay services.

• Automated Builds: Every commit triggers a new Client Extensions build, packaged as a LUFFA archive.

• Independent Deployments: Client Extensions builds deploy separately, improving release flexibility.

• Seamless Integration: Works with existing Git-based workflows on Liferay PaaS.

• Zero Downtime Deployments: Deploy client extensions without affecting the main Liferay service.

The SSL Certificate Management view now provides expiration alerts for certificates nearing expiration (e.g., within 30 days) and those that have already expired. Certificates must now be defined exclusively through the LCP.json file, simplifying management and ensuring consistency across deployments. This update reduces manual errors and ensures secure and uninterrupted deployments.

Highlights:

• Expiration Alerts: Notifications for certificates nearing expiration and those already expired, with clear visual indicators.

• Exclusive LCP.json Configuration: Certificates can only be defined through the LCP.json file.

• Improved Visibility: Organized list view showing certificate names, types, associated domains, and expiration dates.

• Proactive Management: Tools and alerts to help users maintain secure SSL/TLS configurations.

The vendor has deprecated OpenSSO/OpenAM, so there's no reason for us to keep it. The alternative, which is PingAM can be integrated using our existing OpenID connector or SAML Authentication.

With this improvement, the Data Migration Center allows users to export and import Object Entries using CSV files. Not all field types are supported but many of the most used ones are:

Supported field types: dateandtime, date, decimal, integer, longint, longtext, precissiondecimal, richtext, text and picklist.

In order to help users, only supported fields are available for exporting at the UI. As new types are allowed, they will appear available in the UI.

SCIM provides a unified, RFC compliant way to keep user/group data in sync between different applications. Liferay is a service provider and enables clients to be connected. Through the defined RESTful APIs and schemas, clients can perform CRUD operations to keep resources in sync.

Pages served by Liferay might make use of third party cookies. In order to inform Liferay to manage them as part of the user cookie consent, now Portal developers and Content creators have a way to indicate the portal about them.

In order to make Liferay aware of them, the content creator or portal developer will need to update the markup to the following:

First, indicate the type of cookie following this format:

Second, change the markup depending on the element affected:

For example, embedding a video from a video provider, will see the markup changed in the following way:

• Before: <iframe src="..." />
• After: <iframe data-src="..." `data-third-party-cookie="CONSENT_TYPE_FUNCTIONAL"  />

We are excited to introduce enhancements to streamline your cloud management experience! With our updated cloud console view, you will have a detailed breakdown of subscription metrics per environment, empowering you to manage resources more effectively. Additionally, our new storage consumption tracker offers real-time insights into project storage usage, ensuring you're always informed about quota limits.

Under all supported formats, users can select the origin and destination site of the data so it is possible to export and import object entries between any site.

This release expands the support of the Timeline History feature to Blogs, Wiki pages, Bookmarks, Forms, Knowledge base, Message boards, and Categories. The feature enhances the publication toolbar with tools to detect and manage collaboration conflicts.

• A timeline icon shows recent modifications in the same asset, which may have been done in production or parallel Publications.

• The user can view, discard, or move these changes directly from the toolbar.

• Warning icons appear to make users aware of current conflicts in the Publication.

Key benefits:

• Enhanced context for content editors and managers for a streamlined collaboration.

• New capabilities to detect conflicts before publishing time, while users may have more time to decide how to resolve conflicts without the go-live pressure.

Improved keyboard navigation and column resizing for Miller columns. Users can now navigate between columns both horizontally (deeper levels) and vertically (same level) using the keyboard. Column widths are also responsive, adapting to different screen sizes.

Added logging to indicate the completion of fragment deployments via the deploy folder. This provides better visibility into the deployment process and allows for tracking deployment duration.

There are some advantages of including a message like that, for example:

• Count the duration of a deployment
• See the fragment progress deployment until it is deployed.

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

• Fine adjustments in the User Experience when managing page components through in bulk multiselection

The updated Clay chart colour palette improves accessibility and usability by creating more contrast and adding more variations. Now users can easily distinguish charts, icons, and field sets, reducing confusion and improving clarity.
 

Key benefits:

• Now we have more design flexibility for Liferay’s current and future products.

• Accessible and distinguishable colours that will improve and unify the platform usability and UI.

The batch engine's export endpoints now support filtering for object entries. This addresses a previous limitation where filtering was not applied to object entries during batch exports. This update ensures consistent data handling and filtering behavior across all entity types.

Key benefits:

• Object entries Personalization
• Equalize capabilities for all entities

Allow applications built on top of Service Builder to leverage the benefits of the Liferay Objects framework

Key benefit:
Applications built on top of Service Builder can now be migrated to Liferay Objects

We refactored the way Liferay scripts were managed, so admins can define stricter policies like:

script-src '[$NONCE$]'; script-src-attr 'unsafe-inline';

Limitations: If a policy like the one above is configured, the parts of the product that uses a rich-text editor will not work correctly. Analyze your scenario to identify how strict your policy can be in order to make the solution work.

Now, admins can customize the configuration of the Rich Text Editors with this new client extension, allowing them to set the toolbars that are available on different applications. In the form, you will have to define the instances in which the configuration will be taken into account as well as the JS that contains the configuration:

Now users can configure the values for the following properties from settings (system, instance or site settings):

• session.timeout.auto.extend
• session.timeout.auto.extend.offset

When the Upgrade Report is enabled, the output directory of the report can be configured with the new portal property upgrade.report.dir

If this property is not set, the upgrade report can be found in the default directory:

• portal-tools-db-upgrade-client/reports for the upgrade tool.
• {liferay-home}/reports if upgrade was executed on startup.

With this feature we extending the SCIM implementation with User Group un/provisioning as well with the User Group membership un/provisioning.

Previously customers would add captchas using a TagLib. But this is no longer useful since customers are not deploying JSPs. The Captcha API enables this functionality to be used in arbitrary contexts.

Allow clients to request a quote for individual products instead of setting a price. Includes the option to use a Price List or a Promotion to price the Product as "Price on Application". There is also the ability to activate the "Request a quote" option on a fully priced cart for a particular channel.

Sell and manage SKUs by adding different Units of Measure to the SKU. Configure the Unit of Measure to optionally allow for sales in decimal quantities. Units of Measure have their own pricing and inventory. Once configured, they add to the shopping experience of the buyer who can now purchase SKUs in different Units of measure.