Cascade CMS 8.4

Cascade CMS version 8.4 includes a number of features and improvements centered around improving the user collaboration and editing experience. This release also includes a large number of improvements and fixes.

  View Requirements

Concurrent editing notifications

To help avoid overlapping edits, users will now be notified if they begin editing an asset which has a recent draft from another user.

 concurrent edit notification

Asset locks and workflows

Improvements have been made to the lock and workflow experience to further help with user collaboration. These features address ideas we've heard from you on our customer idea exchange:

Working Copies of an asset can now be re-assigned to other Users at particular steps of a Workflow. Step re-assignment can be restricted to individual Users or to Users of a particular Group or Role.

Users are no longer able to create drafts when an asset is locked or currently in Workflow. Instead, users are presented with a message indicating who the current owner is, and depending on their Site Role abilities, can quickly re-assign the lock or working copy.

locked working copy

Mentioning users (@mentions)

Ever wish you could easily pull someone into a conversation on a particular page or task? Certain comment areas now support the use of autocompleting "@mentions" as a means to include users in a conversation by simply typing the @ symbol and part of the username, or their full name, to see a list of suggestions.

Current comment fields that support @mentions include:

Page header improvements

The look and feel of the page header has been updated for improved flexibility across all types of devices. Longer page titles are now being truncated better mobile support.

page header improvements


  • Auto-complete @mentions of usernames/full names in Asset/Task Comments.
  • Notify Users of concurrent edits
  • Do not allow submitting drafts to a locked asset (manually or through workflow). Also, users can send requests to lock owners to unlock assets.
  • Locked assets can be reassigned to other users
  • Allow reassigning of Working Copies held at particular steps of Workflow
  • Update look and feel of page header for consistency and flexibility
  • Support for SQL Server 2016 for on-premise installations. Note that currently supported versions are 2016, 2014, and 2012. SQL Server 2008 is no longer supported.
  • Upgrade detects and migrates some common problem assets associated with the Global area when upgrading from 7.x.
  • Use full SHA for build id
  • Intercom for Cascade Cloud customers
  • WCAG accessibility checker when previewing pages for Cascade Cloud customers

Issues Fixed

  • Search functionality pegging CPU and possibly causing more widespread performance problems
  • Users table takes a long time to load for instances with a lot of audits
  • Write access error during assignment of Workflow edit step if Asset lock does not belong to user
  • User can not commit changes to their own locked assets if they are required to go through Workflow
  • Owned By column in Content Up for Review/Stale Content reports not being populated
  • User Comments: it is not possible to mention usernames with spaces
  • Content Ownership Report: Created column has same value as Last Modified column
  • After deleting Workflow, Lock/Working copy left on asset can't be removed
  • Errors encountered when attempting a search/replace are not displayed to the user
  • Catch all 403 errors from Google Analytics
  • Asset Details menu shows system metadata for the draft
  • Tinymce failed initialization in Firefox on consecutive modal open
  • Intermittent error when committing locked asset
  • Error: "This asset edit was not saved because another edit was submitted"
  • Chooser panel does not show details for site management area asset types
  • Modal backdrop doesn't get removed after closing second modal
  • EmailProvider workflow trigger sends duplicate emails when an error occurs during send
  • Viewing draft message is confusing when there is a working copy present
  • Start workflow screen throws null pointer when there are no ordered transition steps in workflow definition with default user or group assignments
  • Review workflows should create a working copy
  • Workflow builder: escalation hours incorrect after submission
  • Full Screen Preview when viewing a Page is not taking currently selected Output into account
  • Unable to restore assets from Recycle Bin when using custom 7.14.2 build when rolling back from 8.x upgrade
  • IE11: Inserting external links in WYSIWYG places content at the beginning of the content. Recommended to use Edge or a different browser
  • Dollar signs ($) in title/display name of assets selected in choosers prevent Edit modal from appearing
  • Disappearing checkboxes on publish dialog
  • Un-publish on move/rename does not work when starting workflow and then selecting "None"
  • Disabled outputs are still able to be toggled on publish
  • "Welcome" widget missing for users without a full name
  • Safari 10.1: Can't scroll vertically beyond viewport
  • Allow custom CSS classes within Editor Configruations to contain spaces
  • Adding new repeatable groups will no longer duplicate the previous group's values.

Upgrading from 7.x to 8.4

For those who are upgrading from the 7.x series, Cascade CMS 8.4 introduces a new migration tool that will automatically address problematic assets that are commonly encountered during the process of preparing for the Cascade 8.x upgrade. More information can be found on the preparation guide.

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 instance.
  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.
  4. Cascade CMS 8 requires a full installation.
  5. Certain versions require that specific steps be taken during the upgrade process. Be sure to read over any and all items that apply to the version to which you are upgrading:

Cascade 8.3 requires that Tomcat be upgraded to 8.0.41 which happens automatically when using the full installer.

ROOT.war upgrades should be avoided unless Tomcat has been manually upgraded to 8.0.41

Cascade CMS 8 will not run if any content or site management components still exist in the Global area. Please review the prepration guide.

Cascade CMS 8 will not run in any other version of Tomcat except Tomcat 8 at this time. For this reason, use of the full installer during upgrade is required. ROOT.war upgrades are not supported.

As of this release, Java 8u40 or later is now required to run Cascade. The OS X, Linux, and Windows packages all ship with Java 8 JREs included for easy execution. If you're using the ZIP installer or the ROOT.war, you'll need to ensure you're pointing the application to a Java 8 JRE. See this page for instructions on updating Cascade to point to a JRE.

Organizations that use the ROOT.war upgrade method and are using SQL Server or Oracle are required to upgrade their drivers using the steps below:

    SQL Server Users
  • Download jtds-1.3.1.jar from the jTDS web site
  • Replace the file tomcat/lib/jtds-1.2.5.jar with the jtds-1.3.1.jar file
    Oracle Users
  • Download ojdbc7_g.jar from the Oracle web site
  • Replace the file tomcat/lib/ojdbc14_g.jar with the ojdbc7_g.jar file

7.12.5 and later do not support SQL Server 2005. This version of Cascade will no longer start against SQL Server 2005. Please upgrade to a supported version

All other versions of SQL Server must be running above compatibility level 80. To view and/or change the current compatibility level of your database, follow the instructions in this article: SQL Server: View or Change the Compatibility Level of a Database. We recommend setting the compatibility level to 100.

Organizations that use the ROOT.war upgrade method and are upgrading to 7.12.3 or later must follow these steps:

  • If running in a load balanced environment, check to see if the file tomcat/conf/ehcache.xml exists on each node. If this file exists, please contact support [at] prior to performing the upgrade. If the file does not exist, proceed with the upgrade as usual.
  • If not running in a load balanced environment, remove the file tomcat/conf/ehcache.xml prior to performing the upgrade.

Organizations that use the ROOT.war upgrade method and are upgrading from 7.12.1 or earlier to 7.12.2 or later and use MySQL 5.6 must manually update the driver library in tomcat/lib folder from mysql-connector-java-5.1.18-bin.jar to mysql-connector-java-5.1.31-bin.jar. The file mysql-connector-java-5.1.31-bin.jar can be obtained by downloading ZIP version of Cascade CMS.

Organizations that use the ROOT.war upgrade method and are upgrading from 7.10.1 or earlier to 7.10.2 or later must remove the ehcache-core-*.jar and slf4j-api-*.jar from the ${CATALINA_BASE}/lib of Tomcat.

Organizations upgrading to 7.8.2 or above for the first time may notice a delay during the initial startup accompanied by messages like these in the log file:

2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned assets...
2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned Data Definition nodes...
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Deleted 7 orhpaned Data Definition nodes
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 11:54:57,350 INFO  [OptimizeDatabaseServiceImpl] Deleted 14 more orhpaned Data Definition nodes
2014-01-01 12:02:30,529 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 12:02:58,724 INFO  [OptimizeDatabaseServiceImpl] Deleted 0 more orhpaned Data Definition nodes
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Finished clearing 224 orphaned Data Definition node record(s)
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Fixing Structured Data with missing owner entity property
2014-01-01 12:03:29,712 INFO  [OptimizeDatabaseServiceImpl] Found 211 broken Structured Data nodes
2014-01-01 12:03:32,451 INFO  [OptimizeDatabaseServiceImpl] Fixed a total of 9 assets with broken Structured Data nodes
It is important that the Cascade CMS process not be stopped during this time. Once the orphaned Data Definition nodes have been removed, the application will start up normally.

If you are upgrading from Cascade CMS 7.4.1 or later, you should rebuild search indexes after the upgrade is complete and the application is running. To do so, navigate to System Menu -> Utilities -> Search Indexing, check the Rebuild Index? checkbox and then click Submit.