Uploading a File

Images and other binary files (like PDFs, videos, Flash files, Podcasts, etc.) are uploaded to the production server by default. These files never exist on the staging server. Web pages and other editable text files (like HTML, XHTML, PHP, CSS, XML, etc.) are uploaded to the staging server and must be published before going live to the production server. If enabled, files may also be uploaded to alternative publish targets.

Uploading multiple files contained within one containing folder can be accomplished using the Zip Import feature.

Uploading a File

Navigating to Upload

  1. To upload a file, navigate to Content > Pages.
    Content Navigation
  2. Navigate to the location on the site to where the files should be uploaded. Selected files will be uploaded to the directory open on the screen.
    Use the Zip Import feature in order to automatically create subfolders within the folder to which the files are being imported.
  3. If the site has alternate publish targets defined, chose the tab for the appropriate production server to which to upload.

Click Upload in the upper right-hand portion of the screen.

Upload Screen

Setting the Properties for an Upload

  1. From the Set Access To drop-down, select the group that should have access to the files. Level 9 and 10 users can set permissions to any available group. All other users must choose from any group to which they belong.
  2. Select an Upload Type. The default is Standard. To import a zip package, select Zip. For more information about the Zip Import feature: Zip Import
  3. By default, files are not overwritten. To allow files to be overwritten, select the Overwrite checkbox. Only Level 8 users and higher have this authority level.

Selecting Files to Upload

  1. Under File Selection, click Choose File to browse local files.
  2. Select a file to upload.
  3. Repeat this process to upload multiple files.
  4. The file can be renamed by entering the new name in the File field.
  5. Click Upload to upload the files. Allowable file types are indicated with a green check mark. Red text and a red circle indicate the file type is not acceptable for upload.

    The subsequent Notice dialog lists the files that were uploaded and where they were uploaded to. It also lists files that were not uploaded and indicates why. For example, a file name that contains spaces is not acceptable. If a file named "todays updates.txt" is attempted to be uploaded, the Notice message would read:

    “todays updates.txt is an invalid filename because it contains invalid characters.”

Addtional Information and Reminders

  • The ability to upload files is available for users with permission level of 6 or above. Users with permission level 8 or above have the authority to overwrite an existing file.
  • Lower level users (1-5) can be granted the rights to upload through the folder structure in the user's settings. This permission includes Zip Import.
  • To import multiple files using only one selection and containing subfolders, use the Zip Import feature.
  • Zip Import is available to users Levels 6-8 through the user's settings.
  • Note: All binary files (images, documents, PDFs) are uploaded directly to the target production server. All editable files (HTML and text) are uploaded initially to the OmniUpdate staging server and must adhere to the approval process prior to being published to the target production server. Select the appropriate view of staging server or production server in the Pages tab to confirm that files have been uploaded properly. Below are a list of files types that can be uploaded to the staging server:

    File types that can be uploaded to the staging server and are automatically published to the production server as binary files are as follows:

    ".gif", ".jpg", ".bin", ".hqx", ".sit", ".zip", ".exe", ".pdf", ".mov", ".mp3", ".avi", ".flv", ".mpg", ".au", ".wav", ".doc", ".tar", ".z", ".gz", ".ram", ".ra", ".rm", ".jar", ".class", ".png", ".cab", ".bmp", ".cgi", ".jpeg", ".jpe", ".psd", ".jp2", ".svg", ".wmv", ".tiff", ".tif", ".swf", ".mid", ".mdx", ".mso", ".ico", ".ai", ".db", ".tgz", ".xls", ".ppt", ".wpd", ".rtf", ".rcv", ".mbi", ".elm", ".cnt", ".asa", ".tof", ".wmz", ".htx", ".fla", ".dlz", ".mdb", ".pwd", ".pub", ".lck", ".mno", ".dwt", ".mcw", ".wfm", ".dat", ".ctl", ".ind", ".lst", ".thn", ".pps", ".ksc", ".ext", ".mcw", ".ds_store", ".jbf", ".wrf", ".vcs", ".docx", ".xlsx", ".pptx", ".mpeg", ".mp4", ".mkv", ".amv", ".m4v", ".aif", ".aiff", ".flac", ".ogg", ".mde", ".nb", ".mde", ".ppsx", "epub", "ibooks"

    File types that can be uploaded to the staging server and do not automatically get published to the production server are as follows:

    ".html", ".htm", ".shtml", ".shtm", ".jsp", ".php", ".php3", ".phtml", ".asp", ".chtml", ".cshtml", ".dna", ".cfm", ".inc", ".aspx", ".mht", ".ssi", ".css", ".xsl", ".xslt", ".tmpl", ".tcf", ".js", ".xhtml", ".gsp"

    Note: An .ibooks file is actually a folder containing files. Only the Mac Finder and Safari browser treat .ibooks as a file. To upload .ibooks folders to OU Campus, they must be compressed to a ZIP file first, with the following naming syntax: Then when published to a web server, downloaded, and decompressed the proper folder name will be retained for the iBook player to recognize the folder.


Was this page helpful?

Additional Comments:

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

Procede to