TTUHSC Information Technology
HomeInformation TechnologyInformation ServicesInformation Services TrainingOU Campus CMSEditing Content

OU Campus Content Management System

Training Guide

Using Dependency Manager

Dependency Manager manages links to pages that are moved or renamed, and automatically updates the link because a dependency tag was created with the hyperlink.

When using Dependency Manager, links are created using the file browse button. However, when the link is inserted it will appear with a dependency tag, which will start with a “d” or an “f”. These appear similarly to those of Assets. The Dependency Manager supports linking from within an asset; dependency tags can be added when creating and using assets.

Links can be inserted using the WYSIWYG Editor. Once the appropriate page is selected, a dependency tag will appear instead of the page path. Dependency links can be selected across publish targets if Multi-Target Publish is configured and in use for the account. Depending upon the configuration in the site record (Setup > Sites), Dependency Manager can generate root relative links or fully qualified URLs (Short URL is set to Absolute), and to the correct target. Dependency Manager only pertains to pages maintained within OU Campus.

Tags will appear as follows:

  • {{d:####}} -- Directory tag
  • {{f:####}} -- File/Page tag
  • {{a:####}} -- Asset tag
  • {{s:####}} -- S-tag: Used with XML/XSL templating to pull content from a PCF file on staging

Example of a Dependency Tag

Example Dependency Tag

The actual path to which the link will be pointed will appear below the Dependency tag.

The Dependency tag will appear as a tag in the source, regardless of how the source is viewed.

Example Dependency Tag

About Triggered Publish

A tag, which appears similarly to a Dependency tag but is preceded with s: instead of d: or f:, is accessible through filechoosers, which are commonly used in Page Properties. When using the tag on a page, that page will have a triggered publish when the source file is republished. The XSL can use the path generated by the tag to display content being maintained on a different page. This is similar in concept to an include file or an asset. When the original file is updated, the page containing the content is also published automatically. One example of how this is used is when using content from the main web site on a mobile page. When the content on the main web site is updated and published, the mobile page is also published with the updated content.

Learn about Binary Manager for documents, PDFs and image files.

Previous PagePrevious Page

Next Topic Next Topic