Release Notes 3.1.435
Publication Date: April 8th 2018
The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.435 release.
Cloud CMS API
- Added API and service methods to compress repository changesets for a given node. This provides a way for DB administrators to reduce allocated space within their Mongo DB installations.
- Performance improvement for recursive lookup of group memberships to reduce DB locks and work more efficiently over large data sets
- Updated default MongoDB collection indexes to include "_system.created_on.ms" and "_system.modified_on.ms" so as to support the most common default sort strategies
- Node transfer import crawls non-system text properties for nodes and associations to perform substitutions of IDs within embedded textual elements (such as <a> tags)
- Additional safety check logic to ensure that the master branch cannot be archived
- Gitana Ticket cookie now automatically cleans up when decryption of the JWT value fails
Cloud CMS Application Server
- Improvements to module deployment and module descriptor cache state handling allowing for faster, more immediate module deployment and invalidation
- Improvements to remote configuration retrieval
- Enhancements to awareness service to provide a more reusable and extensible class-based implementatin pattern, performance improvements and additional awareness capabilities
Cloud CMS User Interface Server
- Added field to administration console allowing for the import strategy to be specified
- Bug fix so that clicking the "modified by" user name on a "Documents" list item takes you to the correct place
- Fix for a bug in require.js where loading could time out on slow connections
- Increase default HTTP timeout to 120 seconds for resources loaded within web browser
- Fixed a bug whereby trial user logouts could fail
- Added some backward compatibility logic to automatically clear out legacy session and local storage values
- Fix so that default theme loads in event of a bad theme reference or a loading timeout
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.