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

Published on 07/01/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.55 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 (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

Data Export Wizard
  • When exporting ZIPs of content using the Export Wizard, any exported JSON is now prettified by default.
Indexing
  • Indexing of nodes for full-text search now always runs as a background job as opposed to running in-transaction. This speeds up write operations for the vast majority of cases. The makes full-text search indexing consistent across the board.
  • Indexing now optimized to run faster by delaying the indexing calls to the very end of multi-stage transactions. This results in fewer indexing calls and lower CPU usage for the system.
  • Improved usage of Elastic Search Bulk API so as to have fewer indexing background jobs and faster overall completion.
Login
  • The error messages and feedback provided to the user upon a failed login has been limited so as to be more secure and less descriptive of the underlying reasons why the login did not succeed.
MongoDB
  • Improved support for conversion of BSON V2 Types in MongoDB for cases where existing MongoDB 2.x or 3.x databases are migrated to newer versions of MongoDB.
Node Statistics
  • The accumulation and tracking of association type counters is now disabled by default. This provides a significant performance improvement for the vast majority of use cases where those counters are not required. This general association-type counter accumulation can be enabled using either a feature or a repository-level configuration option. For more information, see https://www.cloudcms.com/documentation/api/statistics.html.
Permissions
  • Added permissions for DEPLOY and UNDEPLOY that can be used to control the availability of those functions within the API and the user interface.
  • The Deploy Node Action now requires the current user to have the DEPLOY permission against the targeted content instance.
System
  • The metrics collections thread now includes disk usage information along with other healthcheck information in the periodic log.
  • Added a background thread that periodically cleans temp file space to facilitate the management of long-running pods or containers that may have otherwise relied on JVM shutdown hooks to clean up disk space.
Transfer
  • Tip-mode imports will now automatically execute any property mappings for any property mapping associations during the import. This makes sure that property mappings are established when the import completes.
  • Faster performance due to improved management of caches
Translation
  • The Azure Translator integration now supports very large text arrays by chunking text translations into multiple calls.
User Interface
  • The Content Instances page now has more actions available on it to make it consistent with the Document Library page.
  • Various improvements across the user interface to establish consistency between the number of selected items (0, 1, more than 1) and the available action set that can execute against that selection.
  • The Change Type Action modal now offers a checkbox to let you decide whether to show system content types.
  • The Attachment Picker now supports maxFileSize and fileTypes. For more information, see https://www.cloudcms.com/documentation/forms/fields/attachment-picker.html.
  • Added a success message that displays when a lock is successfully released.
Workflow
  • The Web Hook workflow handler now supports additional HTTP methods (GET, PUT, DELETE) along with POST which was already supported. For more information, see https://www.cloudcms.com/documentation/workflow/workflow-handlers/webhook.html.

Bug Fixes

Actions
  • Fix so that the Change Type renders properly for some cases where actions had missing properties.
Associations
  • Fix so that the proper error HTTP response is provided for cases where a failed attempt is made to manually associate a source and target node via the API.
Content Model Builder
  • Fix so that drag/drop works consistently across a wider variety of browsers along with improvements to Field Editor selection, support for nested fields within Array and Object containers and updated inspectors for editing field properties.
Dashboards
  • Fix so that drag/drop works consistently across a wider variety of browsers.
Email
  • Fix so that the case for email addresses is ignored when creating password reset requests.
  • Fix so that lower case email addresses are enforced more consistently within forms.
GraphQL
  • Fix so that GraphQL results no longer strip off null values for cases where they are regarded as legal values in GraphQL Schema.
  • Fix so that the UI display of HTML from within GraphQL results renders properly.
Indexing
  • Fix so that bulk indexing will complete successfully for cases where an encrypted PDF document might be inserted into the middle of a indexing chunk, causing that document's text transformation to fail and causing the remainder of the chunk to fail.
PDF Generation
  • Fix so that PDFs with embedded images generate properly when using a PDF generation template and referenced images from within Cloud CMS.
Print
  • Fix to Print and Print Preview within the user interface so that print dialog is compatible with a wider variety of browsers.
Releases / Branches
  • Fix so that Release or Branch creation and merging works properly for cases where a branch had a large number of changesets and no snapshot to support incremental diffs. In this case, a faulty snapshot was being generated and consistently had to be re-created.
  • Fix so that branch to branch copies work properly using MongoDB 3.6 and beyond bulk index calls.
  • Fix so that the Retry Merge button no longer appears while resolving merge conflicts between Releases.
Teams
  • Fix a bug so that team identifiers cannot overwrite when custom team properties are overwritten via API call.
  • Fix a security hole that, in some cases, permitted users without the UPDATE authority against a Team's underlying Domain Group to add or remove users from a team.
User Interface
  • Fix so that user default projects are automatically cleaned up when any kind of project is deleted (not just projects in the oneteam family).
  • Fix so that versioning diffs (JSON RFC 6902) are computed in the correct direction when visually selected for some cases.
  • Fix so that Dashlet default maximums are enforced.
  • Fix so that thumbnail and preview icons show up properly on the Attachments screen for cases where you have multiple attachments.
  • Fix so that Node Picker, File Picker and Upload controls support null or false for the uploadPath setting to indicate that uploaded nodes will not be linked to a folder.
  • Fix so that Release Finalization results don't show on the Release Overview page after a successful Release execution.
  • Fix so that the Project Publishing configuration pages show the correct listing of content types for cases where the content types had one or more missing values.
  • Fix so that PDF Preview works consistently across a wider variety of browsers.
  • Fix so that the Grant Authority action's "Unselect All" option work as intended.
  • Fix so that the Add Permission to Role action shows each permission's description.
  • Fix so that the Rule Actions editor's "Action Type" field is required.
  • Fix so that links to incorrect (or no longer valid) Project IDs or Branch IDs redirects as appropriate.
  • Fix so that username is forced to be lowercase on field entry.


Cloud CMS Release 3.2.54

Published on 05/27/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.54 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 (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

Logs
  • Logs now include additional stack trace information if available
  • Improved formatting of downloaded log files to include additional stack information, more detail and a greater default length
Performance
  • Improved performance throughout due to optimizations to DB layer and service event handlers.
Releases / Branches
  • Release finalization now performs a dry commit merge to allow for early detection and resolution of schema-related merge issues.
  • Release finalization errors are now reported on the Release overview page. Previously, these were detected during release execution (instead of finalization) and could only be inspected via logs.
  • Releases now include additional flags to track finalization results as well as execution stage errors.
  • Release and Workspace Content and Activities pages now show more information about content changes including property level differences

Bug Fixes

  • Fix so that deleting a workspace or a release redirects away to the listing page for the case that the user currently has that workspace or release selected
Logs
  • Fix so that project-level logs scope properly to just project-level exceptions
Memberships
  • Fix to principal memberships caching so that principal memberships reflect updated values when members are updated separately.
Pickers
  • Fix so that Picker Upload button preserves the selected entries when populating the list of selected nodes after upload
Property Mappings
  • Property mappings now execute much faster and in linear time (impact cases where a large number of mapping associations exist in the graph). This impacts customers who might have otherwise seen occasional 504 timeouts on update.
Stream Handling
  • Fix so that stream handling to S3 is more efficient and populates range headers properly
Snapshots
  • Fix so that snapshots are built properly for cases where snapshots are auto-generated and the changeset history is excessively large. This addresses performance as well as a bug with Releases being created and reflecting incorrect content.


Cloud CMS Release 3.2.53

Published on 05/21/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.53 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 (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

HTTP Range Headers
  • Added support for HTTP range headers to allow for multi-range, multipart downloads of partial content. This improves the ability of Cloud CMS to support large content and media formats (such as video and audio files) with improved operability with streaming services, players and edge caching facilities.

Enhancements

HTTP
  • Improvements to HTTP header management to incorporate more end-user friendly assumptions of header values
Localization
  • Improved the graceful degradation of locales when multilingual content is being localized using internationalization (I18N) translations. This makes the localization of content on the fly more accurate for cases where master nodes manage their locale codes individually.

Bug Fixes

Merge
  • Fix so that branch merge is more accurate for cases where large collections of node deletions are marged at once and there are interdependent owned relationships within the merge set
PDF Export Wizard
  • Fix so that selected PDF template validates upon submit properly
Permissions
  • Fix so that permissions cache invalidates immediately for propagated group memberships when a team is deleted
Transfer
  • Fix so that nodes collection markers are maintained properly after the transfer import of a node


Cloud CMS Release 3.2.52

Published on 05/12/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.52 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 (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

Multi-Factor Authentication
  • Added new Docker-configurable Multi-Factor authenticators for Trusted Tokens (HTOP and TOTP). These are available for on-premise installations and allow for use for Google Authenticator and other 2FA token authenticators.

Enhancements

Administration Console
  • Unify the Administration Console login with that of the main UI so that they both use the same login screen and extensibility patterns (for whitelabeling logos and more). This further enables Multi-Factor authenticated access to the Administration Console.
Host Detection
  • Improved parsing of request headers to detect and handle some short-form hosts and IPV6 addresses more accurately
Performance
  • Improved performance and scalability due to faster and more efficiently invalidation of distributed Hazelcast caches

Bug Fixes

Associations
  • Fix so that Child and Owned associations are processed correctly on deletion to ensure that child associations clean up properly for cases where a node has an owned relationship from an owner node
  • Fix so that a:child and a:owned inherited association types are detected and handled correctly on deletion for additional cases
Content Types
  • Fix so that Content Types customized lists properly appear in certain places within the Manage Project > Publishing interface and other places within the user interface
Multi-Factor Authentication
  • Fix so that MFA challenges are disabled for some cases where they were errantly appearing due to a cache invalidation glitch
Tree
  • Fix so that duplicate tree entries do not appear on some refreshes


Cloud CMS Release 3.2.51

Published on 04/25/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.51 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 (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

Kubernetes
  • Added native support for Kubernetes API discovery. This allows Cloud CMS API servers running in a Kubernetes cluster to discover each other without any additional network configuration.
Multi Factor Authentication
  • Added support for second factor authentication using TOTP and HOTP codes with support for SHA, SHA256 and SHA512
  • Added support for trusted auth code issuances for protection of priviledged accounts (on-premise only) with pluggable notifiers for Email, Web Hooks and more

Enhancements

Auto Translation
  • Added the excludePaths setting to the f:auto-translate feature to allow content modelers to skip certain fields during automatic translation
Caching
  • Distributed caches now invalidate much more efficiently by using predicates for key discovery and removal
Graph QL
  • Added the ability for the nested relator content to be exposed via the GraphQL API
Teams
  • Teams now support custom properties when being created or updated via the Teams API
Tenant Invalidation
  • Added separate tenant invalidation messages to notify user interface tier of pre-emptive cache invalidation ahead of tenant creation
Versions
  • Faster query and pagination through versions including introduction of from based pagination via the API
  • Versions API now optionally hands back differences information on the API call for each row in the result set
Views
  • Added progress tracking for Branch Tip View rebuilding

Bug Fixes

Attachments
  • Fix so that the attachment event handler methods always process correctly after the first create or update invocation for all cases. This resulted in situations for the end users where _attachment properties might only end up having their id field filled out on document create
Branches
  • Fix so that the Branch API's Tree list method (which delivers a flat representation of the branch tree) always come back in a consistent and correct order
Identities
  • Fix so that deletion of a domain or a principal will always result in the association of a principal's identity to a directory identity policy. There were cases discovered where this did not occur
Releases
  • Fix so that release limits are calculated only against active releases (and not all releases)
User Interface
  • Fix so that the Locale Filter works correctly for the Add Translation action via the UI
  • Fix so that the Content Type Picker correcftly shows system content types when nothing in configured on the UI Content Types page
Workflows
  • Fix so that project-scoped workflow elements (workflow instances, tasks, etc) are always cleaned up from the global context when a project is deleted.


Cloud CMS Release 3.2.50

Published on 03/16/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.50 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 (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

API Keys
  • For on-premise installations, the org.gitana.platform.services.apikeys.defaultBaseURL property can be configured for API containers to configure the baseURL that API Keys will use (the default is https://api.cloudcms.com)
Relators
  • Improved performance of relators properties and relator associations on save including optimizations to remapping logic
Transfer
  • Improved performance with more efficient use of paginated iterators
  • Inline Link associations (a:links-to) and Linked Resources (n:linked-resource) are now traversed and included when exporting nodes
Undeletes
  • When undeleting nodes, the child associations that once related that node into the folder hierarchy are also restored provided that the parent node exists
User Interface
  • Remove limit on the number of Project templates made available for selection
Versions
  • Faster list and query retrieval of node version history using less memory and optimized indexes

Bug Fixes

Transfer
  • Fix so that domain users transfer correctly for cases where the domain itself may not be included and may be optional
  • Fix for an error that could occur when a user was being added to a team on import (and the user was already a member of the team)
  • Fix for a concurrent modification exception that could occur when optional dependencies were removed in partial imports
  • Fix for a case the f:inline-links feature prevented nodes from auto-publishing when f:publishable lifecycle state was set upon creation
User Interface
  • Fix so that Content Type dropdown used in the Create Document wizard only shows enabled types
  • The "Rules" folder now hides along with other system folders when the Hide System Folders option is selected
  • Dashlets now only show branch information is either Workspaces or Releases are enabled within a Project


Cloud CMS Release 3.2.49

Published on 02/20/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.49 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 (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

Logging
  • Improved the documentation for the API logging facility to now include examples for how to route the logging of API calls, audit records, job operations and exceptions to a variety of out-of-the-box AWS endpoints including S3, Kinesis, Kinesis Firehose, SQS and CloudWatch. For more information, see https://www.cloudcms.com/documentation/docker/configuration/api-server.html#logging.

Enhancements

Actions
  • Improved the extensibility of the Remote IFrame Action to make it easier for customers to build UI wizards and modals that render from remote servers
Forms
  • Added the ability to disable the Upload button within Pickers (upload: false)
Transfer
  • Faster performance and lower memory requirements for import, export, copy and publish operations

Bug Fixes

Permissions
  • Fix so that the Propagates Authorities feature (f:propagates-authorities) correctly unwraps authorities and works as intended during deletion
Releases
  • Fix so that Releases cannot be unfinalized or finalized once they've already been released
Rules
  • Fix so that the Start Workflow Action (when fired from a Rule) correctly assigns the current users for workflow models that have an initial task with an auto-completion route
S3 Binary Storage
  • Fix so that S3 connection threads are managed more efficiently with improved caching of clients, resulting in a smaller and more responsive connection pool
Translation
  • Fix so that Auto Translated values for I18N multilingual documents aren't HTML escaped before being inserted back into translated document
Tree
  • Fix so that the Tree API now correctly prunes the tree (and all inheriting leaves) for cases where the invoking user lacks sufficient read authorities against a given node
User Interface
  • Fix so that Favorites display correctly in the UI for all cases
  • Fix so that the Copy Documents Action works as intended for cases where source documents didn't have their references populated


Cloud CMS Release 3.2.48

Published on 02/05/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.48 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 (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

Import / Export
  • Improved the transfer subsystem to allow for much larger archive payloads to be processed more quickly. This has a positive impact on any copy, move or duplication operations including publishing and deployment and also allows for more efficient handling of larger data sets for backup and restore.
  • Optimizations to speed up transfer including in-memory indexes and more efficient use of EHCache when managing off-heap storage
  • Added the ability to Select All Branches within the Project Export Wizard
Logging
  • Additional logging for deployment handlers
Relator properties
  • Improved error logging for cases where relator property members are missing their ref attribute

Bug Fixes

Branches
  • Fix so that branch comparison operations that encounter single entry deletions will display properly within the user interface
Search Indexing
  • Fix so that bulk index operations that use a paginated query handler (for large data sets) will calculate the offset correctly on iteration ensuring that all content items index for those cases
Import / Export
  • Fix so that text token substitution processes delimitters properly for some cases where HTML is being processed and the delimitter splitter size differs from token splitter size
Web Hooks
  • Fix so that node paths are consistently applied to payload for deletion cases that follow from a merge operation
Releases
  • Fix so that multiple conflicting future Releases can be scheduled as intended for certain cases where the intentionality of a specific conflicting nodes wasn't clearly defined. This allows for the Scheduling of Content Availability for these cases - whereby content is published on one Release and then unpublished on a second Release. For information about Scheduling Content Availability, see https://www.cloudcms.com/documentation/releases.html#scheduling-content-availability.
Archives
  • Fix aso that Archive pagination works as intended for cases where Archives are errantly present with duplicate IDs
Workflow
  • Fix to the user interface so that users can be assigned via override to a swimlane for pooled task cases where swimlanes are assigned to a group
Paths
  • Fix so that document paths are displayed correctly for cases where UI encoding is force enabled
Forms
  • Fix so that Markdown field toolbar settings can more easily be configured
  • Fix so that SimpleMDB field events fire for all cases
  • Fix so that Array field raises separate events for add, remove and move operations


Cloud CMS Release 3.2.47

Published on 12/22/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.47 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 (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

Amazon Services
  • For On-Premise, added logging support for Amazon Kinesis, Amazon Kinesis Firehose and Amazon CloudWatch. This allows customers to configure custom loggers for request logging, audit capture and general reporting that log to these endpoints, allowing downstream services to process log streams using business intelligence tools, Amazon Kinesis Analytics and AWS Lambda Functions.
IBM Cloud / Watson Services
  • Added support for IBM's Watson Translation Service. This works nicely with Cloud CMS auto-translation feature to automatically create and populate I18N translations. For more information, please see https://www.cloudcms.com/documentation/integrations/watson/translate.html
  • Added a Binary Storage Provider for IBM Cloud Object Storage. This allows on-premise installations to persist binary objects to COS as part of their architecture. For more information, pleasee https://www.cloudcms.com/documentation/binaries/ibm-cos.html
  • Added a Deployment Handler for IBM Cloud Object Storage. This allows customers to publish and deploy content from Cloud CMS to IBM COS for any purpose including backing of a CDN for edge distribution. For more information, please see https://www.cloudcms.com/documentation/deployment/deployment-handlers/ibm_cos.html

Enhancements

Transfer
  • Significant performance improvements and better management of heap for Transfer (import/export)
Deployment
  • Performance improvement and optimized code paths for better tracking of deployment and undeployment activities
Tokens
  • Access Tokens can now be expired without concurrently expiring the Refresh Token
Preview
  • Preview templates now support paths and rootPath variables, allowing nodes paths to be used while building Preview URLs
Attachments
  • API methods are now available to inspect attachment information and download attachments from any version of a node (not just tip)
Azure
  • Added support for Azure account name / key authentication for Azure Blob Storage Deployment Handler and Azure Blob Storage Binary Storage Provider
Branch Changes
  • Improvements to the accuracy of branch changes via improvements to differencing
Logging
  • Improved logging for script errors that capture a few nuanced errors and ensure that source code, line and column numbers are available in the error message
User Interface
  • Additional customization options are now available for the the new_folder action to allow for better control of content types and setting the default click state of the content type selection checkbox
  • When forceUriEncoding is set on the project, show raw folder paths in the breadcrumb
  • The full-text search regex now allows for single quote within the expression to allow for better compatibility with Elastic Search Query String syntax
  • Updated the links for the Project nad Platform Favorites list so that they go to the node's /overview and /browse pages depending on whether the node is a document or a folder)

Bug Fixes

Web Hooks
  • Fix so that web hook invocations triggered on a p:afterDeleteNode policy are consistent with other policies and will contain node.paths as expected
  • Fix to ordering of events so that re-entrant Web Hooks calls on "after" handlers cannot encounter an invalid dictionary state
Branch Changes
  • Fix so that branch changes paginate as expected when browsing through them via the UI
Tokens
  • Fix so that API response defaults to JSON format for cases where accept header is provided in expected manner, ensuring proper handling of 401 invalid token errors (and allowing for clients to properly refresh as expected)
Transfer
  • Fix so that Export Configuration is respected for Team Members such that team members aren't exported when flag is false
Paths
  • Fix so that path indexing handles deletion for some cases much better and updates the path index as expected
User Interface
  • Fix so that the screen full refreshes after a release is archived
  • Fix so that the Recent Project Activities dashlet correctly uses the configured pagination limit
  • Fix so that Tools > Import Project Data action works as intended
  • Fix so that UI templates for Selected Items work as intended


Cloud CMS Release 3.2.46

Published on 12/01/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.46 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 (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

Transfer
  • Transfer exports now execute more quickly with more efficient use of iterators and lookup maps\
Branches
  • Branch Changes now hand back more information and compute more quickly, making it easier for editors to cherry pick for content from other branches

Bug Fixes

Transactions
  • Fix to correct for an occasional path by which nodes could be committed to the master collection without the required _system._op and related tracking information. The result of this bug was that items could be missing on a Branch Changes calculation and editors might not see the items they expect on the Copy or Compare branch actions. The should obviate the prior workaround which involved running the command line tool to reapply those properties.
Favorites
  • Fix so that Favorites are pulled back on the Project and Platform dashboards as intended for users with minimal permissions
Transfer
  • Fix so that memory is managed more efficiently allowing for exports of much larger sets of content to properly paginate on query and store to disk with less heap growth
  • Fix so that transfer exports execute more quickly
Behaviors
  • Fix so that behavior bindings are correctly remounted after a branch merge operation for some cases
Principals
  • Fix to assert that principals can neither be created nor updated with missing or incorrect type information in the JSON payload
Tree
  • Fix so that the order of the flattened results computed in the tree controller sorts with the master branch at the top
Attachments
  • Fix so that nested _attachment properties and Attachment form fields are supported within content types as expected









Get Started with Cloud CMS

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