Cascade CMS 8.20

Features/Improvements

• Purging file assets from the recycle bin now uses less memory.
• The WYSIWYG editor will now correct o:p tags introduced when pasting content from Microsoft Office applications to paragraph elements to prevent XML validation issues on submit.
• Improved load time of large (un)publish report notifications by displaying an overall summary and a link to view the full report in a new browser window/tab.
• New Velocity Tool methods for determining "type" of an object or if an object is numeric, shuffle collections using ListTool.shuffle, and convert a HashMap to a JSON string using a new SerializerTool.toJson method.
• Publish jobs that are in progress when the application is shut down will now be re-queued so they can be restarted on application startup.
• Background jobs such as report generation and sync operations that are in progress when the application is shut down will now be restarted on application startup.

Fixed

• Create Drafts for folders with previously-recycled children will no longer prevent the Draft from being deleted when a Draft's parent folder is in the recycle bin and being purged.
• Using listSubscribers batch operation will now return a proper listSubscribersResult.
• Times throughout the system now display based on the user's timezone. Fields that display the server's time zone, such as the Broken Link Report schedule, now note which time zone is being displayed. In addition, dates returned by the REST API will now be returned in UTC.
• Fixed an issue with the Export CSV feature for the Stale Content Report when filtering for a site.
• When viewing an asset that is scheduled to (un)publish later, the Destination(s) that were selected to (un)publish to will now be shown instead of the Destination(s) checked by default.
• Contents of Folders created through an Asset Factory will not be created until the draft of that Folder is submitted.
• Timestamps in rendering error screens, such as when viewing an invalid Feed Block, will now show the correct current date and time.

• Log4j Upgrade
• Internet Explorer 11 End of Life
• First time installation?
• Upgrade Steps

Log4j Upgrade

Custom Plugins

Custom Asset Factory plugins, Custom Authentication, Publish Triggers, etc. referencing Log4j must be updated and recompiled or they will no longer work.

Specifically, any reference to org.apache.log4j and subsequent classes must be updated to use the SLF4j (org.slf4j) logging framework that is bundled with the application. For example, if your plugin contains the following code:

import org.apache.log4j.Logger;
...
private static final Logger LOG = getLogger(CreateResizedImagesPlugin.class);

or

import org.apache.log4j.Logger;
...
private static Logger logger = Logger.getLogger(CascadeShibAuth.class);

You must change the code to:

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
...
private static Logger logger = LoggerFactory.getLogger(CascadeShibAuth.class);

Additional examples can be found in:

• Asset Factory Plugins Github project
• Custom Authentication Github project

Custom Logging Configuration

If customizations were made to the application's logging configuration at tomcat/webapps/ROOT/WEB-INF/classes/log4j.properties, those customizations must be migrated to a newer Log4j2 format   and configuration file located at tomcat/webapps/ROOT/WEB-INF/classes/log4j2.properties

Internet Explorer 11 End of Life

Internet Explorer 11 will no longer be officially supported once it reaches its end of life on 6/15/2022.

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.

Server Requirements (for CMS deployment)

Supported Platforms