Enabling Live Delivery Platform


Live Delivery Platform (LDP) is a set of interactive features provided as optional modules in OU Campus. LDP helps foster a dynamic website experience by allowing visitors to take advantage of popular interactive applications. With LDP, visitors have more access to the information they want, and live data on how these site visitors interact with the various applications can be gathered quickly and easily. LDP is accessed and managed through the secure OU Campus Interface. Some applications may require initial intervention by administrators and the installation of a server-side module (SSM).

Server-Side Modules

Each site in OU Campus needs to be registered with the Server-Side Module (SSM) in order to use forms on that site. However, one SSM installation can work with as many sites as necessary. Each site includes its own unique identifier. When working with a Managed Form Asset, which is one of the Live Delivery Platform modules, forms also require a unique identifier to be submitted. The SSM that is required for forms to function properly is installed as part of the implementation of LDP.

The SSM is installed on the institution's production server. It can be installed on the same server or a different server than that of the website. It is written in Python, and the installation includes a MySQL database, which is where the form data are stored. As part of the configuration of the SSM, a server-side connector script is installed on the same server as the website. The connector script’s language is determined based on the needs of the institution. The purpose of the connector script is to act as a bridge between the website where the data is being submitted and the SSM.

Note: Live Delivery Platform is an optional set of features in OU Campus. Please contact the university’s designated OmniUpdate Sales Director for details.

Activating Live Delivery Platform

To access all of the features of the Live Delivery Platform, both Assets and LDP must be turned on at the Account level by a Level 10 administrator.  Make sure the checkboxes next to Asset Manager and LDP are both checked.

Comments Setup

Live Delivery Platform's Comments feature gives website visitors an opportunity to have their voice heard on the institutional website. Users can provide their perspective on a topic, like or dislike a page or another user's comment, create comment threads, and much more. Administrators have the tools to monitor all feedback, approve and moderate comments, and have granular control over who can input a comment.

LDP Comments relies on the Disqus-hosted commenting system. Disqus provides the best available platform to ensure high-bandwidth and high-reliability.  OmniUpdate's Support will assist to set up, test, and train how to manage comments where needed on the site. Unlike other LDP modules, Comments requires no system settings in OU Campus, but does requires that the Support team do the implementation.

To configure Comments for pages, contact Support.

There are multiple options for configuring Comments within the site. The following steps can be followed to configure Comments to be included as an asset, which is the advised process:

  1. An account is to be created on Disqus for the site.
    • Additional details can be obtained in Disqus's Quickstart Guide.
    • When creating the account, a shortname will be configured. This will be used in the code that is entered on the page.
  2. Navigate to the Universal Code within the Developer Help documents on Disqus.
  3. Copy the code, and:
    • Replace "example" in "var disqus_shortname = 'example'" with the shortname that was created when the Disqus account was created.
    • Replace "unique_dynamic_id_1234" in "var disqus_identifier = 'unique_dynamic_id_1234'" with a unique identifer for the current page. See the documentation on "disqus_identifier" to see some suggested options for this identifier.
    • Replace "http://example.com/permalink-to-page.html" in "var disqus_url = 'http://example.com/permalink-to-page.html'" with the URL to the site. Specific directories or pages can be specified for tracking purposes, but in this case, a unique Asset would need to be created for each one.
    • Example Code:
      <div id="disqus_thread"></div> 
      <script type="text/javascript">


      var disqus_shortname = '[YOUR DISQUS SHORTNAME]'; // required: replace example with your forum shortname

      // The following are highly recommended additional parameters. Remove the slashes in front to use.

      var disqus_identifier = '[YOUR DISQUS UNIQUE IDENTIFIER]';
      var disqus_url = '[URL TO THE RESULTANT PAGE]'; 

      /* * * DON'T EDIT BELOW THIS LINE * * */
      (function() {
      var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
      dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js'
      (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);

      <noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>

      <a href="http://disqus.com" class="dsq-brlink">blog comments powered by <span class="logo-disqus">Disqus</span></a>
  4. Within OU Campus, create a new Code Asset.
  5. Complete the asset fields, clearly labeling the asset so it can be easily selected for use on pages.
  6. Paste the Disqus Universal Code with the modifications to the identifiers into the code box.
  7. Save and publish the asset.
  8. Insert the asset on the pages in which Comments are desired.
    • Click on the Insert Asset Icon.
    • Locate the appropriate asset.
    • Insert the asset, which will not render a preview in the WYSIWYG.

It is advisable that an Add-On be created in the account settings to the Disqus Dashboard and marked for Admin Only in order to easily moderate the Comments.


Live Delivery Platform's Forms features utilizes a server-side module (SSM) and allows users to easily create and manage forms, surveys, and polls in OU Campus. Users will create forms as Assets, which can then be inserted into the appropriate page(s). Within the form creation, a user will be able to utilize eight available fields, including single line text, multi-line text, radio buttons, checkboxes, drop-downs, multi-select, date/time picker, and instructional text. Users can also elect to have the results of form submissions emailed to one or multiple recipients. Form Assets are not available across site, which means that a form that needs to be available in multiple sites will need to be created in each site.

It is valuable to understand that OU Campus's LDP Forms module is a data collection tool. However, the product offers a lot of flexibility, and administrators can customize the server-side script to retrieve collected information in order to present an even more dynamic experience to the visitor, including presenting results of polls upon submission.

Prior to users creating Forms, a Level 10 administrator or a developer will need to complete some preparatory steps within the site setup and the files in order for the forms to render properly when used on the pages, as well as to define the action to take place upon submission.

LDP Settings

In order to activate and utilize the Forms module, a server-side module needs to be installed on the Production Server. Please contact the university's OmniUpdate Project Manager to schedule this installation. Keep in mind that the university should have already purchased LDP.

Each site will require registration on the SSM, which installs a connector. During installation of the SSM, the current sites will be registered with the SSM. Going forward, registration will be done using the registration file found in the site settings.

Files will need to be updated in order for the forms to render properly within the pages. It is advised that the file preparation take place prior to activating LDP within the account as not doing so may result in pages being published without the proper formatting. Format the appropriate XSL files with the instructions on how the forms should appear on the page, as well as the post command for sending the data to the database.

Once these steps have been completed, forms can be created utilizing the Asset Manager, and then inserted onto the appropriate pages.

Image Galleries Setup

Live Delivery Platform's Image Galleries feature allows users to easily create and manage image galleries in OU Campus. Users can upload images into the gallery, provide a title, caption, and description information, and drag and drop images to modify the order. OU Campus will automatically generate thumbnails based on user-defined settings. LDP Image Galleries are centrally managed assets that can be used on multiple pages, even with a different look and feel.

Prior to users creating Image Galleries, a Level 10 administrator or a developer will need to complete some preparatory steps within the account settings and the files in order for the galleries to render properly when used on the pages.

After activating the Asset Manager and LDP, a gallery directory should be set up for each site on which creating a gallery is desired. This is done by a Level 10 administrator in Setup > Sites.

Enter the desired directory path into the LDP Gallery Directory field.

Additionally, files will need to be updated in order for the galleries to render properly within the pages. It is advised that the file preparation take place prior to activating LDP within the account as not doing so may result in pages being published without the proper formatting.

There are two methods in which an Image Gallery Asset may be included on a page.

  1. Within Existing Editable Regions: Users can utilize the Insert Asset icon on the WYSIWYG toolbar and have a gallery inserted anywhere into the editable region.
    • This would require that the Insert Asset icon is available in the WYSIWYG toolbar.
    • For .pcf files, this requires an additional XSL declaration with the JavaScript necessary to render the desired gallery type (e.g. Lightbox) be added to the XSL files that are being utilized with the PCFs in which the gallery is desired.
    • For non-.pcf files, only the JavaScript is required.
  2. With a New Gallery Editable Region: PCFs can be updated to have a specific editable region for the gallery placement.
    • This will produce an editable region that only permits the selection of a gallery and has no other editable content.
    • This requires that the affected PCFs have a new editable region added with an editor selection of wysiwyg="galleries." This must be done on a page-by-page basis and should not be added to the template files.
    • Additionally, for .pcf files, this requires an additional XSL declaration with the JavaScript necessary to render the desired gallery type (e.g. Lightbox) be added to the XSL files that are being utilized with the PCFs in which the gallery is desired.
    • For non-.pcf files, only the JavaScript and new editable region are required.

It is important to note that if the Insert Asset icon is available in the toolbar in the other editable regions of the page, it is possible for a user to inadvertently insert a gallery in a location that may not be properly configured to handle it. However, turning off the Insert Asset icon for the toolbar within these editable regions will prevent any Assets from being included.

Lightbox Example

The following example will describe the steps for inserting a gallery into an editable region designated for a gallery only on a .pcf file. The type of gallery being created configured is a lightbox.

  1. Locate the .pcf file on which the gallery should be placed.
  2. Create a new editable region within the code, and include the following:
    <!-- com.omniupdate.div label="content" group="Everyone" button="787" break="break" --> <!-- com.omniupdate.editor wysiwyg="gallery" csspath="/_resources/ou/editor/css/onecolumn.css" width="950" --><!-- /com.omniupdate.div -->
    Feel free to change group setting and button selection. Ensure that wysiwyg="gallery" is included however.Locate the XSL that is being used as the stylesheet for the PCF on which the editable region was added.
  3. Add the necessary XSL declaration and JavaScript, which are included in the example below.
    <!DOCTYPE xsl:stylesheet SYSTEM "<a href="http://commons.omniupdate.com/dtd/standard.dtd">http://commons.omniupdate.com/dtd/standard.dtd" ><xsl:stylesheet version="2.0" xmlns:xsl="<a href="http://www.w3.org/1999/XSL/Transform">http://www.w3.org/1999/XSL/Transform"
    xmlns:ou="<a href="http://omniupdate.com/XSL/Variables">http://omniupdate.com/XSL/Variables"><xsl:output indent="yes"/>
    <xsl:param name="ou:action"/>
    <xsl:template match="/"><html>
    <head><title> Lightbox Image Gallery </title><script type="text/javascript" src="/_resources/js/jquery-1.4.4.min.js" >&nbsp;</script>
    <script type="text/javascript" src="/_resources/js/jquery.lightbox-0.5.min.js">&nbsp;</script>
    <link rel="stylesheet" type="text/css" href="/_resources/css/jquery.lightbox-0.5.css" media="screen" />     
    <script type="text/javascript">
             $(function() {
               $('#gallery a').lightBox();
    <!-- The for each statement assumes that the primary PCF has a node structure of document->content  -->
        <!-- Every gallery is encapsulated in the "gallery" root node and the node structure is as gallery->images->[independent image elements]  -->
        <xsl:when test="$ou:action='edt'">
         <xsl:copy-of select="document/content/comment()"/>
        <div id="gallery">
        <ul class="pframes"> 
        <xsl:for-each select="document/content/gallery/images/image">
          <a href="<a href="mailto:{./@url">{./@url}" title="{./title}" alt="{./description}"> 
           <img src="<a href="mailto:{./thumbnail/@url">{./thumbnail/@url}" alt="{./caption}" /> 
  4. Activate LDP and configure the Image Gallery Directory.
  5. Create an Image Gallery Asset.
  6. Publish the asset.
  7. Go to the PCF on which the editable region was placed, and click the Edit button.
  8. Select the desired gallery in the pop-up.
  9. Save and publish the page.