BASICS

ADMINISTRATION

DEVELOPMENT

SUPER ADMIN

  LAST UPDATED
4/8/2014

Required Actions

Required Actions is available to Level 9 and 10 administrators. It contains the broken dependencies, which are specific to the site and match those found on the Broken Pages area of the Dashboard and out-of-sync pages. 

Navigate to Required Actions by going to Admin > Required Actions:
Required Actions

Fix Broken Pages

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. Dependency Manager has no effect on Assets. 

To help solve the issue of a directory, page, or Asset being deleted, administrators can use the Fix Broken Pages section, which is found in Admin > Required Actions. The panel has two tabs. The first tab is the Fix Broken Pages tab, which contains a list of the 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. In this area, it will produce a list of pages that have broken links due to external content being removed. The administrator can then edit the content, view and edit the source, or preview the page. Once the page has been edited to address the dependency issue, it will be removed from the list in this area.

Required Actions

 

Next Page

 

Dependencies and Assets

Assets can cause dependency issues when 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 is to delete the Asset from the WYSIWYG Editor. To do this, navigate to the page, and choose to edit the page in the WYSIWYG. Once there, find the broken Asset wrapper that looks like this:

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 is created. The system has various indications of a broken link. The pages with broken links will appear in the Broken Pages listing.

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.

*** Broken a:21230 documentation: Dependency Manager Broken Link Tags ***

 

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

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. The broken link with the path and file name is 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, dependency tag, path and file name are displayed within the asterisks and with the Asset-like hash box:

Hash Box with Broken Link

 

Previous PageNext Page

 

Publish Out of Sync Pages

Pages will appear in Publish Out of Sync Pages when an error occurs during a publish. An example of the type of error that would result in pages appear in this tab is a loss of internet connectivity during the publish process. It is anticipated that pages should rarely be marked as out of sync. Simply click on the Publish Out of Sync Pages button and all publishing updates will be completed. The Publish Out of Sync Pages is cross-site, which means that regardless of the site in which the administrator is working, the Publish Out of Sync Pages will display pages that are out-of-sync on any site within the account.

Out of Sync Pages

 

Previous Page

 


Was this page helpful?

Additional Comments:


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

Procede to http://support.omniupdate.com/