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.
Currency Selector/Multicurrency Product Support Commerce
This feature allows buyers to actively select their preferred currency from a list of currencies enabled by the administrator for the specific sales channel they are interacting with. Once a currency is selected, all prices will be displayed in that chosen currency throughout their shopping experience.
Changing the currency automatically creates a new order in the newly selected currency.
Crucially, this feature allows merchants to better manage their international pricing strategies (e.g. smart pricing per currency), fine tuning prices when not relying on exchange rates only.
Install Cloud Payment Apps Directly from Marketplace Commerce
This feature enhances flexibility and convenience for users by allowing them to easily expand their payment method options within the DXP. Users can seamlessly discover, purchase, and integrate new payment methods availbale in the Marketplace directly from the DXP, eliminating the need to navigate external platforms or seek manual solutions. This streamlined process empowers users to quickly adapt to evolving market demands and offer a wider range of payment choices to their customers, ultimately improving their overall user experience.
Site Template Connection for Asset Libraries Sites
Connecting Asset Libraries to Site Templates allows content creators to validate new assets directly within a template before deploying them to live sites. This feature fills a critical gap where templates currently can’t access Asset Library assets, forcing users to create full sites just to test content. This inefficiency leads to errors and poor user experience.
Key Benefits
Improves Efficiency and Workflow: It saves time by letting content creators test sites and assets directly in the Site Template. This eliminates the need to create a new site for every round of testing, which is a slow and cumbersome process.
Enhances Data Integrity: This feature prevents the creation of orphaned reference links that occur when a template’s content pages point to Asset Libraries it can’t access. These broken links can cause unexpected behavior and data corruption.
Reduces UI Errors: By ensuring proper connections between templates and asset libraries, the feature mitigates UI errors that happen when editing site connections with orphaned data. This provides a more stable and reliable user interface for managing site assets.
Highlights
Site Templates can now be connected to Asset Libraries. New sites generated with a Site Template connected an Asset Library will automatically be connected that Asset Library.
Users can now download a CSV file containing the complete list of all search terms collected from a page, providing easy access for analysis and reporting
Highlights
New export feature: Users can now download a CSV file with all search terms collected from a page.
Easier analysis and reporting: The export enables deeper analysis and custom reporting outside the platform.
Enhancement to previous update: Builds on the improvement from LPD-26181, which made all search terms visible in the Search Terms card.
Update Usage Page for SaaS Customers Personalization
To reduce confusion and improve transparency for SaaS customers, we’re updating the Analytics Cloud usage limits page. SaaS users will now be redirected to the Customer Portal when they access the Usage Limits menu in AC. This ensures they see the correct consumption metrics associated with their plan: Anonymous Page Views (APVs) and Monthly Active Logged-In Users (MALUs) as previously, the usage page displayed default limits based on Page Views (PVs) and Known Individuals (KIs), which do not apply to SaaS customers.
Highlights
Redirect for SaaS users: SaaS customers are now redirected to the Customer Portal when accessing the "Usage Limits" page in AC.
Accurate metric display: Customers will see the correct usage metrics—APVs and MALUs—instead of outdated PVs and KIs.
Eliminates confusion: Removes misleading limits that previously appeared for SaaS users.
Prevent sharing of AC tokens between environments Security
To prevent token duplication in lower-level environments, we’re introducing a new portal property. When set to true in the portal-ext.properties file, this property will automatically clear the AC connection on startup. This ensures that if the production token is copied to a UAT environment during migration, it will be removed on startup—preventing data contamination, eliminating the need for manual disconnection, and preserving the integrity of the AC connection in production.
Utility page for cookie policy lists and describes all cookies in use. Users can add and update cookies in the list with the cookie object. When the cookie manager is enabled, Analytics Cloud only tracks data from users who consent to statistics cookies.
Customizable Permissions for Publication Owners Sites
This feature introduces customizable permissions for the "Owner" role and other user roles within Publications, allowing administrators to define exactly who can publish, edit, invite users, or manage permissions at the publication level. A new "Permissions" section has been added to the "Enable Publication" settings, along with an "Edit Permissions" button that opens the Publication permissions modal. Admins can now revoke the "Publish on Production" permission for any user on a publication-by-publication basis. Once revoked, the change is reflected immediately, the user will no longer be able to publish content to production, and the revoked status is saved and visible in the publication permissions settings. Only users with the Admin role or the specific permission to manage publication roles can make these changes. This enhancement provides granular control over user capabilities within each publication, helping teams better manage their content workflows and avoid accidental publishing.
Key benefits:
Safeguard Production Changes: Blocks users from publishing or modifying production content via Publications unless explicitly granted.
Enhanced Role Governance: Admins now have complete oversight of publication-level permissions for all user roles, including Owners.
A new warning has been added to the Publications configuration screen to alert admins when "Sandbox Only" mode is enabled but publication Owners still have permission to publish. In this scenario, any user who creates a sandbox publication can still push changes to production, potentially bypassing the intended protection. The system now displays a warning message when this configuration is detected, guiding admins to review and adjust permissions for the Owner role accordingly.
Key benefits:
Prevent accidental publishing by alerting admins when Owner permissions still allow publishing in Sandbox mode.
Increase visibility into role-based permissions that may unintentionally allow production changes.
Request Navigation Menu via External Reference Code Sites
We enabled navigation menus to be retrieved using their External Reference Code (ERC) through Liferay’s headless APIs. This enhancement enables a more precise and consistent identification of navigation menus across sites and environments, particularly useful in multi-site and content migration contexts. It complements the existing functionality by providing an alternative for IDs.
Key benefits:
Improved data consistency: ERC-based retrieval ensures references remain valid across environments.
Easier data migration: ERCs streamline the export/import process across different Liferay sites by providing a consistent identifier.
Better filtering options: Admins can now export navigation menus based on creation or modification date range, giving finer control over headless operations.
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. CK Editor 5 has been made available in DXP under Beta Feature Flag. (FF-11235):
Access Marketplace Fragments Directly from the Page Builder Sites
To help users build pages faster with more design options, Liferay now allows direct access to Marketplace fragments from within the page builder. In addition to native and already-installed fragments, users can now browse and install additional fragments available on the Marketplace—expanding their library without leaving the editor.
This gives customers the ability to use pre-built fragments shared by Liferay, technology partners, and the broader community, making it easier to create flexible, high-quality pages with less effort.
Object one-to-one Relationships in Page Builder Sites
With the introduction of the new CMS approach for managing object entries, the existing 1:1 nested object entry functionality in the Page Builder (LPD-20213) is now deprecated and will be removed. This feature has proven to be complex and underutilized by end-users.
The new approach, being developed under the CMS 2.0 initiative, will offer a more intuitive user experience for object relationships, allowing users to configure child structures as repeatable or non-repeatable.
Standardized Side Panel Component in Clay React Platform
The newSide Panel (also known as Info Panel) is a reusable Clay React component that provides a consistent, accessible, and responsive sliding panel for use across Liferay applications. It supports common use cases such as content editing, navigation, and contextual information display.
Key benefits:
We established a uniform look and feel across all instances of the Side Panel, reducing cognitive load and improving usability and also ensured compliance with accessibility standards (e.g. keyboard navigation, ARIA roles), enabling inclusive design by default.
Reduces redundant implementations and streamlines maintenance by offering a centralised, reusable component.
Reinforces design consistency and reusability across the product ecosystem.
The addition of new translations and locales ensures that users in Myanmar, Bosnia & Herzegovina, Ireland and Serbia can interact with the platform in their preferred languages or regional variation.
Key benefits:
Tailors the user experience for specific markets and regions, improving relevance and usability
We made the platform more inclusive by expanding language and locale options.
The Accessibility Checker Component is being deprecated as part of our effort to improve accessibility tooling and simplify our component library. After evaluating its usage and overlap with other accessibility solutions in Liferay, we found it to be redundant and we stopped using it long time ago.
Blueprint Collection Provider Extended Type and Subtype Support Search
By displaying the blueprint's results in a Collection Display fragment (available since DXP 7.4 U88 as Beta), you can leverage search to return your assets dynamically, and reap the benefits of the fragments toolbox to lay out the page.
Enhanced Type Support
Now, the Blueprint Collection Provider supports asset types (like structured web content and Objects) allowing to map specific item fields beyond the the basic information fields (i.e., asset entry fields) in fragments, depending on the Searchable Types settings of your blueprint.
When selecting Web Content Article as Searchable Types, the subtype selector becomes available
Selecting an available Web Content Structure (Subtype) as Searchable Types in a blueprint
Web Content Article with a specific Web Content Structure selected as subtype in a blueprint
Mapping a Web Content Structure field from a Blueprint Collection Provider with a specific return type in a fragment
Web Content Article with no subtype restriction selected as Searchable Type in a Blueprint
Mapping Web Content Article field from a Blueprint Collection Provider with a specific return type in a fragment
Document with a specific subtype (Document Type) is selected as Searchable Types in a blueprint
Mapping Document Type fields from a Blueprint Collection Provider with a specific return type in a fragment
Object type selected as Searchable Types in a blueprint
Mapping Object fields from a Blueprint Collection Provider with specific return type in a fragment
Message Boards Message selected as Searchable Types in a blueprint
Mapping basic information fields from a Blueprint Collection Provider with return type Asset in a fragment
Opt-in Collection Provider
Configure if a collection provider should be published when creating a new blueprint, or later via the Configuration tab or through the action menu in the table view in Blueprints.
Enabling a blueprint as a Collection Provider on creation
Enabling/disabling a blueprint as a Collection Provider via Configuration later
Enable blueprint as a collection provide via the action menu in the Blueprints admin
Benefits
Access and map type specific item fields fields in fragments for an extend range of types including Web Content Article and structures, Documents and Document Types and Objects.
Limit searches to specific subtypes via Query Settings in Blueprints
Liferay Self-Hosted deployments can update their Elastic stack to this version. For Liferay PaaS projects a new Elasticsearch image will be provided under Liferay Cloud’s Docker Hub account.
Liferay Tomcat Bundles and Docker Images ship with Elasticsearch 8.18 as the sidecar search engine.
Benefits
The Elasticsearch server runtime included in Liferay DXP Tomcat Bundles and Docker Images (aka. Sidecar Elasticsearch, located under [Liferay-Home]/elasticsearch-sidecar) is provided as a convenience for local development and testing only. It is neither suitable nor supported for production.
Frontend Data Set Cell Renderer CX Upgrade Low/No-Code
Addressing prior limitations, custom cell renderers created with Client Extensions now provide full row data access. This empowers developers with expanded options and greater flexibility for their implementations so they can create a renderer for a cell and include data from all the row mixing the contents. For example, you can create a cell to calculate the volume of a furniture good based on the different dimensions fields.
Benefits
Expand developer capabilities to create more powerful Client Extensions for Data Set Cell Renderers
The Data Set has a revamped experience in terms of selection that also provides a quicker way to contextualize the user interaction.
When facing any of the visualizations (table, card, row) the user can click on the item body to perform single selection. This enhances rapid selection and better interaction.
Benefits
More modern selection pattern that follows industry trends
Clearer states for the user to distinguish when an item is:
With this release, the Liferay DXP is now built with the modern, cloud native technology provided by the Jakarta EE 10 platform. The legacy Java EE platform will no longer be supported on this and future releases, allowing Liferay DXP to continue to evolve and build innovative solutions to meet your business needs.
Benefits
Liferay DXP now certified on Jakarta-based application servers: Tomcat 10.1, Jboss EAP 8.0, and Wildfly 30. This also provides support for newer specifications such as Portlet 4.0, Servlet 6.0, and Spring Framework 6.0. The update paves the way for faster feature development and rapid security fixes available in the modern Java enterprise ecosystem.
PostgreSQL migration now supports all source databases Platform
The Beta feature to migrate databases to PostgreSQL has been updated to support all supported database types. PostgreSQL is the Liferay recommended database server, especially for PaaS and SaaS users and Liferay provides this tool to simplify the migration.
Benefits
Users on MariaDB, SQL Server, Oracle DB, and IBM DB2 are now able to migrate their database to PostgreSQL. The tool was previously limited to users on MySQL. Now all users have access to the DXP and Cloud performance benefits of using PostgreSQL.
The DXP database upgrade process has been enhanced with a suite of verification checks that are executed before any data modifications are made.
These checks have minimal impact on the overall upgrade process execution time, but they can be optionally disabled with the property upgrade.database.preupgrade.verify.enabled=false
Benefits
It can be frustrating when a database upgrade process executes a large amount of modifications to the system and then fails due to a misconfiguration, prompting the need to restore the database and restart the process. Now the database upgrade process will perform a series of configuration checks and report them to the user before modifications are needed. This prevents the need to always restore the database or document library before re-running the upgrade. The upgrade report will still be generated if the preupgrade checks fail, and provide details of any issue.
This feature adds workflow support for Root Models. Child object definitions which are part of a root context will inherit the workflow configurations of the root parent. This simplifies the administration of objects which are part of root model applications.
FriendlyURL support for Object Entries Personalization Low/No-Code
Friendly URLs, also known as clean URLs or pretty URLs, are web addresses that are human-readable and search engine-friendly. They typically use descriptive keywords instead of cryptic file names or query strings. Users can define a friendly URL for entries, making them more human readable and search engine friendly.
Enhanced Batch Deletion Flexibility with External Reference Support at Site Scoped entities Integration
New improvement to make easier the way to promote content among environments. Liferay expands the capabilities of the Batch Engine by introducing a powerful tool for site scoped entities:
Batch Delete by External Reference Code( Site Scoped entities ) – Users can now delete items using external reference codes instead of internal IDs, making batch deletions simpler and more consistent across environments.
Now, covering all scopes, the way teams manage bulk deletions is more simple and safe because it is based on the use of external identifiers so the consistent data maintenance across staging, production, and other instances is possible without changing between environments
Key Business Benefits
More reliable environment synchronization: External Reference Codes allow you to delete the same entities across different environments without depending on internal IDs, reducing risk of mismatches.
Simplified bulk deletion workflows: Deleting large sets of data is now easier, with fewer manual steps and lower chance of errors.
Greater control over delete operations: Choose whether the process should stop on errors or complete fully—helping teams tailor the behavior to fit their operational needs.
Increased resilience and fault tolerance: Deletion jobs are less likely to fail entirely due to minor issues, ensuring smoother maintenance processes.
Consistent support across entities: These enhancements are available for all entity types supported by the batch engine, making them broadly applicable across different use cases.
Context: Both features are part of the “Promote content among environments” strategic initiative.
RESTBuilder generates Jakarta compatible code Integration
Describe the feature:
With the migration to Jakarta, RESTBuilder needed to adapt to be able to generate the classes with the right namespace.
Use the javaEEPackage property to define whether to use javax as namespace (for pre-Jakarta versions of Liferay) or set the value to “jakarta” for newer versions.
Upgrade /siteId and /by-external-reference-code path patterns Integration
In our headless APIs, we have many endpoints with /siteId/{siteId}/ as part of the path for many entities. Now, siteId not only accepts the siteName or the siteId as value, but also the External Reference Code of the site can be used.
Delete Application Data Before Importing in Staging Personalization Integration
Until now, when executing a staging import, users could choose, prior to the import, to delete all existing information in the destination environment. This option has been deprecated due to its low usage (verified directly with clients and partners) and the high risk it entails, as deletion affects not only the elements already in the import but also their related entities. This could lead to the loss of necessary information or the possibility of some entities becoming disconnected from the rest, making both the import and error resolution extremely complicated due to the lack of a list of affected elements. There will not be a substitution, so the alternative will be to delete the elements manually, either from the UI, API or directly in the database before performing the import.
Copy as new update data strategy in Staging Personalization Integration
When executing a staging import, users could choose different strategies to update the data. ”Copy as new” was one of the option, that allow the importer to create new items if they were already in the system. This could lead to create more elements than expecting that later on the user would need to clean. We are deprecating this feature in order to simplify the UI and avoid users to do mistakes.
Extension point for integrating custom CAPTCHA solution/service Security
The Captcha extension point allows customers to integrate custom or third-party CAPTCHA solutions into their system, enabling greater flexibility and control
Key benefits
Removes restrictions on supported CAPTCHA providers
Empowers customers to choose and configure CAPTCHA solutions that best suit their needs
Enhances extensibility and adaptability for diverse use cases and compliance requirements
Just-in-Time (JiT) user provisioning for OIDC and SAML enables automatic synchronization of user data, including user groups at every authentication event. This ensures that user profiles are always up to date
Key benefits
Ensures real-time synchronization of user attributes and group memberships
Reduces administrative overhead by eliminating the need for pre-provisioning
Enhances security and compliance with up-to-date access control
Improves user experience by streamlining access without delays
