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.

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.

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.

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.

Liferay now automatically re-prompts end users for consent when your cookie policy changes — for example when the cookie list, a cookie's purpose, or its lifespan is updated. Administrators can also force the banner to reappear immediately for every end user.

Key Benefits:

• Keeps cookie consent aligned with current policy without manual outreach

• Supports ongoing GDPR/ePrivacy compliance as cookies evolve

• Gives admins direct control over when re-consent is requested

Automatically detects Global Privacy Control (GPC) signals sent by supported browsers and privacy tools, allowing Liferay to honor users' opt-out preferences without requiring manual consent interactions. This helps organizations align with emerging privacy standards and regulatory expectations while providing a more privacy-centric user experience.

Key Benefits:

• Privacy compliance
• Improved user trust

Provides a live preview of the consent banner and preference panel while configuring them, allowing administrators to see exactly how they will appear before publishing. This enables faster customization and reduces the need for trial-and-error adjustments.

Key Benefits:

• Faster configuration

• Better user experience

Ensures that consent management elements, such as the banner and preference panel, are displayed only after the entire configuration has been completed. This prevents end users from seeing incomplete, misconfigured, or non-functional consent experiences.

Key Benefits:

• Prevents misconfiguration exposure

• Improved compliance and UX

Prepares the Consent Management framework for automatic script blocking by introducing the necessary underlying architecture and integration points. This foundational work enables future support for preventing non-essential scripts from loading until user consent is obtained.

Key Benefits:

• Future-ready architecture

• Reduced implementation effort

Objects will include a dedicated Phone Number field type with built-in validation and country-aware formatting, so administrators no longer need to rely on generic text fields for contact data.

Key Benefits:

• Improves data quality and consistency for phone numbers

• Reduces custom validation work for developers

• Supports international phone formats out of the box

Users will be able to upload files directly from the CMS Item Selector when working within an Object layout, removing the need to leave the flow to manage documents separately.

Key Benefits:

• Reduces context-switching during content and data entry

• Speeds up file association with object entries

• Streamlines the day-to-day workflow for business users

Objects will include a dedicated Email field type with built-in validation, so administrators no longer need to rely on generic text fields to capture email addresses.

Key Benefits:

• Improves data quality for contact information

• Reduces custom validation work for developers

• Provides consistent behavior across forms, APIs, and notifications

This epic makes Root Model behavior explicit and configurable, allowing admins to choose between strict root scoping and standalone, parent-optional objects while preserving backward compatibility.

Key Benefits:

• Choose whether a Data Set enforces root scoping, preventing unrelated standalone entries from appearing in the results.

• Configurable instead of relying on implicit platform assumptions.

• Maintains backward compatibility with existing object models

Object Definition Inheritance is now Generally Available (feature flags LPD-34594 and LPD-69877 removed). This feature lets a "root" object definition share its permissions, widget/page configuration, and REST API endpoints with child object definitions bound to it, so hierarchies of objects can be managed and exposed as a single unit instead of individually. No behavior change for existing users of the feature.