Release Notes
This new feature introduces a composable, fragment-based way to build and customize the account selector experience.
It enables developers and business users to assemble panels, buttons, and account/order views without hardcoded dependencies.
The main orchestrator fragment manages navigation, dropdown behavior, and interactions across configurable panels, delivering greater flexibility, improved user experience, and fine-grained control directly from page building.
With Liferay's New Headless Content Management System (CMS), creating, organizing, and publishing content is simpler because all content management tasks are brought together in a single interface. Your content is independent of its presentation, allowing you to reuse it across sites, pages, and APIs. You can work with articles, documents, media, and more, while taking advantage of features like global asset views, organized spaces, and cross-site publishing. Thanks to Liferay Objects, the CMS provides flexible content structures and ensures a smooth, consistent authoring and publishing experience. Key Benefits:
|
To prepare for Microsoft’s removal of Azure Access Control Service (ACS) for SharePoint in Microsoft 365 starting April 2, 2026, we’ve evolved the SharePoint connector authentication model. This ensures customers can continue accessing SharePoint seamlessly after April 2026, without disruption.
Key Benefit:
Ensures uninterrupted access to SharePoint after ACS deprecation
Aligns with Microsoft’s supported and future-proof authentication standards
Improves long-term security and compliance
The permissions-check modal introduced during content publishing is now optional. While this feature provides additional control by allowing users to review permissions before publishing, we recognize that it may add unnecessary steps for some workflows. Customers can now publish in just one step without having to check the permissions first.
Key Benefits:
Greater flexibility to adapt publishing workflows
Maintains enhanced permission control where needed
Avoids unnecessary steps for existing or streamlined flows
Respects different customer contexts and usage patterns
This epic delivers a comprehensive solution for exporting and importing vocabularies and categories with associated data across Liferay environments, tackling potential roadblocks to ensure a smooth and efficient migration process.
This epic delivers a comprehensive solution for exporting and importing tags with associated data across Liferay environments, tackling potential roadblocks to ensure a smooth and efficient migration process.
This feature introduces “Lazy References” to ensure import success regardless of deployment order. If an imported item references a missing Vocabulary or Category, the system creates a temporary “incomplete” dummy object. This special status allows the main content import to succeed immediately. The project’s focus is managing the status lifecycle to allow a smooth transition of these incomplete dummies to a fully approved state when the complete taxonomy object is imported later.
We’ve added a Maintenance badge to several applications related to the current CMS. This informs users that these applications are in maintenance mode, meaning no new feature development is planned, as we continue focusing on our new CMS.
The Question Widget is a legacy application that was primarily maintained to support Liferay Ask. With the recent migration from Ask to Discuss (Liferay's new forum platform), this widget is no longer needed. Therefore, the Question Widget is being deprecated to reduce technical debt and ongoing maintenance costs.
As Liferay continues to invest in platform flexibility and enterprise stability, empowered by Jakarta EE, we are pleased to share that DXP is now certified for use with Oracle WebLogic Server 15c. This application server will be fully supported for Enterprise tier customers. Additionally, to empower DXP deployment on Oracle’s server, we have released a dedicated DXP WAR file optimized for WebLogic 15.
Key Benefits:
Modernized Tech Stack: Provides compatibility with the latest release from Oracle, ensuring your infrastructure is ready for the next generation of enterprise Java applications.
Simplified Installation: Streamlined deployment provided through the dedicated Weblogic WAR file.
Security Compliance: Moving to WebLogic 15c ensures you stay ahead of the security and patch lifecycles of older, non-Jakarta-based application servers.
Platform flexibility and enterprise system support is important to our users. With this release we have expanded the Compatibility Matrix to include some new environments. Application Servers:
Databases:
Operating Systems:
Key Benefits:
|
Liferay has released a new version of the Liferay Faces (JSF) portlet bridge framework that is now compatible Jakarta EE, allowing users to migrated JSF portlets for usage with 2026.Q1.
Key Benefits:
Jakarta Support: JSF portlets can now be used on DXP with Jakarta namespace.
Simplified Migration: Liferay continues to support JSF 2.3-built portlets to make it easy to migrate to Jakarta with minimal breaking changes.
PrimeFaces support: Liferay has enabled usage of PrimeFaces portlets with Liferay DXP.
AI Rules Files (.workspace-rules) are now available OOTB with new Liferay Workspaces. These files provide AI agents with the Liferay-specific logic, context, and guardrails needed to generate accurate, best-practice customizations for Liferay DXP. These rules are symlinked for automatic discovery by Claude Code, Cursor, Gemini, GitHub Copilot, and Windsurf. Blade 8.0 or higher is required to automatically set up new Liferay Workspaces with the AI Rules Files. Key Benefits:
|
In order to run integration tests locally, customers previously had to manually identify and set the correct test dependency versions for their corresponding Liferay version in build.gradle, which was a tedious and error prone process. We now provide a dedicated Integration Test Bill of Materials (BOM) file, release.dxp.bom.test, that automatically provides the correct test dependency versions and is included by default with Liferay Workspaces.
Key Benefits:
Liferay Workspaces will automatically pull in the integration test BOM.
Customers can omit the versions when declaring test dependencies in build.gradle, the integration test BOM will provide the correct versions automatically for their Liferay version.
Previous: testIntegrationImplementation group: "com.liferay.portal", name: "com.liferay.portal.test", version: "24.5.1"
Now: testIntegrationImplementation group: "com.liferay.portal", name: "com.liferay.portal.test"
In order to assist customers with upgrades to newer Liferay versions, Blade and Workspace users now have a dedicated gradle command For customers migrating to Jakarta for the first time, the Jakarta Migration Tool Key Benefits:
This tool simplifies the process for users migrating their code to newer Liferay versions, providing:
|
This feature introduces a cleaner, more flexible empty-state experience in the Frontend Data Set by allowing the search bar and management bar to be hidden when no content is present.
Key Benefits:
The Dataset Consumer is able to hide Data Set management bar by just clicking a toggle
If toggle is enabled, management bar won’t be rendered in case of a “real” empty state
This can be configured both in system and custom datasets
This feature introduces User Views in Frontend Data Sets, allowing end users to personalize how data is displayed by saving and reusing their preferred filters, sorting, and visualization mode across the platform.
Key Benefits:
Users can easily create and switch between custom views tailored to their needs
Personalized views can be saved and reused, improving productivity and consistency
Administrators can control whether Custom Views are available per Data Set
This feature improves how Frontend Data Set view state parameters are represented and managed within URLs, introducing a cleaner, more readable, and user-friendly encoding format. It replaces the previous fully URL-encoded JSON structure with a compact and maintainable serialization strategy while refining how and when view state parameters are persisted. These improvements ensure that URLs remain functional, easier to share, and simpler to debug.
Key Benefits:
Administrators, developers, and end users benefit from significantly shorter and more readable URLs that accurately reflect the current Data Set view state.
View state parameters are only added to URLs when users modify the Data Set view, reducing unnecessary noise and improving clarity.
Data Set states can be reliably shared, bookmarked, and restored across sessions and browsers.
Navigation behavior is improved by establishing push-based history updates as the default, enabling better navigation tracking and user experience.
From now on, most JavaScript files in Liferay DXP have hashed file names generated at build time. For example, a main.js file may appear at runtime with a randomly generated hash value in its name, such as This hash value represents a unique version of the file, so the browser can identify that the file’s contents have not changed. This allows the file to remain in the browser cache indefinitely when the infinite caching strategy is selected. In addition, the frontend caching infrastructure now supports both infinite caching and time/validation-based caching strategies. These strategies can be configured through Instance Settings. For those JavaScript files that cannot be hashed because they are generated at runtime by the server depending on some parameters, a new configuration is available in DXP to define their TTL and the option to add the Also, hashed files have a fallback strategy based on TTL + eTag if they are requested using their canonical name. This acts as a fallback for import map errors or legacy portlets that are not aware of hashed file names. Key Benefits:
The new Liferay DXP caching strategy for JavaScript files improves performance and stability. 1. Faster Page Loads: 2. Elimination of Stale Resources: 3. Reduced Origin Server Load: 4. Cache busting: |
This change promotes the Save Data Set view state to be recoverable when navigating back to it epic from Beta to General Availability, confirming the feature is stable and fully supported.
This change promotes the CK Editor 5 epic from Beta to Release.
"Promote Content among Environments" is a Liferay initiative that takes content promotion to the next level. By implementing a significant infrastructure change (based on Headless Batch APIs), processes are substantially streamlined, optimizing existing processes and adding new ones that enable more secure, stable, and efficient content promotion. Now you can promote elements at the instance level, such as Object Definitions, Picklists, or Roles, and freely export and import Object Entries with any scope. With the new Lazy References infrastructure based on External Reference Codes, relationships are maintained and updated regardless of the order of importation. Furthermore, the new Report List provides a comprehensive and detailed record of everything that happened during the import process. This new report is essential for new entities because import processes will run from start to finish without stopping with the first issue, reporting all errors so you can resolve them collectively instead of having to address them individually with each run. For non migrated entities, the behavior will be the current one finishing the process with the first error. Key Benefits:
|
We are evolving how content is managed. To align with our new Promote Content standards, the legacy Propagation feature for Site Templates is being retired. In its place, we are building a new solution that prioritizes data integrity by allowing for targeted overwriting of existing information. This change ensures your site updates are more predictable and efficient.
Bridge Your Portal Data and Marketing PowerThe HubSpot Connector for Liferay is a powerful integration tool designed to eliminate data silos. It creates a seamless, automated bridge between your Liferay DXP portal and the HubSpot CRM, ensuring your sales and marketing teams always have the most up-to-date information at their fingertips. Stop wasting time with manual data exports. By connecting Liferay Objects directly to HubSpot, you can ensure that every new contact, company, or lead captured in your portal is instantly synced and ready for your next automated campaign. Key Benefits:
|
This update introduces a full commercial lifecycle for Client Extensions, allowing Publishers to list and sell high-value extensions, and Customers to purchase and deploy them directly into their DXP instances.
Key Benefits:
For Customers (Buyers)
Instant Capability: Acquire complex, production-ready features without long dev cycles.
Integrated Procurement: Purchase and manage licenses directly through the Liferay Marketplace.
For Publishers (Partners/Devs)
Monetization Stream: Turn their custom-built tools into a recurring revenue stream by reaching the global Liferay ecosystem.
Market Visibility: Showcase their technical expertise to a captive audience of enterprise-level decision-makers.
This set of epics aim to complete and strengthen the content page promotion and management system. We have developed necessary endpoints for various page types and implemented a comprehensive catalog of page elements and fragments. Additionally, we enhanced the data architecture through the integration of scopes and secure references. Together, these efforts ensure content integrity during import, export, and staging. The resul is a more stable page editor that handles lazy references and provides a seamless experience across all site components.
Key Benefits:
Comprehensive Site Coverage: By enabling promotion for all page types, organizations can ensure their entire digital presence is synchronized across environments without manual gaps.
Enhanced System Resilience: The implementation of scope-aware identifiers and error-detection spikes prevents broken user experiences caused by missing references or deleted assets during content staging.
We’ve introduced the Multiselector Dropdown Fragment to make managing large amounts of data effortless for users. Instead of scrolling through a long list of checkboxes, It keeps your design clean while allowing users to easily find what they need, manage their choices as removable tags, or clear all selections with a single click—all configurable directly within the page editor.
Key Benefits:
Instead of overwhelming your page with a long, messy list of checkboxes, this fragment tucks all your options into a single, sleek input field. This saves valuable screen space and keeps your design looking professional, even when dealing with dozens or hundreds of choices.
Users no longer have to scroll and hunt for the right option. With built-in filtering, they can simply start typing to find exactly what they need instantly. Selected items are neatly organized as tags, making it easy for users to review or change their choices with a single click.
We’ve added more flexibility to how you build forms by letting you choose the best interface for every field. You can now switch between different visual styles within the same fragment type—for example, displaying a list of options as a multi-selector checkbox for easy scanning or a multi-selector dropdown to save space. This allows you to customize the user experience to fit your layout perfectly with just one click.
Key Benefits:
Enhanced UX Personalization: Designers can select the most intuitive input method for their audience, such as a drag-and-drop zone for files versus a standard button, without changing the backend data structure.
Streamlined Design Consistency: By offering multiple visual interpretations of the same object fields, the platform allows for diverse form layouts that still maintain strict data integrity and mapping standards.
Users can customize the field layout to streamline the content creation experience.
Users can create complex data models by nesting structures and enabling repeatable fields within a structure definition.
Users can utilize CKEditor 5 as the default rich text interface when editing content within Page Builder fragments.
Users can utilize CKEditor 5 as the default rich text interface for 'Description' fields across the platform.
Standardise the pattern so “selected/current items” and “available items” always appear in the same side, and reordering is always done in the same place and in the same way.
Key Benefits:
Users don’t have to re-learn the UI depending on the screen.
Reduces cases where users reorder or move the wrong list because the meaning of left vs right changes.
Consistent patterns speed up repetitive configuration work, especially for power users managing multiple sites/instances.
Predictable placement improves keyboard and screen-reader expectations and makes the interaction easier to document and test.
Aligns one of the most visible admin patterns across Site and Instance settings, improving overall quality perception.
We’ve redesigned the Global Menu to deliver a more intuitive, scalable, and visually engaging navigation experience across Liferay DXP. This update introduces a single, unified entry point to access all platform capabilities, reducing fragmentation and making it easier to move across features. As part of this transformation, the DXP Control Panel has also been rebuilt with a cleaner UI, improved information architecture, live filtering for faster discovery, and a simplified landing home with contextual shortcuts. Key Benefits:
|
We are excited to announce the arrival of the Native Elasticsearch 8 Connector. This isn't just a version update; it’s a foundational shift that ensures Liferay DXP remains at the cutting edge of search and AI technology. As it was communicated in 2025, Elasticsearch 7 has reached end-of-life on Jan 15, 2026 and is no longer available as a supported search engine for Liferay DXP 2026.Q1 and onward. Part of this shift, 2026.Q1 ships with a native Elasticsearch 8 connector, replacing the previous Elasticsearch 7 connector, which had provided a compatibility plus mode to operate Liferay DXP with Elasticsearch 8 servers since 2023. Key Benefits:
The Bottom Line: This update transitions Liferay from "compatibility mode" to "innovation mode," providing a faster, smarter, and more stable search foundation for your enterprise. |
Elasticsearch 8.19 is now the minimum compatible Elasticsearch 8 minor version.
Key Benefits:
Operating Liferay DXP with the latest available minor version of Elasticsearch 8 (8.19) that includes security fixes and enhancements.
Up-to-date, secure Liferay-DXP stack
Performance improvements
A new, dedicated Scope configuration is now available within the Query Builder, allowing administrators to precisely limit search results to specific Sites, Asset Libraries, and Spaces. Key Improvements
Behavior Note: Scope Hierarchy When a scope is defined within a Blueprint, it acts as a strict boundary.
|
Search Blueprints as Collection Providers (GA) The ability to use a Search Blueprint as a Collection Provider has moved from Release to General Availability (GA). This integration allows you to leverage the advanced filtering and boosting logic of Blueprints directly within Collections to display highly tailored results. Key Enhancements
|
Semantic Search with OpenAI Integration (GA) [For LES Subscribers only] Semantic search, powered by direct integration with OpenAI as a text embedding provider, has officially moved from Beta to General Availability (GA). Configuration & Opt-in To ensure zero impact on existing installations, this feature remains opt-in. To begin leveraging semantic search, administrators must manually configure the connection:
Status of Other Providers While OpenAI is now GA, other text embedding providers (such as txtai and Hugging Face) remain in Beta. These can still be accessed and tested by enabling the existing feature flag (
|
The OpenSearch 2 connector is transitioning to Generally Available (GA). A new version of the application is expected to be released on Liferay Marketplace for 2026.Q1 later in Q1 (by the end of March, tentative).
Assets that are currently being modified within a publication are now protected from deletion in production by default. Previously, this behavior was optional and disabled by default. It is now enforced automatically to ensure greater stability and data integrity when working with publications. Key Benefits:
|
Reviewers can now directly access the desired asset edition screen when clicking Edit or Edit in Production from the Publications Review Change screen.
Key Benefits:
|
A new Pending approval publication status and filter option are now available in the Publications list. Publications automatically receive the Pending approval status when at least one linked asset is still in Draft or Pending workflow status. A dedicated filter allows users to quickly identify publications that are not yet ready to be published. Key Benefits:
|
Liferay has enhanced the Publications List and Review Changes screens by introducing automated state persistence for table configurations. Publication users can now save their customizations for their view—including filters, column ordering, and sorting. These preferences are captured directly in the URL, allowing users to return via browser navigation, save specific views as bookmarks, or share their exact configuration with teammates via a simple link. This update eliminates the need for repetitive manual setup, allowing users to maintain a consistent and focused workspace.
Key Benefits:
Seamless Workflow Continuity: Supports a more fluid navigation experience. Users can jump between different portal management areas and return to Publications without losing their place or their preferred data view.
Personalized Review Experience: Empowers different roles to configure the Review Changes screen exactly how they need it to perform their specific duties.
Enhanced Productivity: By persisting the table state, the platform reduces the mental load on users, helping them focus on the content changes themselves rather than the interface management.
Liferay has significantly enhanced how content and experiences are managed with the new CMS, Objects, better content promotion between environments, and many other features that didn’t exist when the Publications' framework was designed. Instead of redesigning the framework for this new scenario, we are developing a new set of tools that will still support Publications' use cases with even greater efficiency and flexibility:
Moving Publications into maintenance mode allows us to continue supporting current users while focusing on this new strategy and the next generation of publishing tools. |
We have implemented a new translation status feature in the web content editor, labeled "Translating," which provides information about the number of translated fields and those still requiring translation. This feature helps users to quickly identify areas needing translation. Additionally, all translatable fields, including metadata, are now conveniently displayed on the left side of the screen, reducing the likelihood of overlooking them.
Users can readily spot content that is not visible to Guest users through an icon, whether it's in list or table view or within the web content editor. Additionally, this feature is accessible in the item selector, empowering users to discern which content is not viewable by Guest users.
Now it is possible to easily identify the content you have created and any recent content you generated. This enhancement streamlines and optimizes this workflow.
Easily configure the friendly URLs for the different asset types, updating URL separators. In addition to that, now users are able to set categories within a blog’s friendly URL and easily identify by the URL what is the main topic of the page they are visiting.
This feature aims to refine the Analytics Cloud Usage Page. Alongside UI enhancements for a better user experience, we focused on enhancing data accuracy and real-time precision. Our efforts aimed to eliminate data discrepancies and prioritize transparency for the users.
Key Changes:
To promote pricing transparency, we removed the outdated prices from the Workspace settings and implemented a clear message prompting users to reach out to their Customer Success Manager for information on upgrading their plan.
Aiming to simplify the interface and highlight pertinent subscription details, some changes were made to the UI of the Subscription and Usage menu, focusing on displaying relevant information to the customer related to their current plan.
To create Sign In, Forgot Password, and Create Account utility pages, it's necessary for these three views of the Login portlet (i.e., Sign In widget) to be available as individual widgets, which can be placed on pages separately. As a result, Sign In, Forgot Password, and Create Account are now accessible as separate widgets.
It's worth noting that the Sign In widget retains its previous functionality.
We aimed to facilitate seamless navigation between various Utility pages, whether there are multiple or just one.
It allows users to map fields on the first level of related elements or any hierarchical structure through a tree view which is searchable and expandable.
In addition, it is possible to map leaf fields, the common use case, but also parent fields which include all the children data to be rendered through a Client Extension.
Until now the Data Set was always rendered as a table with one column for each mapped field. From now on, the admin user can define up to three different visualization modes for the same data: Table, List and Cards.
These visualization modes share the configurations about: filters, actions, sorting and pagination. However, each visualization mode can have different mapped fields decided by the admin users.
Also, a new Settings tab to select the default mode has been added.
Final users will be able to view the visualization modes created by Admin Users and they will be able to change between them to discover the data in the way they want.
The Data Set for actions has been improved to provide new capabilities to the users:
The autocomplete attribute grants the user agent permission to provide automated assistance in filling out form fields. This feature can significantly speed up the form-filling process, especially for repetitive or standard information like names, addresses, and email addresses. This also allows screen readers which use standard attributes such as autocomplete to assist users navigating websites.
Incorporating the HTML autocomplete attribute into your forms is a simple yet powerful way to enhance user experience. By leveraging autocomplete suggestions, you can streamline the form-filling process, reduce errors, and ultimately create a more user-friendly environment. Experiment with different values, test across browsers, and watch as your users appreciate the improved efficiency of your forms.
When publications go out of date, they are completely useless and all changes made to them can not be leveraged in any capacity. The changes in this feature allow publications users to move changes from an out of date publication to another publication. This allows users to salvage changes after an upgrade.
This feature prevents portal from being unusable when a change-tracked entity being modified in a publication is removed from production. If an entity is being modified in a publication, it cannot be removed from production. If a deleted entity in a publication is being modified in another publication, the publication with the deletion cannot be published.
Boost the performance of reverting changes , when the DB has huge amount of records. This way the usability of Publications further increases.
Until now, for a translatable object fields, there was no way to get the values in different languages and always returned the default one. With this change, by adding the Accept-Language header, users can get the selected values properly. This change affects to Rest API and GraphQL.