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:

• Release Change status from Beta to Release

• New Gallery View for files

• Export/Import for Categories, Tags and Content Structures

• UX improvements for Import/Export translations

• General UX improvements on Spaces

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:

1. Added support for WebLogic 15c (see details in dedicated WebLogic 15 release note)

2. Expanded Jboss version support from 8.0 to 8.x to help our users stay up to date with Red Hat support policy

Databases:

1. Added support for MariaDB 11.8

2. Added support for PostgreSQL 17.x

Operating Systems:

1. Added support for Red Hat Enterprise Linux 10

Key Benefits:

• Access to newer versions of environment to ensure the latest performance, compliance, and security patching access.

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:

• Allows AI agents to become aware of the structure of Liferay Workspaces without any manual configuration.

• Assists new users with setting up a Liferay Workspace and running Tomcat bundle, with explanations for commonly used Blade commands.

• Provides Liferay recommended best practices for development.

• Enables AI agents to access the Liferay MCP server to query content, manage objects, and execute actions within the portal.

• Guided experience available to create and deploy a sample Client Extension, allowing users to quickly see Client Extensions in action in a running portal instance.

In order to assist customers with upgrades to newer Liferay versions, Blade and Workspace users now have a dedicated gradle command upgradeSourceCode to migrate their code automatically to their desired Liferay version. This will do in-place updates to custom code to account for breaking changes in the latest Liferay version.

For customers migrating to Jakarta for the first time, the Jakarta Migration Tool upgradeJakarta is also available to automatically convert their source code from Java EE to Jakarta EE for DXP-provided libraries. The Code Upgrade Tool should be executed first before running the Jakarta Migration Tool.

Key Benefits:

This tool simplifies the process for users migrating their code to newer Liferay versions, providing:

• Automatic source code migration for projects to a target Liferay version.

• Liferay version specific code upgrade automations to account for breaking changes.

• Integration with Liferay Workspace.

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 main.(tvERyCVfuRc).js.

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 no-cache header. This ensures the revalidation of the asset with the server before being served.

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:
Significant reduction in subsequent load times.

2. Elimination of Stale Resources:
Hashed URLs prevent users from seeing outdated JavaScript after an update.

3. Reduced Origin Server Load:
Less server overhead, as browsers retrieve unchanged files directly from their local cache, saving CPU and bandwidth.

4. Cache busting:
Updated resources automatically force the browser to fetch the new version by changing the file name hash whenever the content changes.

"Promote Content among Environments" is a Liferay initiative that takes content promotion to the next level. By implementing a significant infrastructure change (based on Headless Batch APIs), processes are substantially streamlined, optimizing existing processes and adding new ones that enable more secure, stable, and efficient content promotion.

Now you can promote elements at the instance level, such as Object Definitions, Picklists, or Roles, and freely export and import Object Entries with any scope. With the new Lazy References infrastructure based on External Reference Codes, relationships are maintained and updated regardless of the order of importation.

Furthermore, the new Report List provides a comprehensive and detailed record of everything that happened during the import process. This new report is essential for new entities because import processes will run from start to finish without stopping with the first issue, reporting all errors so you can resolve them collectively instead of having to address them individually with each run. For non migrated entities, the behavior will be the current one finishing the process with the first error.

Key Benefits:

• Infrastructure improvement: based on Headless Batch APIs executions, the processes are more efficient, faster and more stable, allowing for easy optimization and showing a clear information about the status of each execution. Some of the old staging entities have been migrated to the new framework:

  • Pages (and related entities like templates, utility pages or master pages )

  • Vocabularies

  • Categories

  • Tags

• New capabilities at Instance level: The coverage of entities that can be promoted is expanded by adding a list of entities like:

  • Instance Level

    • Roles

    • Accounts

    • Account Groups

    • Organizations

• Full support for Objects: Now all related Objects entities are supported for export/import:

  • Object Definitions

  • Picklist

  • Object entries with Company Scope.

  • Object entries with Site Scope

• The order of execution no longer matters: Lazy references based on External Reference Code is the key. Now, for entities that are compatible with Batch, the related elements are not automatically exported. Thanks to the External Reference Code the references can be maintained even if the other element does not exist, making the order of importing irrelevant.

  If an element is missing, an empty shell might be created to maintain the correct structure, and if the information is included either manually or in a subsequent import, the element is updated, preserving all existing relationships.

  For the entities still using the old infrastructure, the relationships will be maintained using the old mechanism.

• All Import information in just one click: Thanks to Lazy References, the process will attempt to import all items for batch-migrated entities without stopping for errors or warnings. For non-migrated entities, the process will still stop at the first error. Due to this hybrid mode, batch-based entities will be imported first. All generated information will be available in a detailed list that can also be exported in CSV format for external processing if needed.

Bridge Your Portal Data and Marketing Power

The 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:

• Automatic Lead Generation Forget manual entry. When a record is added to a specific Liferay Object, whether through a registration form, a lead magnet, or a customer portal, the connector automatically creates the corresponding record in HubSpot.

• Smart Mapping Engine Technical complexity is handled for you. The connector features a smart mapping layer that manages naming conventions and field normalization between both platforms, ensuring data integrity without requiring custom code.

• Real-Time Synchronization Your marketing team shouldn't have to wait for "overnight batches." The bridge ensures that data flows to your CRM the moment it is captured in Liferay, enabling immediate follow-up and faster conversion.

• Seamless Installation Built to live natively within your environment, the application is ready to configure immediately after installation from the Liferay Marketplace.

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:

• One clear entry point for all Liferay functionalities

• Reduced navigation complexity with consolidated access points

• Faster discovery through live filtering and improved structure

• Greater productivity for administrators and content teams

• Scalable foundation to support future platform growth

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:

• Next-Gen AI & Search Capabilities: The native connector unlocks high-performance new generational features like dedicated vector search, semantic search queries, and native inference that upcoming and planned Liferay DXP features will benefit from.

• Seamless Forward Compatibility: Thanks to the Java Client API, Liferay DXP is now more resilient than ever. The client is designed to stay compatible with future Elasticsearch updates, ensuring that minor version upgrades won’t disrupt your operations or break your integration. (Liferay will still very the compatibility to ensure.)

• Future-Proof Security & Support: By moving to a fully supported, native Elasticsearch 8 connector and environment, you eliminate the risks associated with end-of-life software and ensure your infrastructure meets modern security standards.

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.

A new, dedicated Scope configuration is now available within the Query Builder, allowing administrators to precisely limit search results to specific Sites, Asset Libraries, and Spaces.

Key Improvements

• Dedicated Configuration: We recommend using this native Scope setting instead of manual filtering via out-of-the-box or custom query elements. It provides a more intuitive and performant way to define the search boundary.

• Default Behavior: If no specific Site, Asset Library, or Space is selected, the Blueprint will search across all available scopes by default.

Behavior Note: Scope Hierarchy

When a scope is defined within a Blueprint, it acts as a strict boundary.

• No Overrides: Search-time parameters (such as those from a Search Bar widget or the Headless Search API’s scope parameter) cannot override or expand the Blueprint’s pre-defined scope.

• Filtering Logic: Any scope requested at search time must be a subset of the Blueprint’s scope. If a user or API requests a scope that falls outside the Blueprint's configuration, the search will return empty results.

 
Besides the new scope configuration, the Query Settings section has been renamed to Source and moved to the main query builder screen, simplifying the editor experience.

 Key Benefits:

• Dedicated Configuration: We recommend using this native Scope setting instead of manual filtering via out-of-the-box or custom query elements. It provides a more intuitive and performant way to define the search boundary.

• Default Behavior: If no specific Site, Asset Library, or Space is selected, the Blueprint will search across all available scopes by default.

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

• Opt-in Integration: This remains an optional configuration. Users who previously accessed this via the LPS-129412 Feature Flag will find the functionality now natively available.

• Subtype Filtering: You can now limit queries to specific subtypes directly within the Searchable Types configuration (located under the Source section, formerly Query Settings).

• Simplified Filtering: For Documents and Web Content Articles, you can now select specific Document Types or Web Content Structures within the UI. This eliminates the manual overhead of creating custom query elements to filter by structure keys or IDs.

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:

• Path: Navigate to Instance Settings > Search > Semantic Search.

• Action: Enable the OpenAI Text Embedding Provider and configure semantic ingestion for your desired content types and languages.

• Documentation: Please refer to the official guide for detailed setup instructions and for customizing search with semantic search.

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 (LPS-122920) under Instance Settings > Feature Flags > Beta.

Assets that are currently being modified within a publication are now protected from deletion in production by default.

Previously, this behavior was optional and disabled by default. It is now enforced automatically to ensure greater stability and data integrity when working with publications.

Key Benefits:

• Prevents most of the deletion modification conflicts that could only be resolved by discarding changes

• Provides safer default behavior without requiring configuration