Kristoffer Petersson
Oct 30, 2009
  6255
(1 votes)

Friendly Url and mobile phones

The EPiServerFriendlyUrlRewriteProvider in EPiServer CMS 5.2 SP2 can cause navigational problems for visitors using mobile phones. I have noticed that the browser in some Ericsson mobile phones does not handle friendly URL’s very well.

Recently this became a problem for a site I have been working on. Menus and all navigation worked well in standard web browsers, however navigating the site from my Ericsson mobile phone was simply not possible. EPiServer lost track of the current page and all menus were loaded from the root page.

One obvious solution was to use the EPiServerNullUrlRewriteProvider and go back to using the old style URL’s (somefolder/somepage.aspx?id=12345). This was not possible for the site I was working on.

My solution was to stop the rewriting of URL’s pointing to pages design for mobile phones and handle the loading of these pages in code.
The first step is to stop rewriting of specific URL’s, in my case all paths containing “/mobile”. This can bee done in Global.asax.

In Application_Start add the following:

EPiServer.Web.UrlRewriteModule.HttpRewriteInit += UrlRewriteModule_HttpRewriteInit;

Then add the following to Global.asax

private void UrlRewriteModule_HttpRewriteInit(object sender, UrlRewriteEventArgs e) { UrlRewriteModuleBase module = sender as UrlRewriteModuleBase; if (module != null) { module.HtmlAddingRewriteToExternalFilter += module_HtmlAddingRewriteToExternalFilter; } } private void module_HtmlAddingRewriteToExternalFilter(object sender, UrlRewriteEventArgs e) { string path = e.Url.Path.ToLowerInvariant(); e.Cancel = path.Contains("/mobil"); }

Now rewriting will be cancelled for URL’s containing “/mobile”. However this alone did not solve the problem. EPiServer still couldn’t load the correct page. The second step is to handle loading of pages.

I retrieve the PageData object for the desired page using the ID-parameter from the raw URL.

PageData pd = null; System.Text.RegularExpressions.Match m = System.Text.RegularExpressions.Regex.Match(url, "(\\?id=)[0-9]*"); if (!String.IsNullOrEmpty(m.Value) && int.TryParse(m.Value.Remove(0, 4), out id)) { pd = DataFactory.Instance.GetPage(new PageReference(id)); } return pd;

With use of the PageData object I can load the correct page, access properties and initiate menus. Problem solved for now. I am looking for a better solution, do you have one?

Oct 30, 2009

Comments

Sep 21, 2010 10:32 AM

Do you know why it does it not work well with the phone? Are the Friendly URL:s to long?

Or do you have the old style links with ID parameter that you want to use? If you want to make id to work you have to take care of this in ConvertExternalToInternal instead since the id and epslanguage parameter is is deleted from the query string by FURL.

Turning off outgoing FURL filter is not recommended and it has a lot of other side effects.
/ Fredrik Haglund (INEXOR AB)

Sep 21, 2010 10:32 AM

No I do not know why, nor does EPiServer. The URL's are not to long, they can be even longer with old style links. The problem was reported as a bug in a previous version of EPiServer CMS5 and has now been fixed. This seems to be a new bug or a local fault in the site. I tried using ConvertExternalToInternal but could not make it work for me. At least this solution works and it is contained to a small portion of the site.
Thank you for your comment

/ Kristoffer

MuraliKrishna@websynergies.biz
MuraliKrishna@websynergies.biz Jul 13, 2011 06:52 AM

Hi,
I am new to Mobile version.Can any one suggest me how to develop a simple page to view in mobiles?...........

MuraliKrishna@websynergies.biz
MuraliKrishna@websynergies.biz Jul 18, 2011 09:36 AM

OK.My problem is fixed.i used EPIModule and Mobile Pack to view the pages of mobile version in episerver cms......still i hv to view it in IPhone.......

Please login to comment.
Latest blogs
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog