6.42 release notes

April 19, 2024

This page describes release information for all Content Management 6.42 versions, including patch releases.

New features

The following features were included in this release:

Content page assets now offer a preview mode (MATRIX-6383)

The Content Page asset now has a preview of the rendered output in the right column.

The preview includes controls for selection A/B testing and Personalization content variations; and for adjusting the width of the preview.

Content page outline panel supports content block navigation

Before this release, the Outline column in content page assets did not function as a navigation element.

With this release, you can select a content block in the outline, and the Content column will scroll to the selected content block.

You can also select blocks using the existing keyboard shortcuts as part of the standard page-building experience.

Upgrade all components in bulk with the Bulk Component Upgrade tool (MATRIX-6385)

The Bulk Component Upgrade tool is available for system administrators and root users. Find it in the Tools  Bulk upgrade components menu.

The tool works on both standard page and content page assets. You can select from which root node in your system the upgrade should apply. You can upgrade both Squiz DXP components managed through Squiz Component Service and core components.

You can test out an upgrade before you deploy it and review a CSV report of the assets that succeeded and failed as part of the test upgrade.

The tool upgrades components included in an A/B test. Doing so could compromise the results of the A/B test, however these components are not excluded yet; future work will allow them to be. This caveat does not apply to components that have a personalization strategy applied.

General improvements

The following improvements were included in this release:

Formatted text editor (MATRIX-6382)

The formatted text editor appears as a content block option in content page assets.

In this release, support is added for breaking lines (<br />) to the formatted text editor using CTRL or CMD+Enter. Keyboard shortcuts are shown correctly in the formatted text editor, depending on your OS.

New and updated formatted text fields now use the <strong> element for bold and the <em> element for italicized text nodes when the page is published.

Finally, the bubble menu no longer obscures the content editing view and hides automatically when the editor loses cursor focus.

Image browser (MATRIX-6384)

You can better manage image assets within the resource browser with these improvements to how images are shown and managed:

  • Preview the image in the preview pane

  • See a thumbnail preview in the formatted text editor

  • Quickly change an image without removing it in the image browser. You can select an existing image or create an image asset, all from the same location.

System configuration > Content editor feature restrictions (MATRIX-5987)

A "Content Editor feature restrictions" configuration screen has been added to the System Configuration menu, available to users with system administrator privileges.

This screen works similarly to the feature restriction screen on user groups. However, it lets you control feature restrictions for all content editors.

Features that are never available to content editors are not available for restriction on the Content editor feature restrictions screen.

Additions to user group restrictions and content editor feature restrictions

The following new features and settings are available for user group assets:

Feature restrictions > General features

"Quick search of entire system" option (MATRIX-6083)

Selecting (restricting) this option limits quick search to the current asset tree. For example, if a user only has access to a certain tree of assets, their quick search will only search within this tree. Or if a user teleports to an asset, the quick search will only search that part of the current tree selection.

"Asset tree of entire system" option (MATRIX-5985)

On the Feature restrictions and Content Editor Feature Restrictions page, there is a new restriction under General features called Asset tree of entire system (restricts to current site only).

An example of enabling this restriction is if you are on a domain that relates to a Site asset, the asset tree will be restricted to that Site asset.

"Cascade status from dropdown menu" option (MATRIX-5688)

On the Feature restrictions and Content Editor Feature Restrictions page, there is a new restriction under General features called Cascade status from dropdown menu (restricts to current asset only).

Enabling this restriction hides the Cascade current status option from users when updating the status of an asset.

For example, when updating an asset from Under construction to Approve and make live, only the current asset can be moved to the new status. All child assets beneath the current asset retain their current statuses, instead of all being updated.

Feature restrictions > Metadata display

These options appear in the Metadata display group in the Feature restrictions section of user group assets:

"Code output" option (MATRIX-5981)

Selecting (restricting) this option hides the code output on the Metadata screen.

"Linked field type and ID" option (MATRIX-5982)

Selecting (restricting) this option removes the links to assets under fields on the Metadata screen.

"Advanced metadata restriction" section (MATRIX-5988)

For this feature to work, metadata schema and metadata section assets can now be marked as Advanced. If a schema or section is marked as Advanced, it is not shown to users with the Advanced metadata feature restriction applied.

You can hide certain schemas or sections of an asset’s Metadata screen for certain groups of editors. You can also restrict a certain user group from viewing schemas or sections of an asset’s Metadata screen.

Bug fixes


The following hotfix was released on April 24, 2024.

The Test upgrade option in the Bulk Component Upgrade Tool was not running the upgrade in report-only mode. Using the tool would result in the components upgrading unexpectedly. A hotfix was introduced to fix the condition check for report-only runs of the tool.