June 2025 Releases

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.

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.

A problem with code in Viper that deactivated a style introduced an infinite loop based on a node’s firstChild not changing inside a while loop. The page would become unresponsive when attempting to deactivate a text format or style (for example, bold or italic.

The fix checks for a node’s firstChild; if the first child does not update, the code skips the while loop.

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.

Non-printable characters were not converted when building the XML that powers the asset tree. Clicking the reveal icon on an asset that has a child asset with a name containing a non-printable character triggered a DOM error.

A function to process asset names and remove non-printable characters is triggered to fix the issue before building the asset tree XML. Users can add non-printable characters to asset names without breaking the asset tree.

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.

An addition calculation was performed on string variables when calculating payment, and taxable amounts. This incorrect calculation caused the Ecommerce form to throw a fatal error when proceeding to the payment step in PHP 8 environments.

The calculation logic now type casts the strings to float values to fix the calculation logic. The Ecommerce form in PHP 8 now calculates amounts correctly, and payments can be processed as expected.

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.

A recently added feature that allowed __data path URLs to be redirected if they errored with 404 caused the backend not to load. The feature did not account for paths containing _admin.

Adding _admin to the end of a __data path would not route to the backend interface. The redirecting of __data paths that 404 now takes _admin into account.

Any __data path URLs with _admin will now route to the backend interface like they used to.

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.

A section within Data_Source_Soap_Edit_Fns attempted to unserialize() data without confirming its type, leading to a TypeError when the data was already an array. While previously suppressed, this TypeError became a fatal error in PHP 8, causing the SOAP data source Details screen to crash on saving. Users encountered a "500 error" toast and a fatal TypeError when attempting to save the Details screen of a SOAP data source asset, preventing successful configuration.

The logic in Data_Source_Soap_Edit_Fns has been updated to correctly handle the serialization state of the data, ensuring unserialize() is only invoked when appropriate and preventing the TypeError in PHP 8 environments. The Details screen of the SOAP data source asset can now be saved without errors, allowing for proper configuration in PHP 8 environments.

The Acalog Basic plugin version 1.4.0 can now support proxy mode.

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 plugin now allows SFTP public key authentication along with userid/password authentication.

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.

Dependencies have been upgraded to address security issues.

Vulnerabilities are addressed, ensuring a safer and more reliable system.