...
| Info |
|---|
The example Friendly URLs in the table above do not take into account the configuration of the |
...
| Info |
|---|
The example Friendly URLs in the tables above do not take into account the configuration of the |
...
| Info |
|---|
The example Friendly URLs in the table above do not take into account the configuration of the |
...
When you create a new content item, XperienCentral assigns a friendly URL to it based on the rules explained in the previous sections. For each new content item you create, a check is made to see whether the requested friendly URL is available. If the friendly URL that the content item wants is available, it is granted. If, however, the friendly URL is already in use, a message will appear in the "Properties of all versions" section of the SEO tab in Content Item Properties indicating that the desired friendly URL is already in use and that a new friendly URL has been assigned to the current content item. A friendly URL can already be used by another content item or it can also be a reserved context path. For example, the friendly URL "Contact" is already claimed by another content item. When the page below entitled "Contact" is created, an indicator that the friendly URL is already claimed displays in the SEO tab of the Content Item Properties panel:
...
- Accept the friendly URL as assigned by XperienCentral.
- Rename the title (URL, navigation, page) of the current content item that is attempting to use the claimed friendly URL to a desired, unclaimed friendly URL.
- If the title of the content item itself conflicts with a claimed friendly URL but you nevertheless want to continue using it, add an unused navigation or URL title that does not produce a friendly URL conflict. For page title conflicts, you can also make use of an alternate URL path to avoid the conflict. Alternate URL paths are described in detail in Using Alternate URL Paths.
- Release the URL from the content item that is claiming it so that it can be used by the current content item. See Releasing Claimed Friendly URLs for complete information.
- If the conflict is caused by a reserved context path, you must either select a different URL or modify the reserved context path in the
application_settingssection of the General tab in the Setup Tool.
...
Since the cached files in XperienCentral contain links with the extension still included, the cache should be cleared entirely (see Server Configuration). There are two ways to do this. You can either use "Initialize caching" or set all the other timestamps. Initialize caching should only be used on an environment which is not currently in production. When the server is not running in production you can use the Initialize caching option and then reindex the frontend search index to preload the cache before going live again.
...
When running XperienCentral without an extension, a few paths should be added to the application_settings.reserved_context_paths (see reserved_context_path) in the General tab of the Setup Tool. The following values should be added:
...