Release Notes 3.2.3
Publication Date: August 10th 2018
The following are the news features, enhancements and fixed issues for Cloud CMS 3.2.3 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
- Project exception logging to tenant log is done more efficiently
- Support for bulk creation of page renditions within cloudcms-server WCM module
- Fix so that Elastic Search Transport Client uses Scroll API more efficiently
- Fix so that Relator Properties that build upon $ref hyperlinks will resolve and save correctly, allowing for correct deep-nested persistence and detection of nested properties
- Fix so that newly created Translation nodes will not take on the Master Node filename
Cloud CMS Application Server
- Updated to latest Gitana JS driver
- Virtual driver background connection loop now automatically disconnects if virtual config authentication fails
- WCM and Dust page and fragment renditions now bulk commit back to Cloud CMS API
- Config parsing now uses JSON5 to allow for some forgiveness of malformed JSON config documents and Gitana driver configuration files
Cloud CMS User Interface Server
- Improvements and fixes to Project and Platform search functionality
- Project Search page now supports empty initial results until a search term is entered
- Improvements to support for IE10 and IE11
- Upgraded to latest CKEditor and Handlebars third-party libraries
- Added a "ckeditor-tools" helper library to make it easier to develop and register CKEditor plugins
- Fix to Manage Content Types link on Content Types left-hand menu
- Fix to some screen formatting edge cases
- When deleting nodes or associations, the type QName of each node is now listed on the pre-delete
Cloud CMS Command Line Client
- Increased the project list size for the connect() command to 100
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.