...
In addition to the friendly URL, a content item can also be navigated to from a second friendly URL that omits the friendly URL separator. For example, if the friendly URL separator is a dash (-) and the friendly URL for a page is gx-products.htm
then the above page is also available at the friendly URL gxproducts.htm
...
Page Title Uniqueness
In XperienCentral it is not required that all web pages have a unique title. Because the friendly URL is determined based on the title of a page plus its location in the navigation structure, two or more pages can have the same title and not have friendly URL conflicts. For example:
...
| Info |
|---|
The example Friendly URLs in the tables above do not take into account the configuration of the |
...
Content Item Title Uniqueness
...
In XperienCentral, when two pages/items attempt to resolve to the same friendly URL, the conflict is resolved automatically. The mechanism for resolving friendly URLs is fully described in How Friendly URLs are Constructed.
| Info |
|---|
The example Friendly URLs in the table above do not take into account the configuration of the |
...
| Anchor | ||||
|---|---|---|---|---|
|
...
| Order Created | URL Title | Navigation Title | Page Title | Friendly URL |
|---|---|---|---|---|
| 1 | Contact | Contact | contact.htm | |
| 2 | Contact | contact-1.htm | ||
| 3 | Contact us | Contact | contact-us.htm | |
| 4 | Contact | contact-2.htm | ||
| 5 | Contact | Contacting GX | contact-3.htm |
...
| Panel | ||||
|---|---|---|---|---|
| ||||
The following applies to XperienCentral versions R36 and higher. |
...
- 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.
...
Maintaining Friendly URLs
...
| Heading | Description |
|---|---|
| id | An internal identifier for the friendly URL within XperienCentral. IDs are assigned in the order that friendly URLs are created, beginning with 1 and incrementing by 1 for each new friendly URL. |
| URL title | The title of the friendly URL as derived from the URL title, navigation title, or page/content item title. |
| Normalized URL title | The friendly URL title after it has been normalized. Normalizing URL titles is necessary in order to ensure that they are valid for browsers. The normalizing of friendly URL titles is described in detail in the section URL Title Standardization. Note: The normalized URL title as it appears in the exported list does not preserve case usage and does not contain the separator symbol that is substituted for spaces in the friendly URL |
| Querystring | An internal string that XperienCentral uses to retrieve pages, content items, and external database objects. The query string syntax for each item type within XperienCentral has a unique form, for example:
|
| Current URL Title | Specifies the identifier (from column 1) that is the current friendly URL for this item. If an item contains an entry in this column, it means that it is no longer an active URL: When this friendly URL is navigated to, the visitor will be redirected to the friendly URL referenced by the id in 'Current URL title' instead.See Maintaining Items with More Than One Friendly URL for more information. |
| WebsiteID | An internal identifier that refers to the channel that the page belongs to. Content Repository items are assigned the value "-1" because they can appear in any channel in the configuration and therefore do not belong to a specific one. |
...
When a content item or page is created that attempts to use a claimed friendly URL, it is assigned a unique URL based on the title of the URL it wants as described in Friendly URL Claiming. To see the items on your website attempting to claim a friendly URL that is already in use, follow these steps:
...
- Navigate to Configuration > SEO.
- On the [Overview] tab, select "All pages without friendly URLs". The items without a friendly URL are listed. If any items appear in the list, you can manually recalculate the friendly URL for some or all items on your website.
- Click the [Friendly URLs] tab.
- Select the type of recalculation to be performed:
- Calculate the friendly URL for all items which have no friendly URL yet. A friendly URL will be assigned only to the selected items currently lacking a friendly URL.
- Recalculate the friendly URL for all items. A friendly URL will be calculated for all the selected items belonging to the current channel. The URL history for pages and content items will be preserved.
- Select the items for which the friendly URL calculation will be performed: "Pages" or "Content Repository items".
- Click
[Calculate]. Items with no friendly URL will be assigned one.
...
| Panel | ||||
|---|---|---|---|---|
| ||||
The following applies to XperienCentral versions R36 and higher. This documentation is meant for developers and application managers. |
...
Update the Friendly URL Setting application_settings.friendly_url_extension
Clear the In the General tab of the Setup Tool, clear the above field.
Clearing the cache
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.
...