Unfortunetly, there is no support for this in EPiServer 7.
In the next version (EPiServer 7.5) there will be support for specifing custom roots for content selectors. Meaning that, in your scenario, you could specify the contact repository root as the root for the content selector and only content beneath that will be available to select.
You could try Joel's approach that means you cut out searching through the tree completely and simply present a list of contact page types:
@Ben: Looking forward to that, it is really useful to have such option.
@David: Thanks, I have used ideas from Joel's approach so that we have now drop-down with all contact pages instead of tree selector.
Hi,
Assume you have some complicated multi-level structure. Somewhere in the structure there is a contact pages repository and now on some page type there is a PageReference property which allows to select contact page
[CultureSpecific]
[Display(Order = 10)]
public virtual PageReference ContactPerson { get; set; }
now when editor is going to edit mode he/she needs to find in complicated structure location of contact repository, is it possible to force page selector dialog to be opened in some predefined location? (localize repository so that editor in initial state is already in correct location to pick up the page he needs). Of course when there is already selected some page it should be opened.
Thank for any help