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.

This feature introduces a centralized administration interface within the Data Set Manager to oversee and moderate User Views. Administrators can now access a global list of all User Views to monitor usage or perform cleanups.

Key Benefits:

• Centralized Oversight: A new "Manage User Views" button in the Data Set Manager provides a complete list of all User Views for easier monitoring.

• Contextual Access: Admins can jump to the management view from specific Data Set settings, where the list is automatically pre-filtered to show only the views belonging to that Data Set.

• Administrative Control: Enables admins to maintain system hygiene by deleting individual or multiple User Views via bulk actions.

• Full Visibility: Provides key details at a glance, such as which user created the view and which Data Set it belongs to, ensuring better governance of user-generated configurations.

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.

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.