Cloud CMS Release 3.2.89
Published on 08/27/2025
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.89 release.
Email
Upgrade Considerations
Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-89.html
With this upgrade:
- MongoDB 4.4 or above is required
- You will need to perform a cold restart of your API cluster.
Enhancements
Auto Compression
- Repository changeset auto-compression is now disabled by default. This prevents auto-compression from running unless explicitly enabled.
- Enhanced the email subsystem to support additional email providers such as Google OAuth.
- Automatic migration of email provider configurations to the new structure.
Find
- Improved performance of Node Find API calls that leverage MongoDB aggregation pipelines and composite cursors into Elastic Search for faster and more efficient execution.
- Faster execution of all sibling systems that utilize the Find API including GraphQL, traversal and path lookups.
- Find API calls now scale to much larger data sets with greatly reduced overhead.
Inline Links
- Faster and more efficent export, import and copy of content with inline links and relator properties.
Logging
- Added more logging for several subsystems to provide greater detail to administrators.
- Removed some internal logging that was unnecessary.
Third Party Dependencies
- Updated to latest thirdparty dependencies including OpenCSV, PDFBox, Jackson and Apache Tika.
Transfer
- Optimized the transfer of documents with
Links To
associations so that any links to system-managed Linked Resources are excluded and simply repopulated during the import. This results in faster exports and quicker copies and publishes.
User Interface
- Faster and more responsive rendering of forms and pickers with loading and progress indicators.
- Removed auto-compression option from the project settings page.
Bug Fixes
AWS ECS / Hazelcast
- Fix so that property type conversions work as intended for all AWS configuration properties. In this case, some integer properties were failing type conversion.
Binaries
- Fix so that binary storage configurations with null prefixes now work (replacing with empty string).
Branches
- Fix so that additional safeguard code catches edge case where potentially errant tip changeset IDs could have been written into the branch upon transaction commit.
Extraction
- Fix so that the Extraction feature will work for some edge cases where the extraction logic could find itself in a loop when an attachment was deleted.
Find
- Fix so that sorting of Find API calls now naturally sort on search score for cases where a composite search is provided.
- Fix so that ordering is consistent across query, search, find and GraphQL for some edge cases.
Publishing
- Fix so that publishing notification calls fail more gracefully and no longer halt publishing in the event of an error.
Transfer
- Fix so that HTML substitutions for inline values within property values are more lenient with respect to malformed HTML. This ensures that HTML is not rewritten or changed in any unexpected way on transfer import.
- Fix so that ordering for some iterations is consistent for all dependency types.
Translations
- Fix so that translation locks are now distributed to as to prevent race conditions that could spawn up in highly concurrent scenarios.
User Interface
- Fix so that filter works efficiently and consistently across pickers, documents listings and content instances pages.
- Fix so that jobs page filter works properly for non-escaped values.
- Fix that UI navigation event loop clears all pending timers on click for faster navigation.
- Fix so that the save button is properly disabled while editing properties until the form is fully loaded in and valid.
- Fix for formatting of some unescaped text values within the UI.
- Fix so that content instances page now defaults to the first project-configured content type when none is selected.
- Fix so that switching the content type properly clears the filter observable.
- Fix so that reload of doclist components preserves the focus and cursor position for the search/filter field.
- Fix so that content entry wizards no longer errantly scroll to the incorrect target fields after validation failure.
- Fix so that array validation errors display with error state css classes (in red).
- Fix so that array item swapping/moving is more consistent.
Ready to Get Started?
Unlock your data with smart content services and real-time deployment