Release Notes
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
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.
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.
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:
|
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.
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:
|
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.
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.
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 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.
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 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
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.
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.