Releases

The Cloud CMS product suite is available to subscription customers for installation on-premise or within your own virtual private cloud. The product suite is delivered as a series of Docker images along with sample installation scripts to help you get running.

Cloud CMS runs on any Docker host including Amazon AWS (via Cloud Formation templates, Amazon Elastic Container Service, Amazon Elastic Beanstalk or the Docker AWS Engine), IBM BlueMix, RackSpace, Digital Ocean and many others.

The download consists of a ZIP with sample configuration files to launch the complete Cloud CMS stack in variety of configurations including development, standalone and clustered. The sample configuration files are provided using Docker Compose.

To run Cloud CMS on-premise, you need to be a Cloud CMS subscriber.
Contact Cloud CMS to purchase a license or request an on-premise trial.

Subscribe to our Mailing List

We'll send you notifications when new product releases and new features are made available.



Cloud CMS Release 3.2.15

Published on 11/17/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.15 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.

Cloud CMS API

  • Fixed a bug that prevented some preflight CORS requests from working properly
  • Added support for {{initiator.name}} in workflow email templates
  • Fixed a bug that prevented the Administration Console from persisting a cookie, requiring users to log in more than once
  • Web Hooks fired when a release goes live now correctly preserve HTTP headers from JSON config
  • New Projects created via the UI now enable the Content Model Builder and the left-hand Folders tree by default
  • Improved automatic QName generation for new Content Type definitions

Cloud CMS User Interface Server

  • Document header now shows modification date, modified by, creation date and created by underneath title of the document
  • Removed the Document Properties panel from the Document Overview page
  • The "Edit Content" action on the Content page is now hidden when multiple items are selected
  • The "Edit Document" action on the Folders page is now hidden when multiple items are selected
  • Edit Actions now redirect to document Edit Properties page (instead of using a modal for content entry)
  • Fixed a bug whereby the Document Viewer page would not render for documents viewed either via document library, via workflow or via a workflow task
  • Added back missing GraphQL icon
  • Changed the sample GraphQL query to be based around n:node
  • Improvements to Content Model Builder to provide better validation, some more defaults and smooth out usability a bit more
  • Pickers now support the optional use of a DataLoader to reduce network traffic and bulk load picked items (DataLoader class is provided out of the box for use in custom pickers)
  • Improvement to automatic QName generation when creating definitions
  • Fixed a rendering issue within Administration Console's when viewing Client objects
  • Fixed a bug in the login page so that original URL is properly retained and redirected to after login

Cloud CMS Command Line Client

  • Added command to List Projects (with pagination)
  • Added command to Query Projects (with query + pagination)
  • Added command to List Applications (with pagination)
  • Added command to Query Applications (with query + pagination)
  • Added command to Download API Keys (gitana.json)
  • Added commands to Get, Set and Remove DataStore configuration key/value pairs
  • Fixed a bug ensuring that the embedded Cloud CMS application server always mounts to the current directory


Cloud CMS Release 3.2.14

Published on 11/12/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.14 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.

Cloud CMS API

  • Support for Multifactor Authentication (MFA - external SMS, Voice or App verification code for sign in) configurable globally as well as per-tenant via service configurations. Initial out-of-the-box providers for Authy and Duo Security. For more information, see https://www.cloudcms.com/documentation/mfa.html.
  • Added formal support for encrypted properties within API configuration properties files using pub/private keys. This allows passwords, secrets and other credentials to be safe guarded so that they are only read by the API server. For more information, see https://www.cloudcms.com/documentation/docker/configuration/encrypting-properties.html.
  • Ensure node service invalidates for branch when branches are archived
  • Added a check to make sure that archived branches are not included in dashlet controllers recent content queries
  • Added command line tool to help customers generate pub/private keys and manually encrypt and validate encrypted values within properties files
  • Updated third party dependency versions

Cloud CMS User Interface Server

  • Added support for Multifactor Authentication (MFA) - services and user settings screens and a new wizard that helps users set up MFA and register their mobile devices. For more information, see [https://www.cloudcms.com/documentation/mfa.html]
  • Fixed a bug whereby admin console wouldn't render in some browsers due to a CSS glitch
  • Fixed a bug that prevented the Authentication Grant Edit page from working for some grant values
  • A message is now shown when an attempt to undeploy a workflow fails
  • Fixed a bug that prevented form "view" attributes from being copied back to the Alpaca config ahead of render of a content form (this prevent some layouts and wizards from working as intended in those cases)
  • Fixed a bug that prevented the UI from rendering properly after a selected release is archived and the active branch is still being referenced in the browser URL (in this case, the browser URL is deliberately reset to prevent this from happening)
  • Document View Properties now shows the edited date instead of the modification date to make it more intuitive and consistent for editorial users
  • Fixed a bug that prevent content types (on the left hand side of the Content page) from being sorted correctly
  • The "My Projects" dashlet now supports specification of sort (recently created or recently modified with the former being the default)
  • Fixed a bug that prevented the Kaltura module's menu options from appearing in the right place


Cloud CMS Release 3.2.13

Published on 11/04/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.13 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.

Cloud CMS API

  • API now populates a special header ("x-cloudcms-api-execution-time-ms") that stores the time in milliseconds between when the API sees the request arrive and the first byte is committed to the output stream. This can be useful while debugging latency issues as it indicates what portion of the latency is network-related versus execution-related (i.e. DB timing or index performance).
  • Fixed a bug that prevented the "_parent" of a definition from being updated from within the user interface
  • Better handling of exceptions while sending emails
  • Branch repair function now automatically handles cases for duplicates QNames in the dictionary

Cloud CMS User Interface Server

  • Better handling of exceptions while sending emails - improved error messages when an email provider isn't available or is misconfigured.
  • Action titles now support config-service specification of titles and other attributes, allowing for dynamic configuration and override of action modals and labels using Handlebars.
  • Improved support for automatic Handlebars processing of values coming out of config service, allowing for dynamic labels for pages, buttons and more.
  • Content Model Builder now refers to "arrays" as opposed to "lists".
  • Fixed a bug that prevented Project-level sorting and display settings for Content Types from saving properly.
  • Fixed a bug whereby the "Copy to Folder" and "Move to Folder" actions were not allowing folders to be picked properly
  • Navigation has been improved so that clicking into a content instance from the "Content" page no longer jumps out to the "Folders" routes. Instead, the "Content" route remains and the breadcrumb is consistent, keeping users in the "Content" section and letting them click back at any point.
  • Fixed a bug that prevented pagination controls from showing up for the document list when viewing large data sets and viewing across subfolders.
  • Improvements to bread crumb to reduce the amount of information shown so that it is shorter and always relative to the left-nav menus.
  • Fixed a bug with the Create Data List wizard where the list item type wasn't being applied correctly.
  • Fixed a bug in which changes to a user's avatar image were not reflecting immediately

Cloud CMS Command Line Client

  • New version of the command line client that provides better support for scripting and non-interactive modes
  • Allows for easier scripting and response handling
  • Added commands for branch query, search, read and repair
  • Latency checks now report API execution time as well as round-trip latency timing inromation


Cloud CMS Release 3.2.12

Published on 10/22/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.12 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.

Cloud CMS API

  • Fixed a bug whereby projects containing legacy datastore types (such as "warehouse") could fail to export
  • Ensure that historic password policy is bypassed when adjusting special principal passwords via Spring bean configuration
  • Speed up API startup time by reducing the number of classes scanned for annotation processing
  • Deployment publishing between branches now increments path and search indexes much faster
  • Fixed a bug where two repositories with the same branch ID could result in incorrectly bound rules and behaviors for certain cases
  • Added chunking for file/folder system when querying node paths recursively, allowing for much larger sets of recursion to be processed more efficiently

Cloud CMS User Interface Server

  • Fixed "Move To" and "Copy To" actions so that they now allow default to picking folder targets exclusively
  • Several improvements to visual Content Model Builder
  • Project list page now shows additional information (creation date, modification date, etc)
  • Fix so that creating a new version of a workflow model preserves the "email" and "emails" properties
  • Fix to the default Set Local and Remove Locale action configs so they show up when expected
  • Fix a bug where the search term would "stick" between clicks which could cause a seemingly empty set of items to show up on the new page (since filter was being errantly applied)
  • Removed "tip view only" form Workflow Models screen
  • Added "Deploy Workflow Model" and "Undeploy Workflow Model" buttons to the Workflow Model overview page


Cloud CMS Release 3.2.11

Published on 10/14/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.11 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.

Cloud CMS API

  • Web Hook calls now include a "projects" array that supplies project information (id, title, type) in the JSON payload
  • Fixed a bug whereby after transaction handlers were not always firing after deployment to a target branch. This was preventing target branch rules from firing off web hooks, among other things, when content was deployed to it.
  • Fixed a bug whereby path indexing that contained nodes with titles that had a slash in them ("/") could be improperly indexed and fail to look up, resulting in UI errors and problems with the Tree API
  • Fixed a subtle glitch in the dictionary compiler wherein local properties were not correctly overriding properties inherited from superclass features
  • Added some performance improvements for S3 storage that utilize new S3 API methods
  • Fixed a bug with the Binary Storage Caching Provider's cache invalidation logic which could cause cached nodes to delete prematurely
  • Project Controller and Project Service now support a "_protected" boolean in the JSON payload to indicate whether the new Project's Stack should have deletion protected enabled by default

Cloud CMS User Interface Server

  • Fixed a UI glitch whereby documents with "/" in their title would fail to load within the document library
  • Improvements to path display and navigation within breadcrumb and within helper templates (doc lists, content lists, search pages)
  • Added a warning when a user tries to add an attachment with an ID that already exists, allowing the user to proceed (overwrite) or cancel the action
  • The Create Project wizard now automatically sets newly created Projects to be "protected" so that they cannot accidentally be deleted (without first toggling off protected mode)
  • The Cloud CMS Image Plugin and Link Plugin for CKEditor now support a "hideUploadButton" option to allow form developers to toggle off the upload button on the respective pickers
  • Fixed a bug wherein wizard modals wouldn't always auto-focus on initial render
  • Fixed a bug wherein the wrong user "viewing" icons could show up on the the Root Folder in the Document Library
  • The Document Translations page now supports configurable buttons
  • Added validation logic so that Release Dates cannot be assigned if those dates are in the past
  • Added check to ensure that bad JSON isn't saved for document definitions when editing by hand
  • Document Listing summary "type" link now takes you to the Content Model Builder (if its enabled) and otherwise takes you to the Definition page
  • Several bug fixes and improvements for Content Model Builder - enhance preview to be more resilient for different display modes, add a validation check to ensure JSON is properly formatted ahead of being saved, disable buttons and dropdowns during preview, improve object handling
  • Improved Embeddia Media HTML generation when using CKEditor - more features and more customizable
  • Fixed a bug whereby the Set Locale and Remove Locale actions could appear at the same time


Cloud CMS Release 3.2.10

Published on 10/08/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.10 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.

Cloud CMS API

  • Added support to Cloud CMS for GraphQL on a per-branch basis with automatic SDL schema generation and full query support for all content types, association types and features. The Cloud CMS GraphQL implementation supports collection-level query, search and pagination, letting you nest calls that leverage MongoDB query and the Elastic Search DSL.
  • Inline Links now properly cleanup when a document is has a touch() operation performed against it
  • Performance optimizations and improvements

Cloud CMS User Interface Server

  • Added a GraphQL page to allow developers to write and test adhoc queries against a branch, supports query, variables and operation name and provides links to endpoints
  • Fixed a mislabeled field for user mappings within SSO configuration screen
  • A few light improvements to the release merge conflict management screens to make them a bit easier to use
  • Several Embedded Media improvements so that users can now see changes in HTML when extra attributes are added, remove the default "data-" prefix for extra attributes, adjustments to CKEditor plugin to make insertion more accurate for multi-HTML elements
  • Improvements and fixes for the visual Content Model Builder - prevent applying JSON with syntax error, fix for a problem where sequential saves on newly created forms could fail, improvements to array type field, auto-submit when enter key is pressed


Cloud CMS Release 3.2.9

Published on 10/01/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.

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")


Cloud CMS Release 3.2.8

Published on 09/23/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.8 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.

Cloud CMS API

  • Added a Project settings option to allow Releases to automatically select "Keep Local" for any merge conflicts that are detected. This reduces the number of steps that editorial users need to take to merge Releases for cases where conflicts may frequently occur (by automatically keeping the release version of the content)
  • The tree API now supports an "object" request parameter (boolean) so that the result items will contain a field called "object" that is a full copy of the node at that level in the branch
  • The tree API now supports filtering via Elastic Search DSL, enabling full-text search across results
  • The tree API now supports both "query" and "search" via its HTTP JSON payload ("query" and "search" can be passed in as sub-objects) and can be run independently or together for a unified record set
  • Fixed a tree API problem where "properties" were not being handed back for the base node result
  • Deployment service has been improved to provide better support for multi-archive deployments
  • Deployment service documentation and reference now includes sample custom HTTP deployment receiver t serve as a guide for folks who want to build their own implementations
  • Branches now automatically take on the title of a release
  • Release titles are now enforced to be unique across a repository

Cloud CMS User Interface Server

  • Document Library and File Picker filter now uses Elastic Search
  • File Picker now provides three ways to filter - "within current folder", "within any subfolders" and "all content", making it easier for editors to find things using pickers
  • The File Picker now allows you to specify a custom query (picker.query) to use in filtering results, making it more consistent with how the Node Picker already works
  • Improvements to Release pages to simplify pages, improve error messaging and reduce the number of options in some cases
  • Improvements to Embedded Media Editors, including support for extra, configurable attributes and additional HTML tags (iframe, div, img). Insert action now displays all html tags defined in xxx-link class.
  • Added support for Automatic Merge Resolution within Project Manage > Releases
  • The Document Properties panel on the Document overview page now shows localized timestamp information for creation and modification dates
  • Fix to IFrame action support lib to ensure modal is cleaned upon handling "reload" and "redirect" events

Cloud CMS JavaScript / Node.js Driver

  • Added support for findRelatives() against a Node
  • Improved loadTree() API to leverage new tree API features including "object", "query" and "search".

Cloud CMS Developer SDK

  • Added HTTP deployment receiver example


Cloud CMS Release 3.2.7

Published on 09/17/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.7 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.

Cloud CMS API

  • Fix to Tree API whereby incorrect folder children could be handed back if a sibling had a similar filename
  • Improvements to file folder indexing for faster performance

Cloud CMS User Interface Server

  • Branch picker now displays branch title when selecting Deployment Targets
  • Fixed a bug whereby the Next button had to be clicked twice when creating new platform users
  • Adjusted UI Templates and UI Pages screens so that they default to storing project global UI views / configs
  • Fixed pages for Content Instances, Documents List and Project Search results so that they use the correct UI config while rendering
  • Fixed multi-select support for node picker control
  • Fixed a bug which prevented a new Authentication Grant from being created within the Administration Console
  • Adjusted the "Remove Locale" action so that it draws uses localized text from localization bundle
  • The "Edit Translations" dropdown on the document properties page can now be enabled or disabled via configuration
  • Fix so that document and content instance row actions link to the proper URLs
  • Updated to latest thirdparty libraries

Cloud CMS Node.js Driver

  • Added support for HTTP and HTTPS proxy servers


Cloud CMS Release 3.2.6

Published on 09/03/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.6 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.

Cloud CMS API

  • Faster performance with reduced set of event handlers
  • Added "http" deployment handler to out-of-the-box configuration
  • Removed legacy warehouse and bulk transaction APIs

Cloud CMS Application Server

  • Fix for awareness service (when running cluster-backed and using Redis)

Cloud CMS User Interface Server

  • Removed legacy warehouse pages and icons
  • Radio fields now resolve to "string" schema type by default within Content Model builder
  • Fix so that CKEditor plugin paths resolved properly
  • The "Make Multilingual" action no longer appears for translated documents
  • Fix so that datetime conversion works properly for all formats
  • Changed the name of the "Add Translation" button on the document translations page to "Create a New Translation" to avoid confusing over "create" vs "add existing".

Cloud CMS JavaScript Driver

  • Removed bulk transaction and warehouse methods









Ready to Try Cloud CMS?

It's Free to Sign Up, No Credit Card Required