July 2025 Releases

A recent update to the external package @rjsf/utils to version 6.67.1 inadvertently introduced an error. This error specifically affected the handling of select fields within a component manifest, particularly those defined as enum oneOf fields with a single array selection.

To resolve this, all @rjsf/* packages within the Matrix package have been updated. Their version numbers have been "hard-coded" to a stable release to prevent similar issues in the future.

As a result of this fix, all component select fields now function correctly.

Page Builder live preview requests were routed through the incorrect proxy. Asset resolution from resolveUri in components failed due to an authentication conflict.

The fix updates the live preview request route to be consistent with typical render paths. Behavior within live preview is now consistent with page renders.

When a SquizLink asset was unselected, instead of populating the value with undefined, the value was populated with null. Once a SquizLink asset was removed, validation would never pass, and the user could not save their page.

The handling of SquizLinks around adding and removing has been updated so that they are now added and removed. This behavior change allows pages to pass validation and save.

Script tags included in the blockElements array were being processed as editable elements, which caused broken editing capabilities and introduced potential errors in the page builder interface.

The fix adds script element filtering to the blockElements array to ensure they are excluded from the inline editing process.

Inline editing works correctly, distinguishing between script tags and editable content blocks.

When a content page was previewed, it treated all blocks as coming from that content page, even if content comes from nested pages through paint layouts. Nested content appeared inline-editable when it should not have been, and editing this content caused problems.

The fix ensures that only content for the loaded content page is inline editable. Nested content now remains read-only and no longer causes any issues with page editing and preview.

An issue with how cut, copy, and paste operations were interpreted within the Squiz DXP WYSIWYG text fields on Firefox caused these browser functions to operate incorrectly.

To fix the issue, changes were made to how these common editing operations are interpreted in WYSIWYG fields, which allows the affected users to use these commands in Firefox browsers successfully.

In PHP 8 or higher versions, strings were not typecast automatically and could not be used in calculations. This condition caused a runtime error that caused the cron manager to fail.

The fix checks string values and ensures they are typecast to the correct type before calculating which prevents the runtime error from occurring.

System Administrators can deactivate password authentication on the Details screen of individual user accounts.

Previously this was set during user creation, usually for turning off password authentication for SSO users. This minor improvement makes it easier for system administrators to deactivate password authentication for users who should not be using passwords.

Changes to handling DOMDocument objects to make them more memory-safe left a bug in how the xpathe keyword modifier was evaluated.

Keywords using the xpathe keyword modifier, if the original keyword was non-empty, would cause a fatal error (and thus an HTTP 500 response) when the keyword attempted to be displayed.

The XPath object is now obtained using the decorated DOMDocument object.

DeJa Vu and Matrix Cache now use the lowest latency ElastiCache node for read operations. DXP stacks previously had a read ElastiCache node that was only used for failover. However it was discovered that this node could service requests quicker for some web nodes.

Response times should be more consistent with this improvement, with the higher peaks being reduced towards the current lows.

The plugin now allows pagination of the results with a default page side of 500.

Identifying spikes in log volume was difficult when relying on the data in the log results table. The Logs Service now offers an Analytics section, which can be expanded to reveal a bar chart.

The chart represents filter criteria displayed in the results table. You can refine the date filter by selecting a date range on the chart.

Showing a chart with the aggregated log volumes broken down by level, which match the configured filters, improves the usability of the available data.

The previous 15-minute log window would frequently result in no logs appearing.

The default log filter time was increased from 15 minutes to 60 minutes to increase the likelihood of finding the log entry you seek.

The content field defined within the conditional schema structures returned an undefined schema. The inline editing field was not clickable because it was missing an expected field definition with ui:metadata: {inlineEditable: true}

The getChildSchema function was enhanced to add conditional schema evaluation logic to resolve the nested content field with the correct schema. The inline editing field now works with the expected field definitions resolved.

Squiz Content Management stores metadata values and links in the database to prevent data loss if metadata fields are accidentally removed from assets through schema updates.

A byproduct of this retention policy was that the reference report and data search tool showed links from related asset metadata fields that were removed.

The system now checks whether the fields with links to other assets are applied to the asset with metadata. If this condition exists, the links are removed from the reports. The data search tool now shows if the link is orphaned or removed.

The reference report only shows links from related asset metadata fields applied to the asset. The data search tool appends "(orphaned)" to any links from metadata fields that are not applied to the asset, preserving visibility of the stored data while showing that the value does not apply to the asset.

The http_build_query() query is responsible for safely building query strings for GET requests in the OAuth2 client code.

With built-in function signatures in PHP 8, the emitted PHP deprecation notice from http_build_query() was turned into an Exception, then re-emitted as a PHP warning by the REST resource page asset. Certain actions relating to REST resource pages did not complete when authenticating using OAuth2 (for example, using an OAuth2 token asset).

Using OAuth2 in REST resource pages (and potentially elsewhere) should now operate correctly by adjusting how the deprecation notice associated with http_build_query() is handled.

A mismatch was identified between the asset tree and the Details screen for a form section. Sort order was updated to null when a user acquired locks (especially in Safe Edit Mode) on the Details screen and then made changes through the asset tree.

The sort order checks are updated to check the already saved children and the added or removed fields for the children in the asset tree.

The Map URL parameters plugin allows mapping input parameters into different parameter names and sets them for an extra search request.

Fixed the issue where parameters were not correctly mapped for an extra search request.

The Faceted navigation categories - custom sort order plugin lets you modify the sort order for facet navigation categories.

Added support to the existing plugin, allowing faceted navigation category labels to contain a vbar | in the label.

For example, for a oranges | lemons | limes category labels, escaping the vbar between lemons and limes results in two category labels: oranges, and lemons | limes.

To enable CORS, the Access restriction to search results plugin allows passing through an OPTIONS request to resolve headers correctly for subsequent requests.