Because OU Campus is a decoupled system, pages, files, and other types of OU Campus content must be published for changes to appear on your live website.
By default, all users can publish content, but this can be restricted by administrators, requiring users to submit pages for approval instead.
To publish a page or other file, either:
- While viewing the file, click Publish.
- Navigate to Content > Pages.
- Click More Actions .
- Click Publish > Publish.
To publish multiple files simultaneously, from Pages select the file checkbox and click Publish in the list header. Publishing a folder publishes all files inside it. You can't publish files that are checked out to another user or part of a workflow.
If you don't have permission to publish pages, you see the option to Submit.
Publish OptionsLink to this section
Clicking Publish opens the "Publish" box, containing the following tabs and options:
Final check reviews the rendered version of your page or file (i.e., what your page looks like on your live website) before publishing it. Final check reviews reusable content on the page and performs the same checks as page check.
- File Type: Select which item in the dropdown to review.
- Some pages create more than one item when published, i.e., both a web page (HTML) and a PDF file.
- Run All: Click to run all available checks (Spelling, Links, W3C Valid, and Accessibility).
- Spell Check Language: Select a language for the spell check.
- Spelling: Click to check the spelling of the page.
- Links: Click to check for broken links on the page.
- W3C Valid: Click to check for valid HTML and XHTML code on the page.
- Accessibility: Click to check that the page conforms to accessibility standards.
- Publish Target: Select a location in the dropdown.
- If your website has been set up with more than one publish target, you can publish a page or file to a different location than the live website.
- Publish Options: Select the checkbox to include unpublished dependencies.
- If your website has been set up with dependency manager, you can publish pages or images linked to the current page that have not yet been published.
- Version Description: Enter a description of changes for the version history.
Level 10 users can enforce final check at site settings, so that a page has to pass it before it can be published.
Schedule a page to publish instead of publishing it immediately.
Send a tweet or post to a linked Twitter or Facebook account when a page is published. Select the account and/or page to post to, write the tweet or post, and check the "Add URL" box to add a shortened version of the page URL to your post.
This tab doesn't appear if Twitter and Facebook accounts have not been linked to your OU Campus account.
If you are publishing multiple files, the "Publish" box does not provide final check, scheduling, or social media options. Apply the following publish options to the batch of selected files, as appropriate:
- Include Checked-Out Files: Publish files in the batch that are checked out by any user. The files stay checked out after publishing.
- Include Files Scheduled for Publish: Publish files in the batch that are scheduled to be published. The files stay scheduled to publish after publishing.
- Include Files in Workflow: Publish files in the batch that are part of a workflow . The files remain in the workflow after publishing.
- Publish Changed Files Only: Publish files that have been modified since their last published version. This includes checked-out files and newly-created files that have never been published.
- Use Last Published Version: Don't publish files with changes in progress or unpublished pages. This can be useful if a design change or some other modification requires a republish of the folder, but you don't want to update the content.
- Exclude Binary Files: Don't publish binary files, such as images and PDFs.
- Include Unpublished Dependencies: Publish linked files that have not yet been published. This only works if dependency manager is turned on.
- Publish Target: Publish files to a different location than the live website. If your website has been set up with more than one publish target.
- Version Description: Add a description to the version history of every published file in the folder.
Stop a PublishLink to this section
There is no way to stop, or undo, a publish once it starts. If you publish content in error, there are two possible solutions:
- Revert to the last published version of the file. This returns the file to it's previous state. Publish the reverted page to your live website.
- Remove the page from the website by deleting it from the production server. Once a page is deleted from the production server, the only way to restore it is republishing it. Only users levels 9 and 10 can delete files from the production server.
A scheduled publish can be removed before it happens.