At a Glance

Released on
09/16/2016
End of Life
09/16/2017

Next Release: 8.0.2
Previous Release: 8.0

Cascade CMS 8.0.1

Cascade CMS 8.0.1 addresses issues found in versions 8.0 and earlier. It also adds support for SMTPS, ability to preview page renderings in full screen mode, adds ability to locate References through Locator Tool and adds connectivity improvements to SFTP transports.

  View Requirements

Improvements

  • Add support for SMTPS
  • Add "Full Screen Preview" option to pages
  • Add $_.locateReference to Locator Tool
  • Add support for SFTP key exchange algorithms

Issues Resolved

  • Fixed an issue in Workflow Builder where user and group chooser in ordered steps was not persisting selected asset
  • Fixed problems with installing Cascade 8 as Windows service
  • Fixed an issue where chooser's Recent and Browse Search fields were not searching and were resulting inconsistent site location
  • Addressed issues with text being overrun and other small issues in mobile view
  • Fixed issues with inability to verify/edit WordPress Connector
  • Improved speed of Recent tab in chooser in Firefox Browser
  • Fixed Search box in chooser in Firefox
  • Fixed Metadata Set editing"Asset failed validation" error 
  • Addressed rendering issues in Data Definition pages and blocks
  • Fixed deleting assets through multi-op Unpublish on Delete
  • Fixed links inside of Workflows Dashboard widget
  • Fixed viewing Site Role's Users and a System Role's Groups on Oracle/SQL Server
  • Allowed using '#' in strings in imported Velocity Formats
  • Fixed issues where SFTP Shuttle initialization retries were leaving a connection open to the SFTP server

Upgrade Procedure

Important notes about the upgrade

Cascade CMS 8 no longer supports Global

As of Cascade CMS 8, the Global area is no longer supported. Please read the preparation guide to help ensure that you've successfully removed all content from the Global area before attempting the upgrade.

You cannot upgrade to Cascade CMS 8 if content remains in the Global area.

Tomcat 8 Required

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.

First Time Installation?

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

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 instance 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 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 here. 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] hannonhill.com 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.