Highlights

This release contains a number of bug fixes and an improvement related to workflow for end users (CSCD-6456). Now, if Workflow is available to you, Cascade will suggest that you use it by default.

Cascade 6.4.3 is a recommended upgrade for all users.

Issues Resolved

Bug

• [CSCD-2066] - A '&' character is being automatically converted to '&' in a commented area after publishing (when inside of [ system-view:external])
• [CSCD-2216] - IE renders hidden input tags as text boxes in WYSIWYG
• [CSCD-3510] - Editing assets via Web Services does not reflect change until resaved within CMS.
• [CSCD-4205] - Template converter incorrectly processes open tags in "head" tag
• [CSCD-5950] - WYSIWYG adds extra lines to output
• [CSCD-6060] - Site Migration: NPE thrown when user does not select a Target to migrate
• [CSCD-6121] - Global Publish Set publishing ignores applicable groups on Destinations
• [CSCD-6233] - Non descriptive error given when running LDAP sync when no LDAP configuration file exists
• [CSCD-6277] - XSLT formats: document() function does not pull in external XML documents
• [CSCD-6284] - Unable to update assets with more than versions limit when Max Versions value is decreased
• [CSCD-6285] - Null Pointer Exception when adding a link/selecting an asset after clicking red 'cancel' icon
• [CSCD-6287] - To be able to render a draft of a page, the page must have a well-formed xml content.
• [CSCD-6420] - Oracle and SQLServer databases missing indexes after upgrading from 5.5+ to 6.4.x
• [CSCD-6455] - Workflow cannot get expired when user has no email address, logs are filled with same error every 10 seconds
• [CSCD-6458] - "Cancel" button on Start Workflow screen loses Edit changes
• [CSCD-6498] - Invalid past version of a page cannot be deleted

Improvement

• [CSCD-6456] - Check "Start Workflow" checkbox by default if Workflows are available to user and checkbox is togglable

SQL Server and Oracle Users

CSCD-6420 addresses an issue related to database indexes where upgrading to 6.4.x was not adding a number of indexes that would have been added in previous upgrades.  Two of the database updates used to rectify this problem may or may not fail depending on the version of Cascade from which you are upgrading.  Failure of these updates will not cause the upgrade as a whole to fail.  System administrators may notice an exception or two being written to the cascade.log file.  These exceptions will be preceded by a message indicating that the exception should be ignored.  Exceptions that are not preceded by one of these messages should not be ignored.

All Users

Please follow every available release Upgrade Guide for every version you skipped during the upgrade.