6.33 release notes

System administrators only had access to the Maintenance  HIPO Herder menu. This restriction prevented other user account types, such as backend users and content editors, from managing their HIPO Herder tasks. Any user with Admin UI access can now access the Maintenance  HIPO Herder menu.

Metadata descriptions were not visible in custom edit layouts because they were excluded at a system level. Metadata field descriptions now appear in custom edit layouts as configured on the Metadata screen. The exception is when metadata fields are customized by displaying the field input separately using the %metadata-F_{metadata field id}% keyword.

The account manager form included a query string parameter to forward to the inline edit interface upon submission. After submission, a user could have been redirected to a screen they did not have permission to view. The query parameter has since been removed when the user is not inside the Admin UI, which makes any account manager page forms work correctly.

Custom form fields could only be created from the Details screen of a custom form or section, not through the asset tree. Form fields can now be created through the Create new…​ option from the asset tree menu or through the New option in the menu bar.

An issue with the "Cancel Safe Editing" (when using multiple "contexts") logic was that it did not restore the Context checkbox state after canceling a safe edit operation. The state of any changed contexts when canceling safe edit is now validated against the status before activating safe edit.
Given these conditions, the checkbox would not revert to selected after the safe edit operation is canceled:

Customers could not authenticate to a Twitter endpoint using OAuth 1 when the request body contained JSON. When a request content type is specified but is not URL encoded, the request body is excluded from the OAuth 1 signature. This change removes the unsupported content type issue that customers originally encountered.

The Add component panel assumed it should attempt to fetch Squiz DXP components as a nameless set of the Squiz DXP Components:

A minor visual change was made to the DXP Services screen to indicate that the API key field is used for general Squiz DXP services, not just the Component Service.