We recently updated our tracking logic within documents, replacing the previewed event with a new event: impressionMade. To align with this change, we also updated our current API to include a new metric — impressionMadeMetric — which consolidates impressions by summing both the new impressionMade events and the legacy previewed events.

What changed?

The Display tab in the Review Changes screen now renders Display Page Templates and content that uses those templates (e.g., Web Content Articles, Blog Entries). Previously, these were not previewable — the Display tab was either empty or disabled for such content.

Why was this change made?

This change allows content reviewers to see the real end-user layout before publication. It significantly improves quality assurance by reducing publishing errors and increases confidence that the final layout will match expectations — especially for structured content and enterprise use cases (e.g., FHLBNY). This change improves usability and eliminates a gap in the review process that could result in visual inconsistencies post-publication.

How should I update my features or implementation?

• No changes are needed.

What changed?

The Data tab in the Review Changes screen for Web Content Articles now displays all editable fields, including those created via custom structures. It also shows field labels and values exactly as defined by content creators.

Why was this change made?

Previously, only a subset of fields was shown, which often led to missed content changes during the review process. This update makes it easier to catch all modifications, especially in highly customized structures — enhancing accuracy and trust in the publishing process.

How should I update my features or implementation?

• No changes are needed.

What Changed?

The Configuration Headless API now exposes and manages site-scoped configurations that were previously unavailable through export/import operations. During import, existing configurations for a site are now overridden with the incoming configuration data based on groupId scope matching.

Why Was This Change Made?

This change ensures that site migrations are more complete and consistent, including configuration data that was previously missing.

How should I update my features or implementation?

• No changes are needed.

The results of a search haven’t to be shown the content of a fragment is within a collection display and is not indexed.

The change was already done for text editable, since the button fragment have to allow text only, and it was forgotten for the link editable.

The system-wide Mail Settings for DXP were migrated to use the standard system configuration framework.

The system options in Server Administration > Mail were moved to System Settings > Email > Virtual Instance Scope > Mail Settings

The existing settings from previous releases will be automatically migrated during the database upgrade process.

The following portal properties were removed since they are now defined by configuration properties:
LIST OF PROPERTIES

Following standard configuration patterns, Instance Settings > Email > Mail Settings will have default values inherited from the System Settings. The administrator for Portal Instances can now view the default values, override, or reset to default.

Please refer to Configuring Mail - Liferay Official Documentation for additional details.

The Object Inheritance feature has been updated to support more flexible scenarios, which introduces changes to the previous behavior:

• Child definitions can now be associated with multiple parent definitions.
  Previously, a child could only inherit from a single parent.

• Child entries can now exist without a parent (standalone entries).
  Before this change, every child entry was required to belong to a parent.

• The relationship field is no longer mandatory at the object-definition level.
  Previously, the relationship field was always required when inheritance was enabled.
  Now, it becomes mandatory only when the entry is created in the context of a parent.

• Permission and configuration inheritance now depends on whether the child entry has a parent.
  Standalone entries no longer inherit permissions or configuration from a root object.