Adding Links when Using Dependency Manager

When the link is inserted, the Link URL is shown as a dependency tag, which starts with a “d” or an “f”. These links are wrapped in a {{**file####}}.

Example of a Dependency Tag in WYSIWYG

Links can be added to the markup for a page in many ways, but only content that is browsed to with a file chooser has the tag automatically inserted; otherwise, an additional scan can be run. The ways of adding links are:

• Using Insert/Edit Link via the WYSIWYG

• Using the Source Editor

• Using the HTML Source Editor (not automatic)

• When Binary Management is enabled with Insert/Edit Image via the WYSIWYG

• Integrated into template design

When using a file chooser to select the file, once the appropriate page is selected, a dependency tag is shown in both the modal and the code view of a page. The page path is shown below the field in the Insert/Edit Link modal.

Links can also be added without browsing (for example, in the HTML Source Editor) and then a directory scan can be performed to convert the paths to dependency tags.

Example syntax for the tags are shown 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

Broken Links

If content is deleted, a broken link is created. The system has various indications for broken links. Dependency Manager provides informative reporting for broken links and broken assets. When a dependency is lost, such as a linked-to page or a subscribed-to asset is deleted, the dependency tag, path, and file name are shown within asterisks, e.g. *** Broken f:1234 /training/about/filename.html***.

Related Links

• Dependency Manager (OU)