Feature Status Change
The Liferay Theme tasks are being deprecated and they will be removed in the future. The feature is based in Gulp 4 which is also deprecated. Customers are encouraged to use third party tooling to substitute it.
Release Notes
Feature Status Change
The Liferay Theme tasks are being deprecated and they will be removed in the future. The feature is based in Gulp 4 which is also deprecated. Customers are encouraged to use third party tooling to substitute it.
Feature Status Change
The AMD Loader are being deprecated and they will be removed in the future. Liferay DXP officially supports ESM, which is the official standardized module system for JavaScript, while AMD was a third-party solution.
By adopting ESM, products align with the language's native capabilities and future direction. Modern browsers now natively support ESM, allowing for direct use without transpilation or additional loaders. This can lead to reduced bundle sizes, faster initial page loads and simplified development workflows. This will imply also the deprecation of Liferay-CLI.
Feature Status Change
The Walkthrough is being deprecated and it will be removed in the future. Liferay will investigate new ways to offer this functionality.
Feature Status Change
The Liferay Talend Components feature is being deprecated and will be removed in the future.
Feature Status Change
Enabling this feature will allow users to work with base64 format in object attachments fields.
Feature Status Change
The functionality for sharing widgets is being deprecated and it will be removed in the future. The feature has been deemed obsolete.
Feature Status Change
The functionality for Supported Clients for widgets is being deprecated and it will be removed in the future. The feature has been deemed obsolete.
Feature Status Change
The functionality for Most Viewed Assets Collection Providers is being deprecated and it will be removed in the future in light of more advanced Analytics Cloud content tracking.
Feature Status Change
Scope of the widgets in a page: Page, Site or Global is being deprecated and it will be removed in the future.
Feature Status Change
The "Featured Content" contributed fragment set is being deprecated and it will be removed in the future.
Feature Status Change
The widget pages are going into maintenance.
Feature Status Change
The Asset Publisher widget is going into maintenance.
Feature Status Change
Users can easily identify components that may cause performance issues in their Pages. We have added a new tab on the Page Audit to show the users the back-end render times of the different components, as well as warnings to help identify specific components configurations that may lead to performance issues. Those warnings also appear on the Edit mode, so the user is aware of possible issues during the page creation.
This feature is now fully released.
This features is now fully released.
Object definition creators can now set default values for specific field types during the object design phase. When a user (or an external system via API) creates a new object entry, these fields will be pre-populated with the specified values if no other data is provided.
Key Benefits:
Reduced Manual Labor: Users no longer have to manually fill in "standard" information for every new entry.
Data Integrity: Ensures that critical fields (like "Status" or "Initial Score") are never left empty or inconsistent during the initial creation phase.
Object entry pages can now use meaningful, human-readable URLs even when built with custom layouts. Instead of relying on automatically generated numeric identifiers, administrators can define addresses based on business data, such as an event name. This improvement brings the same flexibility already available in other layout experiences to scenarios that require more advanced or tailored UIs. The result is clearer links, easier sharing, better discoverability, and a more consistent navigation pattern across the portal. Key Benefits:
|
As the CMS feature flag is removed, this functionality will be promoted from beta to release status.
As the CMS feature flag is removed, this functionality will be promoted from beta to release status.
As the CMS feature flag is removed, this functionality will be promoted from beta to release status.