Cloud CMS Release 3.2.56

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.56 release.

Update Recommendations (On-Premise Only)

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

New Features

Localizers

• Adjust the localization strategy that is used to resolve a localized piece of content for a requested master node and locale (example: en_UK). This allows customers to either select or implement the localization strategy that their business requires, allowing for desired fallback or graceful degradation selection. On-premise customers can build their own Localizers using custom Spring beans. For more information, see: https://gitana.io/documentation/docker/configuration/api-server.html#locale-resolution

Script URL Resolvers

• You can now configure the base URL to be used by templates and the scripting engine when building incoming links that externally resolved. By default, this will fall back to https://{subdomain}.cloudcms.net. For more information, see: https://gitana.io/documentation/docker/configuration/api-server.html#script-resolvers

Enhancements

Attachments

• Attachment information returned from the API now includes an ext field that indicates the filename extension that will be used if the file is ever written to disk or deployed to a deployment endpoint. For more information, see: https://gitana.io/documentation/attachments.html

Localization

• The default localization strategy now gives preference to direct and wildcard matches for language over country (which is now considered last).

Login

• Added UI Server configuration properties to more effectively manage limits around attempted logins. For more information, see: https://gitana.io/documentation/docker/configuration/ui-server.html#login-attempts

Property Mappings

• Property Mappings now run within a single transaction so that any associated nodes with mapped properties commit along with the original node in one fell swoop, resulting in faster execution and smaller changeset counts.

Relator Properties

• Relator properties execute their mappings within a single transaction, resulting in much faster performance and updates to all related nodes within a single transaction.

Translations

• Translation Nodes now preserve attachments when auto-generated from master node via the API or user interface.
• Refreshing a Translation Node will copy forward any Master Node attachments if no attachments are currently present on the Translation Node.

Bug Fixes

Branches

• Fix so that processing of merge conflicts of type definitions work as intended for complex cases where inherited types may have been deleted or modified within the same transaction.

Cluster

• Fix so that cluster initialization performs some additional safeguard checks to protect against concurrency issues that may occur when multiple servers haven’t yet joined the cluster (known as a the “Split Brain” problem). A database journal is now maintained to track non-joined servers on startup and fail early.
• Fix so that a force kill of a server in a cluster (that happens to be holding a branch lock on a committing transaction) cannot result in multiple tips being recorded (one active and one inactive). This yielded cases where some nodes might not write to the correct tip for a duration of time until the remaining server rebalance. A database journal now guards against this and inactive tips are cleaned up immediately.

Content Model

• Fix for Content Model Form Builder so that Attachment Field and Content Field render as expected for nested cases.
• Fix so that click handling within the Content Tree works properly and displays as produces consistent results between the tree and list views.

HTTP Range Header Support

• Fix so that single range requests come back as non-multipart.
• Fix so that range parsing supports open-ended start and finish markers (i.e. Range: bytes=-999 or Range: bytes=1000-).

Permissions

• Fix so that node updates that fail due to insufficient permissions won’t leave an intermittent cache in an incorrect state. This cache could leave the perception that the node had been updated so long as subsequent requests arrived to the same API server (via sticky session).

Transfer

• Fix so that exporting a definition now automatically exports all parent definitions as well.
• Fix so that relator properties are detected at export time and any nodeType or associationType definitions of those relator properties are exported as well.
• Fix so that properties are scanned at export time and any schema-level referenced definitions (via $ref using the qname:// loader) are exported as well.

User Interface

• Fix so that Deploy Nodes Strategy action shows the title in the form.
• Fix so that the Add Publication State modal lets you select based on configured States.
• Fix so that the Create Policy action will show association definitions in the definitions list when working with Association or Associated Node Policies.
• Fix so that Jobs List search term produces more accurate results.
• Fix so that the Attachment Picker maxFileSize setting excludes values less than zero.