OU Campus Content Management System
Using Dependency Manager
Renaming or Moving a Directory or File
When a file or directory is either moved or renamed, a prompt that all dependent pages will be republished will appear. This will republish the page based on the current version of the page on the live Production Server with the new Dependency links. If changes have been made but not published to the live site, those changes will still not be published to the live Production Server but will be available in OU Campus and still saved on the Staging Server. This includes backed up versions.
Renaming a File or Directory:
Moving a File or Directory:
If a directory or file is deleted, a broken link will be created. The system has various indications of a broken link.
As of Version 9.15.6 the Dependency Manager broken link tags provide more informative reporting of broken links and broken assets. Previously, when a dependency was lost; for example, when a linked-to page or a subscribed-to asset was deleted, only the term BrokenLink or BrokenAsset would be displayed within a set of asterisks. This is no longer the case. Instead the dependency tag, path, and file name are shown within the asterisks.
For example, this:
*** Broken f:1234 /training/about/filename.aspx***
Please note that this change does not retroactively correct existing pages with broken dependencies. It only appears on pages with broken dependencies as of the date of the release and going forward. Existing pages with broken links or deleted assets continue to display the BrokenLink or BrokenAsset term. This is because the details, such as the path and file name are already lost, and in some cases the terms are hard-coded into the page. Once all old occurrences of the BrokenLink or BrokenAsset term are resolved or removed, no new ones should appear.
This change is currently implemented with the following:
- Page Preview
- WYSIWYG Editor
- Page-based Link Check
- Publish-based Link Check
- Site Check
- Custom Reports
If a recycle bin has been set up for the site, when recycling a file, a prompt will appear indicating how many links will be broken if the page is recycled.
After the file is recycled, the system will display which pages have broken links as a result.
When previewing a page, a broken link is displayed in the status bar (if the status bar is turned on) when the cursor hovers over the link.
OU Campus indicates that a link is broken is within the WYSIWYG Editor as well. When on the link in question, click on the link icon, and this will bring up the Insert Link dialog box. It is within this pop-up that the broken link will be displayed below the Link URL box.
It is possible to configure the URL on the page to indicate that the link is broken when in the WYSIWYG. In this case, a broken link will appear similarly to that of an Asset with hash marks. In order for this option to be available, the URL will have to be displayed as part of the page content.
- To get the Dependency tag ID, simply create a link on the page as described above.
- Access the source through the HTML button in the toolbar.
- Find the Dependency tag and link.
- Replace the text being displayed on the page with the Dependency tag.
- Save the changes.
- This will display the URL on the page.
Keep in mind that the Dependency tag will render the root relative URL if that is the selection that has been made in the site settings, and in this case, it is advised that the HTTP root be appended to before the Dependency tag in the content portion. Adding the root to the tag text should the desired effect be that the whole URL appears on the page.
To display the link on the page, configure it as seen here:
This will then create an Asset-like hash box around the dependent part of the link in the WYSIWYG view:
If the linked page is deleted, broken link Dependency tag is shown within the hash marks for easy identification:
One way to avoid broken links is to utilize the Include unpublished dependencies checkbox during the publish to publish the unpublished content. Dependency Manager reports at page publish time if there is dependent content that has not been published to the target server. This includes content that is linked or referred to by the page that is being published, as well as any unpublished assets. By selecting to include the unpublished dependencies, those unpublished files are published as well. This action prevents broken links (for example) from existing on the current page being published.
This checkbox is only shown if the Dependency Manager is being used on the site, dependency tags are used in the page being published, and one or more of those dependency tags refer to files that have not been published to the target yet.