We integrated the Clay Table’s column visibility dropdown and column sorting functionalities into the Frontend Data Set. This makes a unified approach to table interactions across Liferay, replacing inconsistent custom implementations.
Key Benefits:
- A more standard column visibility and sorting that guarantee a more usable and predictable interaction across the platform.
- Reduces redundant code by aligning with the Clay Table’s native functionalities.
- Developers no longer need to manage multiple implementations for similar features.
- Ensures UI and UX consistency with Liferay’s design system.
Status: Release Flag (opt-in)
Related Tickets
The AMD Loader is being deprecated and it is not included in the bundle unless deprecation FF LPD-48372 is enabled.
As a result of the AMD Loader deprecation, the npm-bundler will stop working too, it is recommended to use standard bundling tools such as webpack, esbuild, vite, etc.
Status: Deprecated (previously Maintenance)
Related Tickets
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:
Key Benefits:
Benefits when CK Editor is available across all DXP, note that current effort only includes Webcontent
- Support modern web standards, including HTML5 and Content Security Policy (CSP).
- Provide a seamless copy-paste experience from external tools.
- Leverage OOTB features like the inline editor for a more flexible editing workflow.
- Adopt a supported and actively maintained version of CK Editor.
- Remove reliance on multiple editors and standardize the editing experience across Liferay DXP.
More highlights and benefits here
Status: Beta
Related Tickets
We’ve introduced a new bulk operations feature that allows you to select multiple changes within a publication and perform actions on them all at once. This feature streamlines the process of managing multiple changes, saving you time and effort when working with large publications.
Key Benefits:
- Efficiency: You can now select multiple changes and perform bulk actions (like moving or discarding them) without needing to handle each change individually. This is particularly helpful in large publications where managing changes one at a time can be cumbersome and time-consuming.
- Improved Workflow: The ability to select and execute multiple operations at once significantly reduces the number of steps needed to manage your content, improving your overall workflow and productivity.
Status: Beta
Related Tickets
More Information
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.
Status: Release Flag (opt-in)
Related Tickets
Customers very commonly deploy fragments through the deploy folder, we identified that we are missing one log once the fragment import finished. Until now Liferay added a message in the application server logs that show that the fragment import has started, but it never indicates when it finishes. Some advantages of logging when the import process finishes is that customers can check when the deployment is still in progress and when it ends, not only being informed in case of failures.
Status: Release Flag (opt-in)
Related Tickets
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.
Status: Generally Available (aka OOTB)
Related Tickets
More Information
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.
Key Benefits:
- Enhanced Buyer Experience: Buyers can shop and view prices in their familiar local currency, leading to increased trust and potentially higher conversion rates. This localized experience can significantly reduce cart abandonment caused by unexpected currency conversions at checkout.
- Centralized Currency Management: The new “Currencies” tab in the channel configuration offers a dedicated space for administrators to manage and restrict available currencies, providing a clear and intuitive interface for controlling currency settings.
- Easy Currency Selection: The new Currency Selector Fragment provides a user-friendly interface for buyers to change their preferred currency at any point during their shopping session.
Status: Release Flag (opt-in)
Related Tickets
More Information
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.
Status: Release Flag (opt-in)
Related Tickets
More Information
The Concurrent and Sync Reindex Modes, providing high-availability, introduced in Liferay DXP 7.4 Update 98 / Liferay DXP 2023.Q4 are now GA.
Reduce downtime, improve operational and resource utilization efficiency with the new Concurrent and Sync reindex execution modes providing high-availability in search capabilities while the operation is running.
Status: Generally Available (aka OOTB) (previously Beta)
Related Tickets
More Information
A new toggle has been added within the Specifications and Product Specifications sections of the admin UI.
This toggle allows Catalog Managers to easily show or hide individual specifications associated with a product. This functionality provides the flexibility to curate the information displayed to customers on product detail pages.
Key Benefits:
- Enhanced Product Presentation: Control which product specifications are visible to customers, allowing for a cleaner and more focused product presentation on the storefront.
- Improved Data Accuracy and Relevance: Hide internal or less relevant specifications, ensuring that customers only see information pertinent to their purchasing decisions.
Status: Generally Available (aka OOTB)
Related Tickets
More Information
It’s going to be available without enabling the BETA flag, and from now it’s officially supported.
Status: Release Flag (opt-in) (previously Beta)
Related Tickets
More Information
Field visibility can now be configured based on values within the same custom fragment. This enables fields to dynamically show or hide based on user input, supporting more responsive and context-aware interfaces.
This update gives teams more flexibility when building custom fragments, making it easier to support complex use cases without additional custom code.
Status: Release Flag (opt-in)
Related Tickets
More Information
With the release of Liferay DXP 2025.Q2, we are deprecating the Elasticsearch 7 compatibility due to the end-of-maintenance and upcoming EOL of the Elastic Stack 7.17. Liferay strongly recommends all customers with 7.17.x or earlier deployments to upgrade to the latest compatible version of Elasticsearch 8.x. Learn more.
Status: Deprecated (previously Generally Available (aka OOTB))
Related Tickets
More Information
To continue broading the CSP support now 2 new directives are supported: base-uri and object-src
With these two new directives support Liferay DXP covers all the directives recommended in the Google CSP Evaluator.
Key Benefits:
- Enhanced Security: Mitigates risks of XSS and data injection attacks by controlling resource loading and execution.
- Compliance-Friendly: Aligns with industry-standard security requirements, supporting stricter compliance protocols.
- Customizable Policies: Allows developers to tailor CSP directives to meet specific project or organizational needs.
- Improved Trust: Strengthens end-user trust by providing a more secure and reliable platform experience.
Supported directives with recommended values:
script-src
script-src-attr
style-src
style-src-attr
connect-src
img-src
frame-ancestors
frame-src
base-uri
object-src
Status: Release Flag (opt-in)
Related Tickets
When issues happen during maintenance periods, end users saw an unbranded default maintenance page. This leaves part of the user flow unattended, with customers unable to forward users to the correct next steps. Setting up and managing maintenance pages that work when DXP is down requires technical skills that not all customers possess, making it impractical for many.
Now we allow customers to upload a maintenance page they designed, fitting their brand and instructing customers on what to do. The implementation functions indepedently from their DXP instance so, as soon as they detect a downtime, they can enable the maintenance page in their Cloud Console to be displayed for their users while they address the issue that caused the downtime.
Status: Generally Available (aka OOTB)
Related Tickets
More Information
Managing and synchronizing content across multiple environments just became easier and more reliable. With this release, Liferay expands the capabilities of the Batch Engine by introducing two powerful enhancements:
- Batch Delete by External Reference Code – Users can now delete items using external reference codes instead of internal IDs, making batch deletions simpler and more consistent across environments.
- Import Strategy Support for Deletion – When performing a batch delete, users can now define whether the operation should be partial (stop on error) or complete (continue even if some items fail), offering more control and fault tolerance during the process.
Together, these updates streamline how teams manage bulk deletions—especially in environments that rely on external identifiers or require consistent data maintenance across staging, production, and other instances.
Key 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.
Status: Generally Available (aka OOTB)
Related Tickets
Style Books in Liferay are now explicitly tied to a specific theme at the moment of creation, using the frontend token definition provided by that theme (via OSGi or themeCSS client extension). This structural link now ensures that each Style Book can only operate within the boundaries of its associated theme, eliminating cross-theme token contamination and enforcing clearer theme-based design governance.
Key Benefits:
- Users can no longer save Style Books that accidentally combine tokens from different themes, avoiding visual inconsistencies and design regressions.
- Every Style Book now visibly shows which theme it belongs to, reducing errors and making it easier for teams to manage design assets across multiple sites.
- When applying a Style Book to a page, the system will only list those created with the same theme as the page’s current one—no more trial-and-error or guesswork.
- If a Style Book becomes incompatible with the applied theme (e.g., after a theme change), it will be automatically unlinked to prevent display issues.
- During platform upgrades, existing Style Books are automatically linked to the site’s current public theme (as defined in Site Builder > Pages > Options > Configuration), reducing manual cleanup work.
- If a Style Book is imported without a valid
themeId, the user gets a clear warning and knows exactly what’s missing to fix the import. - Style Books based on themes that are no longer deployed or no longer provide a valid frontend token definition are automatically marked as inactive—clearly flagged and non-selectable.
- The OSGi or themeCSS client extension ID is displayed for inactive Style Books, helping devs or admins identify which theme needs to be re-installed or fixed.
Status: Release Flag (opt-in)
Related Tickets
More Information
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
Status: Release Flag (opt-in)
Related Tickets
More Information
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.
Status: Release Flag (opt-in)
Related Tickets
Allow users to modify only the first collection display item.
Status: Generally Available (aka OOTB) (previously Release Flag (opt-in))
Related Tickets
Working with Global Services to identify pain points in Javascript resources distribution and unused code was the trigger to:
- Remove unused packages
- Deprecate old packages
- Set configurations to let users to not use/load some functionalities
- Create a JS size comparision report
- Create tooling to be able to split modules in smaller submodules
Key Benefits:
-
Reduced total JS bundle size → Faster portal loading
-
Reduced total exports → Faster portal loading
-
Taking as example Masterclass home page:
- Reduced JS Size in MB by 20%
- Reduced number of request by 12 %
- Mobile Lighthouse score from 52 to 56
- Desktop Lighthouse score from 70 to 77
-
Allow teams to divide modules to offer smaller entry points when they detect some part of the module is not commonly used.
-
Size report tooling able to trigger risks.
Status: Generally Available (aka OOTB)
Related Tickets
The Liferay Developer Studio installer now includes JDK 21 as a selectable option if it’s available, simplifying the initial setup and providing a more convenient and user-friendly experience for developers wanting to use the latest Java version supported by Liferay.
Status: Generally Available (aka OOTB)
Related Tickets
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.
Status: Generally Available (aka OOTB) (previously Release Flag (opt-in))
Related Tickets
More Information
Captcha engine needs to be configurable on instance level to satisfy the multi-tenant environments’ need. That has to be possible to configure them for one instance without interfering with the configuration for other instances.
Key Benefits:
Enabling CAPTCHA at the Instance level adds flexibility in configurations without affecting global settings. This supports tailored security and user experiences, and enables compliance per instance, all while retaining centralized control when needed
Status: Release Flag (opt-in)
Related Tickets
More Information
This release introduces in-context translation for all the form fields directly within the page editor. This empowers content creators to easily create localized form experiences for their users, enabling them to complete forms in their preferred language. Only designated localizable form fields will be translated, ensuring precise control over localized content.
Key Benefits:
- Faster time to publish localized forms: Translating directly in the editor reduces the steps needed to launch forms in multiple languages.
- Reduces reliance on external tools or workflows: Content teams can manage translations within the same interface they use to build pages, simplifying the process.
- Improves accuracy and consistency: Only the form fields marked as translatable are included, so there’s less risk of translating the wrong content or missing something important.
- Better experience for global audiences: Visitors can complete forms in their preferred language, which can increase completion rates and engagement.Gives teams more control over localization: Editors can choose exactly what gets translated and when, without needing developer support.
Status: Release Flag (opt-in)
This feature enable the creation of multi steps forms in Page Editor.
Status: Generally Available (aka OOTB) (previously Release Flag (opt-in))
Related Tickets
More Information
Configuring the scaling behaviour of Liferay is not simple. Customers are required to have a deep understanding of how their application’ metrics behave to set their thresholds. Since charges are also incurred depending on the hours and instances scaled, customers can feel confused on the value they are being invoiced.
That’s why we allowed for customers to set the maximum and minimum number of scaled instances in their Cloud Console scaling page. This means non-technical customers now can control how little or how much they want to spend in scaling their application. Allowing them pinpoint precision when balancing between improved user experience with more instances, and the increase in costs associated with that.
Status: Generally Available (aka OOTB)
Related Tickets
More Information
Seamlessly integrate cloud payment method apps into the DXP. Allow users to directly download and install these apps available in the Marketplace from within the DXP, eliminating the need to leave the platform. This enhanced integration ensures users have access to a wider range of payment methods, addressing potential limitations that may exist within their current DXP instance.
Available only for Payment Method Free cloud apps.
Note: Before using the feature, ensure that the user has teh right permissions to view and install the payment methods needed.
Key Benefits:
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.
Status: Release Flag (opt-in)
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.
Status: Deprecated (previously Generally Available (aka OOTB))
Related Tickets
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.
Status: Deprecated (previously Generally Available (aka OOTB))
Related Tickets
Enhancenment of the review change screen by adding a progress bar to provide clear, visual feedback during the publication process.When you initiate the publication, you’ll now see a progress bar that tracks the status of the publishing process, helping you understand how much time is left before the process is complete.
Key Benefits:
- Better Visual Feedback: The progress bar offers a clear, real-time indication of where you are in the publishing process, so you always know how much time is remaining.
- Enhanced User Experience: With the addition of the progress bar, the publishing process feels more responsive and user-friendly, providing you with a smoother workflow
Status: Release Flag (opt-in)
Related Tickets
The existing documentation for Clay components and the API Table has been inconsistent in quality, often lacking detailed explanations and practical examples. This inconsistency makes it difficult for developers to effectively utilise these components, leading to confusion and an increased number of support requests.
Key Benefits:
- Developers now have a better mechanism for generating API Tables for components, improving the overall understanding of component usage and available APIs. With detailed explanations and real-world examples.
- With this new standardised documentation practices we can ensure a uniform quality and completeness across all components.
- Clearer, more structured, and more practical documentation will reduce frustration and improve the development process.
- Clearer documentation minimizes the need for external support, freeing up resources and improving response times.
Status: Release Flag (opt-in)
Related Tickets
More Information
The Lodash library is being deprecated and it is not included in the bundle unless deprecation FF LPD-48975 is enabled.
Status: Deprecated (previously Maintenance)
Related Tickets
Publishers can now easily upload and offer low-code fragment configurations via an intuitive workflow on the Liferay Marketplace. In this initial phase, customers can download these fragments directly from the Marketplace. The next quarter will introduce seamless installation of fragments within the Liferay DXP page builder (LPD-34938).
This update also allows publishers to list Client Extensions and Composite Apps on the Marketplace. Customers can then download and install these app types directly into their Liferay instances, following the developer guidelines provided on the app details page.
Key Benefits:
- Customized Publisher Dashboard
- Dedicated Publisher Workflow for New App Type
- Personalized Customer Experience for New App Type
Status: Release Flag (opt-in)
Related Tickets
More Information
In order to add more flexibility to every execution in batch engine, we have added a new parameter ( batchExternalReferenceCode ) to be capable to send it to the backend without updating the ERC of the import task.
Key Benefits:
- Simplicity of execution with one parameter for each purpose.
- Add new capabilities for all entities that supports batch.
Status: Generally Available (aka OOTB)
Related Tickets
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.
Status: Generally Available (aka OOTB)
Related Tickets
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
Status: Release Flag (opt-in)
Related Tickets
More Information
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.
Status: Release Flag (opt-in) (previously Beta)
Related Tickets
More Information
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
Status: Generally Available (aka OOTB)
Related Tickets
More Information
Capabilities
Product
Education
Knowledge Base
Contact Us