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 links in your website that point to pages, files, dynamic content (from Instinct™), or calendar events in Omni CMS. 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. When you insert a link on a page or event, a tag {{f:####}} is inserted into the URL source. Use the file chooser File chooser to link to Omni CMS content, rather than pasting in a full URL, to create the dependency tag.

Dependency tag created from file chooser with URL path.
Dependency tag created from file chooser with URL path.

The dependency tag stays the same, even when the page or event URL changes. Omni CMS records the tag in the page content and inserts the current URL of the linked file when the page is published.

When you rename or move a file this changes its URL. Pages and events that link to that file are republished using the last published version, with the updated URL. When you delete a file, dependency manager identifies the broken link. Find broken links as follows:

  • Run the Required Actions report to list all broken links on pages you have access to.
    • Use the Broken Events report to find broken dependency tags in Omni CMS calendar events.
  • Click the Link Check gadget or run Page Check to search broken links on a page you are editing.
  • Search the source code of a file, broken links are highlighted in red.

Dependency manager keeps track of links to files in your Omni CMS account. It doesn't manage links to external websites. Dependency manager searches the staging server and the last published version of each publish target.

The five types of dependency tags are identified by a letter inside the tag; the four types of tags do not vary in function.

  • {{d:####}} Directory
  • {{f:####}} File/page/event
  • {{a:####}} Asset
  • {{p:####}} Dynamic content
  • {{s:####}} S-tag: XML/XSL templating pulls content from a PCF file on the staging server for a triggered publish.

Activate dependency manager at the account and the site level.

Turning off dependency manager does not remove existing dependency tags from pages, though any newly linked files will show as link paths. To convert existing dependency tags back into link paths, revert the site.

Finding Dependency TagsLink to this section

Find the file path, name, and other metadata for a dependency tag as follows:

Binary ManagementLink to this section

Binary management is a subset of dependency manager that keeps track of binary files such as images and PDFs. A binary file is assigned a tag that is used when you insert an image onto a page or link to a file. When the binary 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 production server and aren't stored in the Omni CMS staging file system. This means they can't be published, recycled, etc. in the way that page files are.

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