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.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


Cloud CMS Release 3.2.5

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

  • Improved handling for post-release case where a snapshot may fail to generate and the release still appears unreleased (even though it had successfully released)
  • Cleaned up and improved the logging of release process into stdout logs
  • Handle an error case where concurrent publishing and unpublishing under high load could cause a deployment package to bypass its reporting of failed deployment records
  • Enhanced node merge resolver to automatically work out what to do for cases where multiple nodes with the same QName or the same ID in a release target branch could exist and collide
  • Improvements to branch fork, merge and merge conflict management to align with release service adjustments

Cloud CMS User Interface Server

  • Added Handlebars processing of action config to allow for full I18N localization capabilities within the UI (using message bundle string replacement)
  • Fixed a bug into Data View query builder so that views can be dynamically constructed as intended
  • Data View now supports paginated scrolling of record sets
  • Data View export now lets your properly specify the number of records to export (fixing bug where this would default to 25)
  • Back by Popular Demand! Re-introduced the Manage Project > Forms page to allow folks to see all of their forms in place (instead of viewing within definition)
  • Updated icon for document associations
  • Fixed a bug where the Create Form action could fail when creating forms for associations or features
  • Project Branch Picker now shows branch title when it can (instead of just Branch ID) - helpful when configuring Deployments
  • Fixed a form bug whereby Number fields had null min and max by default

Cloud CMS JavaScript Driver

  • Added ability to paginate executeReport() call


Cloud CMS Release 3.2.4

Published on 08/22/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.4 release.

Cloud CMS API

  • Upgraded to Tomcat 9.0.11
  • Fixed a bug whereby schema references (using $ref) were not being tracked properly as dependencies during dictionary compilation
  • Fixed a bug whereby Tree API path resolution and query could fail for some special characters (non-ASCII or big charset)
  • Improved logging for Hazelcast cluster configuration
  • Upgraded to latest Hazelcast and ensure Hazelcast SSL disabled by default
  • Fixed a branch merge bug wherein a source node merging into an existing, saved target node could cause the target node to lose track of its previous changeset ID
  • Improvements to branch merging and release execution
  • Fixed support for Zookeeper discovery with clustering
  • Merge conflicts are now cleaned up on finalize() and release() so that other release branches that a given release branch had conflicted with (or who had conflicted with us) will automatically purge old merge conflicts that are no longer required given that the given release branch had already executed successfully

Cloud CMS User Interface Server

  • Improved support for message bundles and localized text within the UI (extensible via config service)
  • Enhanced default message bundle for locale and language text
  • Added ability to customize Publishing by content type (customizable workflows per type and also custom HUD buttons on document page per type)
  • Fixes and improvements to visual Content Model Builder to support more field types and form configurations
  • Visual Content Model Builder supports content types with features and $ref references
  • Improved support for custom Media Type and Field Editor implementations within custom UI modules
  • Fixed a bug that occurred when Copying a Form on the Project Forms page

Cloud CMS Developer SDK

  • Added sample implementation for a custom Content Model Field Editor
  • Added sample implementation for a custom Media Type


Cloud CMS Release 3.2.3

Published on 08/11/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.

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


Cloud CMS Release 3.2.2

Published on 08/03/2018
The following are the news features, enhancements and fixed issues for Cloud CMS 3.2.2 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 event handlers to prevent scenarios in which the root node for a branch could accidentally have its QName or its Type modified
  • Elastic Search queries now automatically apply "keyword" analyzers for paginated sorting of system managed properties
  • Improvements to logging for Elastic Search related errors
  • Added API method to find the nearest ancestor from a file in a file/folder hierarchy that matches a given type
  • Fix so that web renditions correctly apply model variables on preview generation
  • Fix so that complex find operations (paginated across ES search and MongoDB query intersection) won't error out on reporting call
  • Fix so that tenant error logs capture with project/stack resolution correctly

Cloud CMS Application Server

  • Added support for server.driver() function to allow for registration of custom functions to determine how driver gets loaded and applied to downstream middleware (to power req.branch() and so forth)

Cloud CMS User Interface Server

  • File Picker control is now more extensible and uses Handlebars to process picker options, allowing for ease of extensibility through method overrides
  • Fixed helper text when working with preview servers so that Handlebar syntax is recommended
  • Fix so that user settings persist back correctly for empty values
  • Resolved an issue with the Alpaca Color Picker control whereby persisted values would display incorrectly
  • Node picker filter now works directly against Title and Type field for more accurate selection
  • Fix to Cloud CMS Math Pack Add-on
  • Corrected a bug whereby custom content type config (from module) would not correctly apply to document creation wizard type selector
  • Fixed a bug where selection of content types from the Manage Project > UI Content Types would not pick up right away
  • Clicking on the Advanced Search page leads to the search results page but doesn't populate right away and instead waits for search filter entries before hitting search API


Cloud CMS Release 3.2.1

Published on 07/30/2018
The following are the news features, enhancements and fixed issues for Cloud CMS 3.2.1 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

  • Link Tracking now extracts and tracks plain-text inline links (http:// and https://)
  • Reduced logging on API startup
  • Fixed a bug whereby unresolved definitions during branch compilation phase would raise errors
  • QName downloader now supports validation of in-flight, compiling definitions
  • Fix so the localized nodes retain system properties for master node on retrieval
  • Upgraded server-side script support to Rhino JS 1.7.10
  • Added new associated node policies (beforeReadAssociatedNodeAttachment, afterReadAssociatedNodeAttachment, beforeCreateUpdateAssociatedNodeAttachment, afterCreateUpdateAssociatedNodeAttachment, beforeDeleteAssociatedNodeAttachment, afterDeleteAssociatedNodeAttachment)
  • Improvements to scripting engine for some faster performance, caching
  • Faster permission and authority checks, improvements to a few places where role invalidation will now be more accurate
  • HTTP Content-Disposition header now has double quotes around the attachment file name if it contains a space
  • Fixed a bug whereby bulk search indexing could miss some attachments

Cloud CMS Application Server

  • Fix so that recursive rmdir will fail silently for cases where long file names may not work as intended (on some Node.js / operating system permutations) - this fixes an issue where modules could fail to deploy
  • Store adapters now support stats() and use last modification time to compute a more accurate timestamp for module descriptor caching
  • Fixed a bug with SSO SAML logging

Cloud CMS User Interface Server

  • The "help" dropdown menu is now configrable and can be extended/overridden through modules and custom config
  • Improved the document translations view to be more concise (fewer columns, shows language and edition under "details")
  • I18N locale now shows language in addition to language/country ISO code
  • Fixed a bug whereby module deployments were not always appearing (due to a caching bug)
  • Added support for Embedded Media editors with CKEditor plugin and support for YouTube, Vimeo, SoundCloud and BrightCove
  • Added single column layout for dashboard (1-column)
  • Updated Alpaca library
  • Fix to form options loading via $ref

Cloud CMS JavaScript Driver

  • Added support for download of Node.js compatible streams

Cloud CMS Developer SDK

  • Added sample CKEditor Plugin Module


Cloud CMS Release 3.2.0

Published on 07/21/2018

Release Notes

Publication Date: July 15th 2018

We're pleased to announce the Cloud CMS 3.2 GA release. This is a major release that includes a vast number of product improvements and fixes as well as a multitude of new features. We've been hard at work at these features for several months and are happy to have them finally make their way into general availability.

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.

New Features

  • Elastic Search 6.2.4 - Cloud CMS now ships with support for Elastic Search 6.2.4. Accordingly, the product now also offers improved search capabilities that leverage the enhanced search and property/type support offered by the most recent version of Elastic Search. In addition, Cloud CMS is now compatible with Amazon Elastic Search service offerings (recent 5.x and 6.x versions).

  • Deployment - Cloud CMS now lets you manually and automatically deploy content from a source Project branch to a target Project branch (or to a deployment receiver). This lets you move content between Projects on the same Cloud CMS installation or to Cloud CMS installations running within other data centers anywhere in the world. With Deployment, Cloud CMS makes possible true, end-to-end multi-channel content delivery across enterprise environments (Development, QA, Staging, Production/Live). In addition, Cloud CMS includes a number of out-of-the-box deployment receivers that let you concurrently transform and publish content to a path-based, file system locations such as Amazon S3, FTP, disk and Custom HTTP listeners.

  • Publishing - Cloud CMS now includes a preconfigured content publishing engine that integrates with our workflow offering to provide lifecycle/state management for content along with automatic, rule-trigger deployment to target Projects. Publishing is automatic and instantly happens in the background. Click the "Publish" button to deploy your content worldwide and click "Unpublish" to archive content and bring it offline.

  • Preview Servers - Cloud CMS now offers a new way to manage content Preview Servers. Content that can be "previewed" will have a Preview button. Click the button to see how the content would look on the live web site or within Staging/QA. Furthermore, this integrates with Cloud CMS rendition tracking to let you preview exactly where you want to see it -- choose among all of the pages where a single piece of content may appear.

  • Link Checking - Cloud CMS now provides the Inline Links content feature (f:inline-links). Content tagged with Inline Link tracking will automatically have its HTML properties parsed. Any links contained within (whether referencing internal or external resources) will be parsed out and maintained in an automatically managed relator property. The content graph is updated to reflect those relationships. Link tracking then allows you to automatically check all of the links contained within your content for validity ahead of publish or deployment.

  • Bulk Import - Cloud CMS has improved its support for bulk import via its command-line tool. The command-line facility lets you hook in custom code (written in Node.js) to import your JSON, XML and/or binary content to Cloud CMS. This includes content instances as well as schema definitions, forms, translations and everything that Cloud CMS works with.

  • Single Sign On - Cloud CMS introduced Single Sign On (SSO) in the 3.1 release not long ago and this has been improved in 3.2. In addition to supporting SAML 2.0 and JWT, Cloud CMS now lets you automatically synchronize user properties and group/team membership from SAML assertions and JWT properties. As such, Cloud CMS automatically picks up user properties from your Identity Provider, letting everything work very smoothly with regards to your enterprise security requirements.

  • Releases - Cloud CMS has enhanced its branch and release engine to support more complex merges. A vast array of bug fixes and improvements have gone into this to make the merge process faster and more efficient as well as more reliable.

  • (UI) Easier Navigation - Cloud CMS now has a simplified UI that reduces the number of left-hand menu options. We've added "Manage Platform" and "Manage Project" sections that move all of the administrative or developer links off into their own place. That way, editorial teams enjoy a much smaller set of menu items, making it easier to find what they need to find.

  • (UI) Dashboards - Cloud CMS now features platform and project level dashboards and dashlets that let users and administrators configure their tools and views using nothing more than drag-and-drop. Users can customize layouts and pick which dashlets they want on their home pages. Administrators can lock things down as needed, giving their users the amount of freedom they desire on a per-project basis.

  • (UI) Content Model Builder - Cloud CMS now offers a visual, drag-and-drop schema and form builder that lets your developers and editorial teams quickly assemble content types and definitions. The Content Model Builder lets you rapidly assemble JSON Schema-driven forms that ride on top of the 50+ controls that Cloud CMS offers out-of-the-box, including support for nested objects, arrays and associated relationships.

  • (UI) Image Editor - Cloud CMS now offers inline image editing facilities so that images can be resized, cropped, rotated and otherwise manipulated without the need of an external third-party tool. Images are backed up automatically and can be restored at any point.

  • (UI) Awareness - Cloud CMS now lets you see who else is working within a Project or on a particular document at the same time as you are. User avatar icons appear to show you who is viewing the same space that you're viewing. This provides collaborative insight into what activities your teammates may be working on along with you.

  • (UI) Document Locking / Notifications - Cloud CMS now automatically locks content as soon as you start typing. When you begin making changes to a document, anyone else who is "viewing" that document at the same time as you will see it go into read-only mode. They will be notified that you are making changes. When you are finished making changes, they will be notified that the document can be edited again. Cloud CMS also lets users notify each other when they'd like to make a change (and someone else has the lock). This provides a really nice way to avoid stepping on each other's toes while working on the same sets of content.

  • (UI) Quick Links - Cloud CMS now provides "quick links" for documents that appear in lists (such as the document tree or the content page). Quick Links show up as little icons for each row in the result set and let you do things like quickly edit a document. They reduce the number of clicks needed for frequent activities.

  • (UI) Folder Tree - Cloud CMS now provides a left-hand Folder Tree in the Folders view. When browsing through folders, the left-hand Folder Tree lets you see the hierarchical structure of folders, making easier to understand where you are and to jump around between locations. This left-hand tree can be enabled or disabled from the Project Settings page.

  • (UI) Extensibility - Cloud CMS now provides more hooks and extension points for building out and customizing the user interface. Menus, pages, dashlets, form fields and everything else can be extended through simple JavaScript code to provide the exact user interface that your editorial team desires.

  • (UI) CKEditor Plugins - Cloud CMS Now ships with several CKEditor plugins that let users easily pick from images and linked content within Cloud CMS to hook it into their HTML content blocks. Developers can easily build new CKEditor Plugins using the provided extension framework.

  • Even more Bug Fixes and Improvements - Cloud CMS has invested a lot of time and resource in finding and fixing bugs. We've polished things up and added a lot of improvements that aren't mentioned here. You're bound to find a lot of goodies within.



Cloud CMS Release 3.1.448

Published on 06/20/2018
The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.448 release.

Cloud CMS API

  • Improvements to release and branch merges so that execution is faster and more accurate (removed a case where some updated nodes that had no changes could remain as part of the transaction set)
  • Merge process now automatically detects nodes that are deleted and re-created with same ID or QName and converts them to updates to allow for seamless, non-deletion commits
  • Improvements to merge error handling and error reporting
  • Fixed a bug whereby an internal branch cache would behave improperly when two repositories with the same branch ID (the result of a replication using the COPY_TOP strategy) were being read from at the same time. Optimized cache to use a synchronized LRU cache to yield performance improvement as well.
  • Fixed a bug whereby some rules could trigger before QName and ID uniqueness checks, resulting in errant "duplicate QName" or "duplicate ID" errors
  • Fixed a condition by which a server initializing in a cluster might attempt to load a branch's runtime state if the branch is archived
  • Added an administrative method to refresh a branch without rebuilding the underlying MongoDB transaction view first
  • Upgrade to latest third-party libraries

Cloud CMS User Interface Server

  • Updated release pages to provide better formatting and presentation of release conflicts
  • Fixed a bug whereby print might not work for some browsers due to cross origin issues
  • The "Release Immediately" button is now shown for the Project Manager authority.
  • Fixed a bug whereby error messages on login could be misreported.
  • Fixed a bug whereby lists might format incorrect for some columns where nowrap is specified.
  • The "x-frame-options" header is now set to "SAMEORIGIN" by default (was previously left unspecified)
  • Upgrade to latest third-party libraries


Cloud CMS Release 3.1.447

Published on 06/06/2018
The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.447 release.

Cloud CMS Docker Packaging

  • Updated Docker release, replacing 3.1.446 to account for a Fedora/OS and ES packaging issue

Cloud CMS API

  • Fixed a bug where the logic for finding the closest node version for a changeset could go into a loop and cause a thread to lock
  • Improvement to how node references are resolved
  • Update MongoDB driver version + improvements to MongoDB connection pooling
  • Added support for automatic repository compression which can be enabled at the repository/project level so as to have historical changesets automatically compress in the background, saving disk space and optimizing performance

Cloud CMS User Interface Server

  • Correct to support links to integrate with new Cloud CMS helpdesk system









Ready to Try Cloud CMS?

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