Cascade CMS 8.7.1

Features/Improvements

• The Role creation/editing interface now indicates if an ability has required dependencies before it can be enabled.
• The System Preferences screen has been re-organized into separate tabs and additional help text was added to make the form more intuitive and easier to use.
• We've made suggestions to use secure URLs subtler. Links will default to https:// for placeholders and when no protocol is specified, but users will no longer be prompted when attempting to add non-secure URLs (i.e. those beginning with http://) in the WYSIWYG.

Issues Fixed

• Custom tooltips used on various tables and UI elements no longer persist on the screen when not being hovered.
• Users without the ability to bypass content checks are now able to advance a workflow after an edit step.
• Single space character passwords for Transports or Connectors are converted to null in Oracle databases when upgrading to prevent issues with application startup.
• Orphaned working copies are no longer left behind when a create workflow is rejected or deleted before the working copy is merged.
• The Save & Preview button is no longer disabled after editing an asset in Workflow.
• The Save & Preview button is no longer disabled after re-uploading a file while editing an existing file asset.
• Folders once again expand when clicking the show contents arrow (>) in the asset tree.
• Creating/editing a User, Group, or Role will no longer redirect back to the main Users, Groups, and Roles screen.
• It is once again possible to enter content into the code editor while in fullscreen mode.
• Additional fixes to prevent asset version chains from being broken during workflows with a Version trigger.

• First time installation?
• Upgrade Steps
• Which installer should I use?

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.
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.