Øyvind Hognestad
Aug 4, 2009
  14033
(1 votes)

Globalization, categories and sorting using LINQ

I have been working with a globalized website for some time and have a couple of tips to share regarding globalization.

I’m using FindPagesWithCriteria to get pages based on categories defined on pages. As we teach during the EPiServer developer course FindPagesWithCriteria uses queries directly to the database. The method has got a performance boost in EPiServer CMS5, but should never be used on a typical landing page without caching.

Categories are quite useful if you do not need the complete Topic Maps structure. Anders Hattestad has written a nice post on how to create a custom property to display a part of the categorytree.

Well, back to the topic. Using FindPagesWithCriteria will not return the pages as they are displayed in editmode with fallback and replacement languages (which I hopefully thought). After some testing I found that the best way to get the pages I needed was to use LanguageSelector.AutoDetect(true) as the last parameter.

   1: PageDataCollection pages = 
   2: DataFactory.Instance.FindPagesWithCriteria(searchFrom, crits, 
   3: language, LanguageSelector.AutoDetect(true));

The pages collection will now also contain pages not translated to the current language. So, with a little help from reflector I removed the unwanted pages like this.

   1: public static PageDataCollection FilterForFallbackLanguages(PageReference pageLink, string languageBranch, PageDataCollection result )
   2:        {
   3:            PageLanguageSetting setting = PageLanguageSettingsTree.Instance.Get(pageLink, languageBranch);
   4:  
   5:            if (setting != null)
   6:            {
   7:                List<string> fallback = new List<string>(setting.LanguageBranchFallback);
   8:  
   9:                for (int i = result.Count - 1; i >= 0; i--)
  10:                {
  11:                    if (result[i].LanguageBranch != setting.LanguageBranch && fallback.Contains(result[i].LanguageBranch) == false)
  12:                        result.RemoveAt(i);
  13:                }         
  14:            }
  15:  
  16:            return result;
  17:  
  18:        }

Then my collection was complete. The last step was to sort the collection so the pages of the origin language – Norwegian – came first in the list and the fallback language – English - at the bottom of the list. In addition the sorting inside the language should be PageName. I could write my own comparer or my own filter but a better, and much easier solution, is to use LINQ (thanks Ahsan at support who suggested this solution to a partner in a post I came across while surfing around).

   1: var sorted = from page in pages
   2: orderby page.LanguageID descending, page.PageName ascending 
   3: select page;
   4:  
   5: pageList.DataSource = sorted;
   6: pageList.DataBind();

To get this to work I needed to change the webcontrol which render this list from EPiServer:PageList to Asp:Repeater. EPiServer:PageList do not support this and you will get an error like this if you try.

System.NotSupportedException: Specified method is not supported.

After changing the webcontrol from EPiServer:PageList to Asp:Repeater, remember to use the FilterForVisitor.Filter(pages); to set the right security and remove the unpublished pages.

 

Globalization is cool, it works like a charm in most cases, but be aware of that the time used to develop could take a little longer than you think. Perhaps more important – put some effort when testing the site after the content is in place and real fallback and replacement language is set.

Aug 04, 2009

Comments

Apr 3, 2017 11:14 AM

Please login to comment.
Latest blogs
Translating Optimizely CMS 12 UI components

Optimizely CMS 12 have been out for a while now, but still some elements haven't been properly translated resulting in a GUI defaulting to english....

Eric Herlitz | Jan 26, 2023 | Syndicated blog

Image preview in Optimizely CMS12 all properties view

With these simple steps, you can now see an Image and its Metadata, including size and dimensions, when editing an Image property in Optimizely...

Tomas Hensrud Gulla | Jan 26, 2023 | Syndicated blog

Setting up the ImageEditor in Optimizely CMS 12

Setting up certain configurations on Opimizely CMS 12 differs quite a bit from prior versions of (Episerver CMS 11 and older). Here's a small guide...

Eric Herlitz | Jan 25, 2023 | Syndicated blog

Happy Hour Returning in February

Hi everyone! It's been a while and we're excited to resume our Happy Hour in February for more learning, sharing, connecting, relaxing, and just to...

Patrick Lam | Jan 24, 2023