TTUHSC Information Technology
HomeInformation TechnologyInformation ServicesIS TrainingOU Campus CMSPublishing

OU Campus Content Management System

Training Guide

Publishing a Page

Pages and other content files within OU Campus are located on a staging server. They must be published in order to be viewable on the World Wide Web. By default, all user levels can publish content, but this can be restricted by an administrator with the use of access settings or with an approver workflow. The following items may be on the Publish menu:

Publishing a page or other content can be as simple and easy as clicking the Publish button. There are quite a few other features related to publishing that may or may not be enabled for a site.

Pages can be published inherently by all user levels. However, it is possible to restrict publishing permissions by assigning an approver. That can also be overridden with a group assignment whose members can override the approval process and publish directly. Also, users can only publish pages to which they have access.

If an approval workflow is in place for a site, a user sees a Submit for Approval button rather than a Publish button; otherwise both options are available. In this case, the user should send the page to the approver or other user if applicable, for review and publishing. If the Submit for Approval is the only option available, then the page must be sent to an approver as part of the publishing workflow.

Additionally, at the time of publish, various automated reviews of the page to check spelling, compliance to an accessibility standard, broken links and W3 standards validation can be configured by an administrator to run automatically. The Page Check/Final Check feature can be configured to be available, but not run automatically, but rather at the discretion of the user.

Dependency Manager tracks when a page includes dependencies that have not yet been published. When publishing a page an error message indicates that the page includes unpublished content that might result in broken links or missing content. The unpublished content can include assets and unpublished content; basically when any dependency tags are included on the page.

Binary Files and Publishing

Binary file types also must be published to the production server if under management with the Binary Management and Dependency Manager features. For more information about publishing binary files:

Publishing Binary Files

Assets and Publishing

A separate topic is available with more information about publishing assets and the various configuration options available:

Publishing Assets

"Unpublishing" a File: About Recycle, Delete, & Restore

Even though, files are "published" to make them live on the production server or publish target, they are not "unpublished" to have them removed from a server. Pages and files can be recycled to have them removed from the web. Inherently, only administrators and Level 8 users can recycle and delete files, pages, directories, and assets. The delete permissions for Level 8 include only the files and directories to which they have access. Administrators can assign access rights for recycling and deleting files and pages to Level 1–7 users. By default the recycle bin function is configured for a site, and this allows pages on the staging server to be recycled rather than immediately and permanently deleted. When a page is recycled rather than deleted, it can later be restored if necessary. When a page is recycled on the staging server, the published derivatives are automatically deleted from production servers. Likewise, a file can also be solely deleted from the production server or other publish target by navigating to the Production tab or tab for the publish target, and deleting it. The recycle bin functionality does not extend to these servers. Once a file is deleted from the production server or publish target, it cannot be restored. It can be re-published from the main file on the staging server with any routine form of publishing, such as publish, site publish, directory publish, or scheduled publish. Directories cannot be recycled on staging nor on a production server. Directories that are deleted are immediately and permanently deleted. There is a multiple file recycle function. All or multiple files within a directory can be selected with the checkbox and the recycle bin function for multiple files can be selected. Then the directory can be deleted. Recycling files within a directory in this method enables the ability to individual restore the files from the directory. Restoring a file is performed from the recycle bin. From the recycle bin a file can be restored or permanently deleted, or the entire recycle bin can be emptied. For more information:

Recycle & Restoring

Previous PagePrevious Topic

Next Page Next Page