June 2025 Releases

When bringing elements in and out of view, such as clicking through slides in the image slider, the calculations of where the inline editable fields were, and hence the border display, were incorrect.

To fix this issue, a comprehensive visibility detection system has been added with these features:

Regions properly reflect their visibility state based on all relevant factors, improving the overall editing experience. The system is more responsive due to optimized observer management and debounced updates.

Component developers needed a way to identify whether a component was in editing mode or standard front-end render mode. Previously, there was no straightforward method to determine the display mode of a component in their code.

Components can now access the ctx.editor boolean attribute in their context object. This attribute indicates whether a component is being rendered in Page Builder’s display mode. Developers now have the option to conditionally render different content or behaviour based on whether the component is being edited or viewed.

The component validation could fail when the field was non-required, but its oneOf property was required. Users were forced to complete the non-required field. Otherwise, the component could not pass validation and be saved.

To fix the issue, the validation now handles nested oneOf fields to prune the empty objects within the form data recursively. The component validation will pass regardless of the non-required (with oneOf required) field being filled up.

The keyword replacement process against Rest Resource headers incorrectly reduced the total number of headers to process. Any headers with badly formatted keyword replacements prevented the headers' tail end from being processed.

The total headers counter has been moved outside the processing loop, which stops the count from being reduced incorrectly. All request headers in Rest Resource are being processed for keyword replacements.

Assets referenced through a multiple-selection Related Asset metadata field did not always appear by the Linking screen’s reference report. The query was changed, which now inspects multiple-selection Related Asset fields using JSON document-type queries. These queries find the presence of either the "number" or "string" versions of a non-shadow asset ID. All affected assets now appear in the Linking screen’s reference report, regardless of how they were stored.

A memory-unsafe method was used to read the log file when downloading files larger than 100MB. This method could cause the system to run out of memory (OOM) and prevent users from downloading a log file.

The memory safe version of file reading was implemented, so the system no longer runs out of memory when downloading large files from the Log Manager.

An issue prevented the proper saving and retrieval of the Request Function and associated parameters when configuring a SOAP data source asset, leading to an "Error finding 'uri' property" upon re-entry to the Details screen. Users could not reliably configure the request function and body for SOAP data source assets, resulting in incomplete setups and hindering the asset’s functionality.

The underlying mechanism for handling and persisting the Request Function selection and its parameters within the SOAP data source asset’s Details screen has been corrected. The Details screen interface for the SOAP data source asset now correctly saves, displays, and allows for the complete configuration of the Request Function and Request Body.

The token validation in use was rejecting authorization based on the IAT in the token being set slightly in the future. This was caused by the token minter’s clock and the data service’s clock drifting slightly.

To fix the issue, leeway is applied to allow clocks to drift somewhat and not cause a token to be rejected.