March 2025 Releases

The implementation of how data paths are used is changing. 404s from the data are now redirected if they appear valid.

The existing implementation was causing an unacceptable number of 404 errors.

The authentication MAC cache was not cleared when the user logged out. After logging out, the user could see logged-in page content if the instance was behind a MAC cache.

A call to regenerate the session ID has been added during logout to prevent MAC from using the same cached session immediately. When the user on a MAC instance logs out, the page no longer has cached content for authenticated sessions.

The Acalog Basic plugin required updates to its API to allow program metadata information to be passed through.

Some minor changes to the logic about http client double-encoding were also made. Configuration settings were updated for the Search data source settings.

An issue with client-side JavaScript caused it to not run for actions other than refreshing the browser or saving a page and reloading the content page asset. Any reload or refresh action taken on the content page iFrames was not re-added, and components with custom Javascript failed to run.

Script tags are now re-added to the page correctly upon reload action for content page assets. A livePreviewUpdated event is emitted to signify that javascript should re-append any eventListeners.

Fixed the issue where a deleted workspace was not removed from the list of workspaces in the left sidebar.

Fixed the issue where a recently deleted workspace did not disappear from the UI’s View All Workspaces page.

Fixed the issue where the mapper error was not displayed on the thread page, ensuring better visibility for troubleshooting.

Fixed the issue preventing users from setting the log level to Warning for a step through the UI.

Fixed the issue where an inactive webhook flow returned a successful response instead of an appropriate error.

Fixed the issue where executions contained no records when the flow type was changed to webhook.

Fixed the issue where personal workspaces were incorrectly displayed in the Other Contract Workspaces section when the user had the Member role in the contract.

Fixed the issue where webhooks failed to recognize valid credentials due to a basic authentication username/password mismatch.

Fixed the issue where the HTTP Reply component failed to send the correct message if it was added to a flow version other than the first.

Not all selections were restored due to the options being incorrectly removed from the address bar. Only some options were restored after obtaining locks to the page.

The fix stores all selections temporarily to be restored after locks have been acquired. Personalization, A/B Tests, Page Width and the active block in the outline are remembered and restored after obtaining locks to the page.

Very large serialized objects were being encoded. In some cases, this could cause the system to run out of memory (OOM) (for example, purging many assets).

Very large serialized objects are now truncated before encoding. Purging thousands of assets will no longer cause an OOM fatal error.

Enabling ESI for 404s is a best practice, and doing this today requires multiple manual steps. The steps can be replaced by a feature flag option, which will enable the 404 without manual intervention.

When the ESI 404 settings are enabled and the appropriate conditions are met, Matrix will automatically wrap the 404 in an ESI include when responding.

To enable the feature:

The conditions required for the ESI include response to work are detailed here:

Re-initialization of Viper instances on the page was a blocking process. Page builder loaded very slowly on pages containing multiple components with inline editable Viper fields.

The fix updated how the inline Viper instances are loaded into the page. The initializations of the Viper instances will not block page Builder on the page.

When selecting an image in a Viper text field, selection handles were placed inside a div and appended to the main input. While all Viper instances successfully remove this element when losing focus, Page Builder mirrors content between elements.

It was, therefore, possible for another Viper instance to inject its overlay element into another instance. This unintended behavior happened when resizing an image in the Page Outline view, which caused an erroneous HTML element to appear in user content.

The fix removes the overlay element entirely and creates a shadow DOM node directly on the main Viper element, which is automatically hidden when the page is saved.