We have introduced a new publication size classification feature to help users better manage and plan the publishing process, especially for "large" publications where there are many changes involved. This feature categorizes publications into three tiers: Small, Medium, and Large, based on factors such as the number of changes made and the size of the database. This will allow users to better understand the scale of their publication and take the necessary steps to avoid potential conflicts or performance issues during publishing. Publication Owners are also notified whenever a Publication has changed sizes.

Key Benefits:

• Improved Planning: With the new size classification, users can see the current "size" of their publication and allocate the appropriate time and resources for publishing. This helps avoid rushing through a publishing process that might take longer depending on the publication's size.

• Better Visibility of Potential Impact: The classification provides users with a visual indicator that highlights the size of the publication, offering transparency about what to expect during the publishing process. It also helps reduce the chances of errors or performance issues related to publishing "large" publications.

• Clear Communication: When users hover over the size classification, a helpful tooltip explains what the classification means and the potential consequences for the publishing process, ensuring users have all the information they need to make informed decisions.

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.

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

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

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.

• 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

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.

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 administrator

Allow users to move web content and document structures between environments

Key benefit:
Addresses a feature gap when moving web content and documents between environments

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.

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:

1. Customized Publisher Dashboard
2. Dedicated Publisher Workflow for New App Type
3. Personalized Customer Experience for New App Type

Liferay 7.4 introduces the ability to manage language translations directly within client extensions. This enhancement allows developers to provide multilingual support for custom labels and properties without relying solely on OSGi bundles.

Key benefits: 

• Developers can now define and manage language keys and translations within the client extension itself, ensuring that all labels and custom properties are displayed correctly across different languages.

• This feature eliminates the issue of untranslated labels with dashes, providing a consistent and professional appearance on multilingual sites.

• Simplifies the process of adding translations, reducing the need for manual intervention and external OSGi bundles, thus accelerating the development and deployment of multilingual features.

• Empowers developers to create more flexible and fully localized custom elements and themes, enhancing the overall versatility of the Liferay platform.

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.

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.

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.

Allow users to modify only the first collection display item.

This feature enable the creation of multi steps forms in Page Editor.

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.

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.

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.

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.

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.

We’ve introduced robust Content Security Policy (CSP) capabilities to enhance the security of your digital experience platform. This feature supports eight key directives, including script-src and style-src among others, ensuring secure handling of scripts, styles, images, and more. By leveraging these directives, developers can mitigate cross-site scripting (XSS) attacks and data injection risks. The CSP implementation aligns with modern web security standards, offering both flexibility and protection. Administrators can now enforce stricter security policies without compromising functionality.

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.

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.

Implemented proactive access token management with automated email notifications. Users will now receive alerts 1 month, 10 days, and 1 day prior to token expiration, allowing for timely renewal and preventing service disruptions. Notifications are automatically cancelled if a new token is generated.

Key benefits:

• Users are notified before token expiration, allowing for timely renewal and uninterrupted access.

• Reducing administrative overhead, as automated notifications eliminate the need for manual monitoring and intervention.

• By prompting timely renewals, the risk of using expired and potentially compromised tokens is minimized.

Data imports, using batch engine, now allows users to preserve content creator information (if required). Previously, imported content with batch was always assigned the user performing the import, resulting in loss of original authorship data when moving content. This update ensures accurate attribution of content ownership (if required).

Key benefits:

• Able to keep critical user information during data promotion between environments

• Can be configured separately per import process

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.

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.

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.

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. 

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.

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:

The Lodash library is being deprecated and it is not included in the bundle unless deprecation FF LPD-48975 is enabled.