6.39 release notes

The Release Locks button did not appear when users did not have permission to edit an asset. If the user had lost permission to edit an asset while holding the locks (for example, through workflow), there was no way for them to release the locks on that asset. Locks are automatically released when loading screens for an asset you cannot edit due to permissions. Users can now acquire the locks when others have lost permission to edit the asset.

The necessary check for a trigger folder linked outside the Trigger Manager did not exist. That link could not be deleted if a trigger folder was linked in the asset tree outside the Trigger Manager. The parent of a link to a trigger folder is first checked when attempting to delete it. Upon checking that the parent is not another trigger folder or the Trigger Manager, the folder can be deleted.

When search weightings were set, only the first match was considered. If asset types were parents of other types, then attributes of the child types would not be indexed. Since all asset types are children of the “asset” type, this also applies to customizations of all asset types. All weighting sources are now considered when indexing an asset in the order of default weights, asset tree weights, and asset weights, with the latter being applied if set. Asset attributes are reliably indexed when asset tree weights or default weights for their parent types are set.

Much of the processing for the logs screen was done in PHP across all matching logs rather than just those appearing in the results. The log screen could fail to load when large log volumes were present for the selected date range and log types. The database now handles how logs are selected along with most of the processing. The logs screen is now faster and more stable.

The metadata controller was not making the rest of the system aware of the current screen. Fields could be wrongly edited when not contextualized for the current context. The metadata controller now updates the system that the user is on within the metadata screen. Fields are now in the correct state for editing and contexts.

There were overly strict constraints for printing the related asset field note on the Metadata screen. The note was not being printed in a location where it should appear in the Admin UI. One of the strict constraints was removed, and the note was printed in the correct location.

Highly Intensive Processing Objects (HIPOs) for Edit permissions jobs remembered the asset types when they were started. If an asset were morphed to a different type, the HIPO would fail to complete and continue to fail when attempting to resume the job. The edit permissions HIPO job now ignores any previous types of assets. Permissions can now be applied to assets that have been morphed since the HIPO started.

When returning a status code 503 for maintenance, a page is treated like a failing server. Therefore, the Edge Side Includes (ESIs) did not render. Treating a page like a failing server breaks the page as the content does not render correctly. The 503 status code is no longer being returned under this condition. The page now correctly renders the content.

When attempting to disconnect an A/B test from a content block on a Content Page, an error was shown to the user that prevented the disconnection. The A/B testing service would return a 422 response code for A/B tests in a Finished state, which was incorrectly handled in the Page Builder. The Page Builder will now appropriately handle a range of response codes from the A/B test service. It is now possible to disconnect the A/B test from a content block once the A/B test is in a Finished state.

Using a DXP design area and a globals asset keyword in a Design parse file simultaneously would cause page timeout. The mix of these operations in a Design resulted in an infinite loop of resolving keywords. The Design processing logic will no longer continue to attempt to resolve keywords that reference other keywords infinitely.

The way that Component Sets were made available to a Content Page and Standard Page was different, resulting in these assets behaving differently. The logic controlling how a Component Set is made available was inconsistent between the two asset types. These asset types now use similar logic to determine which Component Sets are available in their respective page-building experiences.