By continuing to use this site, you agree to the storing of first- and third-party cookies on your device to enhance site navigation; analyze site, product, and service usage; and assist in our marketing and promotional efforts. Cookie Policy

 
Skip to Content

Sites

Create and manage sites in your OU Campus account. Sites are a division of content within OU Campus. For your site to be visible on the web, ensure you have configured a web domain and server outside of OU Campus. 

NewLink to this section

Create a new site, as follows:

  1. Navigate to Setup > Sites.
  2. Click +New.
  3. Enter the site settings.

You can also create a new site using Site > Clone, which copies the site record with or without cloned files, as appropriate.

EditLink to this section

Edit the access to a site, as follows:

  1. Navigate to Setup > Sites.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Edit.
  4. Click
  5. Edit the settings, as needed.
  6. Click Save.

PublishLink to this section

Publish a site to the live website, as follows:

  1. Navigate to Setup > Sites.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Publish.
  4. To publish all files on the site, click Publish Site.
    • Options are the same as those for publishing folders. Does not publish assets, RSS items, or other content types not in the file structure.
  5. In the "Publish" box, click Publish.
  6. To create an index of the site, as an XML file, and save it to the production server, click Publish Sitemap.xml.
    • Pages and files are included in the index if published from staging to production (as opposed to being directly uploaded to production). Exclude pages and folders from the sitemap via access settings.
    • Regenerating the sitemap overwrites the existing XML file.
  7. In the "Publish Sitemap.xml" box, click OK.

ScanLink to this section

Scan for links and tags on a site, as follows:

  1. Navigate to Setup > Sites.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Scan.
  4. To synchronize the database with the files on the staging server, click Dependency Scan.
    • If dependency manager and binary management are enabled, the scan converts valid links and binary files to dependency tags.
    • Scanning your site for the first time can take one to two hours for a large site. Subsequent scans are quicker.
    • To prevent errors or discrepancies, ensure users are not editing or moving pages within a folder while you scan it.
  5. In the "Confirm Database Scan" box, click OK.
  6. To replace dependency tags in pages and files with URLs (type determined in site settings), click Dependency Revert.
    • Revert can take one to two hours for a large site.
    • This is useful when preparing to copy a folder or when searching your site to replace URLs.
    • To prevent errors or discrepancies, ensure users are not editing or moving pages within a folder while you revert it.
    • Revert does not restore pages and files to previously saved or published states; see version revert.
  7. In the "Confirm Site Revert" box, click OK.

You can also perform dependency scan and revert on a folder-by-folder basis.

SiteLink to this section

Clone

Create a clone of the site.

Save Version

Backup the entire site to the versioning system, adding a new version of each page to the version list of each page. 

  1. Navigate to Setup > Sites.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Site > Save Version.
  4. In the "Confirm Site Commit" box, type a version description.
  5. Click OK.

Initialize

Add a DirectEdit button to all pages on the staging server. Publish the site to add the DirectEdit button to files on the production server.

  1. Navigate to Setup > Sites.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Site > Initialize.
  4. Click OK.

Purge Staging Binaries

Remove binary files (images, PDFs, etc.) from the staging server, if binary management is enabled for your site. This does not affect or delete any files on the production server.

  1. Navigate to Setup > Sites.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Site > Purge Staging Binaries.
  4. Click OK.

Export as ZIP File

Export all files on the staging server as a ZIP file to your computer. The ZIP includes previous versions of files, but not access settings, directory variables, RSS feeds, tags, reusable content, or other items. 

  1. Navigate to Setup > Sites.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Scan > Dependency Revert.
    • After the ZIP exports, click ScanDependency Scan to restore the dependency tags.
  4. Click Site > Export as ZIP File.
  5. In the "Start New Export" box, click "Download last export file" or New Export.
    • When you export site files, a link to the export (ZIP) file will be available to download for 72 hours.

Delete

Delete the site from the database and site record (the staging server entry and settings). This action doesn't delete files from the production server or any publish targets. This action deletes assets created in this site, even if they were available for use on other sites.

To partially restore the site, create a new site with the same name to restore all files from the staging server without database information, permissions, dependencies, or settings.  

  1. Navigate to Setup > Sites.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Site > Delete.
  4. In the "Delete" box, click Delete.