Cascade CMS 8.23

Support for Google Analytics 4

This release introduces support for Google Analytics 4 in our analytics data integration. You can now pull in GA4 data to see in Site reports and at the Folder and Asset level including metrics new to GA4 like engagement rate. 

You can find more details on configuring the GA4 integration in the knowledgebase.

Content Owners in Report CSV Exports

We're now including the asset's content owner data in CSV exports of the Stale Content and Up for Review for reports to help identify responsible users when reviewing these content exports outside of the CMS.

Stronger password policies

We're enforcing strong password requirements for users using native password authentication. This is to help comply with the NIST 800-53 security standards. Visit the documentation on managing users for more details on the requirements of the new password policy. 

Features/Improvements

• Viewing relationships for admin area assets, such as Shared Fields, Data Definitions, Publish Sets, etc. will no longer appear to be missing a table column. Additionally, relationships display as errors or warnings when deleting assets will now contain site and path information for extra context.
• Passwords for normal authentication users are now required to be stronger. More information about the new password policy can be found on under the Adding a User documentation.
• Updated processing of Google Analytics Reports to prevent timeouts from long running queries.
• Connectivity issues encountered during publishing will now retry using a backoff to help address possible rate limiting issues.
• Improved memory usage during the Page rendering process. Also updated XML namespace handling to no longer remove unused namespaces.
• Google Analytics Connector will now support for Google Analytics 4.

Fixed

• Addressed an issue where under certain situations performing multi-op operations (e.g. publish, copy, move, delete) would not check the proper site for available destinations/connectors or user abilities.
• Working copies will no longer become orphaned if an error occurs while attempting to start workflow.
• Relaxed asset naming restrictions to allow for successive underscores (e.g. __foldername).
• Long words and URLs within asset comments will now properly wrap instead of appear to be cut off.
• The audits table will now default to sorting chronologically by the Time column.
• Entering a version comment that contains special characters, such as a percent sign, and submitting after performing data checks will no longer display an error.
• Words containing special characters will no longer be split up during spell checking. Also improved the way full search handles these same words.
• Addressed an issue in which creating a File using an Asset Factory that has a base asset and switching to the bulk file upload interface uploads the files incorrectly. Also improved UX when switching between single file upload and bulk file upload.
• Long Asset Factory descriptions will now wrap to new lines.
• The CSV export for Stale Content and Content Up for Review reports will now contain the asset's owner.
• Addressed an issue in which drag 'n drop of structured data field fields would not work correctly when expanding a group that is collapsed by default.
• Addressed an issue where a warning would be displayed if the user does not have access to the restricted folder of a chooser field.
• Addressed an issue where, under certain circumstances, the user would be redirected to the login screen despite having the "Remember Me" option enabled.
• Addressed an issue where page regions could not be interacted with after performing an in-context edit.

• LDAP Configuration Orphaned User Behavior Changes
• First time installation?
• Upgrade Steps

LDAP Configuration Orphaned User Behavior Changes

The Delete option for the LDAP Configuration Orphaned User Behavior has been deprecated to prevent accidentally mass deleting users during an erroneous LDAP sync and will be removed in a future release of Cascade CMS. Until the behavior is removed as a valid option, configurations with Delete/Remove will fall back to Deactivate.

First time installation?

Be sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.

Upgrade Steps

1. Shut down your currently running Cascade CMS environment.
2. Before you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.
3. Read the release notes and upgrade guides for all releases between your version and the latest version.

Server Requirements (for CMS deployment)

Supported Platforms