Cascade 7.2.1 Upgrade Notes for Content Editors


Hannon Hill Corporation’s Cascade Server version 7.2.1 introduces several new features that will improve the usability of the software for both administrators and content contributors. Enhancements concerning content editors are listed below:

1.    Autosave Drafts

Drafts now will be saved automatically in the background as the user makes changes in the content. When editing in Cascade, carefully read any new messages regarding drafts.

•    You will see a message at the top of the edit window indicating that you are editing a draft of your asset.

autosave drafts 1

•    You can preview the current version of the asset or preview the draft by using the viewing options.

•    To avoid issues with editing outdated drafts (i.e., drafts of assets that have been edited since the initial draft was created), users now will be directed to current version of the asset when attempting to edit it. When the edit window for the current version is loaded, a link to a draft is presented if a draft already exists.

autosave drafts 2

•    Also, when editing a draft that is outdated, a prominent warning will be displayed.

•    Draft related confirmation dialogs are now inline pop-ups instead of full-page refreshes, which prevents issues with losing unsaved content when confirmation dialog is displayed.

•    Lastly, saving a draft does not perform form validation anymore. This allows saving partially populated forms as drafts without receiving error messages about missing required fields.

2.    Autocomplete Site Drop-Down

For those users that edit multiple sites: When switching to another site, users can now start typing the name of the desired site to be able to quickly find it in the drop-down. You can still see all sites by default when selecting the dropdown. The drop-down is also populated only on demand instead of on each page load. This speeds up page loads.

3.    Drag and Drop Move

Assets now can be dragged on the left-hand side tree and dropped to a desired folder to invoke Move/Rename operation. As the asset is dropped, the Move/Rename dialog is loaded with the Parent Folder pre-populated. While dragging an asset, a user can hover over a folder, which will then expand to display the folder’s child assets.


•    Moving assets may result in broken links or may change site navigation. 

•    If you are moving an asset that has been published, make sure you unpublish that asset to ensure there are no orphaned assets.

4.    WYSIWYG Editor Upgrade

•    In Cascade 7.2, list editing will be more consistent with the way MS Word or Google Docs work.When editing list items, you can now use Tab to indent and Shift+Tab to outdent your list.

•    Cascade will now auto-link text that looks like hyperlinks inside the text. For example, if you type out and press Enter, the text automatically turns into a hyperlink. Make sure you type in the correct URL.You may still have to go in "Insert/Edit Link” option to change the target window.

•    The "Insert/Edit Image" dialog now allows maintaining aspect ratio when modifying dimensions of images. Alternative text now can be left empty if the user checks a box to specify that a given image is a decorative image. Empty "alt" attributes on images are the accessible way to indicate that an image should be ignored by assistive technologies such as screen readers.


•    In the "Insert/Edit Media" option, you will be able to embed the snippet of HTML embed code directly inside the dialog box.

•    YouTube is the most ubiquitous video sharing platform out there and will be the default video type option now, but the editor is flexible enough to handle a wide variety of media type like HTML5 Audio, HTML5 Video and Iframe media types.

5.    Unpublish when Moving, Renaming, or Expiring Assets

Users now have the ability to unpublish content when it is moved or renamed. This helps to avoid leaving stale files on the web server after an asset has been moved. Asset expiration will now also result in an asset being automatically unpublished when enabled via Site or System preferences.


  6.    History Menu

The History link in the top menu is now expandable. When users click on the History they do not need to wait for the page load anymore. The History Menu appears instantly instead. In addition to that, assets in the menu have a sub-menu that displays the same items as context menu does. This means that users can for example navigate directly to an edit screen of an asset that they visited recently. Users still have an option to see the old screen by clicking on the "Full History" item.