• Enable URL Aliasing—let CMS users with permissions create URL aliases.
• Enable URL Redirects—let CMS users with permissions create redirected URLs (for example, 301 redirects). See Creating a URL Redirect.
• Manual—enable manual aliasing. See Creating a Manual URL Alias.
• Folder—allow automatic folder aliases to be generated.
• Taxonomy—allow automatic taxonomya content-level categorization system that uses one-to-many relationships (such as Ronald Reagan is to Actor, Governor, and President) to create a scalable organization of content. A taxonomy lets your site visitors navigate content independent of the folder structure. aliases to be generated.
• User—allow automatic user aliases to be generated.
• Community Group—allow automatic community group aliases to be generated.
• RegEx—allow RegExregular expression; an alias that creates a pattern. For example, blogs.aspx?blogmonth=3&blogyear=2012&blogid=41 can be a RegEx blogs/2012/03/41. From that, a site visitor can infer blogs/2012/03/40 to see the previous post, or enter blogs/2012/03 to see all March 2012 posts aliases to be generated.
• Extensions—Enter file extensions of pages for which aliases can be created and click Add. Begin each extension with a period (.). By default, Ektron supplies the following extensions (which cannot be removed).
  • .aspx
  • / (the slash is actually the lack of an extension at the end of a page’s name)

  Do not add any extension entered into the Handler Mapping list. See Restrictions on Extensions

  The values in this field appear as drop-downs in the Add a New Manual Alias and Add a New Automatic Alias screens.

  —Image—

  

  See Also: Defining Unusual File Extensions Used in Aliasing

• Override Template—A template and an alias can have the same name, for example, www.example.com/dynamic.aspx. If this happens, and a site visitor types such an address into the browser, this check box determines if the template page or the alias appears. If this box is checked, the alias appears instead of the template.

  NOTE: The template must be defined within the Workarea Settings > Template Configuration screen.

• Enable Language Awareness—
  • Off (unchecked)—
    • URL exists in the site visitor's current language: show target.
    • URL does not exist in site visitor's current language: 404 File Not Found appears.
  • On (checked)—
    • URL exists in the site visitor's current language: show target.
    • URL does not exist in site visitor's current language:
      • If the URL exists in a language listed in the language fallback chain: show target. (See Setting the Fallback Locale.)
      • If the URL does not exist in the language fallback chain, but does exist in the site default: show target.
      • If the URL does not exist in the language fallback chain, and does not exist in the site default, but exists as an alias in any language: get the first URL match and show target.
      • If the URL does not exist in the language fallback chain, and does not exist in the site default, and does not exist as an alias in any language: 404 File Not Found appears.
• Default Replacement Character—replace spaces in taxonomy, folder, group or user path names with a default character (such as underscore, _). You can specify replacement characters for other characters in the Replacement Character Map on the Add Aliasing Rule screen.
• Query String Action—Set up a rule to handle an alias’s query string parameters. You can set one rule for your entire site (via this field), and separate ones that override the system-wide rule for specific manual aliases (using the Aliases screen). The following options are available.
  • None—If an aliased URL has a query string, it is ignored. Any query string on the target URL is used.
  • Replace All Parameters within Alias—replaces a target’s query parameters with the alias’ s query parameter. Example:

    alias’s query string parameter: 
    http://www.ektron.com/Contact.aspx?id=84
    Target: http://www.ektron.com/aboutus.aspx?id=35&Userid=1
    Result: http://www.ektron.com/aboutus.aspx?id=84

    (The target parameters id=35&Userid=1 are replaced by the alias parameter id=84)

  • Append Parameters to Alias—appends the alias’s parameters to the target URL. Example:

    Alias: http://www.ektron.com/Contact.aspx?id=84&lang=1033
    Target: http://www.ektron.com/aboutus.aspx?id=35&Userid=1
    Result: http://www.ektron.com/aboutus.aspx?id=35&Userid=1 
      & id=84&lang=1033

    (The parameter from the alias is appended to the target)

  • Resolve Matched Parameters within Alias—Ektron tries to resolve matching parameters (it is case sensitive). If a match is found, the alias’s query string parameter takes precedence. Example:

    alias’s query string parameter:
    http://www.example.com/Contact.aspx?id=84
    Target: http://www.example.com/aboutus.aspx?id=35&UserId=10
    Result: http://www.example.com/aboutus.aspx?id=84&UserId=10

    (id=35 is replaced by id=84 since it matched the query string parameter. UserId=10 was not affected because it did not match the alias query string parameter.)

Setting Default Documents for URLs

You can set the default document file (for example, default.aspx) in the ek_DefaultPage element of siteroot/web.config for client requests of a website that did not specify a document name. For example, if someone types www.example.com/jobs, and the default document is default.aspx, this URL resolves to www.example.com/jobs/default.aspx.

NOTE: The concept of default document is explained in the following Microsoft KB article: Configure the List of Default Documents in IIS 7

The ek_DefaultPage element determines your website’s default document regardless of whether you are using URL aliasing.

If a site visitor enters an address without a page name, Ektron refers to ek_DefaultPage’s values. For example, the first page is default.aspx. If found, that page displays. If not, it looks for the second page listed, and so on. If no pages are found or a page is not specified in ek_DefaultPage, Page not found appears in browser.

Permissions for Working with URL Aliasing

• Alias-Admin privileges apply to members of the CMS Administrators group and CMS users with the Alias Administrator role.
• Alias-Author privileges apply to any CMS user with the Alias Author role.
• CMS User privileges apply to users that do not have the Alias-Author or Alias Administrators role applied.

  NOTE: By default the Alias-Author role is applied to the Everyone group. This role can however be removed to further restrict the permissions to the CMS User state.

Task	Alias-Admin	Alias-Author	CMS User
View Settings Page
Edit Settings
View Rule List Pages
View Rule
Edit Rules
View Alias List Page
View alias
Add Aliases
Edit Alias
Delete Alias
View Redirects Page
Edit Redirects Page
View Alias on content tab
Edit Alias on content tab

Where Aliasing Cannot Be Applied

IMPORTANT: After you enable Aliasing, relative links embedded in your Web pages that are not preceded by a slash (/) may demonstrate symptoms such as runtime error notifications, broken images (you see a red X where the image should be), or missing text styling. The following Ektron Knowledge Base article analyzes this problem and presents solutions: Avoiding Style Problems, JavaScript Errors, and Broken Images When Using URL Aliasing.

You cannot apply aliasing to the following areas of Ektron.

• images
• content in root folder (cannot be automatically aliased, although you can alias it manually and by taxonomya content-level categorization system that uses one-to-many relationships (such as Ronald Reagan is to Actor, Governor, and President) to create a scalable organization of content. A taxonomy lets your site visitors navigate content independent of the folder structure.)
• forums (discussion boards) (links within forum posts can be aliased)
• forms/polls/surveys—the form is aliased but the postback screen is not (for a workaround, see Tip/Trick: Url Rewriting with ASP.NET)
• a link to an HTML form
• eCommerce—items in a (Shopping) Cart server control use an alias unless you assign an .aspx page in the control’s TemplateProduct property. If you assign a page, it is used in the product’s URL, not the alias.
• If you enable .asp as an extension, the alias does not appear when a site visitor hovers the cursor over assetan external file, such as a Microsoft Word document or image, stored in Ektron. It can be managed like native Ektron content.s. Instead, the actual file name appears.

  If a site visitor hovers the cursor over HTML content, the alias does appear.

• The alias does not appear when a site visitor viewing an RSSRich Site Summary; regularly changing content, such as news sites and blogs link and send content to subscribers. page hovers the cursor over assets. Instead, the actual file name appears.
• content links within the Directory server control. If a template is assigned to a taxonomy, the template takes precedence over an alias for content found by a Directory server control.
  —Image—

  

Restrictions on Extensions

IIS7Internet Information Services (IIS) for Windows® Server, version 7 handles Web page extensions other than .aspx. There are 2 scenarios.

• If your site has non-aspx pages, you need to modify the IIS7 Handler Mapping list. In the Handler Mapping list, extensions that are below ek* in the list are handled by aliasing. You need to move non-aspx extensions (for example, .asp, .php, .cfm) above the ek* extensions in the list.
  —Show how—

  1. Open IIS7.
  2. Right click your website.
  3. Click Handler Mappings.
  4. Click View Ordered List.
  5. Move non-aspx extensions used on your site above ek*. For example, if your site uses .aspx pages, move ASPclassic above ek*.

     NOTE: After you do this, you cannot use these extensions as part of an alias. So, do not enter them into the Extension field of the URL Aliasing Settings screen.

     —Image—

     

• If your site previously had non-aspx pages but now it does not, set up aliases to the previous non-aspx pages so that a visitor's bookmarks will continue to work.
  —Show how—

  1. Open IIS7.
  2. Right click your website.
  3. Click Handler Mappings.
  4. Click View Ordered List.
  5. On the Handler Mappings screen, move non-aspx extensions that you want to alias below ek*. For example, if your site uses .aspx pages, move ASPclassic below ek*.
  6. Enter the extensions in the Extension field of the URL Aliasing Settings screen. See Also: Types of URL Aliasing

Clearing the Cache

An alias is cached whenever anyone uses it. You should periodically clear the cache so that aliases are kept current.

IMPORTANT: If your Ektron supports multi-site configurations, you must sign in to each site’s Workarea, then manually clear its cache.

1. Choose Settings URL Aliasing > Settings.
2. Click Clear Cache ().

Assigning an Alias to Multi-Language Content

When a site visitor selects a language for viewing your site and enters the alias, Ektron displays the aliased content in the selected language. See Also: the Enable Language Awareness field in Configuring URL Aliasing.

You can assign a different alias to each language version of content. To do this, select the content, language, go to the Alias tab, and assign a language-specific alias. For example, your English home page’s alias is default, while your Spanish alias is defecto.

Also, alias names must be unique only within a language. So, for example, you cannot have 2 aliases named Ektron within U.S. English content. But, you can have 2 two aliases namedEktron if one is applied to U.S. English content, and the other applies to Spanish content.

Adding/Editing a Manual URL Alias

To add or edit a manual alias, manual aliasing must first be enabled.

1. Choose Workarea > Settings > Configuration > URL Aliasing > Aliases. The Aliases screen appears. You can specify the following filters, or go right to Step 2.

   NOTE: If there are many aliases, use the search to find one. You can filter by alias name, Content ID, and so on.

   —Filters—

   1. Choose Manual from the Type drop-down field. The manual aliases appear in the Aliases screen.

      

   2. Choose the language from the Language drop-down field.
   3. If your Ektron version supports multi-site configurations, use the Site drop-down to choose the site.
2. To create a new alias, click Add Manual Alias. (To edit a manual alias, click an alias then Edit.) The Alias Data screen appears.

   NOTE: After you enable manual aliasing, every content block includes an Alias tab. You can create a new alias by clicking Add Manual Alias from that Alias tab. However, if you insert/update an alias from the Alias tab, the alias is available only after you publish the content.
   Also, a folder may require its content to have a manual alias. In this case, you must add a manual alias before you can check in or submit content.

   —Image—

   

3. Check Active to activate the alias when you save it.
4. Optionally, check Default if you want this alias to be the primary aliasA primary alias is the default link for a content item. So when elements, controls, widgets, or custom code on your page render links to content items, the default link is rendered to the browser.. Even if the content already has a primary alias, this alias will become primary.
5. Optionally select another language for this alias.
6. Enter a name in the Alias field. It must be unique within the site and language, and cannot include the following characters: (comma), (space), \, <, >, “, :, |.
7. To the right of Alias is a pull-down menu of valid extensions. Select an extension to apply to this alias. Extensions are defined on the URL Aliasing Settings screen.
8. Use the Query String Action field to set up a rule to handle an alias’s query string parameters. You can set one rule for your entire site (via this field), and separate ones that override the system-wide rule for specific manual aliases. 4 options are available.
   —Options—

   • None—If an aliased URL has a query string, it is ignored. Any query string on the target URL is used.
   • Append—Ektron appends the alias’s parameters to the target URL. Example:

     Alias: http://www.ektron.com/Contact.aspx?id=84&lang=1033
     Target: http://www.ektron.com/aboutus.aspx?id=35&Userid=1
     Result: http://www.ektron.com/aboutus.aspx?id=35&Userid=1 |
       & id=84&lang=1033

     (The parameter from the alias is appended to the target)

   • Replace—Ektron replaces a target’s query parameters with the alias’ s query parameter. Example:

     Query string parameter: http://www.ektron.com/Contact.aspx?id=84
     Target: http://www.ektron.com/aboutus.aspx?id=35&Userid=1
     Result: http://www.ektron.com/aboutus.aspx?id=84

     (The target parameters id=35&Userid=1 are replaced by the alias parameter id=84)

   • Resolve—Ektron tries to resolve matching parameters (it is case sensitive). If a match is found, the alias’s query string parameter takes precedence. Example:

     Query string parameter: http://www.example.com/Contact.aspx?id=84
     Target: http://www.example.com/aboutus.aspx?id=35&UserId=10
     Result: http://www.example.com/aboutus.aspx?id=84&UserId=10

     (id=35 is replaced by id=84 because it matched the query string parameter. UserId=10 was not affected because it did not match the alias query string parameter.)

9. Enter the Additional Variables. These are used as query string parameters that can track how visitors arrived at the aliased page. You might use these in marketing campaigns to analyze the source of an aliased page’s visitors. For example, the Additional Variables field has ?gclid=CO7gs_L0_ZICFRkTIgodBgV9CQ. Your website's analytics software can track the source of the query through the variable.

   NOTE: Within the page load event that returns the query string parameters, use the Request.RawURL() property instead of request.querystring.

10. In the Content Block section, click Browse. The QuickLink Select window appears.

    NOTE: Content choices are affected by value of the Language field on the Add Manual Alias screen. Only content in the language of the selected alias appears. Also, only approved content appears.

11. Browse through the folder structure and click on the content to which you are assigning the alias. The Title and Quicklink fields are filled.

    NOTE: A folder’s content appears below its subfolder list. You may have to scroll down to see the content.

12. Click Save.

Activating/Deactivating a Manual URL Alias

1. Go to Workarea > Settings > Configuration > URL Aliasing > Aliases. The Aliases screen appears.
2. Click Edit.
3. In the Active column, check the box next to any alias to activate it; uncheck the box to deactivate it. Check the box next to the Active heading to activate all aliases in the list; uncheck to deactivate.
4. Click Save.

Removing a Manual URL Alias

1. Go to Workarea > Settings > Configuration > URL Aliasing > Aliases. The Aliases screen appears.
2. Select Manual from the Type drop down to display only manual aliases.
3. Click Edit.
4. In the Delete column, check the box next to any alias that you want to remove. Check the box next to the Delete heading to select all aliases in the list; uncheck to clear the check boxes.
5. Click Save.

Automatic URL Alias Pattern

Automatic URL alias pattern combines the following elements—separated by a slash (/)—in the following order.

1. site root
2. taxonomy, folder, group, or user path.
   • Spaces are replaced by the replacement character; the default is underscore (_). When you create a new rule, you can specify replacement characters in the Replacement Character Map field on the Add Aliasing Rule screen.
   • A taxonomy path has taxonomy nodes from the top to the level at which content is assigned. For example: www.example.com/Medical_Conditions/Kidney_Disease/.
   • A folder path has folders from the top-level to the folder that contains the content. For example: www.example.com/CMS400Developer/CMS400Demo/About_Us/Company_Profile/Board_of_Directors.aspx. You can determine which path components appear in the Customize Alias Path field on the Add Aliasing Rule screen.
   • A group path may identify the Marketing group: http://www.example.com/Marketing/.
   • A user path may identify a community profile for a user: http://<website>/John/
3. content name source

   Spaces are replaced by the replacement character.

4. extension

NOTE: Aliases must be unique. If you try to create a duplicate alias, a value is appended to the alias to make it unique.

Examples:

Folder-based automatic alias

Suppose that you assign an automatic folder alias called “History” to the MainSite/Content/Company/Company_News/ folder and you specify the additional rule that excludes some of the folder path from the URL. When you create NewHistoryEvent.aspx and put it in the Company_News folder, it has the following URL automatically generated:

www.example.com/Company_News/New_History_Event.aspx

Taxonomy-based automatic alias

Suppose that you create a new job posting called SalesAdministrator and give it the Administration and Sales taxonomy categories.

SiteNavigation
  Company
    Jobs
      [x] Administration
      [x] Sales
      [ ] Marketing
      [ ] Engineering
      [ ] Support

A taxonomy-based alias automatically generates the following URLs based on the taxonomy selections:

www.example.com/Jobs/Sales/SalesAdministrator
www.example.com/Jobs/Administration/SalesAdministrator

User-based automatic alias

A user alias can simplify a reference to someone’s profile page.

www.example.com/member/steve

Group-based automatic alias

A group alias can simplify a reference to a group page.

www.example.com/group_interest/sports_cars

NOTE: Activity streams, SMSShort Message Service (SMS); used for texting., and email notification messages that include links to users or community groups use the community URL alias in their links. If you want to show the template alias, use the proper token in the message. For example, to use the alias for the SubjectUser, use the @SubjectUser.TemplateAlias@ token in your message. See Also: Working with Tokens.

If you enable a user-based community alias, community users display their alias name on their profile's Profile Links tab.

Similarly, if you enable a group-based community alias, community groups display their alias name on the profile's Links tab.

Creating/Editing Automatic URL Aliasing Rules

After enabling automatic URL aliasing, you can create rules in a configuration, which lets you

• identify the content source (that is, a taxonomya content-level categorization system that uses one-to-many relationships (such as Ronald Reagan is to Actor, Governor, and President) to create a scalable organization of content. A taxonomy lets your site visitors navigate content independent of the folder structure., folder, user, or group)
• choose elements of the aliasing pattern
• preview sample original and aliased URLUniversal Resource Locators

NOTE: You cannot create a configuration whose values match an existing one.

1. Go to Workarea > Settings > Configuration > URL Aliasing > Aliasing Rules > Automatic. The Automatic Aliasing Rules screen appears.
   —Image—

   

2. Click on an existing rule, or click Add Aliasing Rule. A rules screen appears.
   1. Specify a unique name for the new automatic rule.
   2. Check the Active field if you want the rule to apply immediately after it is created.

      WARNING! If you uncheck this box, automatic aliases set up using this configuration are deleted from the associated content.

   3. If you have more than 1 site, choose the site to which the rule applies.
   4. Select the Source Type (Taxonomy, Folder, User, Group).
   5. Click Next. The rules screen appears.
      —Taxonomy Rules—

      

      —Folder Rules—

      

      —User Rules—

      

      —Group Rules—

      

3. Specify the following rules:
   • Alias Root (Taxonomy, Folder)—Navigate to and choose a taxonomya content-level categorization system that uses one-to-many relationships (such as Ronald Reagan is to Actor, Governor, and President) to create a scalable organization of content. A taxonomy lets your site visitors navigate content independent of the folder structure. or folder to which you want to assign an automatic alias.
     • If you choose a taxonomy, the automatic alias is applied to all content assigned to it and its child nodes. Furthermore, if your Ektron supports multi-site configurations, the automatic alias applies to content in all sites. This is because taxonomy is site independent.
     • If you choose folder, the automatic alias applies to content in that folder and its subfolders. The taxonomy or folder is part of the automatic alias pattern.
   • Exclude from Path (Taxonomy, Folder)—The automatic alias pattern displays folders or taxonomy levels from the top to the level you select. You can use this field to control which folders or taxonomy levels appear in the pattern. For example, if your Alias Root is based on the following folder path: /CMS400Demo/About Us/Careers, you can choose any option from the drop-down menu to indicate the folder or taxonomy path in the automatic alias pattern.
   • Alias Prefix (User, Group)—Add a prefix to the alias.
   • Alias Format (Taxonomy, Folder)—Use this field to help construct the automatic alias pattern. Choose 1 of the following items to identify the content within the alias.
     • Content Title—Example: Sample Content Block
     • Content Id—Example: 30
     • Content Id and Language—Example: 30/1033
   • Extension—Use this field to help construct the automatic alias pattern. Choose an extension from the list to identify the end of the aliased URL. Extensions are defined in the Extension field of the URL Aliasing Settings screen.

     Do not add any extension entered into the Handler Mapping list. See Restrictions on Extensions

   • Template (Taxonomy)—Choose Taxonomy Template or Quicklink. The alias target URL will be the template of the content item being aliased, along with any querystring parameters (for example, content.aspx?id=123). Taxonomy Template can have its own template assigned to the taxonomy node. When creating the automatic alias, this setting indicates which template to use for the target URL. Quicklink uses the behavior just described. Taxonomy Template uses the template assigned to the designated taxonomy along with the querystring parameters from the Quicklink. For example:
     • Taxonomy Template
       • Content ID 123, assigned to template content.aspx
       • Content assigned to Taxonomy X
       • Taxonomy X has a template taxtemplate.aspx
       • Taxonomy alias rule created targeting Taxonomy X
     • Quicklink
       • Quicklink = /content.aspx?id=123
       • Alias Target with Quicklink Template Field selected = /content.aspx?id=123
       • Alias Target with Taxonomy Template Field selected = /taxtemp.aspx?id=123
   • Query String Param (Taxonomy, Folder)—Enter the query string parameter for this alias. For example, if the alias uses a taxonomy, you could entertaxid. Here is an example of the parameter in a URL: http://localhost/eIntranetv2/Blogs.aspx?id=238&blogid=115&taxId=28

     IMPORTANT: Do not enter id here because that will clash with the content id.

     Do not enter more than one parameter.

   • Example Preview—shows what the alias will look like. To see any content item’s fully aliased URL, view the content and click the Alias tab; the alias is in the Automatic section.
   • Replacement Character Map—Accept the default values, or enter the character that replaces prohibited characters in content titles when they appear within an automatic alias. Examples of prohibited characters are a space and question mark (?). So, for example, if the content title is About Us, and you enter an underscore (_) here, the aliased version of the title is About_Us. Specify other replacement characters in the Replacement Character Map section.

     You cannot enter one of the following as the replacement character: [, \ / < > (Space): |? '] # * &%

     NOTE: If you're using IIS Admin, and specify a plus sign (+), you get this error: HTTP Error 404.11 Not Found The request filtering module is configured to deny a request that contains a double escape sequence. For a solution, see Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 404.11 – URL_DOUBLE_ESCAPED".

Deactivating an Automatic URL Aliasing Configuration

If you deactivate an automatic alias configuration, automatic aliases created by that configuration are removed from content to which they are applied. The configuration is saved, so you can reactivate it.

1. Go to Workarea > Settings > Configuration > URL Aliasing > Aliasing Rules > Automatic.
2. Click the alias that you want to deactivate.
3. Click Edit.
4. Uncheck the Active checkbox.
5. Click Save.

Deleting an Automatic URL Aliasing Configuration

If you delete an automatic aliasing configuration, automatic aliases are removed from content to which they are applied.

1. Go to Workarea > Settings > Configuration > URL Aliasing > Aliasing Rules > Automatic.
2. Click Edit List.
3. Check each configuration that you want to delete.
4. Click Save.

   WARNING! No confirmation message appears when you save the Automatic Aliasing Rules screen, so be deliberate when checking the Delete boxes.

Troubleshooting Group or User URL Aliases

If you do not see the community alias when you hover over or click a link to a community group or user, check the following.

• The alias is set to Active.
• The alias is the primary alias.
• The server controla server control uses API language to interact with the CMS and Framework UI to display the output. A server control can be dragged and dropped onto a Web form and then modified. that displays the link does not use the TemplateUserProfile setting. If it does, that value takes precedence over the URL alias.
• If you are using eSync, refresh the cache after a database sync.

Creating/Editing a RegEx Expression

1. Find a site page (such as a blog) whose query string parameters let users guess similar pages using a pattern. For example:

   http://ecmintranet/blogs.aspx?blogmonth=3&blogyear=2013

2. Go to Workarea > Settings > Configuration > Url Aliasing > Aliasing Rules > RegEx. The RegEx Rules screen appears.
   —Image—

   

3. Do 1 of the following:
   • To create a new expression, click Add a Regular Expression. The RegEx Alias screen appears.
   • To edit an existing expression:
     1. Click Edit List.
     2. Click the expression you want to modify. The RegEx Rule screen appears.
     3. Click Edit.
4. Specify the following RegEx Alias parameters (example entries shown):
   —Image and field parameters—

   

   • Active—Check this box to activate the expression. If the expression is active, site visitors can enter an aliased URL to access a page on your site. For example, they can enter www.example/com/blogs/2013/03/14 to access a blog page even though the actual URL is www.example/com/blogs/blogs.aspx?blogmonth=3&blogyear=2013&blogid=4
   • Site—If you have more than 1 site, choose the site to which this RegEx applies.
   • Expression Name—Assign an easily recognizable name to this regular expression. It appears on the RegEx Rules screen to help users identify it.
   • Expression Library—A link that displays sample expressions.
     —Image—

     

   • Expression—Enter a RegEx expression that will replace the variables (for example, $1, $2, and so on.) in the Expression map. If you want to insert a question mark into the Expression, you must precede it with a backslash (\).
   • Expression Map—Enter a map of original URL elements. The map lets you replace query string parameters with variables, such as $1, $2, and so on. As a result, a site visitor can identify other pages that use this pattern by changing the variable values. You can click Expression Library to view sample RegEx expression maps. To copy any map that resembles your page pattern, click it then modify it.

     As another example, you can create a pattern without knowing in advance what URL a user may type, using a querystring variable. When a user types:

     www.example.com/catalog/search/christmas

     The alias can use a querystring variable after catalog/search/ to see if content is available in the catalog using the following aliased URL:

     www.example.com/catalogsearch.aspx?term=christmas

   • Example URL—Displays an example Web page that follows this pattern.
   • Priority—Assign a priority to this expression from the following choices.
     • high (assign to the most frequently-used expressions)
     • medium
     • low
     • none

     This field enhances the aliasing feature's response time—it first tries to match a site visitor’s entry with high priority expressions, then medium, then low.

Deleting a RegEx Expression

1. Go to Workarea > Settings > Configuration > URL Aliasing > Aliasing Rules > RegEx.
2. Click Edit List.
3. Check the box in the Delete column next to any RegEx you want to delete.
4. Click Save.

1. Open the site folder for which you want to create aliases. (Site folders have a globe icon, like this: ).
2. Click View > Properties.
3. Click Edit Properties.
4. Click the Site Alias tab.
   —Image—

   

5. Enter the alias into the Alias Name field.

   NOTE: The alias cannot end with a slash (/).

   From now on, if a site visitor enters the alias into a browser address field, he is redirected to the site URL (set on the folder properties tab’s Production Domain field).

   —Image—

   

6. Add each site alias as an IIS host. To learn how do this for your server, please consult IIS help.

Editing a Site Alias

1. Open the site folder for which you want to create aliases. (Site folders have an icon, like this: ).
2. Click View > Properties.
3. Click Edit Properties.
4. Click the Site Alias tab.
5. Click the alias that you want to edit. When you do, it is highlighted and appears in the Name field.
6. Change the alias text.
7. Click Save.
8. Click Update.

Deleting a Site Alias

1. Open the site folder for which you want to create aliases. (Site folders have a globe icon, like this: ).
2. Click View > Properties.
3. Click Edit Properties.
4. Click the Site Alias tab.
5. Click the alias that you want to edit. When you do, it is highlighted and appears in the Name field.
6. Click Delete (). The alias is deleted.