Cascade FAQs

This error is usually caused by <o:p> tags (formatting tags from content pasted from Word) in the source code of the WYSIWYG (you can view source code by clicking on <> icon in your WYSIWYG). If you remove the tags above, the page should save. To locate this tag, go to the <> icon to view html mark up and search for o:p.

You can also prevent those tags from being pasted by choosing *Edit* > *Paste as text* in the WYSIWYG before pasting Word content.

You get this message because the parent folder is excluded from publishing. Do the following:

• Click on the folder that contains the asset you're trying to publish and go to "Edit" tab.
• Select the checkbox that says "include when publishing", then "Submit."
• Go back to the publish tab of the asset that you want to publish, and publish it. You will get a  "publish message sent successfully" message that appears in a green bar at the top of your page.
• Please note that some folders are intentionally set not to publish (for example if they only contain blocks). In cases like these, there is usually another page that is using data from the blocks. You should publish the page instead.

Do the following:

• Make sure you don't have multiple edit forms open at the same time in different browser tabs.
• If the problem persists, restart your browser.

You get this message because the asset is excluded from publishing. Do the following:

• Click on the asset and go to the "Edit" System tab.
• Select the checkbox that says "include when publishing," then "Submit."
• Go back to the publish tab of the asset that you want to publish, and publish it. You will get a  "publish message sent successfully" message that appears in a green bar at the top of your page.

• If you unpublished a page/file:
  1. For a webpage or folder, go to the Edit tab and set "Display in Navigation" to no. Click "Save and Preview" and "Submit" to save this change. This will take the page out of navigation ( if you preview site navigation in Cascade, the page won't appear anywhere in the navigation). Files don't have "Display in Navigation" option. Move onto the next step:
     1. Go back to Edit-->Configure and uncheck "Include when indexing" and "Include when publishing" after this. This will ensure that the page doesn't go live until you are ready to republish it.
  2. Republish the parent folder of the asset. If the asset appears in the top navigation, republish the entire website.
• If you unpublished a folder:
  1. Go to folder Edit tab and set "Display in Navigation" to no. Click "Save and Preview" and "Submit" to save this change. This will take the folder out of navigation (preview site navigation in Cascade, the folder won't appear anywhere in the navigation). Go back to folder Edit-->Properties option and uncheck "Include when indexing" and "Include when publishing" after this. This will ensure that the folder doesn't go live until you are ready to republish it.
  2. Republish the parent folder of this folder. If the folder appears in top navigation, republish the entire website.

• Page 
• Folder ( one or more folder types)
• File ( JPG, pdf, docs..etc.)
• External Link - used to add external links as a navigation item
• Reference ( OGMC doesn't recommend using this asset type)

• Page Title appears in the main content area. If you have a hero image, it appears between two purple slashes.
  
  
• Display name is optional to override asset title in the site navigation (top, side and breadcrumbs), primarily if you want to display shorter text. Go to the Edit tab to change Display Name.
  
• New Page Name ( also knows as system name), along with the placement folder name is what makes the URL of an asset. When you create a new asset, Cascade will automatically convert your page title to New Page Name. You can change it later by going in the Rename tab. New Page Name ( or the system name) should be all lowercase with no spaces. Use hyphens instead. This will ensure that you don't see %20 in your URLs when the asset renders in a browser. See an example below:
  
  URL with spaces renders like this: www.northwestern.edu/cascade-help/accessibility%20considerations/index.html
  
  URL with dashes renders like this: www.northwestern.edu/cascade-help/accessibility-considerations/index.html

• Go to the file that you want to replace.
• Click on Edit tab and upload the new file using the Browse button. You can also drop the file in the file upload area.
• Click Submit to save your changes to Cascade server and go to Publish tab to make it live.
• Go to the Relationships tab and publish all assets that are linking to it.

• If you've added a new page that appears in the top or side navigation, you would need to publish the parent folder of that page.
• Make sure to publish the whole site if the changes affect the first level of your side-navigation and affect the top navigation of your site.
• Wait enough time before you check your changes on the live site. If you've published a page or two, it usually take a few seconds to publish, but if you've published a big folder, or have published the entire site, it may take a few minutes--sometimes longer if you have hundreds of assets.
• Look in the Notifications widget on your dashboard to see if the publish job succeeded or failed. If there is no message there yet, your publish job is still ongoing (see below).
• Check the publish queue to make sure your publish job went through. This can be viewed under the Cascade icon menu (left of Home) in Publisher > Active Jobs.
• Open a new browser window and go to the page that you edited. If you don't see your changes, try clearing your browser cache or open in a different browser. At this point, if you still don't see your changes on the live site, contact webcomm-support@northwestern.edu.

To prevent pages/folders from being published accidentally, you can take take them out of publishing. To do so:

• Click on the page or folder and go to Edit-->Configure or Edit-->Properties option.
• Uncheck the box that says "Include when publishing" and save your changes. This will disable publishing on that asset.
• If you try to go back to the publish tab of the asset, you will get an "Asset is not set to publish..." message. This will remind you to set the asset to publish by going back in Edit-->Configure option and selecting the "Include when publishing" checkbox.

You will need to republish all pages if you:

• Update a common element like the footer or header of your site.
• Move/Rename/Delete or reorder assets that appear in your navigation (including mobile navigation).

To publish your whole site, go to the root directory and publish it.

Deleted assets are stored in the Trash bin for 15 days. To restore an individual asset back to its original location:

• Go to the Trash bin by going to your site content.
• Once in the Trash bin, to restore an individual asset back to its original location, click the green Restore icon in the actions column.
• When prompted "Are you sure you want to restore this item?" click Submit.

• Click on the file and go to the More-->Rename option. Add the appropriate file extension (.JPG for photos or .PDF for a PDF) to the file name and save your changes.

• Go to the page and click More > Versions to see previous edits to the asset.
• Compare previous versions to the current one, and activate them if needed.
• If you reactive a version, you can either make further edits or publish it.

• If it's an external link, check if the destination site is down, or the link is not working.
• Your external links should begin with either http:// or https://
• Some websites do not use the www prefix. Make sure you have the link entered into Cascade exactly as it appears in your browser when you're viewing the destination site.
• If you are linking to an internal asset, make sure the asset is published to the live server.

If your external link on the live site opens Cascade page, do the following:

• Go to the edit tab and click on the link in WYSIWYG. Make sure the link URL starts with http:// or https://. The URL should look like this: http://www.northwestern.edu.
• Save your changes and publish the page.

To view publish queue:

• Make sure that you are still in your site workspace and not on your dashboard.
• Go to the hamburger icon in the top black header ( far right) and click on it. You will see the Publish Queue option there. If you don't see this option, it could be because you are not in your site.

When you create a New File/Page/Folder in Cascade enter page Title as Sentence Case. Cascade will convert it to all lowercase and replace spaces with hyphens.

• Please publish large folder after hours
  Large collections of files should be published after hours (after 5 p.m. or before 8 a.m.). Large publish jobs may delay another user's time-sensitive publish job and can also put load on the server affecting overall system performance. When possible, publish individual pages, or a smaller group of pages.

• Publishing to the test server
  The test server allows you and others on campus to review your website content before it goes live. When you are given your site, your default publishing destination is the LIVE Destination. Please email webcomm-support@northwestern.edu for your test site URL if you don't have it.

• If you wish to move/rename/delete a file from the live server, make sure to unpublish it first, otherwise the page in the old location will stay on the web server indefinitely. Please email webcomm-support@northwestern.edu if you find an "orphaned" page that you want to delete from the live server.
• When you move/delete/rename an asset, the links referring to it from other pages will break. Check the links by going to the Relationships tab and take appropriate action before you move/delete/rename your asset.

• Do not use tables to lay out content in your web pages.
• Apply appropriate table class style when needed. Apply it if you see it in the styles dropdown. Sites using the new branded template may not need to take this step.
• Make sure you have at least one header row or column and you mark it as a header row or column. This is very important for accessibility.
• Do NOT use headings (H3s, H4s etc.) to format text in a table.

See detailed instructions on how to create a table.

• Structure your content using Headings. This creates a visual hierarchy on the page and breaks content in chunks for easier scanning. Headings are also very important for accessibility.
• Do not skip a heading level.
• Do not use Heading 1 and Heading 2 in the main content area. These two are reserved for site title and page title. You can use heading 3 - heading 6 in the main content area.

• Links should be descriptive. For example, if you want to link to 2014 Cash Policy, don't link to "click here." Instead the link text should be "Click here to see 2014 Cash Policy."