Yugeen Klimenko
Feb 8, 2011
(1 votes)

Common properties amongst the pages

Instead of using a lot of dynamic properties one can create a special settings page. On this page all site-wide settings are saved all together. Then you make only the name of this page to be a dynamic property (ref. to http://www.meadow.se/wordpress/?cat=12). This is a common solution. However, code in the code-behind files becomes a little more complicated if you want to retrieve the settings from the settings page.

For example:


        propertyCriteriaCollection = new PropertyCriteriaCollection();

PropertyCriteria criteria = new PropertyCriteria();

criteria.Condition = CompareCondition.Equal;

criteria.Name = "PageTypeID";

criteria.Type = PropertyDataType.PageType;

criteria.Value = PageType.Load("SettingsPage").ID.ToString();

criteria.Required = true;


PageDataCollection pageDataCollection

                = DataFactory.Instance.FindPagesWithCriteria

                    (PageReference.RootPage, propertyCriteriaCollection);

if (pageDataCollection == null || pageDataCollection.Count == 0)



if (pageDataCollection[0]["SomeProperty"] != null)

                TextBox1.Text =

                       pageDataCollection[0] ["SomeProperty"].ToString();


You see how many actions should be performed with a single aim – to get the SettingsPage’s SomeProperty value. Evidently it’s tiresome and error prone.

Instead you can force the page to load properties values from some other page. For this just open the Shortcut/External Link tab in edit mode, assign  “Fetch data from page in EPiServer CMS” to Link type , and choose the page the properties are loaded from (f.e. SettingsPage):


From this time you can apply to SettingsPage as if they belonged to the w1ef page:

string someProperty = CurrentPage["SomeProperty"] as string;


<EPiServer:Property PropertyName="SomeProperty" runat="server" />

Feb 08, 2011


Feb 8, 2011 04:18 PM

What if you need both settings and data from another page? I like the PluginProperty approach:

Description = "PageTypeID: Start Page",
AdminControl = typeof(InputPageType),
AdminControlValue = "PageTypeID")]
public int StartPageTypeID { get; set; }

... and a singelton class to retrieve them.

Yugeen Klimenko
Yugeen Klimenko Feb 8, 2011 05:26 PM

Sure, it's suitable if you want to get data from one page (not more)

Yugeen Klimenko
Yugeen Klimenko Feb 9, 2011 09:46 AM

Sure, it's suitable if you want to get data from one page (not more)

Please login to comment.
Latest blogs
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

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

New Optimizely certifications - register for beta testing before November 1st

In January 2023, Optimizely is making updates to the current versions of our certification exams to make sure that each exam covers the necessary...

Jamilia Buzurukova | Sep 28, 2022

Optimizely community meetup - Sept 29 (virtual + Melbourne)

Super excited to be presenting this Thursday the 29th of September at the Optimizely community meetup. For the full details and RSVP's see the...

Ynze | Sep 27, 2022 | Syndicated blog

Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog

The Report Center is finally back in Optimizely CMS 12

With Episerver.CMS.UI 12.12.0 the Report Center is finally re-introduced in the core product.

Tomas Hensrud Gulla | Sep 26, 2022 | Syndicated blog