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

Published on 05/12/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.33 release.

Recommended Action
  • For improved performance with relators you will need to rebuild the project indexes. Go to Manage Project > Tools > Index Project Data Stores

New Features

UI Templates
Themes
  • Several new Themes have been added -- including a Dark Theme -- to give users more choice and better options.
Command Line Client
  • The Command Line client now supports commands to compress repository changesets and apply patches

Enhancements

Relator Properties
  • Updates and mapping execution for relator properties now executes between 3x to 5x faster than before
  • Updating a node that has a large number of relator properties now updates much faster
  • Reordering items within an array Relator Property now updates with a much small footprint (and thus, much more quickly)
GraphQL
Forms
  • Forms that have many relationships (such as many node-picker, file-picker or related-content fields) will render much more quickly due to optimization of the dataloader mechanism.
Branches
  • When creating a new branch, any problems that might arise during the population of the Elastic Search index are now ignored and the branch is no longer blocked from being created.
Platform Members
  • Fix so that the Platform Members render more information onto the screen when being viewed

Bug Fixes

Relator Properties
  • Fix so that relator properties correctly detect nested properties, aiding ease of migration from non-relator properties to relator properties within the content model
Internationalization (I18N)
  • Fix so that publishing a multilingual master node will not result in the additional publication of translation nodes. Translation nodes may publish separately or they may be shipped all at once (along with master node) via a multi-node commit.
Project Teams and Members
  • Fix so that team members page renders properly for some cases where team permissions were not set for the current user
  • Fix so that projects that do not have their own Domain configured within the stack can still use the Project Members page


Cloud CMS Release 3.2.32

Published on 04/25/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.32 release.

With these release notes, we're trying out a new layout that breaks down changes by:

  • New Feature - new additions to the product
  • Enhancement - improvements to existing areas within the product
  • Bug Fix - a fix to a bug that was reported within the product

Please contact us with any feedback regarding these changes to the release notes.

New Features

Dashboard
  • The platform level My Projects Dashlet now indicates the total number of projects and the number of projects being displayed
Application Server
  • Handle SIGTERM in addition to SIGINT on exit. This helps apps running on docker containers exit cleanly

Enhancements

Branches / Releases
  • Improved the speed and accuracy of branch merging and differencing.
  • A new master node index was added that, if available, will be used to speed up database queries.
  • Reduced the amount of memory required during the merge (tested using very changeset histories in the millions)
  • Clicking on a workspace or release in the Network view now navigates the browser to that respective workspace or release
  • The assigned release date is now validated and must occur in the future
Transactions
  • Improved how transaction bookkeeping is done to improve speed and save on memory required.
User Management
  • Improved password validation on client side for better immediate feedback when creating new users or filling out registration and registration confirmation forms
  • Improved validation messages throughout user registration flow
  • The Create User wizard has been optimized to be a single page requiring fewer clicks and letting you get everything done in one place
Forms
  • The "upload" field now supports a "progressall" option which allows custom field developers to hook in a progress listener (to report progress state back to the user)
Upload
  • User avatar and platform logo upload forms are now easier to use
Publishing
  • Added an Edit Publication action for project publications

Bug Fixes

Branches / Releases
  • Fix to ensure that relator properties and their ref field have their branch ID adjusted when merging between branches.
  • Touching a document now walks the relator properties and automatically corrects any ref fields it discovers that point to the wrong branch
  • When deleting a current workspace, the browser now navigates back to the parent workspace
Content Model
  • Fix to ensure that setting required: false for a property will cause that property to be removed from any top level required: [] blocks
  • Fix to content model builder so that buttons activate for some cases where they were not
  • Fix to content model builder so that targeting for drag/drop of elements into nested objects and arrays works as intended
User Management
  • Fix to ensure that users can be added in bulk to multiple teams for cases where a user might already be a member of a team (the duplication is noted and proceeds with remaining teams)
Security
  • Fix to ensure that admin password can be overridden when specified via docker.properties
Forms
  • Fix to ensure that pagination works on the Choose a Form card when creating a new content instance
  • Fix to ensure that custom HTML tags introduced via CKEditor are preserved in transitions to/from source
Custom Indexes
  • Fix to ensure that creating a custom index will work for all cases
Search
  • Fix to Search properties list so that it updates properly as content types are adjusted
Data Lists
  • Fix to allow for some cases where Create New Item action was not showing up correctly for Data Lists
Publishing
  • Fix project publishing sync when user deletes deployment strategies
  • Fix project publishing sync after editing deployment strategy


Cloud CMS Release 3.2.31

Published on 04/05/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.31 release.

With these release notes, we're trying out a new layout that breaks down changes by:

  • New Feature - new additions to the product
  • Enhancement - improvements to existing areas within the product
  • Bug Fix - a fix to a bug that was reported within the product

Please contact us with any feedback regarding these changes to the release notes.

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

Antivirus
Internationalization
JavaScript Driver
  • Added method branch.queryDefinitions() to allow for querying definitions on a branch
User Interface
  • Allow the Create Project Wizard to load its list of Project Templates from a custom registry (loaded from HTTP). This lets customers store their Project Archives at an HTTP address and have those registries be parsed and made available to the editorial team when they create new projects.

Enhancements

Content Model
  • A filter is now available on the Content Model screen to allow users to filter content types, associations and features by query term
  • The content definitions tree is now more responsive and allow you to filter the list by clicking on items within it
Deployment
  • The family of file-based deployers (File System, S3 and FTP) now allow for configuration driven deployments. Use custom mappings to define how deployed nodes map down into files. Use Handlebars templates to determine deployment paths based on the context and data of content being deployed. For more information, see: https://www.cloudcms.com/documentation/deployment/deployment-mappings.html
Docker (On-Premise)

Java Driver

  • Use explicit UTF-8 charset on JSON response handling (instead of relying on system defaults)
Projects
  • The system now checks to ensure that multiple Projects are not created with the same title
User Interface
  • The Branch Picker now features a hierarchical view of branches (similar to Workspaces page)
  • The configuration section for Custom Locales was moved to its own page under Manage Project
  • It is now possible to edit Service Descriptors after they've been created (if you have Manager rights)

Bug Fixes

Antivirus
  • Fix slow antivirus performance by using the out-of-process Cloud CMS Antivirus service
Application Server
  • Slight fix to ensure SSO user and group mappings (auto principal sync) work as intended
Branches / Releases
  • Fix for node deletions not showing up consistently in the Branch Changes list (when comparing or pulling between branches)
Content Model
  • Fix to ensure that updates to server-side javascript properly rebind for the branch in all cases
Core
  • Fix for save issue that could occur due to the filename feature being applied as mandatory to parent type
Deployment / Transfer
  • Fix to ensure that exports and imports work correctly when multiple nodes are exported in a changeset manifest. This may resolve occasional exceptions for large, multi-document deployments.
Search
  • Fix so that definitions when created, updated or deleted, are incrementally indexed as intended
  • Fix so that Elastic Search Scroll API is used properly for some large paginated calls
User Interface
  • Fix so that password policy validation errors and messages are more accurate when a user is invited and registers for a project
  • Fix so that pressing the enter button when creating text files doesn't auto-submit


Cloud CMS Release 3.2.30

Published on 03/23/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.30 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 branch creation that takes advantage of some improvements to MongoDB that allow for optimized collection copies
  • Improved branch merging that now leverages a memory cache for much faster execution. Many improvements including more efficient string substitution on merged objects, a more robust method for applying JSON patches, reduced event handling overhead
  • Improved support for JSON Patch, patch generation and patch merging as used within the product to detect and resolve merge conflicts. Improved support for nested arrays and enumerated value sets.
  • Added some safety checks to ensure that Access Control lookups that contain any unresolvable references will continue to process and will just ignore the missing reference.
  • Added some safety checks to ensure that module deployments will work even if the Application deployment sub-objects contain bad data or do not parse as expected.
  • Adjusted Remote Deployment Receivers so that they default to using a GET to retrieve remote deployment package status
  • Certain reserved user names are now blocked for being used on creation and update of principals so as to prevent confusion (such as system, admin, everyone and other reserved names).
  • Fixed a bug where some distributed jobs executing in the cluster could error out but remain stuck in a RUNNING state (this impacted some cases where multiple jobs could execute concurrently and get stuck until the sync timeout).

Cloud CMS User Interface Server

  • For Releases and Workspaces, the "Pending Merges" page now only appears when the underlying branch has unresolved merge conflicts.
  • Fixed a bug that prevented the CKEditor-Tools plugin from loading properly for some cases.
  • Fixed a bug that prevented the Project Members page from correctly performing ACL checks when users in the project spanned multiple domains.
  • Added the ability to configure the "maxFileSize" option for Node Picker and File Picker uploads.
  • Removed an extraneous "path" sorting option from the Node Picker.
  • Fixed a bug that could cause the Markdown field to not render properly for some cases
  • Fixed a bug that impacted how fields would internally get named by adjusting how field names with square brackets and slashes are serialized and token replaced
  • Fixed the "Pick A Color" field so that it properly puts the hash ("#") in with any selected values.

Cloud CMS JavaScript Driver

  • Fixed a bug that prevented References acquired using the ref() method from being incorrectly typed for Users and Groups (those types were capitalized when they should not have been).
  • Added the ability to plugin a custom map handler function for chainPost() calls
  • Added a generic ResultMap class


Cloud CMS Release 3.2.29

Published on 03/18/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.29 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

  • Enhanced the ability for moved source folders to export and then import into a target project and auto-resolve previously existing nodes and move them accordingly
  • Improved performance of transfer import for large sets of nodes (includes optimization of a method that performs token substitutions in when running a "copy everything" strategy, improvements to caching, cache tuning and hot spot streamlining for progress tracking updates)
  • Added ability to customize token replacement and lowercase behavior of the "slugify" Handlebars helper during server-side template execution using project-level settings (this allows you to plug in custom character substitutions).
  • Fixed a bug whereby some owned associations were not properly enforcing concurrent deletion of the owner association source node
  • Improvements to Branch Changes calculation to make them more accurate for different views including a "full" view, an "editorial" view and an "editorial pull" view which are more meaningful when merging, comparing and pulling.
  • Adjusted how Platform and Project Owner roles are checked during context load when supporting the main user interface
  • Fixed a bug wherein transfer exports where not properly incorporating some of the settings from the posted JSON into the export config (resulting in larger, non-tip-mode-only export files)
  • Upgraded to Apache Tomcat 9.0.16

Cloud CMS User Interface Server

  • Added Markdown Field to the Content Model builder, letting you drag-and-drop and configure the Markdown field into your content definitions and forms.
  • Fixed a bug in the forms engine to adjust how default processing of multi-value strings (with a comma delimiter) works for checkboxes, radio buttons and select fields.
  • Fixed a few clever bugs in the Content Model builder that could affect usage of the Preview button
  • The Related Content field now formats information for clearly with a display mode when viewing properties for a document
  • Updated third party libraries
  • Fixed a bug that affected the ability to drag-and-drop files into a Related Content field for upload
  • Automatically default to "n:node" for relator property compatible fields that do not otherwise define a "nodeType" (includes Related Content field, File Picker field and Node picker field).
  • Fixed a bug that could cause a modal backdrop to hang when canceling the "create deployment target" action wizard
  • Cleaned up links to definitions so that the consistently link to builder view when appropriate
  • Consolidated the Content Model builder view into the Definition view to make it easier to graphically build your content models and then flip over to interesting aspects such as setting up default paths or forms
  • Improved the "Compare Workspace", "Pull From Workspace" and "Copy from Workspace" actions to make them easier to use and to have them reflect more clearly what precisely has changed in the other workspace for those scenarios.
  • Added Project Manage > Slugify page to allow users to edit token substitutions and behavior of the "slugify" helper used within server-side processing of Handlebars templates
  • Added a "terms" Alpaca forms control that provides an easier way to edit text arrays by putting all values side by side in text bubbles, with auto completion and key-press delimiting (tab, comma, enter). This form uses the Bootstrap Tags Input plugin.
  • The Upload Document action now automatically rolls back uploads when the modal is canceled.
  • Fixed a bug in the Admin Console that prevented exports from launching
  • When viewing Archives within a Vault, the "date" column now shows the modification date and the "published" column shows whether the archive has been made available for usage within the Create New Project wizard.
  • The Document Versions list now shows the specific modification date/time (as opposed to the relative date)
  • Added back the document list header to allow for Select All button.

Cloud CMS Application Server

  • Improved error handling for some cases where file I/O might get interrupted or otherwise fail during configuration service initialization or reload


Cloud CMS Release 3.2.28

Published on 03/07/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.28 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 MongoDB 3.6.10
  • Significant improvements to performance and scalability through benchmark testing of standalone and clustered environments - additional caching for tenant and client services, faster API methods
  • Improved support for bulk node creation via multipart POST to allow for individual property specification using file parts
  • Enhanced S3 storage provider to support improved chunking on large file multipart uploads
  • Improved rule execution so that some critical paths execute as system user, making things faster and also reducing potential of permission check problems

Cloud CMS User Interface Server

  • Updates to workspace and release conflict resolutions screens to tighten them up and improve usability
  • Fixed a bug in the forms engine to improve support for multi-value strings, allowing for custom join and split functions and improved parsing of delimited values
  • Added Markdown field to the Content Model builder
  • Fixed a bug in the Content Model builder that had prevented the Preview button from working for some Related Node fields
  • Improved display rendering on Overview page for some control types including Related Content
  • Fix for responsive layout of workspace bar for smaller screens

Cloud CMS Java Driver

  • Added ref() method to all driver objects letting folks quickly construct a reference (these are commonly used for permission checks, exports and many other aspects of the API)
  • Updated AutoClientMapping properties and methods
  • Removed Warehouse datastore and interaction objects


Cloud CMS Release 3.2.27

Published on 03/04/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.27 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

  • Moving a node now properly re-indexes the node within the FileFolderService for some edge cases
  • Changes to parental path relationships are now propagated to the target during deployment
  • Added a missing title for the "deployNode" action in the actions drop down

Cloud CMS User Interface Server

  • When viewing a document, the "type" link has now been corrected to point to the correct place
  • The "Selected..." dropdown now respects access control rights on individually selected items to reflect whether actions are enabled or disabled. If permissions are not granted for the selected item(s), they will be disabled.
  • When performing UI extensions, custom region overrides now push their configuration down into custom JS gadget implementations
  • Users with the Project Manager authority can now view and utilize the "Release Immediately" button (no need for a separate authority)
  • The Delete and Edit Attachment buttons for Document Attachments now enable or disable basedon the current user's authorities
  • The Delete and Change Password buttons for users at the Platform level now enable or disable based on the current user's authorities
  • On the Document Versions page, the Changeset Link (to admin console) only appears for Project Managers
  • Fixed a bug so that Project Owners can now see the Manage Project button (and no longer need separately have the Project Manager authority assigned)
  • Fixed a bug so that Project Managers can add users to Projects as intended (without the need for a separate authority grant)

Cloud CMS Application Server

  • Updated to the latest cloudcms-server node module
  • Now checks for the existence of a local custom.js file on startup and, if available, calls an init() function to allow for easy extension of the server (including registration of custom Dust functions, routes and more).


Cloud CMS Release 3.2.26

Published on 02/26/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.26 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

  • Introducing Workspaces - Editorial users can now create Workspaces to take advantage of ad-hoc branching with automatic change and activity tracking. Compare, copy and pull content between branches while taking advantage of instant indexing for search, query and GraphQL. Instantly preview changes on live application and merge at any time. Features merge conflict detection, side-by-side visual differencing and a friendly UI for property-level conflict resolution. Workspaces is an optional feature that works alongside Releases to offer flexible scheduled publishing and finalization.
  • Lots of improvements to merge conflict resolution including side-by-side differencing, browsing of workspaces and releases for merge conflicts, individual property-level conflict resolution management, commits and merge re-attempts. Applies to both Workspaces and Releases.
  • Fixed a bug wherein newly created translation nodes could retain the "f:locale" feature from the master node and therefore retain the master node's locale setting (if applied)
  • Improved some error handling paths when running in a cluster with some latency between cluster members
  • Improved transaction error logging so that more log information makes its way to project logs
  • Single and bulk creation of nodes now execute in a single transactions, fixing a bug wherein web hook calls could be fired early and without complete path information
  • Project Type controller now looks up Add Ons using the official Cloud CMS Archives registry (which now includes an updated Sample Project)
  • Added a "branch" sub-object to Web Hook payloads to provide more information about the node's branch
  • Added the "deployNode" action and rule executor to allow for nodes to be deployed or undeployed as triggered via action or conditional rule
  • Changed the behavior of thumbnail generation so that it no longer generates "json" thumbnails (which were printouts of the JSON) - instead it skips generation for those cases and hands back a 404 which offers better compatibility with upstream CDNs
  • Added /ref/deploy endpoint to allow for scriptable, API-drive bulk deployment of nodes using a deployment strategy
  • Fixed a bug whereby deletion of a platform user from within the UI was skipping past a needed permission check
  • Several updates to third-party libraries

Cloud CMS User Interface Server

  • Added support for Workspaces
  • Enhanced pages for resolving Merge Conflicts - now includes side-by-side diff, visual selection of per-property resolutions, merge retries and an easier UI for merge comparison and management
  • Improvements to Releases to be consistent with new user interface for Merge Conflicts and Workspaces
  • Added support for the Alpaca Markdown field - use the "markdown" field type to embed a visual Markdown editor (SimpleMDE) on top of your string fields. Full support for Markdown with in-context preview.
  • Added a "Deploy Content..." action to the Folders and Content Instances view. Available to managers, this action provides a quick dialog to let you deploy an arbitrary piece of content via a deployment strategy.
  • Fixed a bug so that "sort by Attachment file type" works as intended in the File Folder picker
  • Added a UI refresh call so that the document path updates properly when the title of a document changes
  • Added a validation check to the "Add Publication" dialog so that the user cannot proceed unless a valid form valid has been provided
  • Added a catch-all fix for a stale or stuck "open-modal" class that could cause the page to no longer scroll
  • Fixed escaping of titles on some page header sections where HTML was getting double escaped
  • The Content Instances page now derives its selected actions from configuration - allowing third party customers and systems integrators the ability to extend the UI options.

Cloud CMS JavaScript Driver

  • Merge conflict commit() method now takes an optional target branch ID
  • Updated conflict resolve() method and added conflict commit() method
  • Fix to stringify() method to handle boolean false properly

Cloud CMS Developer SDK

  • Added a module example that demonstrates how to override and customize a Cloud CMS action (add-attachment) to provide your own user interface adjustments

Cloud CMS Command Line Client

  • Added list-datastore-deletions and refresh-db-connections commands to make it easier for customers to schedule nightly purges of deleted datastores from MongoDB (without having to call the REST API manually)


Cloud CMS Release 3.2.25

Published on 02/15/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.25 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

  • Improvements to performance and scalability for high load branch operations resulting in faster branch performance and scalability for both clustered and standalone (single server) configurations
  • Fixed a bug that would exhibit itself over time as via a "Cannot find source view" error and was due to certain kinds of repeated operations against a branch that failed to release transient transaction state.
  • Tightened up and improved many aspects related to how nested transactions process and manage state, ensuring that things are cleaned up and transactions neatly and reliably handle failure cases for all possible transaction phases.
  • Fixed a bug that could cause some import jobs to fail with an array index out of bounds exception.
  • Fixed a bug where some jobs could be launched without their tenant platform marked onto them. This didn't prevent them from working but did prevent them from being polled or reported on.

Cloud CMS User Interface Server

  • Fixed a bug that could prevent text selection for controls nested within a drag-and-drop array container.
  • Fixed the linking of Containers (folders) within the Content Instances page so that they properly link to the overview page for the content instance.
  • Added a quick action for Containers within the Content Instances page so that editors can jump over to the Folder view of those Containers if they so desire.
  • Fixed the sort order for the File Folder Picker and the Project Branch Picker.
  • Updated the password validation logic so that the Create User wizard cannot proceed without a password that contains at least 1 numeric character.
  • Cleaned up UI formatting and templates, tightened up CSS and removed a rather contemptible apostrophe from the document view page.

Cloud CMS Developer SDK

  • Now includes drivers to Python, PHP and Microsoft C#.
  • Added Nuxt sample and Cloud CMS Nuxt module to make it easy for developers to generate static web sites that surface Cloud CMS content.
  • Added Gatsby.js sample to help developers generate static sites that hook into Cloud CMS GraphQL and surface Cloud CMS content.


Cloud CMS Release 3.2.24

Published on 02/03/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.24 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 within the job processor whereby child jobs were not carrying forward platform information - this allowed for a UI bug whereby jobs were not correctly being polled for completion.
  • Allow the DictionaryService to lazy fault branch runtime init state
  • Fixed activity service pagination so that it is more efficient and works as intended.
  • Adjusted EC2 Discovery to take advantage of Hazelcast's AwsDiscoveryStrategy. Allow for configurable hazelcast binding ports on discovered instances.
  • Improved default logging for Hazelcast clustering so as to leverage better log4j2 settings

Cloud CMS Developer SDK

  • Updated examples for Angular, Vue.js and ReactJS









Ready to Try Cloud CMS?

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