Page Tagging Overview

The TMPL and PCF files might include several types of tagging including XML, XHTML, echo and set variable statements, and OU Campus-style page tagging.

The OU Campus-specific tagging elements provide functionality for OU Campus. For example the Editor tag determines how regions on a page in the CMS are rendered editable. The tags wrap around certain chunks of code on a page to turn those areas into editable regions. The inclusion of certain attributes for the editor tag can define a group of users that have access, the toolbar to be used, and other options.

The OU Campus elements includes start tags and end tags, or in some cases are self closing. Other OU Campus elements can be used to define the DirectEdit code for a page, automatically include the date and time in a specific format, and customize the WYSWYIG Editor.

As of the 9.15.10 release of OU Campus, page tagging is transitioning. Previously tags were structured in the form of HTML comments and this is being phased out. The change in style provides greater XML compliance and allows the OmniUpdate tags to be represented as valid XML nodes.

For example, currently tags use the following syntax:

<!-- --><!-- / -->

While these will still work, the new form of the tag for new implementations is:


There is an intermediary form of the tag that will get used in current implementations:

<!-- ouc:xxx --> <!-- /ouc:xxx -->
<!-- ouc:xxx / -->

For example, rather than:

<!-- com.omniupdate.div label="new_content" group="Everyone" button="707" -->
<!-- /com.omniupdate.div>

The new tag is:

<ouc:div label="new_content" group="Everyone" button="707">

And the closing tag for the element:


All three styles of tagging will work and continue to be supported.

WYSIWYG Auto-updating

The tags for two elements are auto-updated in current implementations of the OU Campus system. The editor and multieditor tags are converted to the transitional style tagging. For example, when within an editable region in the WYSISYG editor, saving will generate the intermediary style tag for the editor element for that area. Viewing code within OU Campus shows the tagging style. For example:

<!-- ouc:editor / -->

The change in style to the new form of the tag allows an XSD file to be used to validate elements and attributes. The XSD file outlines the schema (attributes, elements, as well as their formats) for each OmniUpdate specific tag; for example, properties, div, editor, multiedit, etc. Now XML validators and IEDs, like <oXygen/> XML Editor have access to a list of all attributes for the tags. Additionally, the XML tags allow developers to use inline styling and JavaScript for buttons. The use of predefined GIF images is no longer required.

Publish Settings for a Site

The site setting Remove OU Tags can be enabled to remove OmniUpdate tags. From the site settings, select Remove   OU Tags. This removes all forms of the OU Campus tags from the  source code of pages when publishing. That includes the OmniUpdate comment tags, transitional tags, and ouc: node formats. For example:
<!--   com.omniupdate.div>
<!-- ouc:div-->


Publish Setting Section from Site Settings


Was this page helpful?

Additional Comments:

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

Procede to