An Alias is an alternate path for an item when browsing the web site. In other terms we can have URL alias in Sitecore.
Suppose, you have an item's URL as:
http://mysite.com/news/2013/cricket/
Now, you want the same page to be opened using some alternate URLs like:
http://mysite.com/cricket-news/
OR
http://mysite.com/news-cricket/
This is quite possible using AliasResolver in Sitecore.
See below image how alias can be set for this item.
/Sitecore/System/Aliases/Site-A/Alias1
/Sitecore/System/Aliases/Site-A/Alias2
/Sitecore/System/Aliases/Site-B/Alias1
/Sitecore/System/Aliases/Site-B/Alias2
See below snap:
This structure might change depending on what folder structure you follow. See how code will go for Custom AliasResolver:
- Sitecore Alias for multisite solution - Marketplace Module
Suppose, you have an item's URL as:
http://mysite.com/news/2013/cricket/
Now, you want the same page to be opened using some alternate URLs like:
http://mysite.com/cricket-news/
OR
http://mysite.com/news-cricket/
This is quite possible using AliasResolver in Sitecore.
How to configure
We will create two different aliases cricket-news and news-cricket under /sitecore/system/aliases/. Both items will have same configuration, means both will point to content item /sitecore/content/Home/News/2013/Cricket/ So, AliasResolver read these settings and work accordingly.See below image how alias can be set for this item.
How can we know URL of alternate URL or Alias?
To see if an alias exists, use the database.Aliases.Exists() method. This will check if both the alias exists and the target item exists sd below:// Code from Sitecore.Pipelines.HttpRequest.AliasResolver class Database database = Context.Database; if (database == null) { Tracer.Warning("There is no context database in AliasResover."); } else { if (database.Aliases.Exists(args.LocalPath) && !this.ProcessItem(args)) { this.ProcessExternalUrl(args); } Profiler.EndOperation(); } private void ProcessExternalUrl(HttpRequestArgs args) { string targetUrl = Context.Database.Aliases.GetTargetUrl(args.LocalPath); if (targetUrl.Length > 0) { this.ProcessExternalUrl(targetUrl); } } private void ProcessExternalUrl(string path) { if (Context.Page.FilePath.Length <= 0) { Context.Page.FilePath = path; } }
What to do in multisite environment?
In multisite environment, we can still use this functionality. We can customize the AliasResolver processor in HttpRequestBegin pipeline, where the alias items will be stored in Site specific folder, so, the Custom AliasResolver will search aliases in site folder only. We can create a alias folder structure site-wise, something like,/Sitecore/System/Aliases/Site-A/Alias1
/Sitecore/System/Aliases/Site-A/Alias2
/Sitecore/System/Aliases/Site-B/Alias1
/Sitecore/System/Aliases/Site-B/Alias2
See below snap:
This structure might change depending on what folder structure you follow. See how code will go for Custom AliasResolver:
namespace SitecoreTactics.Pipelines.HttpRequestBegin { class CustomAliasResolver : AliasResolver { public new void Process(HttpRequestArgs args) { Assert.ArgumentNotNull(args, "args"); if (!Settings.AliasesActive) { Tracer.Warning("Aliases are not active."); } else { Sitecore.Data.Database database = Sitecore.Context.Database; if (database == null) { Tracer.Warning("There is no context database in AliasResover."); } Item aliasItem = getAliasItem(args); if (aliasItem != null) { LinkField linkField = aliasItem.Fields["Linked item"]; if (linkField != null) { Item AliasLinkedTo = Sitecore.Context.Database.GetItem(linkField.TargetID); if (AliasLinkedTo != null) { Sitecore.Context.Item = AliasLinkedTo; } } else { base.Process(args); } } } } ////// Gets the alias item. /// /// The args. ///private Item getAliasItem(HttpRequestArgs args) { string siteName = Sitecore.Context.Site.RootPath.ToLower(); if (args.LocalPath.Length > 1) { Item aliasItem = Sitecore.Context.Database.GetItem("/sitecore/system/Aliases/" + siteName + "/" + args.LocalPath); if (aliasItem != null) { return aliasItem; } } return null; } } }
Read more about Sitecore alias:
- Sitecore language based Alias- Sitecore Alias for multisite solution - Marketplace Module
Is it possible to define and use/consume different rendering on alias items in the UI?
ReplyDeleteBy default it's not possible. But yes, you can achieve this using Personalization rules based on URL referrer or URL, on the content item layout details.
DeleteHi Can we use alias for below requirement .
ReplyDeleteMy URL is like below :
https://www.example.org/-/media/Service%20Areas/Data/PDFs/2017-living-well-flyer
The desired future:
https://www.example.org/Data/PDFs/2017-dh-living-well-flyer
can anyone help on this.
Yes, this is possible in Sitecore 8. Not sure from which version Sitecore started supporting media items, but that works in Sitecore 8.1.3+.
Delete