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.

This affects any custom code using Liferay’s API methods User.getRemotePreference(String) and User.getRemotePreferences().

The API supporting logic has to collect and hold cookies in User object, causing unnecessary CPU and memory overhead. These methods were just a convenient shortcut to get the user's current request's cookies with REMOTE_PREFERENCE_ name prefix. The same logic can be done by directly getting necessary cookies from request.

• What changed? Currently, the translatable object fields use the configured languageId from the user. With this change, it is going to use the preferred Locale given by the DTOConverterContext instead.
• Why was this change made? This change is needed in order to return the appropriate translatable object field values for the language setting in the Accept-Language header.
• Who is affected? Every user that calls the translatable object fields.
• How should I update my features or implementation to better adopt the breaking change? Adding or removing (depends on the cases) the Accept-Language header.