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


Cloud CMS Release 3.2.69

Published on 09/28/2021
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.69 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

Azure
  • The Azure Deployment Handler and Azure Binary Storage Provider has been updated to use the latest Azure driver. This now runs faster and more efficiently, resulting in quicker upload and download.
Branches
  • The repair facility now supports an “incorrect changesets” operation that can be used to find and fix tip nodes that are mounted on changesets that no longer exist. These discrepancies can then be automatically repaired.
Character Sets
  • Faster detection of character sets that optimizes on partial stream processing.
  • Improved conversions between ISO and UTF character sets for textual attachments.
Command Line Client
  • The publishing resync command now supports an optional JSON configuration.
  • The branch repair command now supports switch-based configuration of operations.
File Folders
  • The path indexing service has been optimized to be faster and more efficient.
Hazelcast
  • Improvements to underlying Hazelcast configuration to make more efficient use of resources, now defaulting to Reliable topics and a more efficient distributed lock facility.
  • Added initial and operational beta / non-production configs to support explicit configuration of CP subsystem. This will be formally GA’d as part of the coming 4.0 product release.
JavaScript Driver
  • Team objects now support a ref() function to build out reference strings.
MIME Types
  • Enhanced detection and inference support for YML, JSON and other text-based mimetypes.
Node Refresh
  • Faster execution of refreshes involving nodes that have relator properties and relator assocaitions. This now takes advantage of a topological sort to reduce the number of associations that need to be traversed or considered.
Temp Files
  • Improvement to how temp files are managed on-the-fly so as to reduce the overhead required during the period temp file sweep. This helps guarantee consistency of disk I/O and reduce file leaks that could occur when relying on JVM resource management.
Transfer
  • Transfer Service now runs much faster for all cases with optimizations introduced to the DB layer and JVM layer. A new ZIP storage implementation is now uses which is much faster and DB adjustments were introduced that optimize for compression and speed.
  • Transfer Imports of nodes in tip mode now commit their attachments, related content and any node refresh calls within a single transaction. This ensures that an import of a branch or a collection of content into a Cloud CMS branch commits to a single changeset.
  • An exception is now raised when an attachment is exported and the mimetype for the attachment could not be determined (either it was not stored on upload or could not be inferred from stream analysis).
User Interface
  • The Node Picker now offers a sortable Modification Date column.
  • The Create Text Document action now offers text/yaml as an option.

Bug Fixes

Amazon S3
  • Fix so that the Amazon S3 Binary Storage Provider won’t carry a high load of open S3 connections for cases where the stream isn’t automatically closed when internally managed by the internal S3 driver. The default S3 driver behavior here is corrected and we manually force close any latent S3 streams to keep resources light and throughput quick and speedy.
Character Sets
  • Fix so that JSON text files are properly converted between character sets to correct for a buffer size misallocation which resulted in incorrect file lengths.
Deployments
  • Fix so that nested deployment package commit errors will properly throw back to get captured by the job engine, allowing it to be reported and observed by the user.
  • Fix so that Basic Authentication works as intended for custom HTTP Deployment Handlers (and Remote Receivers).
  • Fix so that error messages (for connection, post payload, resulting HTTP status codes) includes URL information to assist with debugging.
File Folders
  • Fix so that all regex special characters are escaped when performing a path lookup.
Node Preview
  • Fix so that node preview generation works as intended for multiple source attachments.
Node Recreate Filenames / Validate
  • Fix so that the administrative operation to recreate and validate filenames for all nodes in a branch now runs faster and uses less memory. This is an important change for very large branches (say, with millions of nodes) as it allows this operation to complete more quickly and use less CPU.
Node Sync
  • Fix so that exceptions propagate back to the outer sync call for cases where dependency jobs were throwing errors but those errors were simply being logged. These now propagate back as expected.
Page Renditions
  • Fix so that Web Content page renditions are invalidated much more quickly.
Relator Associations
  • Fix so that relator associations aren’t recreated for cases where a relator property has been deleted from a node’s definition.
Search Indexes
  • Fix so that rebuilding search indexes no longer tries to copy an existing historical snapshot’s search index (which could result in an incorrect resulting index for cases where schema changes were not captured correctly).
Transactions
  • Fix so that the determination of previous changeset IDs for nodes within a transaction is done more efficiently and more accurately.
Transfer
  • Fix so that transfer export and transfer import of nodes with relator properties and relator associations results in an optimized payload that processes very quickly. Further inspection is applied to the final set of nodes in the transaction to more accurately determine which nodes need to be automatically refreshed on the import side.
  • Fix so that streams are more robustly handled and always closed to prevent a discovered resource leak that could occur (albeit infrequently). This stream handling has been tightened up throughout.
  • Fix so that transfer exports of a node’s optional dependencies will always correctly identify its branch ID.
User Interface
  • Fix so that Deployment Target rows display properly for cases where the Deployment Target’s Deployment Strategy cannot be found.
  • Fix so that Breadcrumbd display correctly by properly decoding paths with encoded pluses in the filename.
  • Fix so that the Clear button for Pickers now sets the value to undefined (instead of empty object).
  • Fix so that Node Deletion actions work as intended for some cases where a callback was being fired prematurely.
  • Fix so that Node Version differences display on the screen more cleanly and with improved navigation.


Cloud CMS Release 3.2.68

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

Application Server
  • Added support for the GITANA_PROXY_PATH environment variable. This can be used to fine tune the proxied routing of API requests through an endpoint at a specific path. This also enables integration with API monitoring and optimization tools such as IBM API Connect.
Binary Storage Providers
  • Binary Storage Providers now automatically cap file store caches to 64GB. They are now also configurable to allow for custom TTLs and cleanup configuration. This provides administrators with more tools to help manage disk space. This particularly helps when running in Kubernetes where the amount of ephemeral or local disk often needs to be more finely tuned. For more information, see: https://www.cloudcms.com/documentation/docker/configuration/api-server.html#managing-disk-space.
  • Improved the file binary storage provider so that it cleanly separates files into data and metadata directories for better performance and consistency.
Branch Views
  • Improved the speed of building branch tip views by introducing a new index and faster, less frequent DB queries.
Command Line Client
  • Added the import-platform-datastore command to assist with migrating datastores between on-premise Docker installations.
  • Added support for optional vaults when working with archives.
  • Improved support for start/end dates when specifying content export ranges.
GraphQL
Merges / Differencing
  • Improved speed, efficiency and accuracy of branch merges by optimizing the algorithm responsible for computing the graph edge length between merge points of nodes from the tip back to a common ancestor across two branches.
Transfer (Import/Export)
  • Improved the speed of the transfer imports by using less DB queries and less memory.
User Interface
  • When copying a node between branches, all node associations are automatically considered allowing for more accurate copy results.
Web Hooks
  • Standardized the way that Web Hooks are invoked so that Web Hooks invoked from within Workflow Handlers support all the same features including specification of headers, digital signature and more.
  • Added projectId field to capture the ID of the project against whose content the web hook was invoked.

Bug Fixes

Attachments
  • Fix so that deleting nodes with attachments doesn’t errantly cause additional or unexpected downstream propagated update events.
Branch Changes
  • Fix so that Branch Changes more accurately keep up with branch deletion events.
Branch Views
  • Fix so that branches whose views failed to build cannot be written to or transacted against.
Content Range HTTP Headers
  • Fix so that Content Range support works for ranges that exceed the maximum length by auto-restricting the length to the resource length (improving conformance with RFC-7233). This improves support for Amazon CloudFront and other CDNs that deliberately push the length header out on a first call so as to remove the need for an initial call to retrieve full length.
GraphQL
  • Fix so that GraphQL properly reflects required and nullable attributes for content properties that are marked required in their schema.
Localization
  • Fix so that the default localization strategy considers the locale of the master node in its search algorithm. This allows the master node to play a part (along with any translation nodes) when localizing content.
Logging
  • Fix so that the log system does a better job of capturing and reporting project, tenant and user context
Projects
  • Fix so that project title uniqueness is enforced properly across all entry points (including some API methods that were incorrectly allowing this).
  • Fix so that project titles (and other properties) are applied to projects at create time (instead of updated after create) to prevent duplicate project titles from appearing.
Relator Properties
  • Fix so that a refresh() operation against a node with Relator Properties will correctly rebuild any relator properties and associations that originate on different node property (and which point either to or from the node being refreshed, depending on the mapping direction).
Releases
  • Fix so that failures on Release Creation now log with project context
  • Fix so that Releases are no longer exported when exporting a branch or project in tip mode.
Sync Nodes / Copy Nodes
  • Fix so that the Sync Nodes action blocks on a frozen target branch (such as a locked master branch). Use the allowWriteToFrozenBranches setting to indicate that you want the Sync Node action to write regardless onto a frozen target branch.
  • Fix so that translations of a master node are considered as candidates for reconnection when a master node is copied or synced between branches.
Transfer (Import/Export)
  • Fix so that the product works around a bug in the JVM to allow for more efficient extraction from and storage within ZIP files.
  • Fix so that the Store close() method isn’t errantly called twice for cases where you have nested archives.
  • Fix so that exports of branches with ancestral branches that are archived will work as intended.
  • Fix so that recursively referenced node properties are not traversed twice during compile phase.
Tree
  • Fix so that changing node container states more accurately reflects in the tree (by updating file/folder indexes)
User Interface
  • Fix so that the document image editor properly centers when cropping.
  • Fix so that attachment markers are correctly removed from an attachment property when the property is cleared.
  • Fix so that required fields work properly between builder and JSON views.
Workflow
  • Fix so that adding or removing resources from a payload container works for general users as expected.


Cloud CMS Release 3.2.67

Published on 05/24/2021
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.67 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

Indexing
Logging
  • Improved logging for indexing operations (for platform and project tenant logs as well as container-level logs).
  • More detail now offered for server-side script exceptions so as to indicate script node IDs and other runtime information.
Transfer
  • Faster performance of export and import due to improvements in the performance of reference resolution.

Bug Fixes

Branches
  • Fix so that failed node assembly won’t get stuck in a loop for edge cases where interdependencies were not being sorted properly ahead of call.
  • Fix so that reading a branch works consistently for both _doc and alias values.
Domain Users
  • Fix so that shared assignment of an existing identity policy to a new user works as intended for cases where the source user does not have an assigned password.
GraphQL
  • Fix so that nested collections resolve properly for cases where related nodes exist on a parental or ancestral branch.
Transfer
  • Fix so that exports of multiple nodes complete as intended for edge case where export is performed in tip mode and includes one or more nodes that resolve from same changeset ID as final source item.
workflow
  • Fix to resolve permissions issue when launching workflows for certain users/roles within projects.


Cloud CMS Release 3.2.66

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

Attachments
  • Attachment policies now support binding to a specific attachment ID. If an attachment ID isn’t specified, attachment policies continue to work as before and will trigger for all attachments.
  • Preview attachments are now filtered out and do not trigger attachment policy events.
Branches / Merge

Command Line Client

  • Added commands for working with domains and principals. These include list-domains, list-group-members, list-memberships, list-principals, query-principals and read-principal.
  • Added a flag to allow for the configuration of repair-branch operations (--operations).
Distributed Job Queue
  • Adjusted the default job configuration for a few core jobs (including export and import) to improve durability of those jobs during transfer, copy, publishing and deployment. This allows those jobs to retry automatically without any additional configuration.
  • Improvements to performance and state management.
GraphQL
  • Broader support for thirdparty GraphQL client libraries with improved and lenient handling of non-standard Content-Type headers.
Logging
  • The user interface now shows project information alongside log entries rows when viewed at the Platform level.
Transfer
  • Improved performance and resource management resulting in faster and more efficient exports, imports and any dependent operations (copy, deploy and publish).

Bug Fixes

Distributed Job Queue
  • Fix so that a job kill operation will more accurately locate and interrupt a running thread anywhere in the cluster.
File Folders
  • Fix so that path lookups use encoded paths to account for cases where paths with special characters were not being found.
  • Fix so that the file folder index refreshes properly whenever the f:container feature is added or removed.
GraphQL
  • Fix so that top-level GraphQL relator data returns in the correct order.
  • Fix so that multilevel deep relator attachment metadata fetches correctly.
  • Fix so that querying of attachment metadata works as intended.
Logging
  • Fix so that all jobs executing for resources on a stack will properly track the stack ID, allowing tenant log entries to be viewed within the Project Log viewer. This addresses a regression that was introduced when using asynchronous loggers.
Schema
  • Fix so that automatic migration of required boolean properties only runs for legacy JSON Schema v3.
Temporary Files
  • Fix so that temporary files on disk are more actively cleaned up on background thread.
Transactions
  • Fix so that nested transactions broadly support independent, inner transactions against different branches, allowing both pause and propagation transaction behaviors. This both enhances performance and fixes a few subtle bugs for cases such as a merge, where a source branch transaction may trigger events that spawn new transactions on the target branch. Customers had observed inconsistencies with target branch behaviors (such as rules) on the target branch – these should now be resolved.
Transfer
  • Fix so that project exports with optional team members exports will properly import into a target platform without any duplication of principals.
  • Fix so that file path index is properly refreshed after a project or branch import for all cases.
User Interface
  • Fix so that modal pickers work for some cases where the context was being improperly initialized.
  • Fix so that content types always appear on left-hand menu after an import.


Cloud CMS Release 3.2.65

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

Branches / Snapshots
  • Added an API method to support creation of snapshots asynchronously (using job polling). This is now used by the Cloud CMS command line client.
Logging
Transfer
  • Faster transfer exports that are more efficient and use less memory. This is notable for copy, move, publish and deploy operations for a large number of nodes or objects.
Search
  • Inspection of search indexes with REST API now includes ES mappings information.
User Interface
  • Simplified the Project Export wizard so that it performs compressed exports of the master branch. To export multiple branches or run without compression, please use the command line, API or drivers.

Bug Fixes

AWS CloudWatch
  • Fix so that the AWS CloudWatch Appender handles cases where log event messages are filtered out ahead of being invoked (which could result in empty messages).
Branches
  • Fix so that MongoDB branch-level collections are always cleaned up properly for cases where a failure occurs during branch creation.
GraphQL
  • Fix so that GraphQL queries are entirely isolated from node caches so as to prevent issues when querying nodes.
Merge
  • Fix so that merges of branches works as intended when operating within older, legacy repositories.
Node
  • Fix so that nodes read properly by considering case insensitivty when using a projections to tokenize the path.
Search
  • Fix to search type filtering so that the __type property can be search as intended.
Transfer
  • Fix so that imported Node attachments are automatically indexed into Elastic Search upon for all cases.
User Interface
  • Fix so that unlocking the attempted login lock is picked up immediately by the user interface. This allows unlocked users to retry their login right away.
  • Fix so that the Delete Project User action checks permissions against the project, allowing Project Managers to remove users from a project.
  • Fix so that Attachment Pickers validate extensions (if so configured) for existing attachments.
  • Fix so that the “required” property is handled properly for some nested cases.


Cloud CMS Release 3.2.64

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

Multitenancy
  • Improved the multipart resolver so that it supports per-tenant file upload options with global setting fallback.
GraphQL
  • Ensure that both incoming and outgoing property names that flow through the property data fetcher are SDL encoded. This allows property names, such as my:thing, to be queryable using the value my_thing.
User Interface
  • Adjust the pre-delete warning modal to distinguish between nodes that will be deleted and those that will be affected.

Bugs

Deletions
  • Fix so that restoration of deleted nodes preserves original property values for cases when an overlay set of properties are provided.
Actions
  • Fix so that the Move Node action (for both single and multiple sets of nodes) properly calculates the incoming associations, solving for cases where moved nodes wouldn’t appear to move in the content graph.
Search
  • Fix so that older ES Search DSL blocks are parsed and automatically handled, improving on situations where some customers with older ES search blocks might have seen inaccurate results.
Projects
  • Fix so that projects that fail to create can be more easily cleaned up – by allowing the UI to load up even if the project stack is missing.
Tags
  • Fix so that documents created with inline tags are indexed straight away and are discoverable by searches against their tag values.
Transaction
  • Fix so that multi-node transactions now correctly identify their prior value when calculating the diff that informs the ES index. This results in more meaningful and correct deltas being bulk written into the ES index.
SSO
  • Fix so that verification of assertions using a custom digital certificate are picked up immediately upon save.
User Interface
  • Fix so that the Related Content button works as intended when used in an array (with an index as a portion of the label).


Cloud CMS Release 3.2.63

Published on 01/14/2021
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.63 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

Branches / Releases
  • Faster merges with improved transaction ordering for more accuracy when working with complex graph structures.

Bug Fixes

Search
  • Fix so that pagination sorting works as intended when using some _system inner fields.
Branch Merge
  • Fix so that merges work properly for cases where owned associations are being merged with automatic conflict resolution enabled.


Cloud CMS Release 3.2.61a

Published on 12/21/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.61a 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.

New Features

The following features have been backported from 3.2.62 to 3.2.61a:

Command Line Interface
  • The CLI now supports transfer commands to enable developers or administrators to script the import and export of projects, repositories, branches, nodes and more.
  • Now supports Node 15.x and beyond.
Supported Stacks
  • Added support for MongoDB 4.0.21
  • Added support for Elastic Search 6.8 and 7.9
  • Added support for AWS ElasticSearch 6.8 and 7.9









Get Started with Cloud CMS

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