Anders Hattestad
Mar 7, 2011
  3207
(1 votes)

Dynamic Properties with versioning V0.9

One thing I miss a lot is version on dynamic properties. I have been looking for clean solutions to add that to EPiServer, an think I have come up with an concept that can work, while we wait for CMS 7.

I have borrowed some code from Itera.Objects, that can display other properties inside one property. and used that together with Page Objects.

The concept is simple, I have one property that have all the dynamic properties inside it. When I save the page, I also save the dynamic properties inside the Page Object store. If the property is set to inherit, I delete the value from the store on this page. But my get value method checks all the stores up to the top to find the value.

image

As you can see from this picture the value for Writer is retrieved from page id 7 in en.

The pointers here is that we have to make the owner property be modified when a dynamic property is changed. This is because we need to trigger the save event. I also save the values after the page is saved, so the version is correct.

When I need to retrieve the dynamic property value I have made my own property handle. That load the values based on the page.

Hade a lot more of code in this blog post, but Live writer died, and I didn’t have any backup :(, but the core saving is done by creating a class that have the value for the property. This is because its a bit tricky to save a property data object to the store.

Code Snippet
  1. static void Instance_SavedPage(object sender, EPiServer.PageEventArgs e)
  2. {
  3.     foreach (var prop in e.Page.Property)
  4.     {
  5.         if (prop is PropertyDynamicProperties)
  6.         {
  7.             PageObjectManager pom = new PageObjectManager(e.Page);
  8.             foreach (var dynProp in (prop as PropertyDynamicProperties).AllDynamicProperties)
  9.             {
  10.                 if (dynProp.InheritValue)
  11.                 {
  12.                     pom.Delete(dynProp.Name);
  13.                 }
  14.                 else
  15.                 {
  16.                     if (dynProp.Property.IsNull)
  17.                         pom.Delete(dynProp.Name);
  18.                     else
  19.                     {
  20.                         if (dynProp.Property.IsLanguageSpecific)
  21.                             pom.Save(dynProp.Name, DynProperyStoreValue.GetObjectFromProperty(dynProp.Property, e.Page.Property), PageObject.OwnerOption.PageLanguageBranch);
  22.                         else
  23.                             pom.Save(dynProp.Name, DynProperyStoreValue.GetObjectFromProperty(dynProp.Property, e.Page.Property), PageObject.OwnerOption.PageVersion);
  24.                     }
  25.                 }
  26.                 }
  27.             }
  28.         }
  29.     }
  30. }

So i do it like this. As you can see I use the different methods of storing into the Page Object store depending on the dynamic property is unique pr languages or not.

The full code can be found in the code section.

What you need to do is to create a property of type DynamicProperties on each page type, and you are good to go.

Mar 07, 2011

Comments

Please login to comment.
Latest blogs
Creating an Optimizely CMS Addon - Adding an Editor Interface Gadget

In   Part One   of this series, I covered getting started with creating your own AddOn for Optimizely CMS 12. This covered what I consider to be an...

Mark Stott | Aug 30, 2024

Configure your own Search & Navigation timeouts

The main blog Configure your own Search & Navigation timeouts was posted for years but you need copy the code to your application. We now bring tho...

Manh Nguyen | Aug 30, 2024

Joining the Optimizely MVP Program

Andy Blyth has been honoured as an Optimizely MVP, recognising his contributions to the Optimizely community. Learn how this achievement will enhan...

Andy Blyth | Aug 29, 2024 | Syndicated blog

Welcome 2024 Summer OMVPs

Hello, Optimizely community! We are thrilled to announce and welcome the newest members to the Optimizely Most Valuable Professionals (OMVP) progra...

Patrick Lam | Aug 29, 2024