The Publish Settings panel provides default settings pertinent to a page or pages within a site being published, which currently includes Final Check configuration options, default text for tweets and Facebook wall posts, and whether OU Tags are removed at from the source of a page upon page publish.
These publish settings can be altered from the Setup > Sites > Site Settings menu in the regular OU Campus interface, or from the SuperAdmin interface (if the institution is on its own skin of OU Campus and has access to SuperAdmin).
Final Check/Final Check Options
Final Check gives a Level 10 administrator the ability to enforce quality assurance tests to be performed on a page before publishing. These include spell check, link checking, W3C validation, and accessibility compliance. When enabled in this panel, the selected checks will run automatically when a user clicks the Publish button on a page. The page cannot be published until the enforced checks have been completed. Users are able to view the results of each check upon their completion. Users can publish the page/file even if the checks return with errors, though it is strongly encouraged to fix any errors before publishing the page.
Once Final Check is selected, the Final Check Options are shown. For Final Check and the Final Check options to be available for a site, Page Check and the corresponding Page Check Options must be enabled at the account level as only the options that were made available at the account level are available for Final Check at the site level. For more information about Page Check and the available checks, visit the following pages:
Enable Publish Button
The Enable Publish Button option allows an administrator to choose whether pages can be published (or scheduled to publish) if Final Check returns any errors. If the Always option is selected, the Publish and Schedule options will always be available, regardless of whether the page passes Final Check or not.
If the Only when conditions are met option is selected, then a page with errors discovered by Final Check will not be allowed to publish or be scheduled to publish until those errors are fixed. This will only affect users level 0 through 8. In addition, if “Set by User” is selected for “Page Check” at the Account level, a user can turn off Page Check in their User Settings and continue publishing pages.
If “Set by Administrator” is selected for “Page Check” at the Account level, selecting "Only when conditions are met" reveals the ability to select which specific checks are enforced. The options displayed correspond to which checks are run in Final Check. For example, if Link Check and W3C Validation are selected for Final Check, then only those will be available to select as conditions.
The checks that are selected are the ones that must be passed in order for the page to be published.
The checks that are selected must pass in order for the page to publish. If multiple checks are selected, then all selected checks must pass. If none are selected, the page can publish regardless of whether errors are found.
If "If Accessibility Check passes" is selected, two additional options will appear: "For Known Problems" and "For All Problems." The "For All Problems" option applies to Known, Likely, and Potential problems, and if this is enforced a page with any of these Accessibility Check errors can not be published.
Default Tweet/Wall Post
Social media integration within OU Campus allows for the configuration for the use of Twitter accounts and Facebook posts. After setup of these options, when a page is published the user may, at the time of publish, send a tweet to one or more Twitter accounts and post to one or more Facebook pages. This field allows for default text to be defined, which is populated for the user. The user can edit the text at the time of page publish. This default text can also be defined at the account level, but any value entered here at the site level will overwrite the account-level value for the current site.
Remove OU Tags
When activated, 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: