Cascade CMS 8.14

Cascade CMS 8.14 includes improvements to the look and feel of editing interfaces and reports, the ability to restrict asset choosers to a starting folder, improved Data Definition builder load times, support for Windows Server 2019 and MySQL 8 among other bug fixes and enhancements.

  View Requirements

Features/Improvements

  • To help you locate content quicker, collapsed groups in page and block editing interfaces now feature a preview of the first field in the group. We've also updated the design of various form-related components throughout the application.
  • We've introduced a number of improvements to the Browse and Upload tabs in chooser panels to help reduce confusion when choosing assets. Additionally, the chooser panel is now responsive on mobile devices.
  • To avoid obstructing the interface, LDAP sync notifications will no longer display the entire report. Additionally, we've improved performance of LDAP sync report generation.
  • We've updated the look and feel of various reports such as Publish, Folder copy, Site import, and LDAP sync.
  • You can now limit asset selection and uploads to a designated folder for chooser and WYSIWYG fields with the Restrict to folder option in your Data Definitions.
  • Reduced memory usage during Broken Link Report generation.
  • We've improved performance when editing complex Data Definitions in the builder.
  • Windows Server 2019 is now supported.
  • MySQL 8 is now supported; MySQL 5.5 is deprecated and support will be removed in the next on-premise release on or after 5/15/2020.

Fixed

  • Recipients of scheduled publish notifications will no longer see varying "Received on" dates.
  • Addressed an issue where enabling multiples for existing Data Definition groups would cause descendent fields to lose existing values.
  • Addressed errors when a workflow attempts to merge a working copy while it's still in the Publish Queue. Workflows with assets waiting to be published will be put on hold and resume once the publish completes.
  • Addressed an issue in which checkbox/radio icons are not clickable when selecting assets in tables.
  • Changing a Page's Content Type will no longer display a preview error after submitting the change.

Database Publishing and MySQL 8

Version 8.14 adds support for MySQL 8, which defaults to using SSL for connections. SSL is not currently supported for Database Transports. Due to the updated driver that ships with this version, you may experience errors when attempting to publish to a MySQL database if SSL is not disabled completely on the target database.

If after upgrading you experience database publishing failures with an SSL-related error such as:

Caused by: javax.net.ssl.SSLException: readHandshakeRecord
at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1100)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:402)
at com.mysql.jdbc.ExportControlled.transformSocketToSSLSocket(ExportControlled.java:186)
... 38 more

It is recommended to disable SSL completely on the target database by setting ssl=0 in your MySQL configuration file and restarting the database server.

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. Check the table below to see which installer type is required.

Which installer should I use?

With certain upgrade paths, a full installation of Cascade CMS is required in order to ensure that the application has the latest required libraries. See the table below for a summary of which installer you should use based on the version from which you are upgrading. For any versions that do not require a full installation, using the ROOT.war upgrade method is allowed.

Upgrade Path
Upgrading From Full Installation Required
7.x Yes
8.0.x - 8.13.x Yes