The Custom Assets feature has been formally deprecated and removed from Analytics Cloud. The feature had been under a "deprecation" feature flag for several quarters, and the retirement process is now complete.

Reviewers can now see exactly how content will appear to end users when using a Display Page Template, ensuring layout and formatting are correct before publishing.

• Applies to multiple types of content, including Web Content Articles and Blog Entries.
• Reviewers can now see all editable fields for content items in the Data tab — including custom fields created via structures.

Key Benefits:

• Improves content quality: Ensures that reviewers can see exactly how content will appear to end users, helping maintain visual and structural accuracy before publishing.

• Reduces publishing risks and errors: Allows early detection of layout or formatting issues, minimizing rework and post-publication corrections.

• Saves time in the review process: Streamlines validation and reduces the need for multiple review cycles.

Site Settings are now exportable through Headless APIs.

Key Benefits:

• Simplified Environment Migration: Easily migrate all site-scoped configurations together with site content using the Batch Engine and Headless Site API.

• Greater Consistency: Ensures that site settings and behaviors are replicated accurately across environments.

• Enhanced Automation: Supports headless and automated deployment workflows, removing the need for manual configuration updates for site settings.

With the launch of the new CMS 2.0, two fragments have been created that allow the customers to build a more complete and flexible experience for the end-user. These Accordion and Drag and Drop Upload fragments are better aligned with the real needs of a CMS user and content editors in general, as they allow for improved organization of information and increased usability when managing information and files of any type.

Key Benefits:

• Accelerated Time-to-Value: Ready-made fragments allow customers to quickly drag-and-drop functional components, reducing development time and enabling marketing and content teams to create new experiences faster.

• Lower Cost of Ownership: Platform-maintained fragments reduce the burden of custom code, ensuring greater long-term stability, easier upgrades, and less time spent on maintenance.

With the launch of the new CMS 2.0 and the need to integrate and contribute related objects, a new form fragment has been created. This Form Relationship fragment allows users to populate/fill in nested objects within a form container. With this new fragment, we provide customers with the ability to create more complex forms where they can complete the information for these related objects, thereby offering a more complete experience for the creation of complex applications and for the CMS itself.

Key Benefits:

• Maximize Authoring Velocity: By unifying the creation of parent and embedded (repeatable) entities into a single, contextualized screen, customers eliminate clicks and custom code, allowing content teams to publish complex experiences significantly faster.

• Ensure Data Integrity: The out-of-the-box fragments enforce data structure and contextual relevance for child entities at the point of creation, guaranteeing consistent, structured content that provides a unified experience for end users.

Style Books now support 8-digit hex colour codes (e.g. #RRGGBBAA), which include an alpha channel to define opacity. Previously, these values only worked when set as defaults in the frontend-token-definition.json file; manual input in the editor would strip the opacity digits. With this update, customers can directly enter and save full 8-digit hex values in the Style Book editor, and the opacity is correctly reflected in the UI.

Key Benefits:

• User will be able to define colours with both RGB and transparency in a single, standardised format improving Liferay’s design flexibility.
• Aligns with modern CSS and browser support for 8-digit hex codes.
• No need for more workaround formats (like rgba) to manage opacity.

In this case, the feature “Enable JavaScript Client Extensions for Administration in SaaS Environments” has remained under Release Feature Flag for three consecutive quarters. During this period, it has demonstrated strong stability, with no reported bugs or user complaints.

Following this evaluation, we’ve decided to move the feature to GA, based on its proven reliability, adoption, and positive feedback.

Semantic Content Indexing

When the feature flag LPS-122920 is enabled, the platform can now create text embeddings (numerical representations of input text, also known as vector embeddings) for Object entries. These embeddings are generated using the content from the searchable fields and are meant to capture the meaning and the context of the content. You can select from various available third-party providers and models, such as OpenAI or Hugging Face, to generate these vectors.

Customizable Search

Now that semantic indexing is also supported for Object entries, you can create highly customized searches using Blueprints. Specifically, the Rescore by Text Embedding query element is available for use.This element automatically handles the process of creating vectors from the user’s keywords through the configured provider.

For instance, this capability allows you to combine traditional keyword search with AI-powered vector search techniques to implement hybrid search, now also for Object entries. This combination is quickly becoming the new standard for modern content search and discovery.

Key Benefits:

More Relevant Search Results: Create search experiences that understand the meaning and context of your Object based content or application data and user searches.

The Semantic Search capability is planned to be moved to GA status in early 2026. This timeline is intended to outline Liferay’s general product direction and it is subject to change.

The headless Search APIs (GET and POST /o/search/v1.0/search) become GA, enabled by default. No feature flag required.

From now on most CSS files in Liferay have hashed file names at build time. For example, a clay.css file may appear at run-time with a randomly generated hash value in the name, like clay.(tvERyCVfuRc).css.

This hash value represents a unique version of this file, so the browser can identify that the file's contents haven't changed. This allows the file to remain in Liferay's cache indefinitely.

For those files that can not be hashed, because they are generated in runtime by the server depending on some parameter such as the css tokens, a new onfiguration is available in DXP to configure the TTL and the possibility to add the no-cache header, that ensures the revalidation of the asset with the server before to being served.

Also, hashed files have a fallback strategy based in TTL+eTag if they are called by their canonical name, this is a fallback for error in the import maps or old portlets that doesn’t know the name of a hashed file.

Key Benefits:

The new Liferay DXP caching strategy for CSS files improves performance and stability.

1. Faster Page Loads: Significant reduction in subsequent load times.

2. Elimination of Stale Resources: Hashed URLs prevents users from seeing outdated CSS 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, but updating their file name with a new hash when content changes.

When a user visits a page that contains a Data Set, there is a certain amount of data that can be altered in some ways:

• By filtering the data

• By ordering the data

• By changing the columns to show on the Table Visualization

• By changing the visualization mode

When users navigate away from the Data Set and then return, these unsaved changes are lost, leading to a frustrating user experience.

This feature automatically saves the current view state of a Data Set in the URL. This saved state will ensure the Data Set configuration is consistently recoverable when users navigate back (via browser history or links) and, crucially, that a shared URL provides colleagues with the exact same view.

Key Benefits:

• Avoid user frustration: When the user returns to the Data Set they face the same state they had when they left.

• Sharing what you see with other users: Users can share the link of a page with a Data Set and the user acessing that very page will face the same Data Set state.

As in Ck Editor 4, and to cover the feature parity, the AI Creator plugin has been added to CK Editor 5, so content creators can rely on an AI to create content seamlessly.

Key Benefits:

• Accelerate content creation leveraging AI text generation services

Admins can now fully customize the Rich Text Editor configuration in CKEditor 5 using a new Client Extension. This new extension achieves feature parity with the old CKEditor 4 extension, allowing you to define which toolbars are available across different applications.

Bonus Feature: Unlike its predecessor, the CKEditor 5 extension supports dynamic loading of official CKEditor plugins not included by default in DXP, greatly expanding your customization options.

Key Benefits:

• Allow dev users to modify the CK Editor 5 configuration such as new block styles

• Allow the dev users to hide plugins such as the options in the editor toolbaar.

• Allow users to dynamically add more plugins from CK Editor official showcase.

• Administrators can enable the SPA feature at instance level

• This allow different customers in SaaS to have different configurations as previoulsy it was enabled just at System level (same configuration for several customers)

• SPA config at instance level overrides the SPA config defined at System level

Key Benefits:

• Mostly SaaS customers can enable/disable SPA in their instance isolately, so Liferay Cloud administrators can defer this configuration to users.

When administrators turn on CKEditor 5 feature flag (LPD-11235), the Email Configuration will use CKE5 as the default text editor.

Key Benefits:

• Consistency across DXP, enabling the CK Editor 5 is offered in one more experience that now is covered.

The Liferay database upgrade process has been enhanced with automated database repair routines to improve the speed and reliability of DXP upgrades.

During the upgrade process, these routines automatically identify and correct common database inconsistencies or missing references.

These repair routines are targeted at known issues with data structures only, keeping your critical data content safe. Details of these repair processes are provided for review in the Liferay Upgrade Report after a database upgrade completes.

Key Benefits:

• Faster upgrades

• Minimize risks for current and future upgrades

• Automates data maintenance

The following database versions have reached end of life from their vendors and are now under deprecation for DXP:

1. DB2 11.1

2. MariaDB 10.2

3. MariaDB 10.4

4. MySQL 5.7

5. PostgreSQL 12.x

6. PostgreSQL 13.x

7. SQL Server 2017

Please refer to the 2025.Q4 compatibility matrix for the full list of supported Databases.

The following Operating System versions have reached end of life from their vendors and are now under deprecation for DXP:

1. CentoOS 7

2. CentoOS 8

3. Debian 10

4. Debian 11

5. Oracle Linux 7

6. Red Hat Enterprise Linux 7

7. SUSE Enterprise Linux 12

8. Ubuntu 18.04

9. Ubuntu 20.04

Please refer to the 2025.Q4 compatibility matrix for the full list of supported Operating Systems.

This epic introduces multi-parent support for Object Definitions, allowing a single child object (e.g., Address) to be associated with more than one possible parent definition (e.g., User or Account). While the definition can support multiple parents, each Object Entry can still only belong to one parent entry at a time, ensuring data consistency.

Key Benefits:

• This new feature allows more flexibility when organizing your entries with regards to permissions inheritance. 

This feature introduces a new, configurable "On after Login" trigger for Liferay Object Actions. This will empower administrators and developers to define and execute automated processes on Object entries (e.g., creating, updating, or deleting entries, calling external APIs, sending emails) immediately after a user successfully logs into Liferay portal.

Key Benefits:

• Faster Time-to-Market: New features tied to user authentication (like automatically creating a user's dashboard data) can be deployed in minutes via the UI, without involving custom development.

• Extended Low-Code Power: The Objects framework becomes more valuable by handling a critical part of the digital experience—user sign-in—without needing traditional coding skills.

• Real-Time Data Integrity: Ensures that user-specific custom data (like status, last login date, or personalized onboarding tasks) is created or updated instantly and automatically upon login, keeping all systems synchronized.