Cascade CMS 8.9

Features/Improvements

• Publishing related content is now easier with the ability to add Relationships to an asset and associate Publish Sets with Content Types; both of which can be included when publishing the content you're working on.
• Content tagging now allows you to assign reusable site and systemwide Tags to assets. Tags are searchable within Cascade CMS and can be leveraged to create related content indexes via Query API.
• We've updated the look and feel of the Plugins tab when editing an Asset Factory.
• We've improved loading speeds for the Notifications table, Dashboard widget, and notification count in the user menu.
• Searching within the asset chooser's panel will now display more than just 20 results.
• We've updated the look and feel of the Site switcher, Add Content menu and type-ahead search in the application header.
• Dropdown/multi-select fields on the advanced search and asset naming rules preferences are now alphabetized.

Issues Fixed

• Illegal characters are no longer permitted when editing a Site name, and attempting to use them during Site creation will display a more helpful error message.
• Using the Fullscreen button in the WYSIWYG in conjunction with the Show All Editor Features button or when editing an XHTML/Data Definition block no longer causes the interface to render incorrectly.
• The getLinkingAssets Cascade API method will now return assets linked through Data Definition chooser fields.
• The suggestion provided when an asset name does not follow the Site's asset naming rules will now properly handle spaces and invalid characters.
• The Data Definition builder will now show smart field rule help text for WYSIWYG fields.
• Unpublish options are once again available when moving or renaming a Folder.
• The ability to Run Transport and Destination diagnostic tests now requires the Access the Manage Site Area ability, instead of the Access Administration Area ability.
• Updating a reviewable entity's reviewEvery property via Web Services is now validated to ensure the provided value is 0, 30, 90, 180, or 365.
• Addressed an issue where the Role assignments for a Site may not be persisted properly under certain circumstances such as mixed case Role names in case-sensitive databases or when non-administrative users update a Site's settings.
• It is once again possible to link to a Page's rendering by supplying a confId parameter to the "internal" rendering URL. However, the recommended method of linking to a Page's rendering would be to use the ?raw parameter.
• Addressed a JavaScript error thrown when using the typeahead search in IE11.
• Addressed an issue where attempting to move a folder would fail if its system name didn't comply with the Site's asset naming rules.
• The Data Definition Field(s) to System Name Asset Factory plugins will once again properly set the name of pages on creation using the configured Data Definition field identifier(s).
• WYSIWYG Editor Configurations are once again editable once the max number of asset versions has been reached.
• Improved error handling for cases where WCAG 2.0 accessibility checks take longer than normal or if the Tenon.io service is temporarily unavailable.
• Deletion of a Site will no longer be prevented if previous versions of Manage Site assets that have been moved out of the Site still reference it.
• When viewing a Metadata Set in the Manage Site area, Custom Metadata fields will now be listed in the order they're defined.
• Addressed an issue where users were sometimes forwarded to an instance's /favicon.ico URL after logging in.
• Inserting external links in the WYSIWYG in IE11 and Edge works again.
• Inserting internal images in the WYSIWYG will once again automatically populate the descriptive text with the File's Title, Display Name, or system name.
• When editing an asset from the context menu, the publish link pop-up will now publish the edited asset as opposed to the asset in the preview window.
• WYSIWYG Editor Configurations can once again be configured with Custom Styles without requiring a CSS File to be chosen.
• Addressed an issue where updating the dimensions while inserting/updating an image within the WYSIWYG (with Constrain proportions enabled) will use incorrect values.
• Addressed an issue where correcting items on multiple pages during a content check such as Spell Check would only update items on the last page viewed.
• WYSIWYG Editor Configurations with trailing commas in the Custom Styles field no longer cause the Insert/Edit Link and Insert/Edit Image buttons in the WYSIWYG to stop working.
• Addressed an issue in which searching/re-indexing would intermittently stop working on Windows installations.
• Images inserted within the WSYIWYG editor will no longer have an invalid caption attribute added to their markup.
• Google Analytics Connectors will no longer fail to sync when processing a URL containing 4-byte characters.
• Addressed an issue in which an error, "Request header too large," would be shown when viewing Feed Blocks or link checks are performed (i.e. during asset submission or Broken Link Report generation).
• Search results will no longer contain past versions of assets.
• A server-side error message will no longer appear when updating the System Preferences with an invalid System URL.
• Improved submission times for Content Types that have many page regions and structured data fields.

• Notifications performance improvements
• First time installation?
• Upgrade Steps
• Which installer should I use?

Notifications performance improvements

For databases with a very large number of notifications, an extended startup time may occur while the database update associated with the notifications performance improvements in this release is being applied.

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.