May 2025 Releases

The implementation of inline editing caused regions to be clickable, which inadvertently gave focus to the underlying contenteditable fields.

Consequently, users were unable to position their cursor on a specific part of the contenteditable field with their initial click.

The implementation has been updated to allow the contenteditable field to be clickable through the region, rather than the region directly providing focus.

As a result of this adjustment, users can now position their cursor precisely where they want within the contenteditable field on their first click.

The Recent Locations list was not being updated to reflect the most recently selected asset’s location.

This meant that users selecting multiple assets within the same location would not have that location readily available, requiring them to navigate through the folder tree repeatedly.

To address this, the logic for adding new recent locations to local storage has been corrected to ensure that the latest values of hierarchy and source are used.

As a result, the Recent Locations list will now be updated whenever a user selects an asset in a new location, improving the efficiency of asset selection.

Previously, the component preview reload would not trigger the component’s JavaScript to re-run, leading to a broken reloaded live preview. Additionally, the image slider’s inline editing button was not clickable.

To resolve these issues, the dispatching of the livePreviewUpdated event has been added during the component preview reload. Furthermore, an additional event listener for pointerdown has been implemented specifically for handling the image slider component.

As a result of these changes, the component preview reload now functions correctly for these specific components, and the inline editing within the image slider component is now working as expected.

Viper encountered an issue where it could not unapply a style, such as bold or italic, when no text was selected within a viper editor field.

This lack of handling for unapplying styles without a selection led to the page entering an infinite loop.

Eventually, this infinite loop would cause the page to crash due to excessive memory consumption.

The fix implemented ensures that Viper no longer attempts to unapply a style when there is no text selection present.

As a result of this change, the page will no longer freeze when users attempt to unapply styles without selecting text. Users will now need to manually select the desired text before unapplying any styles.

The component primitive inline text field could be unintentionally hidden when the system incorrectly detected that it was outside the component’s boundaries.

This resulted in the component primitive inline text field becoming hidden and non-editable after editing in the Viper field.

To resolve this, the check for being outside the bounds has been modified to not apply to containers with a zero dimension.

This ensures that the primitive inline text field is no longer incorrectly considered out of bounds.

Consequently, the component primitive inline text field will now function as expected during editing.

Previously, the page outline was not correctly constrained to the same height as the preview panel.

Consequently, the page outline had the potential to expand beyond the dimensions of the preview panel.

This could lead to a situation where the viper toolbar, which is anchored to the top of the preview panel frame, would scroll out of sight.

To address this, the styling has been adjusted to ensure that the page outline is now limited to the same height as the preview panel.

As a result of this fix, the viper toolbar will remain visible and will no longer be able to scroll off the screen.

Previously, errors encountered while requesting a REST Resource page were not properly handled.

As a consequence, a REST error occurring within a Cron process would lead to a fatal error, causing the entire Cron run to terminate prematurely.

The handling of errors by REST Resources has been modified. Instead of triggering a fatal error, errors are now treated as non-fatal and are recorded in the cron error log.

This change ensures that a single Curl or REST error no longer disrupts the entire Matrix Cron run, while still providing a record of the error in the log for diagnosis.

An issue arose where retrieving asset information for deactivated users would fail. Specifically, when an asset was created or updated by a user who had since been deactivated, getting the user for the asset would return a null value. This null value was then incorrectly used to look up the user asset. Consequently, any attempt to update a Squiz Search collection with the null value would result in an error that blocked all subsequent updates and led to errors within the HIPO Manager.

To resolve this, the code has been modified to include checks that a user asset is successfully retrieved, if not, the creator and updater fields will now default to empty strings.

As a result of these changes, assets associated with deactivated users no longer cause errors. The creator and updater fields for these assets will now simply appear blank, and Funnelback collection updates will now complete successfully.

Fix the bug for the Acalog API - Get catalogs is not a valid XML.

The plugin now handles the invalid XML response from the Acalog API gracefully by converting the invalid XML to a valid one.

This change added an option, Metadata class, from which to source weight. This option allows the weight for auto-completion suggestions generated by the plugin to be sourced from a mapped metadata class.

This change added an option, Suggestion weight, that allows the default weight for auto-completion suggestions generated by the plugin to be defined.

This change extends the Split HTML or XML plugin to support sourcing a document’s URL from an XML attribute when splitting XML documents.

Fixed a bug where the plugin returns the message: record_type which should be set to 'CUSTOM', while the record type is set to custom in the configuration file.

Squiz Data Services requests sent through the /__dxp URL would return a 404 response code when the request included a query string. This meant that requests containing filtering, sorting, or pagination query strings were not supported.

The way URL routing paths are constructed and joined was updated to cater for query strings after the / character in URLs. Requests with query string parameters to Data Services through the /__dxp route no longer fail with a 404 response code.

Updated xml-crypto package

All associated auth-clients and auth-secrets are now automatically removed when a contract is deleted.

The migrations process cleans up any existing auth-clients and auth-secrets that are not linked to active contracts or workspaces.

Initial component release

Initial component release

Initial component release

The local runtime used node:vm to sandbox the component execution. This did not provide a consistent environment with the deployed components.

Certain runtime APIs such as Headers and URLSearchParams were not available during local development.

Re-implemented the local development runtime to use Miniflare to have a close match with the runtime that deployed components have. All expected runtime APIs are available.