6.31 release notes

June 22, 2023

This page describes release information for all Matrix 6.31 versions, including patch releases.

New features

The following new features were introduced in this Matrix release.

You can now create link assets through the asset management API.

Read Asset Management API for information about the capabilities of this API and links to the latest API reference documentation.

Bug fixes

The following bugs were resolved in this version of Matrix.


Matrix doesn’t report when the Virus Scanner fails to scan a file (MATRIX-3291)

If the file upload failed to find the virus scanner service, the process did not attempt to warn the user or log the problem and allowed the file to be uploaded without scanning. This silent failure could result in files with virus payloads silently being uploaded. More informative error messages are now shown in the Matrix Admin UI about the failure to scan the file. Additionally, better log messages are shipped when the scanner can not be found or when the scanner is found but the file was not scanned.

Consistent timeouts break the generate links report HIPO (MATRIX-5662)

If the link report processed many links that caused timeouts, the HIPO step would fail. The HIPO job could be resumed. However, users may need to continually retry the job. The batch size is now limited to the maximum size that can be processed if all batches timeout in the allowed time. The HIPO steps should always complete, which means the HIPO will complete on its own.

DB Data Source fatals when used with Oracle DBs (MATRIX-5670)

The core Matrix database abstraction layer (DAL) had some Oracle specific code removed during refactoring. DB Data Source assets were no longer able to work with Oracle DBs. The Oracle-specific DAL logic was reintroduced which fixes the introduced regression.

LDAP Bridge sometimes logs DN: [] could not be found (MATRIX-5695)

The LDAP Bridge in Matrix would sometimes look up the shadow ID for objects. Using LDAP may log "DN: [] could not be found" repeatedly. The LDAP Bridge now consistently looks up objects using the full asset ID, preventing the error.log from filling up with LDAP warning messages.