Release Notes
Liferay now automatically re-prompts end users for consent when your cookie policy changes — for example when the cookie list, a cookie's purpose, or its lifespan is updated. Administrators can also force the banner to reappear immediately for every end user.
Key Benefits:
Keeps cookie consent aligned with current policy without manual outreach
Supports ongoing GDPR/ePrivacy compliance as cookies evolve
Gives admins direct control over when re-consent is requested
Automatically detects Global Privacy Control (GPC) signals sent by supported browsers and privacy tools, allowing Liferay to honor users' opt-out preferences without requiring manual consent interactions. This helps organizations align with emerging privacy standards and regulatory expectations while providing a more privacy-centric user experience.
Key Benefits:
Provides a live preview of the consent banner and preference panel while configuring them, allowing administrators to see exactly how they will appear before publishing. This enables faster customization and reduces the need for trial-and-error adjustments.
Key Benefits:
Faster configuration
Better user experience
Ensures that consent management elements, such as the banner and preference panel, are displayed only after the entire configuration has been completed. This prevents end users from seeing incomplete, misconfigured, or non-functional consent experiences.
Key Benefits:
Prevents misconfiguration exposure
Improved compliance and UX
Prepares the Consent Management framework for automatic script blocking by introducing the necessary underlying architecture and integration points. This foundational work enables future support for preventing non-essential scripts from loading until user consent is obtained.
Key Benefits:
Future-ready architecture
Reduced implementation effort
Objects will include a dedicated Phone Number field type with built-in validation and country-aware formatting, so administrators no longer need to rely on generic text fields for contact data.
Key Benefits:
Improves data quality and consistency for phone numbers
Reduces custom validation work for developers
Supports international phone formats out of the box
Users will be able to upload files directly from the CMS Item Selector when working within an Object layout, removing the need to leave the flow to manage documents separately.
Key Benefits:
Reduces context-switching during content and data entry
Speeds up file association with object entries
Streamlines the day-to-day workflow for business users
Objects will include a dedicated Email field type with built-in validation, so administrators no longer need to rely on generic text fields to capture email addresses.
Key Benefits:
Improves data quality for contact information
Reduces custom validation work for developers
Provides consistent behavior across forms, APIs, and notifications
This epic makes Root Model behavior explicit and configurable, allowing admins to choose between strict root scoping and standalone, parent-optional objects while preserving backward compatibility.
Key Benefits:
Choose whether a Data Set enforces root scoping, preventing unrelated standalone entries from appearing in the results.
Configurable instead of relying on implicit platform assumptions.
Maintains backward compatibility with existing object models
Object Definition Inheritance is now Generally Available (feature flags LPD-34594 and LPD-69877 removed). This feature lets a "root" object definition share its permissions, widget/page configuration, and REST API endpoints with child object definitions bound to it, so hierarchies of objects can be managed and exposed as a single unit instead of individually. No behavior change for existing users of the feature.
Customers can now leverage a Liferay Toolkit to quickly and reliably spin-up Liferay in GCP. By leveraging our toolkit, customers can speed-up their deployments, as well as benefit from a robust and reliable infrastructure that reduces costs and increases predictability in the long run.
Key Benefits:
Increased visibility of Liferay Application and every other application in your GKE cluster;
Reliable deployment process with easier to spot drifts;
Operational cost reduction for running Liferay in GCP.
Customers can now leverage a Liferay Toolkit to quickly and reliably spin up Liferay on any conformant Kubernetes distribution, independent of cloud provider, including environments like OpenShift. By leveraging the toolkit, teams can speed up deployments on their own Kubernetes infrastructure without being tied to a specific cloud, while benefiting from a robust and reliable infrastructure that reduces costs and increases predictability in the long run.
Key Benefits:
Increased visibility of Liferay Application and every other application in your GKE cluster;
Reliable deployment process with easier to spot drifts;
Operational cost reduction for running Liferay in GCP.
Front-end Client Extensions no longer count toward your subscription plan's resource consumption. Front-end Client Extensions (such as custom themes, JavaScript, and CSS that run in the user's browser) are now excluded from the Plan & Usage page, so deploying them no longer draws down the CPU, memory, and storage allotted to your plan.
Key Benefits:
More accurate resource consumption and billing figures on the Plan & Usage page, reflecting only server-side usage
Lower risk of hitting plan limits when extending and customizing the UI.
Content administrators can now export and import Content Structures from the CMS, making it easy to move content models between environments. Following the same pattern already available for Categories and Tags, an Export/Import option next to the Content Structures page title lets administrators download structures and import them into another instance.
Key Benefits:
Speeds up environment promotion (e.g., from UAT to Production)
Eliminates manual, error-prone re-creation of content structures
Complements the existing export/import for Categories and Tags
This improvement addresses two high-impact usability gaps. Space administrators can now define a meaningful Friendly URL for each space, replacing the auto-generated "/asset-library-{id}/" segment in display page URLs, with validation and full support in the Headless API. In addition, authors can duplicate an existing content item in place with a single "Make a Copy" action instead of a multi-step workaround.
Key Benefits:
Improves SEO with readable, brandable URLs
Content and embedded links move cleanly between environments without breaking
One-click duplication speeds up content creation
Site administrators and developers can now edit the External Reference Code (ERC) of vocabularies when creating or editing them, in both the CMS and DXP. Previously the ERC was read-only in DXP and hidden in the CMS, creating friction when synchronizing taxonomy between environments. The misleading "Name" label is also renamed to "Title" to match how users think about vocabularies.
Key Benefits:
Keeps environments in sync so Headless API calls and scripts don’t break
Reduces integration friction in staging and headless scenarios
Clearer labels reduce confusion for administrators
The CMS side panel now shows a Technical Properties section for file assets (extension, aspect ratio, resolution, and size) so content creators can verify an asset meets technical requirements without downloading it. The information adapts to the asset type (images and videos show all properties; documents show only the relevant ones) and works across Gallery, Card, and List views.
Key Benefits:
Prevents layout errors caused by wrong aspect ratios or low-resolution images
Saves time by removing downloads and separate detail views
Aligns the CMS with enterprise DAM standards
Site administrators can now create and edit Collections directly from the Asset Publisher configuration panel, without navigating to the standalone Collections app. This includes editing the rules of an underlying collection in place and easily identifying and adjusting collections generated automatically by the upgrade that converts Asset Publisher legacy filters into Collections.
Key Benefits:
Manage asset groupings without losing working context
Quickly fix wrong content being displayed by editing collection rules in place
Smooth transition for sites still relying on legacy filters
Site administrators can now connect Spaces to Site Templates, so sites created from a template automatically get access to the shared content managed in those spaces. Connections can be managed from both the site template configuration and the space’s connected sites, and new sites receive access only to the content actually used in the template.
Key Benefits:
Faster rollout of new sites at scale from common templates
Better reuse and governance of shared content
Closes the feature-parity gap with Asset Libraries
Administrators and reviewers can now proactively keep content fresh. The CMS notifies authors and reviewers when their content is expiring soon, has expired, or reaches its review date, and quick filters in the All section let users filter content and files by status.
Key Benefits:
Reduces exposure of outdated or misleading published content
Enables scalable governance without heavy manual audits
Improves content quality and trust across the organization