6.37 release notes

Calculations of sort orders for the asset tree were incorrect when expanding “bridge” assets containing shadow assets (such as LDAP User, Trigger, and Thesaurus assets). Under some circumstances, attempts to show the asset in the asset tree using the binoculars would fail. No assets would appear, and this condition would remain until the asset tree was refreshed while in a collapsed state. The paging calculation in the asset tree for shadow assets and some extra sort order fixes specifically for Trigger and Trigger Category assets were corrected. The asset tree now more reliably finds shadow assets, and the parent asset does not lose its ability to show children when using binoculars.

Value comparison form validation rules would always call a function to get the value in the field being compared. When a field was set to compare to itself and required, the value lookup would loop indefinitely. This loop led to a PHP fatal memory exhaustion error. The field’s current value is used directly rather than looking it up with a function call when comparing a field to itself, which fixes the originally discovered issue.

The scheduled job process ran as root while the safe-trash scheduled job was created under a normal user. When a scheduled job to move an asset to trash ran, it failed to move the asset to the trash due to a locking issue, even when the asset itself could be trashed. The problematic link is ignored when the scheduled job executes. A scheduled job can move an asset to trash when the safe-trash feature is enforced and the asset is in acceptable status.

Cloning component templates did not have the necessary checks. Users could clone assets to which they had write access, but lost some content during the cloning process. Checks concerning component templates were added, so this could also be cloned. The user can now clone a page to which they have write access, and the component template will also be cloned.

Feature restrictions were intentionally turned off for LDAP Users as they were causing fatal errors in 6.22 as per MATRIX-5213. However, these feature restrictions would not apply to LDAP users. Fixes previously applied for MATRIX-5213 were confirmed to get feature restrictions functional for LDAP users and are now re-enabled.

When a SAML Account Manager was loaded from Deja Vu, it sometimes would not correctly populate the SimpleSAMLphp config. Certain authentication paths would intermittently trigger a fatal uncaught exception error with the message Call to a member function getSimpleSamlConfig() on null. When a SAML Account Manager is loaded from Deja Vu, it now reliably populates the SimpleSAMLphp configuration.

Diff checking methods for HTML tags were expecting only strings, and in certain cases, null was being passed. When null was passed in, the server would fail. The methods have been updated to either check for or accept null being passed. When null is passed to these methods, the server does not fail, and the tool functions.