PropertyData object with name "FooBar" already exists

Wed, 02 May 2012 16:51:00 GMT

I ran into this during the weekend while I did some work from home. The site I was working on is running EPi6r2 with PageTypeBuilder and I was just adding a couple of new properties for a page type when I suddenly and unexpectedly got the yellow screen of death exception message thrown a me. I couldn't access any page, nor the edit or admin modes.

Googling a little, there was some talk on forums and blogs about the problem being related to language handling and such but none of the things I found applied to my situation.

...so I started tracing the origin of the exception back through Reflector and ended up in EpiServer.Core.PropertyDataCollection:

public void Add(string name, PropertyData value)
{
    this.InternalApproveObject(name, value);
    if (base.BaseGet(name) != null)
    {
        throw new ApplicationException("PropertyData object with name \"" + name + "\" already exists");
    }
    value.Parent = this;
    base.BaseAdd(name, value);
}

EPi, rightfully I might add, detected that I had added more than one property with the same name. (On a side note, I can think of a bunch of more pleasant behaviors to handle property doublets than to just throw an Application Exception; use the first (lowest id) and automatically remove the clones, rename the clones using a prefix or suffix, etc.). How could I add several properties with the same name on the same page type? To be honest I'm not exactly sure but I think this is what might have happened:

First off, at the time I was on a fairly slow Wifi connection, running the site locally but connecting it to a remote database over VPN. The fact that, after compiling. I hit the reload button in Chrome for both the site, edit mode and admin mode in three different tabs pretty much at the same time probably also contributed since, iirc, they each run as a separate application. Delays in contact with SQL probably enabled PTB to insert multiple copies of the same property from the different applications in question.

Once I figured this out it was easy enough to manually edit out doublets from tblPageDefinition in the database and the site would work as expected again.

Programmatically adding options to EPi CMS 6 R2 drop-down list property when using PageTypeBuilder 2.0

Tue, 21 Feb 2012 11:19:00 GMT

Since EPi CMS had property types with custom settings added I have found the drop-down list (EPiServer.SpecializedProperties.PropertyDropDownList) especially useful for allowing an editor to choose from a few different teaser content block appearances when creating teaser page types. The out-of-the-box approach is for an CmsAdmin or developer to manually add key-value pair type options in the CMS admin mode for the property but when using PageTypeBuilder there is a nice way of adding settings programmatically:

I implemented it in a way so that I can add a drop-down list using the attribute class PropertyDropDownListSettings like this:

[PageTypeProperty(
    EditCaption = "Layout",
    DefaultValue = "default",
    Required = true,
    SortOrder = 11,
    Type = typeof(EPiServer.SpecializedProperties.PropertyDropDownList))]
[PropertyDropDownListSettings(
    Settings = new string[]
    {
        "Default|default",
        "Compact|compact",
        "Video|video",
        "RSS Feed|rss",
        "Wide|wide"
    })]
public virtual string TeaserLayout { get; set; }

Attribute classes only accept primitive constants and arrays of primitives as parameters and I wanted to add one to many name-value pairs of <string, string>. I settled for a string array with pipe separated pairs and some old fashioned string handling in the UpdateSettings method. I only tested this lightly so the following may be subject to update:

using System;
using System.Text;
using EPiServer.Web.PropertyControls.PropertySettings;
using PageTypeBuilder;

public class PropertyDropDownListSettingsAttribute : Attribute, IUpdatePropertySettings<MultipleOptionsListSettings>
{
    //// { "Name|value", "Name|value2", "Name|value3" }
    public virtual string[] Settings { get; set; }

    public bool OverWriteExistingSettings
    {
        get
        {
            return true;
        }
    }

    public int GetSettingsHashCode(MultipleOptionsListSettings settings)
    {
        StringBuilder sb = new StringBuilder();

        foreach (string optionValue in settings.ListOptions.Values)
        {
            sb.Append(optionValue);
        }

        return sb.GetHashCode();
    }

    public void UpdateSettings(MultipleOptionsListSettings settings)
    {
        if (this.Settings != null)
        {
            foreach (string pair in this.Settings)
            {
                string[] splitPair = pair.Split('|');

                if (splitPair.Length >= 2 &&
                    !string.IsNullOrEmpty(splitPair[0]) &&
                    !string.IsNullOrEmpty(splitPair[1]))
                {
                    if (settings.ListOptions.ContainsKey(splitPair[0]))
                    {
                        settings.ListOptions[splitPair[0]] = splitPair[1];
                    }
                    else
                    {
                        settings.ListOptions.Add(splitPair[0], splitPair[1]);
                    }
                }
            }
        }
    }
}

As you can tell, this allows for adding new name-value pairs and updating values for existing names. It's still possible to add additional values in admin mode since UpdateSettings will not remove anything. If a name-value pair is removed in the page type definition class file, then that value must be deleted in admin mode since it will remain active until someone does so.

Blog posts by John Frings

PropertyData object with name "FooBar" already exists

Programmatically adding options to EPi CMS 6 R2 drop-down list property when using PageTypeBuilder 2.0