Page History

...

...

Google News ID for Articles

...

...

Back to top

...

Content Item Title Uniqueness

In XperienCentral, content items must have a unique friendly URL title compared to the following

Content Item Title Uniqueness

In XperienCentral, content items must have a unique friendly URL title compared to the following:

• All titles used in the friendly URL of all other content items in the Content Repository (URL title/ content item title)
• All titles that are currently used in the friendly URL of a page (URL title, navigation title, page title)
• All titles that are currently used in the friendly URL of all pages in all channels where the content item can appear
• All friendly URLs assigned to external (database) objects

...

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.Back to top

Back to top

...

Anchor
friendly_url_claiming friendly_url_claiming

Friendly URL Claiming Anchorfriendly_url_claimingfriendly_url_claimingFriendly URL Claiming

In XperienCentral, it is possible for two or more pages/items to resolve to the same friendly URL as a result of your website's structure. This can occur, for example, when through a combination of URL titles, navigation titles, and/or item titles, the calculated friendly URL for two or more pages/items turns out to be identical. Naturally, only one item can claim a specific unique friendly URL if this occurs. All other items that try to claim a friendly URL that is already claimed (in use) will be automatically assigned a different friendly URL in order to resolve the conflict.

...

Back to top

...

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. For example, the A friendly URL title 'Contact' is already claimed can already be used by another page or 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 above the pagein the SEO tab of the Content Item Properties panel:

Image Added

In the example above, the message that displays is: "URL is set to 'Contact/contact-1.htm'. The URL Contact is already used by 'Contact.htm'" ". In this case, because the friendly URL 'Contact"contact.htm' " is already claimed, the current page content item is automatically assigned the URL 'Contact"contact-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 ('"Contact' " in the example above).

When the friendly URL you want to use for an item is already claimed, you have the following options:

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

Image Added

In the example above, "salesforce" is a reserved context path. If you create a content item with the same name, you will see a message similar to that shown above.

When the friendly URL you want to use for an item is already claimed, you have the following options:

• Accept the friendly URL as assigned by XperienCentral.
• Rename the title (URL, navigation,
• 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 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.

Back to top

...

Maintaining Friendly URLs

...

Running XperienCentral without a Friendly URL Extension

It is possible to run XperienCentral without using a friendly URL extension. This means that a URLs like /contact are possible. In order to activate this feature, a few changes need to be made to both the configuration of Apache and XperienCentral.

...

When the friendly URL is blank (extensionless), it can no longer be redirected. Use the following code to run XperienCentral without a friendly URL extension.

DirectoryIndex index.html 

<IfModule mod_rewrite.c>
   RewriteEngine On

   #Optional to make sure that old urls are redirected to XC properly
   RewriteRule ^(.*).htm$ $1 [R=301,L]

   RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-f
   RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-d
   RewriteCond %{REQUEST_URI} !^/web/ 
   RewriteCond %{REQUEST_URI} !^/systemlogs       
   RewriteRule ^(RewriteCond %{REQUEST_URI} !^/static
   RewriteCond %{REQUEST_URI} !^/upload
   RewriteCond %{REQUEST_URI} !^/upload_mm
  RewriteRule ^(.*)$ /web/seo$1 [PT,L]   
</IfModule>

In order to active extensionless friendly URL's in XperienCentral, the following steps should be executed:

Update the Friendly URL Setting application_settings.friendly_url_extension

Clear the 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.

The other option is to click "Update timestamps" for all options except for "Initialize caching". This means that a page is refreshed in the background after it's been served from the cache the first time it was requested after the timestamps have been updated. This does mean that the user that requests the page for the first time after the timestamps have been set will be served a cached version with links that won't work. In order to prevent the user from getting 404 errors, you can configure Apache to rewrite any URLs containing the old extension to the version without the extension. See "Updating the Apache Configuration" above for an example.

Reindex the Frontend Index

The frontend index contains links with the old friendly URL extension, so in order to fix that the frontend search index should be rebuilt. If the Apache RewriteRule to strip the extension from any incoming URLs is used, this may be done in production because the old URLs will be rewritten by Apache to the new format.

Configure Reserved Context Paths

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:

• web
• static
• upload
• upload_mm
• cfg
• info
• wm