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.

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.

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.

What changed?

From Liferay DXP 2024.Q2 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 2024.Q2 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.