Profiling settings
The Profile section contains profiling settings for the Web Content Viewer, specifying categories, site areas, and authoring templates that can be used as menu search options.
We can profile the Web Content Viewer by selecting categories, site areas, and authoring templates. A menu can use this profile to display a list of content items that are profiled with the same categories, site areas, or authoring templates.
- Categories
- Add or remove categories to profile content rendered with the Web Content Viewer.
- Site Areas
- Add or remove site areas to profile content rendered with the Web Content Viewer.
- Authoring Templates
- Add or remove authoring templates to profile content rendered with the Web Content Viewer.
Locked settings
We can lock settings in the Configure mode of the viewer. When a setting is locked, a lock icon is displayed in the Edit Shared Settings mode of the viewer, and no Edit link is available.
Content paths and unique IDs
When we configure the viewer, content paths are represented as readable paths that include the library and site areas containing the content. However, in the viewer configuration, the location of a content item is typically stored as the unique ID of the item. The use of the unique ID is helpful because the viewer can still render the content even if the item is renamed or moved.
If we configure the viewer with xmlaccess.sh (xmlaccess), we have the option of specifying content location with the content path instead of the unique ID. With the content path, we do not have to determine the unique ID of the content item. But if the content item is moved or renamed later, the viewer can no longer render the content.
If a viewer is configured to use content paths, a path icon (
) is displayed after the title path. If we change the configuration to reference different content, the location of the new content item continues to be stored as a content path.
To store the location as a unique ID instead, click Clear before we select the new content.
The path icon is also removed to indicate the content path is no longer being used.