|Number of votes:||1|
For those of you who are not aware of the Filtered Page Reference property controls I have created please refer to the following two blog posts:
One of the features that was irritating me a bit about the FilteredPageReference property controls I created was their inability to function correctly when they were not page property definitions of a page type.
For example if the property was added programmatically to a page for editing or used by my Multiple Property Controls any property settings set against the property would be lost as they were not persisted through the various popup dialogs.
v1.3 of the assembly persists the property settings in the users session if the property instance does not belong to a PageData object. This ensures that any property settings set either by using my Multiple Property Controls or possibly by the next version of PageTypeBuilder (if it will allow property settings to be programatically defined against a page type property. Joel will this be in the next version?) will be persisted through the various dialogs and the filtered page picking functionality will be consistent wherever it is used. Although session may not be the best solution it was the simplest to implement.
The code example below demonstrates how you would programmatically set the FilteredPageReference property settings while using a property that is based on the Multiple Property Controls.
The FilteredPageReference assembly will only work with EPiServer CMS 6 and onwards.
To install just simply place the assembly into your web applications bin folder. The assembly can be downloaded from
Please feel free to email or twitter me with any feedback @croweman