At a Glance

Released on
05/08/2015
End of Life
05/08/2016
Customer Votes Satisfied
256  

Next Release: 7.14.1
Previous Release: 7.12.5

Cascade CMS 7.14

Cascade CMS 7.14 includes a new, faster link checker, the ability for administrators to login as another user and formalized content ownership.

  View Requirements

Java 8

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.

Support for Oracle 12c

Cascade now supports running against Oracle 12c. Support for Oracle 10g has been deprecated and will be removed in a future release. This release ships with a new version of the Oracle JDBC driver so any users that typically upgrade with the WAR file will need to use the ZIP installer to ensure they're using the latest driver.

Support for SQL Server 2014

This version also supports running against SQL Server 2014 and support for SQL Server 2008 has been deprecated and will be removed in a future version. This release also includes new versions of the SQL Server JDBC driver so users that typically upgrade with the WAR file will need to use the ZIP installer to ensure they're using the latest driver.

Faster external link checking

The external link checker has been dramatically improved in this release. The process has been revamped to provide more accurate reporting and parallelized to check multiple external links at once. The broken link report and the link checker on asset submit will be expontentially faster when dealing with assets containing lots of external links.

If you were previously using a really low external link check timeout to avoid long wait times on asset submit, please set this timeout back to a reasonable setting like 2-3 seconds. This will help avoid false positives in the broken link report.

Login as user

By popular demand, the ability for administrators to login as other users has been added.

This feature allows administrators to see what other users are seeing to help troubleshoot issues or help guide the user through a process.

This was the most popular idea on our customer idea exchange at the time of release.

Content Ownership Assignment and Reporting

If your organization is anything like ours, you have a lot of content and limited resources to manage it all. It's often difficult to tell who's responsible for what. Enter formal content ownership.

In Cascade 7.14, users can now assign assets a user content owner. Addtionally, we've added a report to let you quickly see what content you're responsible for, what content others are responsible for and what content has no owner assigned. The report can also be used to bulk assign content owners to sets of assets.

Features/Improvements

  • [CSI-877] - As a Content Manager, view report of all assets in a Site without Content Owners
  • [CSI-878] - As a Content Owner, see a report of all assets that belong to me or other users
  • [CSI-879] - As a Content Manager, bulk reassign content to a new user from a report
  • [CSI-880] - As a Content Manager or Content Contributor, assign a user or myself as Content Owner of asset while viewing the asset
  • [CSI-874] - Support for Oracle 12c
  • [CSI-876] - Support for SQL Server 2014
  • [CSI-625] - Parallelize and speed up External Link Checking

Issues Resolved

  • [CSI-866] - Ability to modify system preferences via web services
  • [CSI-870] - Rules for hidden smart fields are being applied unexpectedly
  • [CSI-872] - Spectate form embed code does not render on SSL sites including Cascade Server
  • [CSI-882] - Link checker needs to un-escape HTML special characters

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. If your current version of Cascade is earlier than 7.0, then you must use the full installation instructions.
  5. If your current version of Cascade is 7.0 or later, you can perform a full installation or upgrade in place using the ROOT.war installation.
  6. 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:

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.