Feature Status Change

The Subscription Manager Widget is being deprecated and will be removed in the future.

Feature Status Change

In a future release, DXP will be moving to modern Enterprise Java API, Jakarta EE 10. Announcing the JavaEE deprecation to give time to prepare for this significant breaking change scheduled to occur in the 2025 calendar year.

Moving to Jakarta EE will require:

• Application Server upgrades
• All code, including custom modules, that use the javax package name will need to migrated to respective jakarta packages

Feature Status Change

With the upcoming move to Jakarta EE 10 and expansion of Client Extensions, DXP is focusing attention a new generation of customization options.

Liferay Faces support for JavaServer Faces (JSF) is being deprecated.

Feature Status Change

With the upcoming move to Jakarta EE 10 and expansion of Client Extensions, DXP is focusing attention a new generation of customization options. PortletMVC4Spring is being deprecated.

Feature Status Change

With the expansion of Objects functionality, Custom Fields are going into maintenance.

Feature Status Change

Deprecating the filter for lastLoginDate on the Headless Admin API because it negatively impacts search performance.

Controlled by feature flag LPD-36010.

New true/false filter hasLoginDate can be used to efficiently check if a user has already logged in to their account at least once.

Feature Status Change

The Liferay Theme generator is being deprecated and it will be removed in the future. Customers are encouraged to use Theme Client Extensions or third-party tooling to generate themes.

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.