Release Notes 3.2.9

Publication Date: September 30th 2018

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.9 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

• Fix to Tree API so that containers are properly marked on leaf nodes
• Fix to Tree API to allow for an empty JSON POST payload
• Added Elastic Search HTTPS support when using Elastic Search HTTP Client
• Adjusted the default Elastic Search index mappings so that _system and _features are queryable and common timestamps (_system.created_on.ms, _system.edited_on.ms, _system.modified_on.ms) are all queryable as Elastic Search Dates
• Text searches now include an additional trim() call (ahead of being converted into ES query string JSON blocks) so as to help with a common editorial case where an extra space might be appended or prepended
• The HTTP Deployment Handler now gracefully handles non-JSON responses with a fallback to non-status URL polling
• Fixed a bug with inline link tracking whereby inline links could accumulate instead of overwrite
• Inline links now regenerate from the ground up when a node is a touched

Cloud CMS User Interface Server

• Document Library now supports the same updated filter that was made available for the File Picker and now offers multiple search modes (current folder, all sub-folders, all content)
• Fix to flicker that occurred in wizard when a page was automatically next'd based on initial conditions
• Adjusted all file picker actions to use the updated file picker control, standardizing all file selection actions to a common picker
• Made the auto-generation of ES search from text more aware and forgiving of Elastic Search query string structure - now applied across the product including in node picker
• Updated to latest JSON editor plugin
• Added the ability for some pages to be switched to read-only mode based on config / evaluators ("definition-json" and "form-json")