Broken Pages. Overview

Transcription

1 Broken Pages Overview Authority Level: All user levels. Level 9 and Level 10 administrators will see all broken pages in the report. User levels 0 through 8 will only see broken pages to which they have access. To help solve the issue of broken links due to content being deleted, administrators can use the Broken Pages report. This report shows all content that has broken links that are managed by Dependency Manager. This makes changing or fixing the links easier and can be used on a page-by-page basis. Administrators can click the linked content to preview the page or content in question. They can also hover over each item in the list view and click Edit to travel directly to the Edit or Source Editor screen of the selected page. From the Broken Pages report, users can: View a list of all pages that have broken links Filter the results by name using the Filter tool Sort the results by column Export the results to a CSV file Click the hyperlinked page path to preview the pages View the status of the page (checked out, checked in, or locked to another user) Hover over the edit menu found in the Options column to travel directly to the WYSIWYG or Source Editor for the page Unlike the Link Check on pages or Site Check, the Broken Pages report only tracks links that are managed by Dependency Manager. Links that are not dependency tags (e.g. relative and root-relative URLs, links to external content, and mailto links) will not appear in the report even if broken. If Dependency Manager is active on the site, the system will update the links should a directory or page be renamed or moved, but any links to content that has been deleted still need to be repaired manually. OU Campus Broken Pages Page 1 of 5

2 For more information about Dependency Manager and Assets, please visit their respective pages. Once the page has been edited, saved, and published to address the dependency issue, it is removed from the Broken Pages report. Broken Links and Dependency Tags When a dependency is lost (for example, a linked-to page or a subscribed-to asset is deleted) the dependency tag or asset tag, path, and file name are shown within asterisks when hovering over the status bar in a browser. For example: gallena.edu/training/about/***broken f: about/filename.html*** or *** Broken a:52 Gallena_University: Image Gallery Asset *** Broken links are reported in the following locations depending upon the XSL for the implementation: Preview/Edit/Version Compare Modes WYSIWYG Editor: Insert/Edit Link Dialog WYSIWYG Editor: HTML Source Page-based Link Check Publish-based Link Check Site Check Custom Reports Broken Pages Source Editor Additionally, depending upon the XSLs for the implemention, broken links or assets may appear differently in some of the above views. Viewing Broken Link Tags Clicking on the page hyperlink in the Broken Pages report will take users to the Preview view of the page in question. Alternatively, users can hover over the Options column and travel directly to the page's Edit view or Source Editor. Keep in mind that the below examples represent a sample implementation and may look different for each institution depending on how the XSLs are configured. Preview View For Assets, the broken link information is shown encapsulated in asterisks. Broken hyperlinks will not appear any different in the Preview view than functional hyperlinks; when clicked, the link will lead to a 404 error page. OU Campus Broken Pages Page 2 of 5

3 Edit View Assets and hyperlinks appear the same in the Edit view as they do in Preview view. Clicking an editable region's Edit link will allow users to view the content in the WYSIWYG Editor. WYSIWYG Editor Within the WYSIWYG Editor, a broken asset is shown in the editing area. It includes an a gray striped wrapper and text indicating that the asset is broken. Broken hyperlinks are not shown as broken in the WYSIWYG editing area. The URL will appear as a normal link in the WYSIWYG as well as in the Insert/Edit Link modal. To effectively determine where broken hyperlinks are located, it is recommended to look in the Source Editor, where broken dependency tags for both assets and hyperlinks will be shown clearly. OU Campus Broken Pages Page 3 of 5

4 Source Editor In the Source Editor, any broken link will have its dependency tag highlighted in red. Both assets and files will be highlighted in this manner. Deleting Broken Dependency Tags Deleting or Changing an Asset Tag from the WYSIWYG Editor 1. Navigate to the Edit mode of a page and select the appropriate editable region. 2. Find the broken asset wrapper. It will appear in gray. 3. Click anywhere on the asset wrapping, turning it green, and press the Delete key and click OK in the ensuing confirmation modal. 4. Alternatively, click the Insert/Edit Asset button in the JustEdit Toolbar and browse for a new Asset to replace the broken one. Deleting a Broken Asset or Dependency Tag from the WYSIWYG Editor Deleting a broken page dependency tag requires first identifying which links are broken on a page. Once that has been determined: 1. Position the cursor on the link in question. 2. Click the Insert/Edit Link icon on the WYSIWYG toolbar. 3. This displays the Insert/Edit Link modal. The broken link's path is displayed in grey below the Link URL box. 4. To remedy the broken dependency tag, perform one of the following actions: Delete the tag from the Link URL field Select another page by clicking the Browse icon Enter the URL of a page to which to link Deleting a Broken Asset or Dependency Tag in the Source Editor If the page is viewed in the Source Editor, the broken dependency tag or asset tag is highlighted in red. Once the page has been edited to address the dependency issue, it will be removed from the Broken Pages report. Assets that are broken appear in the Source Editor as a highlighted red {{a:###}} tag. Dependencies or pages that are broken appear in the Source Editor as a highlighted red OU Campus Broken Pages Page 4 of 5

5 {{f:###}} tag. To delete a broken link from the Source Editor: 1. Select the entire broken {{a:###}}or {{f:###}} tag and press Delete. Simply clicking anywhere on the highlighted tag will select the entire tag. 2. Click Save in the Source Code Toolbar. Once the broken link has been deleted, users are able to insert a new or correct link directly into the Source Editor by clicking Insert File Path or Insert Asset in the Source Code Toolbar. NOTE: Changes do not take effect on the live page until the page is published. Publish out the page once the broken tag is removed and the change has been saved. OU Campus Broken Pages Page 5 of 5