Release Notes 3.2.30
Publication Date: March 23rd 2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.30 release.
Upgrade from 3.1.x
For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the [Cloud CMS 3.2 Migration Documentation](https://www.cloudcms.com/documentation/docker/maintenance/upgrades.html).
Cloud CMS API
- Faster branch creation that takes advantage of some improvements to MongoDB that allow for optimized collection copies
- Improved branch merging that now leverages a memory cache for much faster execution. Many improvements including more efficient string substitution on merged objects, a more robust method for applying JSON patches, reduced event handling overhead
- Improved support for JSON Patch, patch generation and patch merging as used within the product to detect and resolve merge conflicts. Improved support for nested arrays and enumerated value sets.
- Added some safety checks to ensure that Access Control lookups that contain any unresolvable references will continue to process and will just ignore the missing reference.
- Added some safety checks to ensure that module deployments will work even if the Application deployment sub-objects contain bad data or do not parse as expected.
- Adjusted Remote Deployment Receivers so that they default to using a GET to retrieve remote deployment package status
- Certain reserved user names are now blocked for being used on creation and update of principals so as to prevent confusion (such as system, admin, everyone and other reserved names).
- Fixed a bug where some distributed jobs executing in the cluster could error out but remain stuck in a RUNNING state (this impacted some cases where multiple jobs could execute concurrently and get stuck until the sync timeout).
Cloud CMS User Interface Server
- For Releases and Workspaces, the "Pending Merges" page now only appears when the underlying branch has unresolved merge conflicts.
- Fixed a bug that prevented the CKEditor-Tools plugin from loading properly for some cases.
- Fixed a bug that prevented the Project Members page from correctly performing ACL checks when users in the project spanned multiple domains.
- Added the ability to configure the "maxFileSize" option for Node Picker and File Picker uploads.
- Removed an extraneous "path" sorting option from the Node Picker.
- Fixed a bug that could cause the Markdown field to not render properly for some cases
- Fixed a bug that impacted how fields would internally get named by adjusting how field names with square brackets and slashes are serialized and token replaced
- Fixed the "Pick A Color" field so that it properly puts the hash ("#") in with any selected values.
Cloud CMS JavaScript Driver
- Fixed a bug that prevented References acquired using the ref() method from being incorrectly typed for Users and Groups (those types were capitalized when they should not have been).
- Added the ability to plugin a custom map handler function for chainPost() calls
- Added a generic ResultMap class
See Gitana with your own content
Talk with a solutions engineer about your content model, governance requirements and deployment — hosted in our cloud or running in yours.