Overview

The goal of Cascade 6.2 is to further enhance the Sites feature introduced in Cascade 6.0 by adding:

• Cross-site linking
• Template sharing across sites

We've also added:

• Script Format improvements
• Site Dashboard improvements
• Folder copy improvements

---

Cross-Site Linking

Cascade 6.2 allows end-users to create links in content between assets on different Sites. These links always worked when clicked inside Cascade, but only with Sites and Cascade 6.2 do the links in the published content. Read more about linking on the Linking pages.

Template Sharing Across Sites

In combination with the changes made for cross-site linking, it is now possible to share a single template across multiple Sites for easy template management. When selecting a template for use in a Page Configuration, there is a Site dropdown that allows you to switch between Sites to which you have access. Read more about Template sharing on the Templates pages.

Additional Velocity Tools

Cascade 5.7 introduced Script Formats in that used the Velocity engine to transform XML in regions as alternative to XSLT Formats. In Cascade 6.2, we've added a few utilities to the Velocity context to make Script Formats an even more viable alternative to XSLT Formats. Read more about the additional utilities on the Script Formats pages.

Site Dashboard Improvements

Cascade 6.2 added the ability to set Content Wizards and Starting Pages on the Dashboard for each Site. You can access associations these by navigating to the Site Management area and editing a Site. At the Site level, you can set an Asset Factory Container and a Starting Page using the appropriate choosers. Read more about the dashboard improvements on the Sites pages.

Folder Copy Improvements

When copying folders, links to assets within the folder are now updated to point to the copied assets. This is great for users that create boilerplate folders and duplicate them multiple times. Read more about the folder copy enhancements on folder pages.

Bug Fixes

In addition to the features above, 6.2 includes a number of bug-fixes listed below.

Issues Resolved

Bug

• [CSCD-4080] - Contributors unable to delete assets to which they have write access even if no workflow is required
• [CSCD-4388] - Blank screen when trying to publish after sorting a folder view by Last Modified, Last Modified By
• [CSCD-4572] - Audit deletion confirmation screen lists asset id's instead of asset name
• [CSCD-4587] - Folders will not inherit workflows from parent if parent option is set to 'Do not inherit'
• [CSCD-4807] - Increase length of CSS Classes field
• [CSCD-4897] - Submitting a template with multiple default regions does not forward you back to the edit screen
• [CSCD-4915] - Can't easily remove any configuration files from the system
• [CSCD-5309] - Web Services: Creating a file using 'data' property leads to 0 byte file asset
• [CSCD-5377] - Web Services: Cannot reference assets by path that live outside the Site of the asset being created/edited
• [CSCD-5388] - sitedestinationcontainer is not one of the entityTypeString in WSDL
• [CSCD-5522] - Links to other page configurations missing configuration extensions in Sites on publish
• [CSCD-5525] - Site Migration Fails with a Null Pointer Exception when it reaches destinations with no transport set
• [CSCD-5613] - Search results in chooser need site name prepended when a result comes from a different site
• [CSCD-5614] - Cross-site Linking: Use context of regions and templates when rendering links in pages
• [CSCD-5619] - Role has ability to create sites regardless of ability if granted Site Management access
• [CSCD-5626] - XSS vulnerability in search action when query contains non-terminated phrases
• [CSCD-5627] - CSRF vulnerability in search action when search query contains non-terminated phrases
• [CSCD-5631] - Align dropdown arrow for quick links with top of line rather than bottom
• [CSCD-5637] - Wrong site id error when rendering CSS file with links to images on other sites
• [CSCD-5694] - TinyMCE won't wrap text in <p> automatically until after a carriage return
• [CSCD-5699] - Using [ system-asset] tags in Sites do not link to correct page configurations
• [CSCD-5703] - Web Services: Unable to read a site by name
• [CSCD-5704] - Publish-working-copy trigger not working properly
• [CSCD-5716] - Unable to edit scheduled Site publishes from publish queue
• [CSCD-5729] - User can select a default site (user preferences) that he/she cannot switch into
• [CSCD-5734] - System messages containing markup are being escaped

Improvement

• [CSCD-4817] - Improve Content Type Index Block performance by using database to sort pages and limit the results
• [CSCD-5035] - Link to a different configuration on a different page while in sites
• [CSCD-5606] - Make the Default Asset Factory container created during Site creation also the selected container for display in Dashboard
• [CSCD-5608] - Installer improvements when upgrading
• [CSCD-5615] - Make folder copy update the selected folder in index blocks contained within folder
• [CSCD-5623] - Add a "Give us Feedback" link to the Success community idea exchange
• [CSCD-5625] - Improve SFTP logging to include "result state" in logging upon successful SFTP authentication phase
• [CSCD-5689] - Remove .sh installer and recommend using .zip or ROOT.war for command line users
• [CSCD-5701] - SerializerTool (VTL) Add new parameter for removal of root-node

New Feature

• [CSCD-4910] - Include data access tools in Velocity context for content manipulation
• [CSCD-5127] - Template sharing across Sites
• [CSCD-5293] - Cross-site linking for assets with managed links
• [CSCD-5376] - Allow folder copy to preserve links relatively
• [CSCD-5690] - Integrate Node Sort Tool and String Tool into Velocity Context

All Users: If you are running Cascade version 5.2.4 or earlier, you must upgrade to version 5.5 or a higher before upgrading to 6.2!  Cascade Server 5.7.3.1 is available for download here. When upgrading to 5.5 or higher, you must allow Cascade to boot until you're able to access the login screen. At that point, you should see the following in the log:

INFO: Server startup in 59457 ms

After the login screen is accessible, you can stop the server and install 6.2.

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

Cross-Site Links

<a href="site://sitename/path/to/asset">Home</a>

Links of this type will resolve to a specific asset with path: /path/to/asset on a specific Site called "sitename." In order for these links to resolve correctly upon publish, the linked-to asset must exist on the Site being referenced and must also be published.

NOTE: This functionality is only available in Sites and will not work in the Global area.  Additionally, cross-site links can not link back to the Global area.

For more information on linking, click here.

New System (Pseudo) Tag

[ system-asset:local]/path/to/asset[ /system-asset:local]

This tag is used to link to an asset by path relative to the Site in which the tag is being used. A good example of this would be if you had a single Template being shared by two different Sites, each with their own CSS file. In each site there would be an asset residing at the path specified inside the [system-asset:local]. The tag will allow the system to know that each Template should link to their respective CSS file.

NOTE: Links of this type are not tracked within the system due to the fact that they are designed to be relative to the site where the tag is being used.  In the scenario mentioned above, if the CSS file were moved to a different location in the site, the links to the file would not be automatically rewritten.

For more information on linking, click here.

Links to Different Outputs of a Specific Asset

[ system-asset:configuration=configuration_name]

This tag is used for supplying a link to a different output of the specified asset. By supplying the page path and the name of the desired Configuration, the CMS will provide a link to the appropriate output. This syntax is preferred over the following, deprecated [ system-asset:page:target=TargetName].

<!-- DEPRECATED --> [ system-asset:page:target=target]/path[ /system-asset:page]

This syntax and the use of Targets is deprecated in favor of the method above.

Copy Folder Function

Folders can be copied and moved as desired within the system for easy duplication and content archival. With versions of Cascade Server 6.2 and newer, when copying a Folder, the system will now rewrite/resolve links within that folder to reflect the new location.

Consider the following scenario:

• FolderA contains PageA and PageB
• PageB contains links to PageA and PageC
• PageC is not contained inside FolderA

Prior to Cascade Server 6.2

Copying FolderA will produce:

• FolderA-copy containing PageA-copy and PageB-copy
• PageB-copy linking to PageA (original) and PageC

Beginning with Cascade Server 6.2

Copying FolderA will produce:

• FolderA-copy containing PageA-copy and PageB-copy
• PageB-copy linking to PageA-copy and PageC

In general, links contained within assets in the original folder (or any sub-folders) that point to other assets also contained within the original folder will be updated during the copy process; specifically, they are updated to point to the new copies. 

This behavior is true for all links being updated, whether they are XML links (i.e. "href=" or "src=") or "system-asset" links. This link rewriting process applies to Formats, Pages, Files, Templates, and Blocks linked to within the Folder being copied. In addition, links in text files that have the "Rewrite links in file" checkbox checked will have links resolved.

This folder-copy mechanism works either by using the standard "copy" command at the folder level, and also, by copying a folder via web services.

NOTE: Folder copying is intended to resolve links contained by the Pages and other assets of the copied Folder, and not those Pages' related Configurations. For example, when copying a Folder, links in the child Pages will get updated, but chosen assets in Page Configuration Regions will not be updated.