Troubleshoot Common Errors

Make sure you're logged into builder.wcms.iu.edu, not sites.wcms.iu.edu.

If you're logged into the WCMS Builder server and still can't find your site, contact WebHelp.

New assets are placed in the folder you were in when you clicked Add Content. Look through the folders on the left-hand side of the screen to find the asset you created.

You can also try finding your new page or folder by clicking My Content at the top-right of the screen and then clicking Recent.

You can move a page or folder to the correct place by right-clicking on it in the folder view and selecting Move.

Not all components are available on every page type. Each page type includes a curated set of components that support the kind of content that page is designed for.

Check the documentation for your page type to see which components are available. You can also look at a component's documentation to see which page types it can be used on.

Replace any ampersands in text content with &. Replace non-numeric HTML entities (e.g., …) with their numeric equivalents (& #8230;).

For rich text fields, you might need to click the infinity symbol (∞) in the text editor, and then click Source Code (the button showing two angle brackets) to view the HTML.

You'll need to republish the _side-nav asset in each folder you changed pages in. If you changed top-level pages or folders, you'll need to republish _includes/header.

Republishing navigation assets to SiteKube Test updates navigation within the WCMS preview. Republishing to SiteKube Production updates navigation on your live site.

For more, see Navigation.

The Show in Navigation setting only controls a page or folder's appearance in your site's primary or side navigation. The page is still published and accessible if someone has the direct link.

If you need to prevent access, right-click the page in the folder view and select Unpublish or Delete.

When you first get a new Site Builder site, you can only publish to SiteKube Test (the preview environment).

To publish your site live for the first time, you'll need to submit a launch request form. Once your site is approved and launched, you’ll be able to publish to SiteKube Production going forward.

Your browser may be showing a cached version of the page.

Try hard refreshing the page (CTRL + F5 on Windows; ⌘ + Shift + R on Mac) or clearing your cache. You can also open the page in a private/incognito window to confirm you’re seeing the latest version.

If you're using an Automatic card grid, the cards pull their titles, descriptions, and images from each source page.

After updating a page, make sure you save and publish the page, then republish the Card Grid page so the feed refreshes. If you changed the card image, update the page's Feed image in Page Settings and republish the page.

If you still see old information, try hard refreshing the page (CTRL + F5 on Windows; ⌘ + Shift + R on Mac) or clearing your cache. You can also open the page in a private/incognito window to confirm you’re seeing the latest version.

If you see an error message where your header, footer, or sidenav should be, it usually means those elements haven't been published to the SiteKube test environment.

In WCMS preview, those global elements load from what's published on SiteKube test—not your draft changes—so make sure _includes/header, _includes/footer, or _side-nav assets are published there.

If everything is published and the issue continues, check status.iu.edu to see if there's a temporary SiteKube outage affecting preview.

Make sure you've entered your privacy notice ID and API token in settings.

Note that your site's privacy notice will only show on the published page—a placeholder message will be shown within the WCMS preview.

For more, see Privacy Notice.

Site Builder uses a newer version of LiveWhale feed URLs than legacy IU Web Framework sites. Older feed URLs aren't compatible with the Feed component.

Generate a new feed URL using the LiveWhale Storyteller Feed Builder or LiveWhale Events Calendar Feed Builder.

The Code component only accepts XHTML snippets, not full HTML documents.

To avoid render errors, make sure your code is wrapped in a single parent element (such as a <div>), contains only the HTML you want to embed (not <html>, <head>, or <body> tags), and uses valid XHTML markup.

If your code is written in HTML5, you may need to use an HTML-to-XHTML conversion tool or the Site Builder GPT before pasting it into the component.

This usually means one or more of the files your Code component depends on haven't been published.

Publish the relevant files in your site's _code folder, then republish the page. Once the required files are available on the published site, the Code component should render correctly.

This error can occur if a page or file in your WCMS site has two dashes in a row (--) in its name, such as program--requirements.

Rename the asset to remove the double dash (for example, program-requirements), then try publishing your site's settings again.