BASICS

ADMINISTRATION

DEVELOPMENT

SUPER ADMIN

  LAST UPDATED
6/20/2014

Creating and Editing Site Settings

 Sites in OU Campus are created by Level 10 users in Setup > Sites. An account can have an unlimited number of sites.
Setup Sites 

Click on New Web Site, and complete the form. It is also possibly to clone an existing site.
New Site

This page can also be used as a guide for configuring the settings of an existing site:

Site Settings Screen

Next Page

 

Site Information

The site information section provides read-only access to the site name and the ability to view or re-generate the site's public SSH key.
OU Campus Site Information

  • Site name: This is the name given to identify the site being edited. It is also the filename of the folder that contains the sites files on the Staging Server. This cannot be changed once defined during site creation.
    -- Keep in mind that when setting up the site structure (the sites that are created within the account), if it is desired that a site be set up with a subfolder, such as "http://www.college.edu/admissions," and that there will also be a site at just the domain (e.g. "http://www.college.edu/"), it is possible that users may create folders within the domain site that essentially overwrite the contents of the other sites. Use caution when setting up this site structure.
    -- The read-only UUID is used with Live Delivery Platform.
  • Public Key: The public key field allows displays the site's SSH public key. This key can be used to create a secure SFTP connection from OU Campus to the Production Server without using a username and password combination. Pressing the "Re-Generate" button will create a new key. Warning: Be aware that if the server has already been configured to authenticate with a public key, re-generating a new key will break that existing connection and it will need to be re-configured on the server to authenticate with the new public key.

Previous PageNext Page

 

Production Server FTP/SFTP Settings

In order to update the website using OU Campus, access to the Production Server must be granted.
Production Server Settings

  • Server: The FTP address where the site is hosted. This can be used in three different modes. Either Active FTP, Passive FTP, or Secure FTP. These modes are denoted by a "p:" for Passive FTP or "s:" for Secure FTP. The default is Active FTP, which does not require a node. When setting production server settings for a SFTP connection, additional items will be displayed, Authentication Type and UMask.

Production server sftp settings

  • Username: The username for the FTP server.
  • For SFTP ONLY: Authentication Type can be Password or Public Key and will depend on how the Production Server is configured.
  • Password: The password for the FTP server.
  • For SFTP ONLY: UMask settings set the UNIX based file permissions for files within the site. Changing this setting will not change existing files, it only applies to new files. By default OmniUpdate sets all file permissions to 644, user writable. By selecting, "User + group writable" the permissions will be changed to 664, user and group writable. NOTE: The addition of group writable applies to the UNIX files system and does not have a direct relationship to the groups setup in the OU Campus system.
  • FTP Root: Usually "/," but sometimes the root of the FTP is not always the root of the server it resides on. This allows the FTP root path to be defined if this is the case (such as "/site").
  • HTTP Root: The URL root of the website; which is usually "http://www.college.edu." If a path exists in the "FTP Root," that path must follow the HTTP Root (such as "http://www.college.edu/site").
    -- If the HTTP Root changes, the entire site will need to be republished.
  • FTP Home: The highest level files can be written to for the site. Should be a subdirectory of FTP Root.
  • FTP Directory: FTP directory is optional. This is where users will be placed when logging into the site if not using the DirectEdit Link. Should be a subdirectory of FTP Root.
  • Image Directory: This is an optional path where users will be placed when inserting an image. The defined FTP root must precede the page to the image directory.
  • LDP Gallery Directory: This is required when LDP Image Galleries is being used and defines the location that the Asset files will be placed.
  • Use Local Templates: Checking this box allows a path to be defined that resides on the Staging Server on which templates can be found. Templates that have been added to the hidden OMNI-INF folders will also be inherited, allowing global templates and local templates to be utilized. OMNI-INF templates can be inherited from the Skin, Account, or Site level.
  • Remote Template Directory: This allows a path to be defined on the Production Server for site-specific templates. These templates will be used in addition to the templates found in the OMNI-INF folders. When identifying the path for these templates, remember to include the defined FTP Root.

    If "Use Local Templates" is checked, this will change to "Local Templates Directory" and the path will point to a file on the Staging Server. Do NOT include the FTP Root when defining the path when using "Local Templates Directory."
    Local Template Directory

NOTE: Image Directory, Template Directory, FTP Home, and FTP Directory require that the defined FTP Root be included in the entered path, but the FTP Root should not be included with the LDP Gallery Directory. Include only '/' and the directory name.

Previous PageNext Page

 

LDP Settings

The LDP Settings are used only when Live Delivery Platform Forms are being used. Each site on which forms will be placed must be registered with the Server Side Module (SSM).
LDP Settings

  • LDP Admin Host: The host on which the SSM resides.
  • Download Reg File: When downloaded, the registration file contains the necessary components, which must then be run on the server with the SSM.
  • Test Connectivity: After registering the file on the SSM, test the connectivity to ensure that the file has been registered properly.

Previous PageNext Page

 

Direct-Edit Button

The Direct-Edit button is the "button" on the live site on which users can click in order to access OU Campus and begin editing pages. When a user clicks on this link and logs in, he/she will be taken directly to the page in OU Campus in which he/she was viewing on the live Production Server
Direct-Edit Button

  • Button Type: Determines if a button is used and where the button is located. The "None" button type will not add a Direct-Edit button to the bottom of each page. The "Standard" button will add the defined button code, and "Transparent" will add a transparent gif.
  • Button Code: The button code can be an image or other text. The standard "Last Modified" link would be configured as follows:
    <a href="^0" target="_top">Last Modified: ^2</a>
    • ^0 as part of the href indicates that this is the Direct-Edit link and will take the user to the login page.
    • ^1 is the complete URL path. This is generally used in back-end code only.
    • ^2 will format the date that the page was last updated in month/day/year format. (e.g. 1/1/11)
    • ^3 will format the date as a three character month, day, and year. (e.g. Jan 1, 2011)

Previous PageNext Page

 

Site Preferences

Site Preferences is where certain site-specific preferences can set.
Site Preferences

  • Recycle Bin: The recycle bin field allows a directory to be input that will be used to hold files that have been deleted. Administrators can later restore files that may have been inadvertently recycled. It is important to understand that recycling is different from deleting, which cannot be restored.
  • Time Zone: Default Time Zone for the site (Default is "America/Los_Angeles" for SaaS clients). This can be changed to the time zone where the updates are actually occurring providing a more accurate time in the reporting. This is especially use for clients use SaaS. If this is left blank, it will inherit the settings from the Account settings.
  • Locale: Default Locale for the site. The default is "en_US." This setting also identifies which dictionary should be used by default. If this is left blank, it will inherit the settings from the Account settings.
  • Search On: Checking the box next to Search On enables the Quick Search functionality. When initially turning on Quick Search, it is necessary to then click "Build Index." The index can be rebuilt in the future when pages are uploaded via the FTP site.

Previous PageNext Page

 

Publish Settings

These settings set default requirements when the site or pages within the site are being published.
Screen, Setup, Site, Partial

  • Final Check: Allows administrators to force a final page check for all users. Granular control is available through the subset of checkboxes.
    • Spell Check
    • Link Check
    • Page Validate
    • Accessibility Check
  • Default Tweet/Wall Post: Sets default Tweet and wall post text for the site to be used when pages are published and Send to Twitter and/or Send to Facebook is selected. This will overwrite any text that was entered at the Account level.
  • Remove OU Tags:  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-->
    <ouc:div>
  • Available To: A group can be added to limit publishing to the production server to specific group members. The default group of Everyone indicates that everyone can access the production server unless otherwise restricted at the directory or page level. This allows for preview, and publish to the server unless restricted with an approver otherwise in the workflow. The None group indicates that no access group has been specified; this allows Level 9 and Level 10 administrators to publish, but no other users.

Previous PageNext Page

 

WYSIWYG Editor

The WYSIWYG Editor section allows behaviors of the editor to be set for the site.
Setup Site WYSIWYG Editor

  • Use HTML5 Schema: Select the checkbox to enable the HTML5 schema for the WYSIWYG Editor for the site. When selected, the WYSIWYG Editor expects to utilize HTML5-type HTML, which includes the addition of HTML5 elements and the removal of deprecated elements. XHTML is utilized when this checkbox is not selected. This also affects page validation during Page Check and Final Check. When selected, page validation is for HTML5. If non-HTML5 elements are included in the XSL, this does not change WYSIWYG editing, but can be possibly listed as an error or warning during validation with Page Check or Final Check.

    Currently with the XHTML schema, the WYSIWYG Editor does not remove HTML5 elements, such as section and article, but there is no way to automatically add these elements to the page without going into the source code or using a snippet. The XHTML schema also allows for attributes that have been identified as invalid in HTML5 but not in XHTML. When the HTML5 schema is enabled, invalid attributes are removed. Additionally, the HTML5 block-level elements, such as section and article, are now be available in the Format drop-down, making them easy to add to the content without having to use a snippet or access the source code. A new tool has also been added to the WYSIWYG Editor in both XHTML and HTML5 states that provides a visual indicator during edit of block level elements, allowing editors to see where they are within the content. Because pages that are edited using the WYSIWYG Editor must conform to the HTML5 schema once it is enabled, which will result in the invalid attributes being removed, it is possible that the entire tag may be removed. For instance, the name attribute in an anchor tag is invalid in HTML5. As such, anchor tags that contain only a name attribute without any other attributes are removed. This may, essentially remove any anchors/bookmarks within a given page. These particular tags are easily fixed by changing the name attribute to an id attribute.

    It is strongly advised to review page content prior to enabling HTML5 schema. A complete backup of the site should be created. The W3C validation tool can be used to help check the page's HTML5 validation. This requires that the templates, specifically the declaration in the XSL, be set to HTML5. Global Find/Replace can be used to search for any invalid attributes, but that may not be the best option for fixing or replacing any potential issues. For more information on invalid/obsolete attributes in HTML5, see the W3 documentation:

    http://www.w3.org/TR/html5/obsolete.html

Note: When enabling HTML5 Schema for a site, IE 8 will not create a line of text
by pressing return after an HTML5 tag (e.g., article, section) has been created.

  • Short URL: Defines format of link and image URLs.
    NOTE: If Dependency Manager is being used, links referencing other pages/directories within the account will be rendered as root relative or absolute based in the settings defined, but they cannot be rendered as page relative.
    • Absolute renders a complete URL (e.g. http://www.college.edu/folder/file.html)
    • Root_Relative renders the URL from after the "/" of the configured root.
    • Page_Relative renders the URL from after the "/" relating to the page that the user is on and on which he/she is entering the link or uploading the image.
  • Decorative Images: This allows users to insert an image without having to include a description, for instance if the image is simply a decorative image (e.g. a horizontal rule that is an image instead of the standard code). Users will be able to select "Decorative Image" when inserting a new image in order to bypass the description requirement. Keep in mind that enabling this option may affect the site's Section 508 compliance.
  • ASCII Only: ASCII encodes all special characters.
  • Disable Image Resizing: Turns off the ability to input custom size dimensions for images. This is not supported by Internet Explorer.
  • Disable Image Alignment Menu: Disallows the ability to align images (left, center, right, justify).
  • Toolbar: Defines a site wide toolbar. If toolbars are defined for a directory, page or editable region, those will override one set for the site. This will override all user settings.

Previous PageNext Page

 

File Naming

The File Naming section controls some of the rules applied naming of new files.
File Naming

  • Default Extension: Default page extension for the site. This is optional and generally left blank.
  • Filename Regex: A regular expression can be input into this field to limit the names of files. Regular expressions (regex) allow specification of whether or not letters, numbers, capitalization, etc. are permitable for page naming. A commonly used regex allows for lowercase letters, numbers, hyphens, underscores, and periods. It is formatted like this: [a-z0-9\-_.]*
  • Filename Regex Must Not Match: Check this field if the regex input above should NOT be allowed.
  • Filename Regex Description: When a regex is entered, a description is used to tell the users what they can use when naming the file if their first attempt does not match the requirements.
  • Test Regex: When a regex is entered, this allows the administrator to test the configured regex to make sure that it is preventing the correct characters.
  • Allow Uppercase Folder Names: Allows that folders can be created with uppercase letters.
    NOTE: If the TCF contains the force-lowercase="yes" attribute, this setting will be overridden. Additionally, if force-lowercase is being used in the TCF with destination="{directory/}{dirname}" in the template tag, all the force-lowercase values (yes or no) must match.

Previous PageNext Page

 

Binary File Naming

Binary file naming controls the rules that are applied to binary files such as pictures, movies, and PDFs.
Binary File Naming

  • Binary Filename Regex: A regular expression (regex) can be input into this field to limit the names of files. Regular expressions allow specification of whether or not letters, numbers, capitalization, etc. are permitable for page naming. A commonly used regex allows for lowercase letters, numbers, hyphens, underscores, and periods. It is formatted like this: [a-z0-9\-_.]*
  • Binary Filename Must Not Match: Check this field if the regular expression input above should NOT be allowed.
  • Binary Filename Regex Description: When a regex is entered, a description is used to tell the users what they can use when naming the file if their first attempt does not match the requirements.
  • Test Binary Regex: When a regex is entered, this allows the administrator to test the configured regex to make sure that it is preventing the correct characters.

 

Previous PageNext Page

 

Dependency Manager

Dependency Manager can be enabled and disabled per site. When activated in the Account settings, Dependency Manager can be turned off per site as needed.
Dependency Manager

 

Previous PageNext Page

 

Assets

The Assets section can be used to restrict the use of Assets to the current site only for the specified group. For the Restrict users to locally-created assets only drop-down, select the group that will be able to access Assets only from the current site. Learn more about Assets.

Shows the Assets section

Previous PageNext Page

 

 

WebDAV

Once WebDAV is enabled by the OmniUpdate Support Team for an account, Level 10 administrators can enable it for a site and allow specific users to access the staging server using WebDAV. For more information:

WebDAV

 

Previous PageNext Page

 

Auxiliary Sites

Allows administrators to setup access to auxiliary sites.  For more information please see this page.
Auxiliary Sites

When adding an auxiliary site, complete all fields. Keep in mind that the auxiliary site, utilized as an additional media or document option, requires that the files be displayed in a folder structure, which is generally obtained via FTP access. This is not meant to be a method by which images on a public website, such as Flickr, are retrieved for use on the site.
Auxiliary Sites Fields

 

Previous PageNext Page

 

Publish Targets

Publish Targets allows for additional production servers to be added and published to. Users can also upload, compare, and preview pages in different publish targets. Different publishing targets can be chosen in the WYSIWYG editor when inserting links, images, and other media. In addition, Dependency Manager continues to ensure that links are always up to date, even across alternative publish targets. For additional information see:

Publish Targets

Settings, Sites, Publish Targets

 

 

Previous PageNext Page

 

Site Setup Screen

Additional functionality is available after the initial creation of the site record.

Site Record

 

Previous Page

 

 


Was this page helpful?

Additional Comments:


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

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