Page History

...

Friendly URL Conflict Indicator

When you create a new page or content item, XperienCentral assigns a friendly URL to it based on the rules explained in the previous sections. For each new page/ content item you create, a check is made to see whether the requested friendly URL is available. If the friendly URL that the page/ 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 page/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:

...

In the example above, the message that displays is: "/contact-1.htm". In this case, because the friendly URL "Contactcontact.htm" is already claimed, the current page content item is automatically assigned the URL "Contactcontact-1,htm" to ensure that all friendly URLs remain unique.  The above action is performed on all XperienCentral pages and content items that attempt to use a friendly URL that is already claimed. To link to the page/ content item that is claiming the friendly URL that the current page/ content item wants, click the name of the item that is claiming the friendly URL that you want to use in the indicator ('Contactcontact' in the example above).

Likewise, when a content item attempts to claim a friendly URL that is a reserved context path, that is indicated. For example:

...

• Accept the friendly URL as assigned by XperienCentral.
• Rename the title (URL, navigation, page) of the current page/ content item that is attempting to use the claimed friendly URL to a desired, unclaimed friendly URL.
• If the title of the page or 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 page/ content item that is claiming it so that it can be used by the current page/ 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_settings section of the General tab in the Setup Tool.

...