Cloud CMS Release 3.2.70

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:

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 (

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.


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:
Gatsby Integration
Nuxt Integration

Bug Fixes

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