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

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.”

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.

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.

You can now have access to the event’s details when selecting a calendar event and be redirected to the already existing details page of that particular event. It is also possible to map a Calendar Event’s specific URL, along with some other fields, in order to use it in emails so the recipient can click on it and be redirected to the Event’s details.

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:

1. 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.

2. 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.

We're introducing advanced script loading options for JavaScript Client Extensions in Liferay, providing developers more control over how JavaScript is applied to pages. This update allows the specification of async and defer attributes directly in the extension's configuration, optimizing the loading process and improving page performance.
Benefits for users:

• Improved Page Load Performance: by setting async or defer attributes, scripts can be loaded non-blocking, enhancing page responsiveness.
• Enhanced Control: developers can pre-set these attributes in the YAML configuration or through the UI, ensuring scripts behave consistently across all pages without further adjustment.
• Streamlined Configuration: once set, these attributes are locked at the extension level, eliminating discrepancies and simplifying script management.

Allow developers to specify additional attributes to the <script> tag when deploying in with the JS Client Extension.

Example usage in client-extension.yaml: liferay-portal/workspaces/liferay-sample-workspace/client-extensions/liferay-sample-global-js-2/client-extension.yaml at master · liferay/liferay-portal

    scriptElementAttributes:
        async: true
        data-attribute: "value"
        data-senna-track: "permanent"
        fetchpriority: "low"

Or, developers can configure the attributes via the create Client Extension UI too:

When configuring a JS CX on a page and async/defer Boolean attributes are present in the CX (set in the yaml / defined through the UI), the following behaviors apply in regards to the Load type options:

1. The attribute set in the CX will be used and the ability to change it when applying it on a page will be disabled.
2. When both attributes are set in the CX, async will be applied.
3. When async or defer is set to false in the CS, the related option will be removed from the Load selector. (e.g. if defer: false the load options available for the user will be default and async).