Cascade CMS 8.18

Features/Improvements

• Improved accessibility of chooser fields used throughout the application among other general button UI improvements.
• Address resource contention by reading XSLT Xalan system preferences once upon startup of Cascade CMS. Note: changing the XSLT Xalan preferences now requires a restart of Cascade CMS.
• Non-fatal Destination errors encountered during publishing, such as temporary networking issues, will no longer cause the Destination to be flagged as "skipped."
• We've added a toggle to enable or disable additional keyboard shortcuts in the shortcuts menu (Shift + ?).
• We've added accessibility improvements focused around the WCAG 1.4.1, 1.4.13 and 2.4.7 guidelines to buttons, links, icons and various other components throughout the application.
• You can now schedule assets to publish or unpublish at a chosen date and time with a new Optionally Publish/Unpublish Later field on the publish/unpublish menu. While an asset is scheduled to be published, it won't be included in other publish jobs but it can still be indexed by other site content.
• We've improved page rendering speeds for implementations using large Index Blocks.
• Added support for TLS 1.3 when performing link checking and Feed Block fetching.
• Properties and methods returned by the PropertyTool's outputProperties method are now unique and sorted.
• Added support for OpenJDK 11.0.10+9.

Fixed

• Users at any permission level can now discard their own Drafts and Notifications in bulk.
• Fixed an issue where an asset could be overwritten by a Draft of a new asset with the same name and location before it's finalized.
• The LDAP configuration will no longer become invalid after renaming a System Role that is being referenced by a user policy.
• Addressed a UX issue where sometimes clicking on dropdown fields would cause the dropdown to open and close immediately instead of remaining open.
• The correct Workflow Owner will now be displayed for workflows in the My Content area.
• It is now possible to view a user that does not have group assignments (or inherited roles), instead of an error being displayed.
• Content Types with a related Publish Set will no longer result in a validation issue during a Site copy operation.
• Fixed a scenario where a workflow resuming background task can become stuck and prevent publish jobs from starting/completing.
• The "back" link when starting a workflow will now return to the asset that is being submitted into workflow.
• Fixed an error where a Publish Date couldn't be set if the site doesn't contain any Destinations checked by default.
• When moving or renaming a Manage Site area asset, the primary button now correctly says "Move" or "Rename" instead of "Unpublish".

• First time installation?
• OpenJDK 11.0.10+9 Required
• 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.

OpenJDK 11.0.10+9 Required

Cascade CMS 8.18 requires OpenJDK 11.0.10+9. The Windows and macOS installer packages are bundled with the updated JDK; however, any installer that ends in a .jar extension requires that OpenJDK 11.0.10+9 be installed on the system already before running the installer app.

If you're using a ZIP installer, you'll need to ensure you're pointing the application to OpenJDK 11.0.10+9. See this page for instructions on updating Cascade CMS to point to a Java environment.

The cascade-8.18-linux64.zip contains OpenJDK 11.0.10+9 in the /java/jdk directory which can be used to run Cascade CMS. Cascade CMS can be configured to use this package using the aforementioned instructions on updating Cascade CMS to point to a Java 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.

Server Requirements (for CMS deployment)

Supported Platforms