We added External Reference Codes for Categories and Tags and their associated API’s, improving their portability for data migration scenarios.

Highlights: 

• Users can now perform CRUD operations using a Tag’s ERC through its headless API (Keyword)

• Users can now perform CRUD operations using a Category’s ERC through its headless API (TaxonomyCategory)

• 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

Official release of Liferay Data Sets, moving from Beta to Release! Data Sets are a powerful and flexible way to retrieve, manage, visualize, and interact with structured data in Liferay DXP. Built on top of Objects and leveraging Liferay’s robust ecosystem, Data Sets exemplify the “build Liferay with Liferay” philosophy. With seamless integration with compatible Headless APIs, administrators can easily configure Data Sets and empower end-users with a rich, customizable experience for consuming and interacting with data.

Key benefits:

• Retrieve Data: Fetch information from any compatible Headless API to use as a Data Set source.

• Manage Flexibility: Administrators can customize what parts of the API response are included, along with filters, sorting options, and available actions.

• Visualize Data: Multiple visualization options make it easier than ever for end-users to consume data meaningfully.

• Enable Interaction: End-users can interact dynamically with data using the filters, actions, and tools configured by administrators.

To ensure the quality, stability, and modernity of Liferay DXP, we've updated to React 18, bringing significant benefits in security, performance, and compatibility. This update is critical to maintaining DXP's status as a robust and future-proof platform.

Key benefits:

• Security Enhancements: Older library versions can expose vulnerabilities. Upgrading to React 18 mitigates these risks by incorporating the latest security patches.

• Performance Improvements: React 18 introduces features like concurrent rendering, which enhances responsiveness and load handling for better user experiences.

• Enhanced Compatibility: Upgrading ensures DXP aligns with modern tools and frameworks, minimizing integration challenges and future-proofing our development processes.

• Continued Support: Staying current with React’s ecosystem ensures ongoing access to community updates, bug fixes, and innovations.

This release introduces a new Stripe Tax connector, now available in the Liferay Marketplace, designed to integrate directly with Liferay Commerce’s core transaction flows. This connector enables dynamic, automated tax calculation powered by Stripe Tax, replacing manual or static tax setups with an automated, accurate, and globally compliant solution.

Once installed and configured, the connector calculates taxes automatically at checkout based on the buyer’s shipping address and the seller’s tax registration settings. The integration is especially valuable for businesses operating in tax-complex regions like the United States, where tax rates and rules can vary dramatically between states, counties, and even cities.

By leveraging Stripe Tax through this connector, merchants benefit from seamless tax compliance, transparent pricing for buyers, and simplified tax reporting for administrators.

Key Benefits:

• Automated Real-Time Tax Calculation
  Eliminate manual tax logic. Taxes are calculated dynamically during checkout using Stripe’s robust tax engine, ensuring accuracy based on product, location, and applicable tax laws.
• Supports Complex U.S. Tax Scenarios
  This is particularly beneficial for merchants selling into the U.S. market, where tax complexity is high. Stripe Tax automatically accounts for state, county, and city-level rules—reducing the burden on sellers.
• Improved Buyer Experience
  Buyers see clear tax breakdowns at checkout, building trust and preventing cart abandonment due to surprise charges.
• Streamlined Operations for Sellers
  Taxes are included in transaction records without seller intervention. Sellers can access tax-inclusive transaction histories and focus on business growth.Streamlined Operations for Sellers
  Taxes are included in transaction records without seller intervention. Sellers can access tax-inclusive transaction histories and focus on business growth.

This feature introduces the ability to define and manage custom address types as sub-types of the main address categories—Billing, Shipping, or Billing & Shipping—in Commerce - Account Addresses. This significantly enhances address management flexibility for B2B businesses operating across multiple locations, departments, or stakeholders.

Previously, address management was limited to only two hardcoded types: Shipping and Billing. With this release, businesses can now define additional sub-types (e.g., Ship-to Party, Sold-to Party, Ordering Address, Payer, Disti Branch Officer, DC Delivery Address) through a newly introduced Picklist-based configuration system. These sub-types are configurable and can be mapped directly under one of the three main categories.

This approach ensures compatibility with common ERP systems like SAP, which already support a range of address roles in the order-to-cash process.

Key Benefits:

• Flexible Address Management: B2B businesses can model complex customer hierarchies and logistical operations with precision. Define specific address roles that align with real-world use cases without being restricted to just billing and shipping.
• ERP Integration Ready: Custom sub-types allow seamless data synchronization with ERP systems like SAP, avoiding manual workarounds and ensuring that address roles like Sold-to, Bill-to, and Ship-to are preserved in external systems.
• Improved Order Fulfillment & Compliance: Tailoring address types to real operational needs supports more accurate order routing, fulfillment, and financial processing, while also aligning with internal compliance and invoicing requirements.

Guests now have the option to sign in or sign up during the checkout process, directly from the mini-cart. Once logged in, users can either select an existing account or create a new one, ensuring that they can move through the purchase flow smoothly without disruptions. Upon setting the account, guests, now logged-in users, will be redirected to the checkout, making the transition to completing the purchase seamless.

Additionally, if a guest decides to sign in without necessarily checking out, the guest cart will now be merged with their account after logging in. This ensures that any items added to the cart during the guest session are retained when they sign in or select an existing account, improving the continuity and experience for returning users.

In this release a new type of Data Set called System Data Sets is introduced, which will allow admin users to clone Java/Code Data Sets, making them editable and customizable through the Data Set Manager, which allow to customize any administration part of DXP built with a customizable Java/Code Data Set.

In this release the Data Sets from Order Pages have been made available as System Data Sets:

• Pending Order Items

• Placed Order Items

• Order Returns

• Pending Orders

• Placed Orders

In the next releases more and more Data Sets will be added to the list.
 

Key Benefits

• This epic increases the flexibility of Liferay DXP by enabling partial customization of previously hardcoded Data Sets.

• Admins will have more control over the user experience, enhancing the platform's ability to meet diverse and evolving business requirements.

• This also reduces the need for custom development efforts to modify or replace hardcoded Data Sets.

When an admin user is managing a Data Set, they might create sorting options, filters and actions. Until now, if the admin user chose not to show them to the end-user, they had to be deleted. From now on, these sub-entities can be deactivated, hiding them from the end-user without losing editing progress.

Key Benefits:

• Easier management of sub-entities without requiring deletion and recreation.
• Improved usability by allowing admins to configure visibility dynamically.
• More flexibility in defining experiences without modifying underlying data.

Liferay DXP now allows on-demand migration of Virtual Instances across different installations, making existing environments portable and easier to manage—especially in cloud-based deployments. Whether you're moving from on-premise to Liferay SaaS, or just shifting between environments (like UAT to Production) on the same installation, this feature simplifies the process by allowing instances to be migrated, instead of the entire database.

Feature can be enabled with Beta Feature Flag: LPD-11342

DXP is now certified for use with the MySQL 8.4 database version. Also applies to 2025.Q1 LTS.

Key Benefits:

Allows users to update to the latest LTS version of MySQL database. As an LTS release, MySQL 8.4 is the most stable and predictable version for production environments since it receives bug fixes and security patches for an extended period from Oracle. This longer support window reduces the need for frequent major upgrades.

With the upcoming release of Jakarta and new application server versions, Liferay is focused on becoming a full feature enterprise platform. Supporting Java 17 prevents usage of Java 21 features that will improve performance and reduce cloud costs. We are marking Java 17 for deprecation as we plan to fully focus on Java 21 in 2026.

The JS Component Support Tabs (data-toggle="liferay-tabs" API ) is being deprecated and it is not included in the bundle unless deprecation FF LPD-47713 is enabled.

Feature Status Change

The Activities Widget is being deprecated and will be removed in the future.

Feature Status Change

The Directories Widget is being deprecated and will be removed in the future.

Feature Status Change

The Group Statistics Widget is being deprecated and will be removed in the future.

Feature Status Change

The Liferay Theme tasks are being deprecated and they will be removed in the future. The feature is based in Gulp 4 which is also deprecated. Customers are encouraged to use third party tooling to substitute it.

Feature Status Change

The Liferay Theme generator is being deprecated and it will be removed in the future. Customers are encouraged to use Theme Client Extensions or third-party tooling to generate themes.

Feature Status Change

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

Feature Status Change

Scope of the widgets in a page: Page, Site or Global is being deprecated and it will be removed in the future.

Feature Status Change

The widget pages are going into maintenance.

This feature allows warehouse managers to define granular eligibility rules for accounts and account groups to access specific warehouses. This enables fine-grained control over which customers can see and purchase inventory from which warehouses.

Key benefits:

1. Improved Inventory Management:

• Prevent unauthorized access to inventory data.

• Strategically control product visibility based on inventory quantities and stock levels.

• Optimize inventory allocation across customer segments.

2. Enhanced Customer Experience:

• Provide a more relevant and personalized shopping experience.

• Improve customer satisfaction by prioritizing access for key customer segments.

3. Increased Revenue:

• Generate higher revenue from valuable customer segments by prioritizing their access to inventory.

4. Reduced Lost Sales:

• Minimize lost sales due to stockouts by limiting product visibility for certain customer groups.

Added External Reference Codes for references in widget configurations in Commerce and User Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.

Key benefits:

References within the following page widgets now use External Reference Codes instead of internal IDs:

• Cart

• Cart Summary

• Category Content

• Commerce Addresses

• Commerce Category Navigation

• Mini Cart

• Open Carts

• Option Facet

• Order Forecasts Chart

• Organization Management

• Placed Orders

• Product Comparison Bar

• Product Comparison Table

• Product Details

• Product Downloads

• Product Publisher

• Search Results(Commerce)

• Specification Facet

We added External Reference Codes for references in widget configurations in Content Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.

Highlights:

References within the following page widgets now use ERC’s instead of internal ID’s:

• Announcements
• Web Content Display
• Category Filters
• Questions

We added several API endpoints for Documents & Media to improve programmatic management of these entities.

Highlights:

• Users can now add, delete, and retrieve document types via headless API (DocumentDataDefinitionType)

• Users can now add, delete, and retrieve document metadata sets via headless API (DocumentMetadataSet)

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.

This improvement allows users to customise the appearance of their Liferay instance more effectively with new properties in the .yaml file for Theme CSS and CSS Client Extensions.

Key benefits:

• Admins can personalise the interface for both the admin panel and the entire platform.

• A more cohesive, branded appearance will improve usability and satisfaction for all users.

• Allows fine-grained control over where customisations are applied.

Elasticsearch 8.17 has been tested and added to the compatibility matrix.

Liferay Self-Hosted deployments can update the Elastic stack to this version. For Liferay PaaS projects, as usual, a new Elasticsearch image will be provided under Liferay Cloud’s Docker Hub account.

As it was first highlighted in the Release Notes of 2024.Q3, per Elastic’s product lifecycle, Elasticsearch 7.17.x versions are supported and maintained until Elasticsearch version 9 is released.

While Elastic does not provide specific release dates for future releases, for Elasticsearch 9.0.0, the new release is anticipated in early calendar year 2025.

Compatibility with Elasticsearch 8 is available on Liferay DXP 7.4 U81+: Operating Liferay 7.4 GA/Update 81+ with Elasticsearch 8 - Liferay.

Note: The Elasticsearch 8.x compatibility is provided through the bundled Elasticsearch 7 connector and the REST API Compatibility of Elasticsearch 8.

Users now have the ability to update folder names and other details without being able to modify the workflow settings. This ensures there are no security issues and that all content within the folder follows the correct workflow process.

Key Benefits:

• Granting “Update” Permissions: Granting “Update” permissions to a role enables the user to edit a folder's properties, like its name and description.

• Granting “Advance Update” Permissions: Granting “Advance Update” permissions to a role enables the user to update the workflow associated with a folder. The folder's properties, such as name and description fields, remain disabled and cannot be edited.

Users can now generate and download a PDF report of their event analysis, enabling seamless sharing of key insights with stakeholders.

Key Benefits:

• The PDF format ensures consistency when sharing insights across teams.
• The feature is accessible directly from the Event Analysis interface, simplifying the download process. 
• Users can optionaly choose to add a date range while downloading their pdf

It is now possible to view where a document is being displayed on a page.

Key Benefits:

• Users can now view a document’s usages through the “View Usage” action in the entry. This will show all locations where the document is mapped or displayed to the end user

Microsoft no longer supports Sharepoint versions 2010/2013. See SharePoint Server 2013 - Microsoft Lifecycle and Microsoft SharePoint Server 2010 - Microsoft Lifecycle.This feature has been in maintenance mode for a very long time and there is just a very small user base. Considering the high costs for us in terms of tests maintenance, we decided to deprecate it.

As customers increasingly adopt HTML5 for content creation, there's a growing need to upgrade the current rich text editing capabilities and CKEditor 5 has been selected as the default editor for Liferay DXP to meet this demand. In this release CK Editor 5 has been made available in DXP and installed in four different experiences under Beta Feature Flag. (FF-11235):

• Web Content

• Object entry (editing a Rich Text Field)

• Document Types (when adding a Rich Text field)

• Metadata Set (when adding a Rich Text field)

• Forms

• Element Sets

After this, CK Editor 5 will be included in other areas and experiences in the near future:

• Page Builder

• Commerce

• Web Content Description

Key Benefits:

Benefits when CK Editor is available across all DXP, note that current effort only includes Webcontent

1. Support modern web standards, including HTML5 and Content Security Policy (CSP).

2. Provide a seamless copy-paste experience from external tools.

3. Leverage OOTB features like the inline editor for a more flexible editing workflow.

4. Adopt a supported and actively maintained version of CK Editor.

5. Remove reliance on multiple editors and standardize the editing experience across Liferay DXP.

More highlights and benefits here

Improved the usability, functionality, and consistency of bulk actions in Frontend Data Sets across Liferay DXP. The selection behaviour of items has been refined, ensuring consistency in visualization modes, enhancing bulk action visibility, and making interactions more intuitive and efficient for end users.

Key Benefits:

• Preserve selection between pages of items so the user can easily select items from multiple pages.
• Add Select All and Clear buttons to allow users to easily work with large amount of items.
• Added contextual menu with access to all bulk actions available.
• Highlighted bulk actions to easily access more common actions.

This feature aims to enable all fields of an object to be localizable and displayed according to the user's chosen locale settings.

Key Benefits:

• The localization feature will support all existing locales in the system

• Custom Object entries and Modifiable System Objects entries

• Localization settings are now managed at the individual field level

Data from third party systems can now be managed in DXP through the use of Proxy Objects. Customers can now rely on a transversal OAuth 2 with proper SSO implementation to display data in DXP with the use of Liferay’s low code frontend application building capabilities.

Important: Because the data does not persist in Liferay’s database, some limitations are placed on proxy objects. Learn more.

This feature provides a way for customers to consume object validations and manage the experience for end users as they require.

Key Benefits:

• In multi-step forms, end user data can be validated in each step without persisting the data