BASICS

ADMINISTRATION

DEVELOPMENT

SUPER ADMIN

  LAST UPDATED
4/8/2014

Broken Pages

Broken Pages shows a list of pages that are marked as broken due to an Asset or dependent page being deleted.

A page gains dependency when it uses an external source for content, such as using an Asset or linking to another page. It then “depends” on the external content to exist. Therefore, it becomes an issue when the directory, page, or Asset is deleted. If utilizing Dependency Manager on the site, the system will update the links should a directory or page be renamed or moved, but those that are deleted will still need to be repaired manually.

Broken Pages

To help solve the issue of a directory, page, or Asset being deleted, Broken Pages shows a list of pages that are marked as broken due to an Asset or dependent page being deleted. The list of broken pages is specific to the site in which the administrator is currently logged in. The list only shows pages for which a user has access to. In this area, it will produce a list of pages that have broken links due to external content being removed. The content can then be edited, or the source code viewed and edited, or the page previewed. Once the page has been edited to address the dependency issue, it will be removed from the list in this area.

Broken Pages

 

Next Page

Dependencies and Assets

Assets can cause dependency issues when they're deleted. When an Asset is deleted, pages must be updated manually to remove the Asset. To delete an Asset from the Source Editor, simply delete the {{a:###}} tag within the broken page.

An alternative method would be to delete the Asset from the WYSIWYG Editor. To do this, navigate to the page, and choose to edit the page in the WYSIWYG. The broken asset will be shown:

Broken Asset Dependency Manager Tag

Click anywhere on the Asset wrapping and press the Delete key. Confirm to delete.

Keep in mind that this will delete the content that was being produced by the Asset, and it may need to be replaced in order to complete the page.

Broken Links and Dependency Manager

If a directory or file is deleted and Dependency Manager has been turned on, a broken link will be created. The system has various indications of a broken link. The pages with broken links display in the CMS on the Dashboard > Broken Pages listing as well as the Admin > Required Actions screen.

For users with Source Editor access, when in the Source Editor, if broken links exist on the page, they will be displayed at the top of the page.

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:

***BrokenLink***

becomes:

*** Broken f:1234 /training/about/filename.html***

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

Source Editor reports broken links both above the Editor window and in-context. The Dependency tag is highlighted red as an indicator.


Source Editor View

This will make changing or fixing the links easier, but it is limited to being on a page-by-page basis.

When previewing a page, a broken link will be displayed in the status bar (if the status bar is turned on) when the cursor hovers over the link.
Dependency Manager Broken Link Tag

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.
Dependency Manager Broken Link in Link 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.

  1. To get the Dependency tag ID, simply create a link on the page as described above.
  2. Access the source, either through the HTML button in the toolbar, or via the Source Editor.
  3. Find the Dependency tag and link.
  4. Replace the text being displayed on the page with the Dependency tag.
  5. Save the changes.
  6. This will display the URL on the page.

    Keep in mind that the Dependency tag will render the root relative URL if pointing to a page within the same site. Add 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:
Display Dependent Link

This will then create an Asset-like hash box around the dependent part of the link in the WYSIWYG view:
Result of Displaying Dependent Links

If the linked page is deleted, the Dependency Manager broken link tag provides the identity of the broken link:

Hash Box with Broken Link

  

Previous Page


Was this page helpful?

Additional Comments:


(Include your email address if you would like a reply)