At a Glance

Released on
08/05/2014
End of Life
08/05/2015
Customer Votes Satisfied
90  

Cascade Server 7.12

This release introduces a site-wide broken link report, improvements to content drafting and filters for stale content reports among other improvements and bug-fixes.

  View Requirements

Broken Link Report

We're pleased to introduce the site-wide broken link report to help you get a handle on all of your content links both internal and external.

The link checker periodically scans your sites for broken links and gives you a comprehensive Broken Link Report on your dashboard.

The best part is that the broken link report can help you find and fix broken links before they ever go live.

Collaborate with your team to find and fix broken links and track your progress using the report's handy "mark fixed" feature.

Broken Link Report

You can also keep track of your progress using the handy Dashboard widgets:

Link Checker Summary Widget

Draft Improvements

We've made some serious improvements to drafting functionality. Drafts are simpler, subtler and more seamless. They're there when you need them but don't get in between you and your content. And, if you don't want to use them, you can safely ignore them.

A few of the improvements include:

  • Simpler and cleaner draft status indicators with clearer messaging.
  • Added information about when your draft was last updated.
  • Old drafts are automatically discarded on submit with no distracting warning messages.
  • Old drafts are automatically overwritten but with a 'Revert' option just in case

Filter Stale Content by Folders

You can now apply one ore more folder filters to the Stale Content report to help you zero in on just the content that matters to you. Folder filters are specific to each user and can by applied both stale assets:

folder filters for stale content

and assets needing review:

folder filters for content needing review

Scheme-relative links

We've improved support for inserting and link-checking scheme-relative external links. Previously the workaround was to use prepend three slashes to external links to make them scheme-relative: ///example.com/test.js.

Now, you can embed them regularly with two slashes. Links with three leading slashes will now be reported as broken but will continue to render fine in the asset's View and in the published document.

We recommend converting these links to use two leading slashes to have them properly link-checked.

Facebook Connectors

Facebook Connector functionality has been disabled indefinitely due to continued issues interacting with Facebook's API. Users can continue to use existing Facebook Connectors but they must be re-reverified every 2 hours in order to function properly.  New Facebook Connectors cannot be created.

In order to create more flexible but still automated social posts that get synchronized with the publish of content, we recommend Spectate, our powerful content marketing platform that is available to Cascade Servers users for free. Spectate's RSS Broadcasts feature can be used to automatically post content to multiple social channels by adding the content to a single RSS feed. To create social posts with more customized content, we recommend using Spectate's Social Posts feature which allows the syndication of content to multiple social networks on a schedule.

We will look to enhance our integration within the Cascade Server and Spectate product suite and bring even better social media management to Cascade Server in future releases.

New Features

  • [CSI-796] - Site-wide scheduled link checker and broken link report
  • [CSI-789] - Apply folder filters for Stale Content Dashboard Widget
  • [CSI-790] - Filter stale content and content for review reports by one or more selected folders and store filters

Improvements

  • [CSI-747] - Check links in [system-asset] tags on asset submit
  • [CSI-748] - Check links in more tags on asset submit
  • [CSI-749] - Check external links during publishing
  • [CSI-750] - Do not check the same external link more than once
  • [CSI-765] - Make Draft messaging and controls more unobtrusive
  • [CSI-791] - Change Submit button to "Send to Workflow" when workflow is enabled
  • [CSI-792] - Disable certain tabs for drafts only when revisiting the draft
  • [CSI-793] - Automatically overwrite old draft but allow reverting it

Issues Resolved

  • [CSI-96] - Edit form should be reloaded when start edit time is less than asset last updated time
  • [CSI-404] - Don't rewrite scheme-relative URLs
  • [CSI-590] - Scheme-relative links in Template are reported as broken during publish
  • [CSI-602] - Adding/removing repeating groups/fields too quickly on a Page/Block moves field values to fields above
  • [CSI-721] - Web services: Role abilities "databaseExportTool" and "sendStaleAssetNotifications" do not read or persist properly
  • [CSI-730] - Facebook Connector must be re-verified every 2 hours
  • [CSI-752] - Entity relationships are created for drafts that contain [system-asset] links
  • [CSI-753] - Entity relationships are not created for cross-site links in [system-asset] tags
  • [CSI-754] - Links to anchors on other Pages don't appear in Relationships
  • [CSI-788] - Valid links reported as broken due to missing User-Agent in HEAD or GET requests
  • [CSI-794] - [system-asset:configuration] links are not checked for cross-site rules
  • [CSI-795] - Broken cross-site links not included in publish report

First Time Installation?

Be sure to import our default database schema prior to installing Cascade Server for the first time. Then follow our standard installation instructions.

Upgrade Steps

  1. Shut down your currently running Cascade Server instance.
  2. Before you upgrade, we strongly recommend that you back-up your production database. as well as set up a test instance 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. If your current version of Cascade is earlier than 7.0, then you must use the full installation instructions.
  5. If your current version of Cascade is 7.0 or later, you can perform a full installation or upgrade in place using the ROOT.war installation.

Important:

Organizations that use the ROOT.war upgrade method and are upgrading from 7.10.1 or earlier to 7.10.2 or later must remove the ehcache-core-*.jar and slf4j-api-*.jar from the ${CATALINA_BASE}/lib of Tomcat.

Important:

Organizations upgrading to 7.8.2 or above for the first time may notice a delay during the initial startup accompanied by messages like these in the log file:

2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned assets...
2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned Data Definition nodes...
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Deleted 7 orhpaned Data Definition nodes
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 11:54:57,350 INFO  [OptimizeDatabaseServiceImpl] Deleted 14 more orhpaned Data Definition nodes
2014-01-01 12:02:30,529 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 12:02:58,724 INFO  [OptimizeDatabaseServiceImpl] Deleted 0 more orhpaned Data Definition nodes
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Finished clearing 224 orphaned Data Definition node record(s)
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Fixing Structured Data with missing owner entity property
2014-01-01 12:03:29,712 INFO  [OptimizeDatabaseServiceImpl] Found 211 broken Structured Data nodes
2014-01-01 12:03:32,451 INFO  [OptimizeDatabaseServiceImpl] Fixed a total of 9 assets with broken Structured Data nodes
It is important that the Cascade Server process not be stopped during this time. Once the orphaned Data Definition nodes have been removed, the application will start up normally.

Important:

If you are upgrading from Cascade Server 7.4.1 or later, you should rebuild search indexes after the upgrade is complete and the application is running. To do so, navigate to System Menu -> Utilities -> Search Indexing, check the Rebuild Index? checkbox and then click Submit.

Warnings:

You must upgrade to at least Cascade Server 5.5 before upgrading to Cascade 6 or Cascade 7.

Contact Hannon Hill Support (support@hannonhill.com) if deploying Cascade Server for the first time in a load-balanced environment as this will require a special license.