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

Published on 11/02/2022
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.79 release.

Upgrade Considerations

Please review the upgrade considerations provided here: https://www.cloudcms.com/documentation/docker/upgrades/3-2-79.html

New Features

ARM-64 Support
Word Count (f:word-count)
Reading Level (f:reading-level)

Enhancements

Analyzed Queries
  • Analyzed Queries now include project ID as a filter option.
Authorities / Permissions
  • Enhanced the diagnostics page for authorities and permissions to provide a more detailed explanation about why a principal might or might not be granted a specific permission or authority against a resource.
  • Faster team-permission checks for node query, find and search API calls.
Branches
  • Added a Branch Repair operation to automatically detect and fix duplicated QNames within a branch.
  • Added a Branch Repair operation to automatically detect and fix invalid QNames assignments within a branch.
  • Branch Repair utilizes bulk commits more effectively for faster operation.
  • Improvements to Branch Merge logic to be more efficient and less memory intensive.
GraphQL
  • Improvements to GraphQL service-level caching and request handling to be faster and use less heap.
MongoDB
  • Adjusted the default for mongodb.default.connectionsPerHost to 100.
  • Adjusted the default for mongodb.default.waitQueueMultiplier to 2.
Preview
  • Preview generation is now faster and less memory intensive with a stronger preference given to deferment to background jobs (instead of transformation on the live request).
  • Improvements to the underlying transformer libraries to provide faster and improved support for Office documents types and images with a particular emphasis on fast transformatons for large Excel/Spreadsheet documents.
Third Party Dependencies
  • Latest updates and security patches applied for Log4j, OpenOffice, Spring Framework, Spring Security and many other third-party libraries.
Search / Indexing
  • Added the elasticsearch.condor.connectionRequestTimeoutMs setting to allow on-premise users to calibrate the timeout so as to help prevent the Elastic Search connection manager from queueing up threads for cases where the Elastic Search endpoint is slow to respond or requests are otherwise timing out.
  • Elastic Search indexes now build in the background and swap into place gracefully with zero downtime even for cases where 1 or more documents may have failed to index (these errors are reported in the logs but the resulting index is retained).
Transfer
  • Linked Relator Associations are now ignored on export for certain cases so as to reduce the overall manifest size on export.
  • Added a configuration option on toggle the forced export of relator associations for given related nodes.
  • Node transfer exports now use a paginated query handler to make the lookup of associations more efficient (to address a potential database-level timeout issue).
User Interface
  • Improvements to the /proxy route to allow for faster streaming of static assets, attachments and preview images.
  • Removed the none options for Rule Conditions.
  • Removed the Reindex Platform Datastore tool from the tools page (this functionality is available via the command line client).
  • The Analyzed Queries page now includes a time column and provides a Project Picker field for filtering by project.
  • Improvements to the Merge Conflicts page to reduce the number of API calls and simplify the user interface flow when retrying merges after resolving conflicts.
  • Updated the use of picker fields throughout the UI, including consistent use of Team pickers, Project pickers and more.
  • Improved the way that socket.io is utilized and the rendering of awareness icons.

Bug Fixes

Authorities / Permissions
  • Fix so that team policies work as intended for complex cases where multiple teams may define overlapping revokes and grants.
Branch / Merge
  • Fix so that merges complete successfully for a specific edge case that involved the resolved target node being in a deleted state.
File/Folder Service
  • Fix so that the merge of a document that has had its title changed will properly updates its path within the target branch for cases where the filename is not explicitly set but is being derived from the title itself.
Find
  • Fix so that pagination is properly applied to find calls for certain cases involving specific field selection.
GraphQL
  • Fix so that GraphQL no longer throws branch initialization errors for certain cases where a branch is being faulted into memory in a distributed, multi-server configuration.
Publishing
  • Fixed a bug where Branch Deployment Handlers were not properly registering themselves as a dependent of the Deployment Commit Handler job which resulted in some publishing jobs completing but marking themselves as having failed.
Transfer
  • Fix so that domain principal importers work properly for cases where an older export might not include a full set of membership information.
User Interface
  • Fix so that the UI server properly configures itself for Redis 4 support across all services (supporting multiple servers in the cluster but also multiple cores on a single machine).
  • Fix so that the Jobs page uses proper display colors and filters as intended when switching between Projet and Platform contexts.
  • Fix so that UI Wizards can no longer errantly duplicate cards when a user hits the back button multiple times in a very short interval.
  • Fix so that the Analyzed Queries page now paginates as intended.
  • Fix so that actions on the Document Versions page work as intended for all cases.
  • Fix so that the Avatar and Attachments fields no longer force regeneration of preview images (allowing for cache to be used more efficiently).
  • Fix so that the Platform and Project Activities dashlets properly reflect the target Branch.
  • Fix so that form buttons and toggles are disabled when a document is locked for concurrent live editing.
  • Fix so that lists render more accurately and reflect pagination information correctly for certain edge cases.
  • Fix so that the Branch/Release selector is more legible and reflects the intended background color for cases where branches/workspaces have custom colors applied.
Versions
  • Fix so that node version information is returned properly for older nodes that no longer conform to tip schema.


Cloud CMS Release 3.2.78

Published on 06/13/2022
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.78 release.

Upgrade Considerations

Please review the upgrade considerations provided here: https://www.cloudcms.com/documentation/docker/upgrades/3-2-78.html

New Features

Analyzed Queries

Queries that execute slowly against the underlying MongoDB database are now automatically analyzed and reported upon. Each analyzed query offers insight and recommendations on steps that should be taken to optimized performance.

An “Analyzed Queries” page is available within the user interface that allows managers to inspect slow queries.

Go Driver

We have a brand new Cloud CMS Go Driver for connecting your Go applications to Cloud CMS with ease! With it you can:

  • Quickly authenticate with the API server and make requests
  • Query and Create content through path traversal, Mongo DB, Elastic Search, and Graph QL
  • Create and Manage content nodes, associations, files, attachments, etc.
  • Manage branches, releases, and content versions

And more to come! Get started using the Go driver today by checking out some more examples in the Go Driver Cookbook.

Enhancements

Clustering
  • Faster and more efficient distributed cluster messages with guaranteed ordering and priority of delivery.
  • Enhancements to the reliability of cluster-wide locks, caches ahd messaging topics.
  • Distributed messages have been tweaked to achieve optimial throughput.
Deletions
  • Added methods to the API + JavaScript and Java drivers to make it easier and faster to perform bulk deletions.
  • Deletions collections are now automatically deleted when branches are archived and recreated when branches are unarchived.
Java Driver
  • Added methods to move nodes and resolve paths.
  • Added methods for bulk deletion of nodes.
JavaScript Driver
  • Added methods to move nodes and asynchronously purge deletions.
Jobs
  • The user interface for inspecting active and historical jobs has been improved. It’s now faster and also provides an entirely new set of filters to let you quickly find jobs by ID, type, date, state and custom query terms. A number of quick config buttons are also available to let you focus on publishing-specific jobs or hide document indexing jobs. Action links are provided per job to things easier to work with.
Logs
  • The user interface for inspecting log entries has been improved. Similar to the Jobs page improvements, the Logs page filter has been moved to the top.
MongoDB
Relator Properties
Transfer
  • Added a fallback during transfer storage side copy of attachments in case one or more binaries cannot be found so that they’ll be manually copied one at a time. This is to accommodate cases where customers might have very old binaries sitting in GridFS (and not migrated out to S3).
User Interface
  • Removed the Reindex Project Data Stores button from the Project Tools page. This functionality is now only available via the CLI.
  • The Content page now sorts content types by title (with a fallback to QName).
  • When deleting content, a loading modal is used during pre-deletion to handle the case where very large sets of content may be deleted in bulk.

Bug Fixes

Binary Storage
  • Fix so that the S3GridFS storage provider properly provisions a disk directory with a storage prefix (as opposed to separate mounts).
  • Fix so that wrapped binary storage providers attempt a manual copy for transfer of assets thata re not in primary storage provider.
Downloads
  • Fix so that file names are URL escaped on download to prevent header special characters (like ;) in filename from interfering with response.
Graph QL
  • Fix so that GraphQL returns proper results for specific cases where deeply nested queries introduced concurrent modification errors.
I18N
  • Fix so that API call to retrieve translations supports pagination as intended.
  • Fix so that an extra update call is no longer made when executing the Make Multilingual action.
Jobs
  • Fix so that decommissioned jobs (due to host server not being in service) are automatically reschedueld without an increment to the number of attempts, preventing failed retries due to max attempts being exceeded.
  • Fix so that jobs in the AWAIT state cannot be prematurely restarted by the Job Watchman thread when depedency jobs transition into a completion state.
Node Retrieval
  • Fix so that access control checks run faster and perform as intended when executing bulk retrieval of nodes.
Transfer
  • Fix so that copy attachments iterates properly over the source attachment set.
  • Fix so that the copy of resources within S3 allows for silent failure (with logging to the API only) so as to permit the operation to continue unabated.


Cloud CMS Release 3.2.77

Published on 05/14/2022
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.77 release.

Upgrade Considerations

Please review the upgrade considerations provided here: https://www.cloudcms.com/documentation/docker/upgrades/3-2-77.html

Enhancements

Binary Storage
  • Enhancements to how binary files are stored to make more efficient use of bulk copy and write.
  • Binary Storage operations now log more efficiently and with greater detail.
GraphQL
  • GraphQL was refactored to make use of purely asynchronous, non-blocking IO. The result is faster implementation of the GraphQL API that features lower CPU utilization and lower memory requirements.
Java Driver
  • Added driver.setPaths() and driver.getPaths() methods to make it easy for customers to enable the acquisition of path information on API calls that return nodes or node result maps.
  • Renamed the archive.publish() method to archive.markAsTemplate() so as to be forward-consistent with Cloud CMS 4.0.
  • Renamed the archive.unpublish() method to archive.unmarkAsTemplate() so as to be forward-consistent with Cloud CMS 4.0.
Server-Side Scripting API
  • Added a branch.getRootNodeId() method to retrieve the root node of a branch.
  • Added a node.getPath() method to retrieve the path of the node relative to the root node of the branch.
Transfer
  • Several improvements to make transfer (both export and import) much faster.
  • Enhanced the management of H2 DB file handles to ensure that file handle leaks do not accrue for cases where an error might prematurely end a transfer job.
  • Deployment Handlers are now entirely asynchronous, allowing for faster execution, more advanced scheduling of work items and higher job throughput.
  • Greatly reduced the number of potential refresh() calls required after importing content with relator properties.
  • Several graph metrics (such as distance from source) are now computed and cached on the fly, allowing for much faster export times.
Traversal
  • The Traversal API code paths were optimized to make retrieval faster and also much less intensive in terms of CPU utilization and heap allocation.
UI Clustering
  • Made it easier to configure Redis as a back end for clustered UI servers. Now only requires a single CLOUDCMS_REDIS_URL environment variable and an optional CLOUDCMS_REDIS_DEBUG_LEVEL variable to globally configure Redis log level. For more information, see: https://www.cloudcms.com/documentation/appserver/clustering.html#configuring-redis
  • Updated the QuickStart samples to use an updated version of Redis and demonstrate UI clustering more effectively.
User Interface
  • Added a 15 second TTL to static resources retrieved via the /preview route. The result is faster execution with less API traffic.

Bug Fixes

ACL Checks / Filtering
  • Fix so that ACL checks and filtering are applied universally to all internal methods that allow for field-level selection or partial result set generation.
Branches
  • Fix so that branch aliases can be used as identifiers when changing a node’s QName.
Job Dispatching
  • Fix so that that start time of a job is not errantly overwritten for jobs that transition into and out of an AWAIT state.
  • Fix so that job decommissioning makes at least three passes and independent checks before declaring a job out of service.
MD5
  • Fix so that dynamic MD5 calculations do not buffer into memory.
Transfer
  • Fix so that the deploy job (and others) no longer use a synchronous timeout block. This was causing some jobs to fail in an ERROR state (even though the actual export or import eventually did run just fine). All deployment-related jobs are now purely asynchronous and utilize the job AWAIT state to passivate activity until one or more child processes complete.
User Interface
  • Fix so that list pages properly teardown event handlers/hooks when the DOM is destroyed or transitioned. The result is faster page rendering and transitioning with less API traffic and a lower number of HTTP requests from the browser.
  • Fix so that Branch Picker pagination works as intended.
  • Fix so that the Project Stack page retrieves and displays all data stores.
  • Fix so that the Project Applications list paginates as intended.
  • Fix so that the Node Versions page properly paginates for cases where the last key was being errantly determined.


Cloud CMS Release 3.2.76

Published on 04/15/2022
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.76 release.

CVE-2022-22965

This release is hardened against CVE-2022-22965. For more information on CVE-2022-22965, please visit: https://www.cloudcms.com/documentation/docker/notices/cve-2022-22965.html

Upgrade Considerations

Please review the upgrade considerations provided here: https://www.cloudcms.com/documentation/docker/upgrades/3-2-76.html

Enhancements

API
  • The API now returns an ETag HTTP header field which is populated with the checksum for the requested resource. The ETag can be retained and compared against future API responses to implement reliable client-side caching. The header value only changes when the requested resource has been modified. The ETag header applies to JSON requests as well as binaries and attachments.
Attachments
  • Any binary attachment written into Cloud CMS now automatically computes an MD5 checksum. This checksum is available on the attachment subobject of a node (or other Attachable type). The checksum can be used to determine if the attachment’s binary payload changed or has remained the same.
Branch Actions
  • The User Interface for Pulling, Comparing and Copying between Branches has been improved to offer a more accurate picture of what has changed and what is available when executing those operations.
Spring
  • The default Spring annotation-based request mapping handler adapter is now wrapped to ensure that Spring web bindings always exclude any Class accessor fields. This is to add programmatic-level innocuation against CVE-2022-22965.
Transfer
  • When transferring binaries and attachments, the MD5 checksum is now used to reduce the time required to import. The checksum is compared to any existing attachments and, if nothing changed, the import operation is skilled for that attachment. The result is faster, lighter imports.

Bug Fixes

Default Forms
  • Fix so that the User Interface will properly default to the first form available (alphabetically) when a document doesn’t have an existing _formKey in place.
Login
  • Fix a bug so that error messages reported properly for additional cases where a user might fail a log in.
REST API
  • Fix so that a 403 HTTP code is returned for additional cases where a user might encounter a NotAuthorizedException.
Sync Node Action
  • Fix so that the SyncNode Workflow Handler properly passes full set of options for all usage cases.
  • Fix so that Sync Node works as intended for cases where related nodes stored as siblings under a common folder export properly.
Transfer
  • Fix so that search and path indexing takes less time for incremental tip-mode Node transfers.
  • Fix that Directory data store Connection objects export and import as intended.
  • Fix so that tip-mode Node transfer automatically repairs cases where referenced changesets are missing.
  • Fix so that platform identifier is properly stamped onto import sub-job for copy jobs.
  • Fix so that the correct tip-mode changeset is resolved for cases involving nested relators. This bug had caused incorrect relator target nodes to be exported.


Cloud CMS Release 3.2.75

Published on 03/29/2022
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.75 release.

CVE-2021-44228

This release is hardened against CVE-2021-44228. For more information on CVE-2021-44228, please visit: https://www.cloudcms.com/documentation/docker/notices/cve-2021-44228.html

Upgrade Considerations

Please review the upgrade considerations provided here: https://www.cloudcms.com/documentation/docker/upgrades/3-2-75.html

Enhancements

Actions
Branch Repair
  • Enhanced the “Branch Repair” function to support validation of relators. This function can be invoked via the CLI to check on the health of a branch at any time. A repair switch allows you to have Cloud CMS automatically fix up any issues that it finds. For more information, see https://www.cloudcms.com/documentation/cli.html#repair-branch.
Elastic Search
  • Updated the default settings applied to new Elastic Search indexes ("index.mapping.nested_fields.limit": 100, "index.mapping.nested_objects.limit": 20000).
GraphQL
  • Faster GraphQL implementation that takes advantage of updated internal libraries and improved caching.
Job Service
Logging
  • Internal improvements to how Log4j2 Appenders store state when running asynchronously to allow for faster logging with less CPU utilization.
Transfer
  • Faster imports and exports that have significant performance impacts for publishing, deployment, copying, project creation and archiving.
  • Reduced memory footprint and CPU utilization.
  • All exports from version 3.2.75 onward use Transfer Schema v3. To import these archives, you will need to be running Cloud CMS 3.2.75 or beyond. Backward compatible with archives generated from earlier versions of Cloud CMS. See upgrade notes on Transfer Schema v3 here: https://www.cloudcms.com/documentation/docker/upgrades/3-2-75.html#transfer-schema-v3
User Interface
  • When forms are edited using a selected form, the form preference is stored using a _formKey property on the node. When editing the node afterwards, the previously used form is auto-selected.
Versions
  • Improvements to the node listVersions API call to provide more metadata and a more accurate accounting of precisely which versions are on which branch and which versions merged or forked from which other versions. The user interface has also been improved to reflect this information, providing for an even better experience when working with versions of content.

Bug Fixes

ActiveMQ
  • Fix so that ActiveMQ sessions are re-established with each batch of new messages to account for case where ActiveMQ session could be flushed and/or closed by the remote receiver.
Hazelcast
  • Fix so that distributed messages coordinate the release of the message lock more accurately. In previous releases, it was possible in an edge case for the lock to get released before the final response was received.
Transfer
  • Fix so that the selectedBranchIds parameter works as intended when invoked directly via the REST API.
  • Fix so that exports work more efficiently for cases where a snapshot branch is being exported.
  • Fix so that importing a node with attachment properties (i.e. _attachment is specified) works as intended.
  • Fix a potential file handle leak that could occasionally occur while importing binary attachments.
User Interface
  • Fix so that HTML escaping for field helper messages is applied correctly.
  • Fix so that Content Types list filters correctly for all cases.


Cloud CMS Release 3.2.74

Published on 02/23/2022
The following are the new features, enhancements and fixed issues for the Cloud CMS 3.2.74 release.

CVE-2021-44228

This release is hardened against CVE-2021-44228. For more information on CVE-2021-44228, please visit: https://www.cloudcms.com/documentation/docker/notices/cve-2021-44228.html

Upgrade Considerations

Please review the upgrade considerations provided here: https://www.cloudcms.com/documentation/docker/upgrades/3-2-74.html

New Features

General Support for AWS OpenSearch 7.x
General Support for ElasticSearch 7.x
General Support for MongoDB 4.x

For supported stack information, see: https://www.cloudcms.com/documentation/supported-stacks/32.html

Enhancements

Job Queue
  • The Job Reaper thread is now enabled by default with a configuration that enables it to clean up older job records more promptly.
Logging
  • Request logging context now includes body (for JSON payloads). This information is automatically logged to the default rolling file appender and is also applied to Kinesis, Cloud Watch and other configured appenders.
Performance
  • Reduced the number of cache writes that occur when retrieving nodes or roles so as to improve overall API throughput.
  • Improved cache speed by streamlining some unneeded initializers and event listening subsystems.
  • Faster localization of nodes via the API.

Bug Fixes

Binary Storage
  • Fix so that cleanup logic on Caching Binary storage system runs within a try/catch to handle cases where files may fail to write to back end provider.
Branch
  • Fix so that cluster branch initialization works more efficiently for cases where containers come online and multiple threads may contend for first access to a branch.
Indexing
  • Fix so that adhoc creation of MongoDB indexes strictly uses background mode for legacy, older databases.
  • Fix so that includes and excludes arrays properly parse when making a repair indexes call.
Pagination
  • Fix so that pagination defaults and maximums are always applied and enforced for cases where branch-level node queries pull back a constrained subset of fields.
Transfer
  • Fix so that exported nodes that have an incorrectly identified changeset will auto-correct and export for the correct changeset.


Cloud CMS Release 3.2.73

Published on 02/11/2022
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.73 release.

CVE-2021-44228

This release is hardened against CVE-2021-44228. For more information on CVE-2021-44228, please visit: https://www.cloudcms.com/documentation/docker/notices/cve-2021-44228.html

Upgrade Considerations

Please review the upgrade considerations provided here: https://www.cloudcms.com/documentation/docker/upgrades/3-2-73.html

Enhancements

Command Line Tools
  • Added new commands to support direct manipulation, build and automatic repair of Mongo DB indexes.
  • Added new commands to facilitate upgrade process
Database
  • Improved management of MongoDB collections and indexes that supports schema retrieval and minimal touch upgrades.
Performance
  • Several performance tweaks to improve response time for queries and other read operations.

Bug Fixes

Job Queue
  • Fix so that handling of abandonded jobs from terminated cluster containers is performed more elegantly and avoids locking up the queue.
Merge
  • Fix so that merges process properly for some cases where definitions were changed concurrent with content instances being pulled.


Cloud CMS Release 3.2.72

Published on 01/25/2022
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.72 release.

CVE-2021-44228

This release builds upon the prior release of Cloud CMS (which was already hardened against CVE-2021-44228). With this release, we have updated Log4j to version 2.17.1.

Cloud CMS recommends that customers upgrade to this release to ensure that Log4j is hardened against this vulnerability.

For more information on CVE-2021-44228, please visit: https://www.cloudcms.com/documentation/docker/notices/cve-2021-44228.html

Update Recommendations (On-Premise Only)

With this version of Cloud CMS, we have disabled the deprecated Elastic Search Transport Client and have switched to using our Condor HTTP client. As such, connectivity between the api and elasticsearch services are no longer using port 9300 by default. They are now using port 9200 by default.

Please check your configuration to make sure that the API can connect to Elastic Search’s HTTP Endpoint.

For information on configuring Elastic Search for Cloud CMS, please see: https://www.cloudcms.com/documentation/docker/configuration/api-server.html#using-the-condor-http-client

For improved performance, we recommend you rebuild your cluster indexes. To do so, we recommend using the reindex-datastore command via the Cloud CMS Command Line Client (http://www.cloudcms.com/documentation/cli.html#reindex-datastore).

You can execute it like this:

cloudcms admin reindex-datastore --datastoreTypeId cluster --datastoreId default --children --username <username> --password <password>

Where the username and password are the credentials for your administrator account.

Enhancements

Application Server
  • Sessions are now automatically configured to use Redis as backing storage when configuring UI servers in a cluster (this was a manual step previously and now just automatically kicks in).
C## Driver
  • Access Tokens will now refresh and retry after an HTTP 401 is received.
  • Additional methods for jobs, projects, releases, versions and paths.
  • Refactoring and naming clean up + additional tests
Java Driver
Log4j
  • Updated to version 2.17.1 to provide further hardening against the CVE-2021-44228 exploit.
PHP Driver
  • Additional methods for branches, nodes, versions, projects, branches and releases.
  • Removed reference to hard coded root node.
  • Added methods for changeQName, resolvePath and resolvePaths.
  • Added GraphQL Support.
Python Driver
  • Additional methods for resolvePath and resolvePaths.

Bug Fixes

Auto Translation
  • Fix so that leading slashes are automatically removed frmo property paths when building auto-translation payload.
Content Model Builder
  • Fix so that user interface refreshes properly for certain clickpaths.
Deployments
  • Fix so that deployments identified as having timed out on decomissioned servers (in a clustered configuration of the API tier) will automatically clean up for all cases.
File Paths
  • Fix so that file path index is more accurate in-transaction for cases where nodes are deleted.
Jobs
  • Fix so that jobs correctly schedule onto the correct target server for some cases involving nested jobs and retries.
Permissions
  • Fix so that permissions and authorities caches have a smaller TTL - allowing for cached access rights to invalidate more quickly.
Sync
  • Fix so that sync actions correctly set the allowWriteToFrozenBranches flag when executed from a rule or a script.
Transfer
  • Fix to ensure that branch deployments work properly for some edge cases where transfer run in copyAttachments mode and move binary items across storage providers.
  • Fix so that API calls to Copy resources (identified by dependency chains) works as intended for cases where partial dependency chains are submitted.
  • Fix so that imports of tip-mode exports of branches cannot be imported on top of an existing branch using the CLONE import strategy (as it would break immutability of the 0:root changeset).
  • Fix so that attachments properly import for cases where a previously published node has an attachment updated and the copyAttachments performance optimization is used.


Cloud CMS Release 3.2.71

Published on 12/14/2021
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.71 release.

CVE-2021-44228

This release contains the recommended Log4j upgrade to version 2.16.0 to address the Log4j vulnerability identified as CVE-2021-44228.

Cloud CMS recommends that customers upgrade to this release to ensure that Log4j is hardened against this vulnerability.

Customers running previous releases of the Cloud CMS API container can harden their environments by following the steps identified here: https://www.cloudcms.com/documentation/docker/notices/cve-2021-44228.html

For more information on CVE-2021-44228, please see: https://www.cisa.gov/uscert/apache-log4j-vulnerability-guidance

Update Recommendations (On-Premise Only)

With this version of Cloud CMS, we have disabled the deprecated Elastic Search Transport Client and have switched to using our Condor HTTP client. As such, connectivity between the api and elasticsearch services are no longer using port 9300 by default. They are now using port 9200 by default.

Please check your configuration to make sure that the API can connect to Elastic Search’s HTTP Endpoint.

For information on configuring Elastic Search for Cloud CMS, please see: https://www.cloudcms.com/documentation/docker/configuration/api-server.html#using-the-condor-http-client

For improved performance, we recommend you rebuild your cluster indexes. To do so, we recommend using the reindex-datastore command via the Cloud CMS Command Line Client (http://www.cloudcms.com/documentation/cli.html#reindex-datastore).

You can execute it like this:

cloudcms admin reindex-datastore --datastoreTypeId cluster --datastoreId default --children --username <username> --password <password>

Where the username and password are the credentials for your administrator account.

Enhancements

Auto Translation
  • Properties described by excludePaths in f:auto-translate will be copied as-is to translations when modified.
C# Driver
  • Updated to improve support for tokens, refresh and retry handling for 401 responses and additional methods for Jobs, Projects, Releases and Nodes. For more information, see https://www.cloudcms.com/csharp.html.
Dictionary
  • Feature configs in a child definition mandatoryFeatures will now override their parent config if present.
Python Driver
SDK
  • Updated sample integrations to Cloud CMS using Next.js, Nuxt and Gatsby. For more information, see:

https://github.com/gitana/sdk/tree/master/nextjs/sample https://github.com/gitana/sdk/tree/master/nuxtjs/sample https://github.com/gitana/sdk/tree/master/gatsbyjs/sample

SSL Termination
  • Added documentation to provide guidance to customers on how to configure SSL termination for API and UI containers. This is provided as an alternative to the recommended guidance of using a separate SSL termination container (such as Nginx or Apache).

For more information on SSL termination for the API, see https://www.cloudcms.com/documentation/docker/configuration/api-server.html#configure-the-api-containers-as-ssl-termination-endpoints.

For more information on SSL termination for the UI, see https://www.cloudcms.com/documentation/docker/configuration/ui-server.html#ssl-termination.

Transfer
  • Faster transfer import thanks to a refactor in how bulk DB writes and updates are being processed.
  • Faster Copy, Deployment and Publishing thanks to a much faster implementation of binary asset copies and archive expansion.
  • Optimized internal DB indexes and methods calls.
  • Transfer archives now include separate .metadata.json files for each exported binary attachment, improving the accuracy of mimetype and filename tracking.

Bug Fixes

Content Model Builder
  • Fix so that clicking back and forth between JSON and Visual builder preserves changes to JSON for local edits.
  • Fix so that required blocks are handled properly.
Forms
  • Fix so that strict HTML escaping is applied to configured helper text for nested form elements so as to prevent the possibility of script injection.
Log4j
  • Updated to the latest recommended Log4j library (2.16.0) to ensure protection against CVE-2021-44228. See above in the release notes for more information.
Merge
  • Fix so that merges work properly for cases where source or target merge objects are missing their _features block.
Preview and Thumbnails
  • Fix so that the f:previewable (Preview) and f:thumbnailable (Thumbnail) features generate multiple attachments in a single transaction.
  • Fix so that notification queue is optimized to reduce the number of invalidation messages sent during generation.
Temporary Files
  • Fix so that temporary files are cleaned up properly during transfer import.

Full Changelog: https://github.com/gitana/cloudcms-docker-releases/compare/3.2.70...3.2.71



Cloud CMS Release 3.2.70

Published on 10/26/2021
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.70 release.

Update Recommendations (On-Premise Only)

With this version of Cloud CMS, we have disabled the deprecated Elastic Search Transport Client and have switched to using our Condor HTTP client. As such, connectivity between the api and elasticsearch services are no longer using port 9300 by default. They are now using port 9200 by default.

Please check your configuration to make sure that the API can connect to Elastic Search’s HTTP Endpoint.

For information on configuring Elastic Search for Cloud CMS, please see: https://www.cloudcms.com/documentation/docker/configuration/api-server.html#using-the-condor-http-client

For improved performance, we recommend you rebuild your cluster indexes. To do so, we recommend using the reindex-datastore command via the Cloud CMS Command Line Client (http://www.cloudcms.com/documentation/cli.html#reindex-datastore).

You can execute it like this:

cloudcms admin reindex-datastore --datastoreTypeId cluster --datastoreId default --children --username <username> --password <password>

Where the username and password are the credentials for your administrator account.

Enhancements

Auto Translation
  • The f:auto-translate feature (Auto Translate) now supports an array of regular expressions for the excludePaths option. These regular expressions are matched against all property paths when deciding what fields to include during auto translation processing. For more information, please see: https://www.cloudcms.com/documentation/features/auto-translate.html
Gatsby Integration
Nuxt Integration

Bug Fixes

Authentication
  • Fix so that various combinations of invalid credentials during authentication consistently come back as 400 with the expected JSON envelope.
Auto Translation
  • Fix so that nested text is properly discovered, parsed and translated for cases where text was deeply nested within certain combinations of objects and arrays.
Cluster
  • Fix so that distributed cluster messages execute more quickly. Distributed messages now time out more quickly and are faster to complete across all nodes in the cluster.
S3 Deployment
  • Fix so that the S3 Deployment Handler no longer duplicates the prefix configuration property when calculating an object’s path.
  • Fix so that S3 network issues are less likely to stall out jobs. Jobs now fail more quickly, allowing for the job queue to respond (either discarding or retrying the job as appropriate).









Get Started with Cloud CMS

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