Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The friendly URL of an item in XperienCentral includes the relative path to the item based on the structure of the navigation tree, the title of the item and an extension, in much the same way that a path for a file is delineated in a file system. The precise URL that an item will be assigned is derived using a set of rules that evaluate the item's title(s) as well as its location in the website's navigation hierarchy. In XperienCentral, you can assign the following three titles to pages/content items:

TitleDescription
URL TitleThe title to use in the friendly URL for the item.
Navigation TitleThe title that will be used for the page in your website's navigation tree. Navigation titles only apply to pages.
Page/Content item titleThe title of the item itself that appears when the page or content item displays in the browser.

...

  • The URL's extension is set to .htm.
  • The separator symbol, which is substituted for spaces that appear in titles, is a dash (-). The separator symbol is defined in the General tab of the XperienCentral Setup Tool. The default is a dash (-).

 

TitleNavigation TitleURL TitleFriendly URL
Welcome to GXWelcome /welcome.htm
   News  welcome/news.htm
      Articles  welcome/news/article.htm
      News Archive  welcome/news/news-archive.htm
   Products overview Productswelcome/products.htm
      XperienCentral  welcome/products/gx-xperiencentral.htm

...

For example, if a content item has the title "GX releases XperienCentral 10", the friendly URL of the content item is 'GX-releases-XperienCentral-10.htm'. There is no hierarchical structure prefixed internally to the friendly URL of the content item because it is stored in the Content Repository. When the content item is displayed on a page, the hierarchical structure of the 'display on' page is prefixed to the content item's friendly URL with the result being the friendly URL for the page and the content item. Based on the example friendly URLs shown in the table above, the friendly URLs for the following sample content items would be:



Content Item TitleDisplay on PageFriendly URL
XperienCentral 10Productswelcome/products/gx-xperiencentral-10.htm
EngagementArticleswelcome/news/articles/engagement.htm
Version 10XperienCentralwelcome/products/gx-xperiencentral/version-10.htm

...

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:

Parent Page Title(s)Page TitleFriendly URL
GX/SupportContactgx/support/contact.htm
GX/SalesContactgx/sales/contact.htm
GX PublicContactgx-public/contact.htm

In the example above, the "Contact" pages all have the page title "Contact" but because of their relative locations in the site structure, the friendly URLs for the pages remain unique. Given the fact that the friendly URL is determined by a page's title (URL, navigation, page), the following situation in which three pages in the same tree have the same page title also does not lead to friendly URL conflicts:

Parent Page Title(s)URL TitleNavigation TitlePage TitleFriendly URL
GX/SalesContacting Contactgx/sales/contacting.htm
GX/Sales Contact usContactgx/sales/contact-us.htm
GX/Sales  Contactgx/sales/contact.htm

...

This is because content items can be displayed on any page and therefore XperienCentral has no way of determining at the time that a content item is created where it will be displayed and therefore what its full friendly URL will be. XperienCentral only compares the friendly URL of newly created content items to last part of all existing friendly URLs '.htm'. For example, creating a content item that resolves to the friendly URL 'Contact.htm' would lead to a friendly URL conflict with all the pages in the following table:

Parent Page TitlesURL TitleNavigation TitlePage TitleLTitleFriendly URL
GX/PublicContact Contacting usgx/public/contact.htm
GX/Sales ContactContact GXgx/sales/contact.htm
GX/Support  Contactgx/support/contact.htm

...

XperienCentral determines which item claims a friendly URL in a straightforward manner: The item that was created first claims the friendly URL it wants — All other items that try to claim that friendly URL are assigned a different, unique URL based on the name of the original. For items that attempt to use a claimed URL, a dash (-) plus a number is appended to the end of the original friendly URL and that is used in the address for the item. The number increments by one for each successive item that wants to claim the original friendly URL in the order they are created. The following simple example assumes that the pages are assigned no URL or navigation title but share the same page title in the same tree structure:

Order CreatedPage TitleFriendly URL
1Contactcontact.htm
2Contactcontact-1.htm
3Contactcontact-2.htm
4Contactcontact-3.htm

...

The example above shows how page titles that attempt to claim the same URL are resolved. It is also possible to have URL conflicts that are the result of more complicated circumstances, such as URL titles and/or navigation titles that conflict with a page or object title or navigation titles that conflict with each other, content item titles that conflict with a page's friendly URL, and so forth. The following table shows what the URL result would be for conflicts at a variety of title and navigation title levels.

Order CreatedURL TitleNavigation TitlePage TitleFriendly URL
1Contact Contactcontact.htm
2 Contact contact-1.htm
3 Contact usContactcontact-us.htm
4  Contactcontact-2.htm
5Contact Contacting GXcontact-3.htm

...

In the overview, the column headings have the following meanings:

HeadingDescription
idAn 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 titleThe title of the friendly URL as derived from the URL title, navigation title, or page/content item title.
Normalized URL titleThe 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
QuerystringAn 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:
  • Pages - &id=43137&langid=42
  • Media Repository articles - &contentid=3
  • External objects - &dbid=12901&typeofpage=40054
Current URL TitleSpecifies 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.
WebsiteIDAn internal identifier that refers to the web initiative that the page belongs to. Content Repository items are assigned the value "-1" because they can appear in any web initiative in the configuration and therefore do not belong to a specific one.

...