Cloud CMS Release 3.2.64

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://gitana.io/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 (https://gitana.io/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).