Cascade CMS 8.12

Features/Improvements

• Data Definition groups and fields can now be reordered and restructured while preserving existing content. We've added drag-and-drop re-ordering to help simplify Data Definition group and field reordering.
• Consecutive calls with structuredData, getStructuredDataNode(), or getStructuredDataNodes() will now be cached to improve rendering times.
• On-submit accessibility content checks will now show a helpful message if they appear to be taking longer than expected.
• We've improved color contrast in various places throughout the application for better visibility and accessibility.
• To improve impact on system performance, applying workflow settings to multiple folders simultaneously will now run as a background task.
• We're doing less frequent recrawl requests of Siteimprove when publishing content from Cascade CMS. Individual asset publishes will still issue automatic recheck, but larger, bulk publishes will not recrawl your entire site as frequently.

Issues Fixed

•   Timestamps for page previews in the Accessibility Report will now show the correct date and time that the preview was generated.
• The readAudits web services operation will now handle the groupname, rolename, startDate and endDate options within the auditParameters request data.
• Addressed an issue where the Query API would return inconsistent results when filtering by multiple Dynamic Metadata field or tag values.
•   Assets associated with an Accessibility Report record can now be fully purged from the recycle bin without error.
•   Addressed an issue where the length of Accessibility Report violation descriptions could exceed the database column length.
•   WCAG accessibility tests relating to CSS and overall page structure will no longer be reported in the on-submit accessibility content check.
• When reading an asset with Structured Data nodes using Web Services, a structured-data-node will now be returned for all fields. This means that if a given asset is missing a value for a field, a structured-data-node with that field's default value will be returned, instead of the field being omitted from the response.
• Addressed an issue where under certain situations cached Index Block renderings would not properly update as assets were created and removed. We also reduced average system memory consumption by Index Block caches.
• Naming Rules will now be applied properly when creating a reference to an existing asset.
• A JavaScript error will no longer appear when inserting/updating links and images within a WYSIWYG field.
• Dashboard widgets configured with a deleted Site will now display a message instructing the user to update the widget.
• Dashboard widgets will no longer become uneditable when configured with a Site to which the current user does not have explicit Site object READ/WRITE permissions.
• The Mark as Reviewed keyboard shortcut when viewing an asset has been changed from w to s to avoid conflicting with the Workflows shortcut when viewing a folder.
• When recovering a folder from the Trash, assets will be restored in order from the parent folder down to ensure cache paths are set correctly.
• Broadcast messages will once again remain visible until the user explicitly closes them.
• Read timeouts during Google Analytics Connector syncing should occur less frequently.
• Folders can once again be recycled if they contain assets which are locked or have working copies.
• Notifications for Tasks with due dates will no longer be sent after the Task has been resolved or deleted.
• Content ownership will be preserved after an asset goes through workflow or a previous version is activated.
• It is no longer possible to schedule Broadcast Messages in the past, or with an end date that is before the start date.
• Asset chooser fields will now properly handle double quotes when displaying assets by their Title or Display Name.
• Copying Data Definitions and Shared Fields to another Site will no longer result in invalid paths.
• The Data Definition Builder will no longer become unusable when editing a Data Definition which references a nonexistent Shared Field.
• WYSIWYG Editor Configurations from another Site will now load when viewing a Data Definitions or when editing Pages/Blocks.
• Fields inside a Shared Field group will no longer lose their values when swapping out a page's Data Definition or Content Type.
• Empty content areas will no longer be tested for accessibility issues.

• Structured Data Updates
• Increased Storage Requirements
• First time installation?
• Upgrade Steps
• Which installer should I use?

Structured Data Updates

Accompanying the new Data Definition drag-and-drop re-ordering functionality is a background job which updates structured data associated with pages and blocks across the system. The duration of this job depends on the number of assets that need to be processed and the complexity of the structured data. This job must complete before the drag-and-drop re-ordering functionality is available.

Progress of this job can be monitored in two ways:

• An Upgrade Structured Data task will be present in the Background Task report where you can monitor the duration and status of the job.
• There is a section at the bottom of the System Information screen, Status of structured page and block content upgrade, which provides information about the status of the job.

Increased Storage Requirements

This release introduces adjustments to Index Block caching wherein the cache can overflow to the local disk. This new overflow mechanism will require additional storage space on the application server. At this time, we are recommending an additional 5GB of storage for a total of 15GB (minimum) or 25GB (recommended) per our latest requirements.

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.