If you have a template-less content type of settings and then have a single settings content node at the root of a site, you can write an extension method that can find the settings content.

Here is some example code for you:

using System.Linq;
using Umbraco.Core.Models;
using Umbraco.Web;

namespace MySite.Web.Extensions
{
    public static class PublishedContentExtensions
    {
        /// <summary>
        /// Find the settings content for a site. This approach allows all sites in a multi site setup to have their own individual settings node,
        /// and also allows for multiple setting nodes within a site, for example if you have different sections.
        /// </summary>
        /// <param name="current"></param>
        /// <param name="contentTypeAlias"></param>
        /// <returns></returns>
        public static IPublishedContent GetSiteSettings(this IPublishedContent current, string ancestorContentTypeAlias = "home", string settingsContentTypeAlias = "settings")
        {
            IPublishedContent settings = null;
            var ancestor = current.AncestorOrSelf(ancestorContentTypeAlias);

            if(ancestor != null)
            {
                settings = ancestor.Children.SingleOrDefault(c => c.DocumentTypeAlias == settingsContentTypeAlias);
            }

            return settings;
        }
    }
}

Then in your views or wherever an instance of IPublishedContent is being consumed you can use any setting you have, for a content picker for example, in a razor view:

@{
    var settings = @Model.Content.GetSiteSettings();
    var stockistContent = Umbraco.TypedContent(settings.GetPropertyValue<int>("stockistContentPicker"));
}

@stockistContent.Url;

Thanks

P.S The above code is untested, I just wrote this here top of my head. You may want to refactor, you can also add a generic type argument incase you're using strongly typed models. So you could have the following as well:

GetSiteSettings<T>...

Am I right in thinking you have just one 'stockist' page type? If so I'm confused as to why you need to set this up in multiple content pickers as you described above?

If not, then maybe I've not drank enough coffee yet this morning. :)

Not sure I'm following you. Where do you need to use these other url's? For the use in nav menus? If so then why not just iterate from the home site downwards and build your menus based on umbracoNaviHide or a custom property in your Razor views?

Something like this:

@inherits Umbraco.Web.Macros.PartialViewMacroPage


@*
    Macro to display child pages below the root page of a standard website.
    Also highlights the current active page/section in the navigation with
    the css class "current".
*@

@{
    @* Get the root of the website *@
    var root = CurrentPage.AncestorOrSelf(1);
}

<ul>
    @foreach (var page in root.Children.Where("Visible"))
    {
        <li class="@(page.IsAncestorOrSelf(CurrentPage) ? "current" : null)">
            <a href="@page.Url">@page.Name</a>
        </li>
    }
</ul>

You should only use a content picker for providing content editors a way to set links to pages, for use with content (say a media gallery, list or such).

I'm with you now. :)

The solution you posted above looks good, and that combined with content pickers is how most of us do it 99% of the time I would think. Just be aware of the following:

• It only works if there is only one content node of a given type/alias.
• You will run into problems if you have multiple root nodes, say in a multi site setup, in which case you'd want to be more specific in the xpath query.
• This relies on a context that has Umbraco helper readily available. If you wanted to ever fetch URL's elsewhere you'd need to make sure to have an instance of UmbracoHelper.

Even given the above, I can't think of any other solution that is as straightforward to implement as this one. Anything else, even if it solved the above rarities, would be overkill I think, since in my opinion standalone querying of any content's URL should be a rarity.

Thanks