By continuing to use this site, you agree to the storing of first- and third-party cookies on your device to enhance site navigation; analyze site, product, and service usage; and assist in our marketing and promotional efforts. Cookie Policy

Skip to Content

Dependency Manager

Dependency manager keeps track of any links in your website that point to pages or files in OU Campus. It prevents links from breaking when a file is renamed or moved and tracks deleted content so you can easily identify and fix broken links.

Each file, directory and asset is assigned a unique dependency tag. You'll notice that when you insert a link onto a page, a tag {{f:####}} is inserted into the URL source. It is recommened to use the file chooser to pick a page to link to, rather than pasting in a full URL, so the dependency tag is used.

A URL field has the text "*** Broken Link ***" in it, and underneath a page path.
The path to the linked page is shown underneath the dependency tag.

This tag stays the same, even when the page URL changes. OU Campus records the tag in the page content and inserts the current URL of the linked file when the page is published.

When a file is renamed or moved, which changes its URL, every page that links to that file is republished using the last published version, with the updated URL. If a file is deleted, dependency manager identifies the broken link. There are several ways to find broken links:

  • The Required Actions report lists all broken links on pages you have access to.
  • The Link Check gadget checks all links on a page you are editing.
  • Running Page Check also checks all links on a page you are editing.
  • In the source code of a file, broken links are highlighted red.

Dependency manager only keeps track of links to files in your OU Campus account. It does not manage links for pages on external websites.

There are four types of dependency tags:

  • {{d:####}} Directory
  • {{f:####}} File/page
  • {{a:####}} Asset
  • {{s:####}} S-tag: used with XML/XSL templating to pull content from a PCF file on staging for a triggered publish.

All of these tags function the same way, but the letter at the front tells you what file the tag is pointing to.

Dependency manager is activated at the account and site level.

Turning off dependency manager will mean links to files in OU Campus will display as link paths rather than dependency tags. It does not remove dependency tags already inserted into pages. To convert existing dependency tags back into link paths, revert the site.

Finding Dependency TagsLink to this section

There are several different ways to find what the dependency tag for a file or asset is, in addition to viewing the tag when inserting a link or image:

  • Use the Dependency Tag Info Gadget
  • View the source code of a page that links to that file and identify the dependency tag
  • Run a custom report:
    • For "Pages," select "Products."
    • For "Directories," select "Dependency Tag."
    • For "Products," select "Dependency Tag."
    • For "Assets," select "Dependency Tag."

Binary ManagementLink to this section

Binary management is a subset of dependency manager that keeps track specifically of binary files such as images and PDFs. It functions in the same way: each file is assigned a tag, which is used when you insert an image onto a page or link to a file. Then when that file is moved or renamed, binary management updates the page with the new image or file path.

Without binary management, binary files are uploaded directly to the prodcution server and aren't stored in the OU Campus staging file system. This means they can't be published, recycled, etc. in the way that page files are.

Like dependency manager, binary management is activated at the account and site level.