Cascade CMS 8.8

Features/Improvements

• The System Dictionary is now centralized and customizable, allowing all users to see a common list of suggestions when performing content checks or when using the WYSIWYG's spell check feature.
• Smart Publishing has been updated so that it is only applicable for large files (10MB or larger) to help improve publish times.
• The "Rewrite links in file" and "Maintain absolute links when rewriting" configuration options are now hidden for file assets that are not editable text files (based on System Preferences) because these options are not applicable.
• We've added a new Feed Block "Request Timeout" System Preference which determines the amount of time to allow before the system times out when requesting a Feed Block.
• You can now specify in System Preferences whether index pages in your Siteimprove account are indexed without "index" in their URLs.
• If your site's URL in Siteimprove is different than the URL of your site in Cascade CMS, you can now specify it in Site Settings.
• Publishing a page or folder will now trigger a recrawl of those pages by Siteimprove. Publishing a Site's base folder, Destination(s), or Site itself will trigger a recrawl of the site by Siteimprove.

Issues Fixed

• Non-editable Files configured with "Re-write links in file" will no longer become corrupt during a nightly relationship-rebuilding job.
• When creating or editing a WYSIWYG Editor Configuration, buttons are toggleable again.
• Feed Block fetching has been refactored to address an issue where remote servers block requests that original from a generic Java user agent.
• Submitting structured data that contains a chosen asset that is recycled will no longer display an "illegal site in this relationship" error and prevent submission.
• Performing an operation using the REST API which accepts optional parameters (e.g. siteCopy) will no longer return a failed response.
• Un-selected replacement terms will no longer be updated when performing a Search & Replace.
• Copying assets will no longer ignore the Applicable Asset Types setting during Asset Naming Rule validation.

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