A new notification capability has been added to the Orders Questions & Answers feature (formerly Commerce Order Notes) to improve timely communication between Buyers and Order Managers, ensuring that Order Managers are notified when a Buyer adds a comment and Buyers are notified when an Order Manager responds. To support both user notifications and email notifications, we created a new System Object: Commerce Order Note. By leveraging Object Actions, it is now possible to trigger notifications directly from the Questions & Answers flow. On the Commerce Order Note object, we introduced two terms — Order Note Recipient Emails and Order Note Recipient IDs, to dynamically determine the recipients of email and user notifications. The recipient selection logic respects channel-level configurations, including Open Orders Visibility Scope, Placed Orders Visibility Scope, ensuring that notifications are sent exclusively to users who are authorized and within the configured visibility scope. Additionally, a new toggle was added in the Channel configuration — Enable Notifications User Scope — which, when activated, ensures that only the buyer user who is the owner of the order receives notifications for responses from Order Managers. This ensures that notifications are both permission-aware and contextually relevant, maintaining privacy while improving responsiveness. Key Benefits:
|
Release Notes
Within the Orders Admin Panel, a new “Recalculate” button has been introduced in the Order Summary. This button enables administrators to recompute overall order totals following manual adjustments to order lines, executing a controlled summary-level recalculation without re-triggering the full pricing engine. Key behavior:
Key Benefits:
|
We have introduced account-scoped order visibility to ensure that Order Managers only see and manage orders belonging to the Accounts they are assigned to. This enhancement includes:
By combining the Order Administrator role with the Manage Accounts Scoped Orders permission, Order Managers can directly manage the full order lifecycle for their assigned Accounts through the Administrative Panels—without exposure to unrelated Account data. 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.
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:
|
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 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.
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 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.
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. |
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 (
|
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. |
A user-centric consent management approach where consent preferences are securely stored on the server and linked to a registered user account, enabling a persistent, cross-device experience while maintaining user control and compliance.
Key Benefits:
Seamless experience: Users are not repeatedly prompted for consent across devices or after clearing browser data.
Stronger compliance & control: Consent is centrally managed, auditable, and can be optionally restricted by the user for cross-device storage.
A configurable consent access mechanism that allows administrators to enable and customize a persistent floating icon, giving end users continuous access to the Consent Panel after the initial banner interaction.
Key Benefits:
Continuous user control: End users can easily revisit and modify or withdraw their consent at any time.
Flexible configuration: Administrators can enable, disable, and customize the floating icon to match site needs and design.
Adding OpenID Connect and Facebook authentication options to the Sign-In utility page.
We’ve introduced the ability to import and export categories and tags directly within the new CMS. This feature allows you to manage your site’s organization in bulk, removing the need to create or edit every individual item one by one.
Key Benefits:
Saves Time: Quickly set up or update large lists of categories and tags through a single file upload rather than manual entry.
Better Accuracy: Easily audit and clean up your tags in a spreadsheet to ensure consistent naming and organization across your entire site.
This epic is focused on implementing targeted improvements to the import/export translations functionality. In the past, due to resource and time constraints, we were not able to fully optimize the user experience for this feature. This work is aimed at addressing those known shortcomings, specifically by improving the UX and the functionality of key buttons and drag and drop for uploading items, to make the process more intuitive and user-friendly.
The product currently relies on a legacy CMS alongside a newly developed CMS, requiring parallel maintenance, duplicated functionality, and fragmented content workflows. This increases operational cost, slows down feature delivery, and creates inconsistencies in how content is managed and consumed.
This epic aims to inform the users that we are putting the current CMS in maintainance mode, preparing the field to add the feature flag in next releases
Key Benefits:
Inform the users about the features set as In Maintenance
During the reviewing of the CMS experience and fixing bugs, we detected some product gaps and improvements that can make the user experience smoother, so this epic’s goal is to tackle them to ensure a stable and reliable user experience.
Key Benefits:
Allow to search members in a space for non admin users
Improved category creation
Filter by space for content structures
List view for Space home view
We have introduced several new bulk actions to the CMS to help you manage large volumes of content more efficiently. Instead of handling items individually, you can now perform complex administrative tasks across multiple selections simultaneously.
Key Benefits:
Assign Workflow for Content Structures in bulk
Expire content in bulk
Delete versions of a content in bulk
Export translations of different content in bulk
As part of improving asset management efficiency, this epic introduces bulk Copy and Move actions for assets within the CMS. These actions will allow content creators to organize and duplicate multiple assets at once, across locations in Spaces they have access to. The functionality should maintain the same user experience principles and behavior as the existing single-asset Copy and Move actions, extended to handle multiple selections simultaneously.
Key Benefits:
Copy assets in bulk
>Move assets in bulk
The Questions 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 Questions Widget is being deprecated to reduce technical debt and ongoing maintenance costs.
Search re-indexing has been optimized to deliver shorter re-index windows, especially for Objects-heavy deployments. In testing against production databases and architecture, we observed re-index improvements of 2x or more across the evaluated datasets, with gains reaching up to 10x on specific workloads. The optimizations primarily targeted improvements that scale with the volume and complexity of Object data being indexed.
Key Benefits:
Shorter re-index windows reduce maintenance overhead and downtime risk
Validated on a production-equivalent distributed architecture
Largest impact for Objects-heavy installations
Building on the automated database repair routines introduced in 2025.Q4, Liferay DXP continues to expand the set of repair processes that run during the upgrade. Based on additional research into customer upgrade issues, new repair routines automatically identify and correct further sources of database inconsistencies, orphan references, and invalid data — before they cause upgrade failures or performance bottlenecks. These repair routines remain targeted at known issues with data structures only, keeping your critical data content safe. Details of each repair process continue to be provided for review in the Upgrade Report after the database upgrade completes.
Key Benefits:
Minimize risks for current and future upgrades
Automates data maintenance
When using the Liferay DXP Database Partitioning feature, the system now enforces strict access controls ensuring only the authorized database partition is accessible for any given request. This completes foundational security work and extends proper enforcement to all Liferay entry points, including Headless APIs and Client Extensions.
Key Benefits:
Prevents unauthorized cross-partition data access in multi-tenant environments
Ensures consistent partition access enforcement across all Liferay entry points (Headless, Client Extensions)
This is a major version release that brings important platform updates and security enhancements alongside several necessary breaking changes to ensure the continued delivery and stability of Liferay Developer Studio.
Key Benefits:
Eclipse Platform Update: The underlying platform was updated to Eclipse 2025.12, taking advantage of the latest features and security updates from Eclipse. For more information, please see https://eclipse.dev/eclipse/news/4.38/.
Blade Version Update: The packaged Blade version was updated to 8.0.1-SNAPSHOT.
From now on CK Editor 5 will be the default rich text editor present in Liferay DXP. For those customers with custom plugins or other particularities over CK Editor 4 that don’t want to upgrade yet, they can enable the deprecation Feature Flag (FF-11235) to have CK Editor 4 as default in DXP.
Note: CK Editor 4 still remains the default editor on some of the DXP features, those which are in Maintenance Mode such as Knowledge Base or Blogs, these experiences will not be migrated to CK Editor 5.
From now on CK Editor 5 will be the default rich text editor present in Liferay DXP.
Note: CK Editor 4 still remains the default editor on some of the DXP features, those which are in Maintenance Mode such as Knowledge Base or Blogs, these experiences will not be migrated to CK Editor 5.
This release rounds out the Pages Management APIs with new endpoints, broader page-type coverage, and refinements to how references and scopes are handled. The updates close long-standing gaps — supporting more page types end-to-end, expanding the catalog of page elements and fragments exposed through the API, and hardening the data architecture around scopes and secure references. The result is more reliable imports, exports, and staging across every site component.
Key Benefits:
Broader API coverage: every page type is now supported end-to-end, not just the subset covered before.
Fewer surprises in staging: scope-aware identifiers catch missing references and deleted assets before they break the live site.
Consistent behavior across sites, staged environments, and imported content — the API no longer behaves differently depending on the page type.
We've refined how users discover and install Marketplace fragments from inside the Page Builder. Browsing, previewing, and installing partner and community fragments now feel native to the editing flow—fewer clicks, clearer discovery, and less context switching between the editor and the Marketplace. Native, already-installed, and Marketplace-available fragments now live side by side in the same experience.
Key Benefits:
Faster discovery and installation of Marketplace fragments without breaking the editing flow.
Clearer distinction between native, installed, and Marketplace-available fragments, so builders pick the right one at a glance.
Less context-switching: everything happens inside the Page Builder instead of jumping to the Marketplace and back.
The Style Book Editor has been improved to make managing design tokens simpler and more intuitive, with a clearer approach to editing colours and improved overall usability.
Key Benefits:
Faster updates: Edit colour tokens quickly through a single, clear interaction point.
Easier to use: Fewer competing controls reduce confusion and make the editor more approachable.
Consistent experience: Interaction patterns now align with the Page Editor, improving learnability.
Built for growth: A stronger foundation to support future design token capabilities and enhancements.
Fewer errors: Improved interactions reduce friction and mistakes when updating styles.
Style Book tokens are now aligned with Clay variables, ensuring that design changes apply consistently across UI components and themes.
Key Benefits:
Reliable theming: Changes made in Style Books now correctly reflect across all Clay-based components.
Real consistency: No more gaps where updating a token doesn’t affect parts of the UI (e.g. alerts, buttons).
Better visibility: Token changes are accurately represented in the Style Book editor.
Stronger foundation: Clay now exposes core variables (colours, typography, spacing) as CSS custom properties, making them easier to control.
Future-ready: Sets the groundwork for more advanced theming and design system capabilities.
The Global Menu has been promoted from Beta to GA and is now the default, fully supported navigation experience in Liferay DXP. It provides a single, consistent entry point to access applications and settings, with improved structure, stable behaviour, and integrated search for faster navigation.
We are excited to announce the General Availability (GA) of the OpenSearch 2 Connector v2.0.0 for 2026.Q1 and v2.1.0 for 2026.Q2. This release is an important milestone in our Cloud Native Experience strategy, providing a viable alternative for Liferay DXP users.
This version has undergone additional testing and validation to ensure dependency alignment with the latest OpenSearch 2 clients and field mapping consistency with our Elasticsearch 8 connector.
The new version of the application is will be released on Liferay Marketplace.
Key Benefits:
- Native AWS Integration & Cost Optimization: Connect Liferay DXP with AWS OpenSearch Service. By leveraging managed infrastructure, organizations can reduce operational overhead, streamline their cloud stack, and optimize hosting costs through AWS-native service configurations.
- Flexible Search Architecture Production-ready alternative to Elasticsearch. This connector ensures that Liferay DXP remains flexible, allowing you to choose the search engine that best aligns with your infrastructure requirements and corporate standards.
Note: Liferay supports the connector and its features. While Liferay can provide an example deployment configurations for AWS OpenSearch Service, the management and maintenance of the underlying service remain the responsibility of the infrastructure provider.
Manage site updates with total confidence using the new Maintenance Mode. This feature allows Site Administrators to take a site offline for the public while maintaining full operational access behind the scenes. When enabled, visitors receive a dedicated maintenance page with the correct SEO-friendly status (HTTP 503), while administrators can continue to navigate, edit, and verify site pages to ensure everything is perfect before going live again.
Key Benefits:
Safe Production Verification: Unlike standard deactivation, Maintenance Mode allows admins to view and test the full site experience live, ensuring that deployments are successful before the public ever sees them.
SEO Protection: By serving a proper 503 Service Unavailable status, the system tells search engines that the downtime is temporary, protecting your search rankings during major updates or migrations.
Users can select and reorder categories for a blog’s friendly URL, so they can preview the order of the categories in the friendly URL and determine how the categories will be presented in the friendly URL along with the title.
Users are able to set different values for the asset types separators in the friendly URLs. Also, they are able to reset to default value, so for those asset types that they have clicked on this option, the separator will be the value defined by default for those specific asset types.
This release expands the support of the Timeline History feature to Blogs, Wiki pages, Bookmarks, Forms, Knowledge base, Message boards, and Categories. The feature enhances the publication toolbar with tools to detect and manage collaboration conflicts.
A timeline icon shows recent modifications in the same asset, which may have been done in production or parallel Publications.
The user can view, discard, or move these changes directly from the toolbar.
Warning icons appear to make users aware of current conflicts in the Publication.
Key benefits:
Enhanced context for content editors and managers for a streamlined collaboration.
New capabilities to detect conflicts before publishing time, while users may have more time to decide how to resolve conflicts without the go-live pressure.
This set of improvements aims to simplify the manual work users must do to resolve conflicts when publishing a publication. Now, instead of raising a conflict to be resolved manually by the user, the system will try to overwrite conflicting changes in production with the modifications done in the publication, meaning that the Modification and Modification deletion conflict types won’t be presented for the user anymore.
In the case of a Deletion modification conflict, the system won’t resolve it automatically, but now it makes it easier to keep the modifications made in the publication. In the Conflicting changes screen, we added a button with the option to "Restore in Production" for conflicts in which the asset was deleted from production and is now in the Recycle bin.
Key benefits:
Reduce the amount of manual work by automatically solving most of the conflicts.
Improve user satisfaction and reliability on publications by ensuring that assets supported by Recycle Bin can be quickly restored, avoiding requiring the user to discard needed changes.
Provided an option to turn the “Out-of-date” feature on/off. When turned on (the default behavior before this release), ongoing publications created in previous Liferay versions were labeled as “Out-of-date” after the upgrade and could not be modified or published. This feature is now off by default, and users can publish these publications without Liferay support.
Key benefit:
Increase manageability over publications and the ability to publish any previous modification, including after Liferay upgrades.
This release introduces in-context translation for text-based form fields (Text, Rich Text, and Textarea) 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. |
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.
