Release Notes
The page reviewing experience now provides a more accurate way to locate and compare changes. The Publications Display tab for Content Pages now provides the Unified view, highlighting additions, removals, and format changes, so you no longer have to hunt for differences on the new page version.
Key Benefits:
Review accuracy: Reviewers feel confident that no change goes to production without the proper attention.
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 feature introduces a centralized administration interface within the Data Set Manager to oversee and moderate User Views. Administrators can now access a global list of all User Views to monitor usage or perform cleanups.
Key Benefits:
Centralized Oversight: A new "Manage User Views" button in the Data Set Manager provides a complete list of all User Views for easier monitoring.
Contextual Access: Admins can jump to the management view from specific Data Set settings, where the list is automatically pre-filtered to show only the views belonging to that Data Set.
Administrative Control: Enables admins to maintain system hygiene by deleting individual or multiple User Views via bulk actions.
Full Visibility: Provides key details at a glance, such as which user created the view and which Data Set it belongs to, ensuring better governance of user-generated configurations.
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.
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.
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.
CMS administrators can now modify content structures and their repeatable fields after publication — adjusting field configurations, nesting order, and repeatable settings without deleting existing content. Teams iterate on their data models as business needs shift, and all previously published entries stay intact.
Key Benefits:
Refine your content model based on real-world usage instead of locking in every decision up front.
Skip the "delete everything and rebuild" cycle when requirements change — existing entries come along for the ride.
CMS admins adjust structures directly, without pulling in developers or database work for every tweak.
Data modelers can now define Link Content fields that let content creators select existing entries from other objects—single or multiple—instead of retyping the same values across entries. The CMS moves from isolated documents to a connected data model, so information like vendor names, categories, or authors stays consistent across every publication.
Key Benefits:
Eliminate typos and inconsistencies by picking existing entries instead of re-entering text.
Reuse the same author, category, or vendor across hundreds of entries—update it once and it propagates everywhere.
Support both single and multi-select relationships, from "one author per article" to "many products per campaign.”
Content teams can now find and replace text, URLs, or terms across the entire CMS repository in a single action — covering titles, content fields, and friendly URLs. Every operation includes a mandatory preview, scoped targeting, and automatic versioning, so large-scale updates like rebrandings or URL migrations are fast, reversible, and low-risk.
Key Benefits:
Cut rebrandings and terminology rollouts from hours of manual edits to a single bulk action.
Preview every change before it's committed, with automatic versioning if you need to roll back.
Scope replacements by site, content type, or field so global updates stay surgical instead of sweeping
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.
Managing large-scale site deployments just got easier. We have introduced new headless API endpoints that allow developers to toggle site states (Active or Inactive) programmatically, bypassing the need for manual configuration within the Control Panel.
Key Benefits:
Automated Site Governance: Enables high-speed bulk management of site states, allowing your team to sync site availability with external business systems or custom orchestration tools.
Enhanced System Stability: Built-in safeguards protect the platform by preventing the accidental deactivation of essential system sites (like Global), while strict permission validation ensures only authorized users can trigger state changes.
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.
Customers can now leverage a Liferay Toolkit to quickly and reliably spin-up Liferay in AWS. By leveraging our toolkit, customers can speed-up their deployments, as well as benefit from a robust and reliable infrastructure that reduces costs and increases predictability in the long run.
Key Benefits:
Increased visibility of Liferay Application and every other application in your EKS cluster;
Reliable deployment process with easier to spot drifts;
Operational cost reduction for running Liferay in AWS.
Reviewing complex page updates is now faster and more intuitive. We’ve introduced a Review Side Panel within the Publications Review Change screen that automatically surfaces content changes made on a Content Page. Instead of manually digging through the full change list or a Pages’ Children tab, reviewers can now see exactly which text and images have been modified in a page’s Fragment Entry Links via a consolidated, easy-to-read list.
Key Benefits:
Focused Decision-Making: Instantly identify high-impact changes (like text and image updates) without getting lost in technical changes.
Streamlined Workflow: Eliminates the need to cross-reference multiple tabs or Fragment Entry Links, allowing content reviewers to complete reviews with total confidence.
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.
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:
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.