6.28 release notes
April 14, 2023
This page describes release information for all Matrix 6.28 versions, including patch releases.
The following new features were introduced in this Matrix release.
The Component Service is now integrated with Matrix in this version release. You can now do the following primary activities depending on your user account type in Matrix:
(Root users only) Configure the Component Service in the Squiz DXP services configuration screen.
Configure a component set path on a site asset so you can add DXP components to standard pages.
Configure a Matrix API identifier to resolve Matrix asset references in DXP component output.
Add and edit DXP components on standard pages, including formatted text and Matrix reference fields.
Read the Component Service documentation for detailed usage instructions.
The following bugs were resolved in this version of Matrix.
- "Unsaved changes" warning sometimes triggers when it shouldn’t (MATRIX-4948)
An issue with form state comparison checks caused users to experience an unsaved changes alert that ordinarily should not have appeared when navigating away after saving a form. State comparison checks that detect that a user has just saved the form were added, which skipped the form comparison step upon saving and navigating away. Users can now correctly navigate away from the form after saving changes without getting an alert saying they have unsaved changes.
- Links to assets in recently viewed go to a 404 page (MATRIX-4952)
Recently viewed links in the screen header were incorrectly HTML escaped, causing users to experience a 404 page when opening recent assets in new windows. The incorrect escaping was removed, which fixes the originally reported issue.
- Support cross-domain preview in Admin (MATRIX-5003)
An issue with the way iframe elements were used in the preview screen caused modern browsers to block the iframe elements from loading in a cross-domain environment. When previewing across domains, the preview screen would fail to load, leaving a blank and confusing interface. In this situation, the user is now presented with a message directing them to the Preview in new window button, which fixes the originally reported issue.
Disabling the “Enforce same origin frame security for frontend” security allows the preview screen to operate across domains. However, this is not a recommended solution.
- Metadata can prevent the use of thumbnails on calendar event assets (MATRIX-5445)
Calendar event assets could only have a maximum of one reference link to image assets. This caused issues with saving screens in cases where multiple reference links could be created (for example, a metadata WYSIWYG field whose contents linked to an image asset, on a Calendar event that already had an Image asset set as its thumbnail). The cardinality for reference links from a calendar event asset to image assets was increased from
Manyto permit more than one reference link to be created.
- Asset keywords in 'Meta Format Tag' cause backend notice (MATRIX-5451)
The metadata manager attempted to replace all keywords in metadata fields with metadata values when a custom meta tag format was specified. Using keywords other than those listed as available in the meta tag format within the custom meta tag format generated an "Undefined index" error from PHP. The fix ensures that only
%metadata_value%keywords can replace metadata values within the custom meta tag format. Using common keywords like
%asset_name%within a custom meta tag format no longer produces errors.
- Teleporting causes Asset Tree refreshes to not occur (MATRIX-5456)
The asset tree code contained assumptions that the root node asset ID would always be
1(the root folder). If the root node were teleported, the asset tree would not refresh, which caused unnecessary user confusion. The root node assumptions were removed, and the root folder asset ID is now removed from the data passed back by Matrix to asset tree requests.
- Sign in as is visible to users who cannot use it (MATRIX-5458)
A missing user permission check allowed non-privileged users to view the Sign in as option under the My account drop down even though they couldn’t use it. An additional permission check was added to ensure the option is only shown to users with the correct permissions.