This change was made in order to prevent fragment changes propagation when a user changes the cacheable option and then saves it. This was creating performance issues for some customers.

This change will benefit customers in terms of performance, as unnecessary propagations will no longer occur when the cacheable option is changed.

No changes are expected for customers' implementations. Just the awareness that this option is now somewhere else.

Support for these application servers is removed from 2024.Q3 or later since they are no longer receiving updates from the vendor.

Wildfly 26.1 and Jboss EAP 7.4 remain fully supported

With the new support of Java JDK 17 and 21 runtimes, Java 11 will no longer be supported for DXP runtime on 2024.Q3 or later. 

Liferay Workspace offers support for re-compiling custom modules on JDK 17 or 21.

What changed?

From Liferay DXP 2024Q2 onwards, localizable object entry fields now default to the instance's language setting, replacing the previous user-language default.

Why was this change made? Is the new behavior better for users?

This change was implemented to ensure consistent language configuration. The new behavior is indeed better for users because:

• It prevents discrepancies that could occur when users with different language settings interacted with the same object entry fields.

• It provides a unified experience across all user interactions.

Who is affected?

Customers using or upgrading from versions prior to Liferay DXP 2024Q2 are affected by this change.

How should I update my features or implementation to better adopt the breaking change?

To adapt to the new behavior:

• Check your existing localizable object entries' default language settings.

• Adjust these settings to match the instance language if needed.

This ensures consistent language defaults and creates a uniform experience for all users.

The AMBackwardsCompatibilityHtmlContentTransformer class was introduced in the Adaptive Media release (~7 years ago) to manage content created before Adaptive Media was implemented. This approach helped to avoid a costly upgrade at the time. However, since much time has passed and newer content no longer requires this processing, we are disabling the AM backward compatibility HTML content transformer by default.

The primary reason for this change is performance: the content transformer can consume significant CPU resources, especially under heavy traffic.

The content transformer can be enabled in Instance Settings > Adaptive Media if necessary.

The "Save as Draft" and "Cancel" options are no longer visible when editing Web Content. Instead, the content is automatically saved as a draft.
With the implementation of autosaving, users no longer need to worry about losing their progress when editing content. Autosaving ensures that all changes are continuously saved in the background, providing peace of mind and reducing the risk of data loss due to unexpected interruptions.

The JVM java.locale.providers setting for DXP has been restored to the default value to account for the move to Java JDK 17 and 21.

Previously, DXP and Portal shipped with and recommended setting java.locale.providers=JRE,COMPAT,CLDR to provide consistent locale behavior for Java 8 and 11 since JRE was previously the default provider. With Java 17 and 21, JRE is now deprecated and the CLDR locale provider becomes the default and recommended provider. See further information from Oracle.

The new recommended value is java.locale.providers=CLDR,COMPAT as it is the new JVM default. The Liferay Tomcat bundles for 2024.Q4 will ship without this JVM property set, since we are using the default.

With this change the default provider, some locale information in the system might display with modified formatting. For example, a Date and Time display may have previously shown as “9/12/24 9:10 PM” but now displays as “9/12/24, 9:10 PM”. This is the expected result from moving to the latest Java locale provider that meets modern language standards.

Fixed a bug that was causing some 404 redirects to direct back to the previous page instead of to the 404 error page.

If any implementations were relying on users being redirected back to the previous page, they might need to be updated to account for the new redirect to the 404 page.

This is a breaking change for Data Sets that are under BETA FF

• Anybody who created data sets before this epic will not be able to see them in Data Set Manager anymore.

• Data Set fragment configuration will no longer display previous data sets as options.

• Data Set fragment placed on a page will no longer show anything.

• The Data Set Views have been removed. From now on a Data Set has only a view.

• New Data Set endpoints are available and working under datas-et-admin (ex: http://localhost:8080/o/api?endpoint=http://localhost:8080/o/data-set-admin/data-sets/openapi.json)

• All Data Set endpoints are still available and working under data-set-manager but not used by the Data Set Manager or Frontend Data Set. Information from created Data Sets before this change is stored in them (ex: http://localhost:8080/o/api?endpoint=http://localhost:8080/o/data-set-manager/data-sets/openapi.json)

More Info: LPD-29979

• What changed?
  Javascript from fragments is now included in the page using a <script> of type module, instead of embedding the code in a function

• Why was this change made?
  We wanted to leverage all the features available in the javascript modules: JavaScript modules - JavaScript | MDN
  For example: the ability to use import statements

• What is affected?
  Code that is not supported directly in a <script> tag of type module
  For example:

  • return statements outside the scope of a function

  • Automatic variable declaration, for example myVariable = 'value'

• How should I update my features or implementation to better adopt the breaking change?
  Code should be fairly easy to migrate, just remove any return statement, and for the variable declaration you either use let or const next to the variable name const myVariable = 'value'
  As a temporary workaround (would be removed soon), we have added disable to this feature. You have to go to Instance Settings -> Page Fragments -> Fragment Javascript and disable the checkbox

Changed the methods of adding a Collection to specify the ERC when is created. If a customer has Java code that is using these services they should modify it to specify the ERC (or Null) when is called.

The functionality of the Date Facet widget introduced under a Developer FF in LPS-153839 in 2024.Q1, has been integrated into the Custom Facet and now available as GA. The Date Facet widget is no longer available.

Refer to the Date Range and Range Aggregation in the Custom Facet under Search for more details.

Liferay’s Countries feature was migrated from being a Commerce feature to a DXP feature, thus Commerce’s Countries page was removed. Users that manage Countries will now be able to manage them through the Countries Management page under the Control Panel.

Content is no longer classified as translated solely upon the translation of its title. Now, when a user translates any field, not just the title, but also the content status changes to "Translating". It will only be considered translated when all fields have been translated.

To bolster permissions management and elevate user awareness concerning content, users will now be prompted to confirm permissions during the initial publishing or saving process, requiring an additional click. Subsequent saving or publishing actions will not require this confirmation.

The "Mine" filter now displays the creation date information instead of the modified date.

The "Recent" filter now displays the creation date information instead of the modified date.

A new SEO menu has been added in Instance Settings with an item selector to include specific Sites or all of them, in the sitemap of the Company through the Company's Virtual Host, and the default site cannot be deleted from the list. If the default site has a Virtual Host defined, it will not be added to the company's XML sitemap although listed in the configuration.

Users are currently presented with a group of features that are not relevant in the configuration page for Utility Pages. These non-applicable features have been removed while preserving the essential HTML Title, HTML Description, and SEO configuration elements.

After searching with a keyword and selecting facets, searching with a new keyword (in either using the header Search Bar or any Search Bar widget instance on a page) will clear all active facet selections.

The old behavior can be enabled via the Search Options widget by ticking Retain Facet Selections Across Searches option.