All Release Notes

Release Notes 3.1.394

Publication Date: August 22nd 2017

The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.394 release.

Cloud CMS API

  • Transfer Export/Import/Copy optimizations to utilize ZIP store, less disk IO and threaded execution of compile and export operations for large sets of dependencies
  • Faster changeset history computation with lower memory footprint
  • Added changeset service queryChangesetNodes method
  • Performance caches on node service with LRU cache support
  • Additional tests for performance and metrics collection
  • Switched disk IO store layer to use Java NIO
  • Better healthcheck calculation for percentageUsedMemory
  • Latest gitana-common, improvement to be sure streams close on web hook request/response commit, invalidate page renditions action test

Cloud CMS Application Server

  • Upgraded to LinkedIn Dust.js 2.7.5
  • Improved chunk error handling
  • Web page cache does not populate if downstream fragments fail to render
  • Improvements to /res route to support cookie-expressed repository and branch bindings
  • Better baseURL handling for virtual driver connects, support for "virtual" store configuration
  • Fix so that performance middleware using mimetypes doesn't overwrite no-cache when it should not
  • Reduced number of markRendition calls back to the Cloud CMS API
  • Fix bug with nodeLimit and nodeSkip params on @associations, allow setting a form’s dom id when using @form tag

Cloud CMS User Interface Server

  • Improvements to "ui" public library
  • Code cleanup, some optimizations to reduce code size
  • Copying a project now defaults to compressed changeset history
  • Data Lists now allow for export of selected items to CSV, ZIP, PDF or download (just as with nodes elsewhere in the user interface)
  • Fix for nested tables in forms
  • Added file-picker mimetypeRegex attribute + image picker defaults to more reasonable image selection settings




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.