The Questions Widget is a legacy application that was primarily maintained to support Liferay Ask. With the recent migration from Ask to Discuss (Liferay's new forum platform), this widget is no longer needed. Therefore, the Questions Widget is being deprecated to reduce technical debt and ongoing maintenance costs.
Release Notes
Search re-indexing has been optimized to deliver shorter re-index windows, especially for Objects-heavy deployments. In testing against production databases and architecture, we observed re-index improvements of 2x or more across the evaluated datasets, with gains reaching up to 10x on specific workloads. The optimizations primarily targeted improvements that scale with the volume and complexity of Object data being indexed.
Key Benefits:
Shorter re-index windows reduce maintenance overhead and downtime risk
Validated on a production-equivalent distributed architecture
Largest impact for Objects-heavy installations
Generally Available (aka OOTB)
Building on the automated database repair routines introduced in 2025.Q4, Liferay DXP continues to expand the set of repair processes that run during the upgrade. Based on additional research into customer upgrade issues, new repair routines automatically identify and correct further sources of database inconsistencies, orphan references, and invalid data — before they cause upgrade failures or performance bottlenecks. These repair routines remain targeted at known issues with data structures only, keeping your critical data content safe. Details of each repair process continue to be provided for review in the Upgrade Report after the database upgrade completes.
Key Benefits:
Minimize risks for current and future upgrades
Automates data maintenance
Generally Available (aka OOTB)
When using the Liferay DXP Database Partitioning feature, the system now enforces strict access controls ensuring only the authorized database partition is accessible for any given request. This completes foundational security work and extends proper enforcement to all Liferay entry points, including Headless APIs and Client Extensions.
Key Benefits:
Prevents unauthorized cross-partition data access in multi-tenant environments
Ensures consistent partition access enforcement across all Liferay entry points (Headless, Client Extensions)
Generally Available (aka OOTB)
This is a major version release that brings important platform updates and security enhancements alongside several necessary breaking changes to ensure the continued delivery and stability of Liferay Developer Studio.
Key Benefits:
Eclipse Platform Update: The underlying platform was updated to Eclipse 2025.12, taking advantage of the latest features and security updates from Eclipse. For more information, please see https://eclipse.dev/eclipse/news/4.38/.
Blade Version Update: The packaged Blade version was updated to 8.0.1-SNAPSHOT.
Generally Available (aka OOTB)
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 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.
Beta