Troubleshoot

I am trying to create a site, but there are no templates

Templates must be installed and shared before you can create a site.

The templates provided with Oracle Content Management must be installed and shared by an administrator before you can use them. Contact your administrator.

Similarly, when you create a template, whether by importing, copying, or creating from a site, the template can’t be used by anyone else until you explicitly share it.

See Configuring Site Settings in Administering Oracle Content Management.

I can’t delete a site

Here are some reasons why you may not be able to delete a site:

The site is online.

First, take the site offline and then delete it. You must have the manager role for a site to take the site offline.
You don't have the required privileges.

You can delete a site if you created the site (you’re the site owner) or if someone has shared a site with you and has given you the contributor or manager role.

See Manage Sites and Site Settings for details.

I can’t open the site tree or edit a page

Site Builder opens in preview mode by default, which allows you to view the site, but not edit it. You can only edit a site if the editor is in edit mode.

Make sure that is set to Edit.

I added a component, but it doesn’t show up on the page

There are several possible reasons for this.

Verify that the URL associated with a remote component (app) is valid. See Register Remote Components.
The editor encloses remote components in an HTML element called an inline frame (iframe tag). Not all remote components allow being enclosed in an inline frame.

Check with the component provider to find out if it can be enclosed in an inline frame.

My folder, file, and conversation components don’t work

Components that communicate with Oracle Content Management require certain resources and settings.

The following components require access to resources in Oracle Content Management:

Folder list
File list
Documents manager
Conversation

Folder and file components require access to the REST application programming interface (API).

Verify the following:

The component must have access to the API endpoint to access folder and file REST operations.

By default, the Oracle Content Management REST API endpoint is available if you use the standard URL provided for the site. If you use a custom URL, you may have to explicitly provide access to the /documents REST API endpoint.

See How do I map a site URL?

I changed the page layout and some of my content disappeared

If you choose a layout with fewer or differently named slots, existing content in other slots won’t display in the new layout.

The content isn’t deleted, it just can’t be displayed unless the layout you choose has a slot with the same name.

Make sure you choose a layout with the same number of slots. If the layout you choose has the same number of slots, but some of your content still does not display, it’s likely the slots have different names. Contact the theme designer to resolve the discrepancy.

I uploaded a new version of an image, but it doesn’t show up on the page

When you select an image to use with a component, a unique copy is created and stored with the site.

When you upload files, they are stored in the site repository. If you upload a file with the same name as an existing file, it creates a new version of the file.

The image file you see on the page is a copy of the file selected from the repository and is not automatically updated. This is by design and prevents inadvertent changes in existing pages when an image file is updated in the repository.

To update the image used with the component, you must explicitly select the image from the component property page. See Images for details.

I added a component based on another service but it isn’t working

You can integrate your site with several different processes and services.

If you created a component based on integration with Process Cloud Service, Oracle Intelligent Advisor (formerly Oracle Policy Automation), and other services, both services must use the same identity domain. Check with the person who set up the integration to verify that the two services use the same identity domain.

My enterprise site shows a warning

If an enterprise site includes v1.0 content layouts, you'll see a warning in Site Builder and when viewing the site because the layouts won't be able to render. They need to be updated to v1.1 content layouts.

This situation can happen in one of two ways:

If you make an existing site translatable, the site will automatically be converted to an enterprise site by being assigned a default language and localization policy. If the site template includes v1.0 content layouts, the content layouts won't be able to render.
If you create an enterprise site from an older template that uses v1.0 content layouts, again, the content layouts won't be able to render.

To correct this issue, update the content layouts to v1.1 content layouts. You can create a new content layout in the component catalog to see the difference. You'll need to add a line to register the version of the content layout and change data.fieldname to fields.fieldname.