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