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.

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.

 
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

1. 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.

2. 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.

3. 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

1. New export feature: Users can now download a CSV file with all search terms collected from a page.

2. Easier analysis and reporting: The export enables deeper analysis and custom reporting outside the platform.

3. Enhancement to previous update: Builds on the improvement from LPD-26181, which made all search terms visible in the Search Terms card.

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

1. Redirect for SaaS users: SaaS customers are now redirected to the Customer Portal when accessing the "Usage Limits" page in AC.

2. Accurate metric display: Customers will see the correct usage metrics—APVs and MALUs—instead of outdated PVs and KIs.

3. Eliminates confusion: Removes misleading limits that previously appeared for SaaS users.

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.

Highlights

1. Prevents data contamination between environments

2. Eliminates the need for manual disconnection

3. Preserves production data integrity

Analytics Cloud Cookie Control (LPD-10588)

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.

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.

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):

• Web Content Description field

• Page Builder:

  • Paragraph

  • Forms → Rich Text

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.

Users can translate text fields from Objects when using Text Input Fragments in Form Containers.

Dynamically show or hide configuration fields in a custom fragment based on user input values.

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.

The new Side 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.

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

Description

• Embedded items now include actions (when the headless entity supports)

• Filter by Workflow Status via the filter request parameter.

  • Filter field: status

  • Examples: status eq 0, status eq 0 or status eq 2

Benefits

• Invoke available actions on the returned items

• Filter results by workflow status