Try our conversational search powered by Generative AI!

Stefan Forsberg
May 7, 2009
  6269
(0 votes)

Page Provider – Part three

Mapping your data to properties on the episerverpage is a fairly simple process. In the GetLocalPage method we simple use the SetValue on our created PageData object.

The standard page has two properties called MainBody and  SecondaryBody so let’s set some values on those properties.

protected override EPiServer.Core.PageData GetLocalPage(EPiServer.Core.PageReference pageLink, EPiServer.Core.ILanguageSelector languageSelector)
{
    PageData pageData = new PageData();
 
    Development.DataAbstraction.SimplePage activeSimplePage = GetSimplePage(pageLink);
    
    // Finds the parent to our page.
    PageReference parentLink = (pageLink.ID == parentPage.ID) ? base.EntryPoint : base.ConstructPageReference(parentPage.ID);
 
    base.InitializePageData(
        pageData, 
        activeSimplePage.Name, 
        standardPageType.Name, 
        activeSimplePage.Guid, 
        pageLink, 
        parentLink, 
        new List<string>() {}
        );
 
    pageData.SetValue("MainBody", "Some text");
    pageData.SetValue("SecondaryBody", "Some other text");
 
    return pageData;
}

01

This works well for simple string based properties  (both MainBody and SecondaryBody are of type xhtml string). So let’s try to work with a more complex property type, for instance the link collection. To do this we start with adding a property of that type called Links to our standard page page type.

To get a feel for how this works let’s start with just setting the property to some string value and see what happens.

   1: pageData.SetValue("Links", "Link1");

This leads to the exception System.ArgumentException: Passed object must be of type LinkItemCollection. So apparently we need to create a LinkItemCollection and map it to the property data.

EPiServer.SpecializedProperties.LinkItemCollection links = new EPiServer.SpecializedProperties.LinkItemCollection();
 
EPiServer.SpecializedProperties.LinkItem linkItem = new EPiServer.SpecializedProperties.LinkItem();
linkItem.Href = "http://www.aftonbladet.se";
linkItem.Text = "Aftonbladet";
 
links.Add(linkItem);
 
linkItem = new EPiServer.SpecializedProperties.LinkItem();
linkItem.Href = "http://www.idg.se";
linkItem.Text = "IDG";
 
links.Add(linkItem);
 
pageData.SetValue("Links", links);

02

This is a somewhat unlikely scenario (to create the links programmatically that is). A more likely task is that the customer wants to add additional info to their data. Say for instance that the customer wants to add some links to their products that they for some reason don’t want or are unable to store in their product database.

What we’d do then is to give the page provider the capabilities to edit the page and when the user saves the page we save the property value of the link collection to some repository and then build logic to fetch the same data on the loading of the page (GetLocalPage).

This is what we’ll explore in the next post.

May 07, 2009

Comments

Please login to comment.
Latest blogs
Solving the mystery of high memory usage

Sometimes, my work is easy, the problem could be resolved with one look (when I’m lucky enough to look at where it needs to be looked, just like th...

Quan Mai | Apr 22, 2024 | Syndicated blog

Search & Navigation reporting improvements

From version 16.1.0 there are some updates on the statistics pages: Add pagination to search phrase list Allows choosing a custom date range to get...

Phong | Apr 22, 2024

Optimizely and the never-ending story of the missing globe!

I've worked with Optimizely CMS for 14 years, and there are two things I'm obsessed with: Link validation and the globe that keeps disappearing on...

Tomas Hensrud Gulla | Apr 18, 2024 | Syndicated blog

Visitor Groups Usage Report For Optimizely CMS 12

This add-on offers detailed information on how visitor groups are used and how effective they are within Optimizely CMS. Editors can monitor and...

Adnan Zameer | Apr 18, 2024 | Syndicated blog