Hi Sandy,

If I understand correctly you would like to use the content on the "Settings" page doctype in different views or partials.

This is a scenario that occurs with many Umbraco websites and is easily solved by using the Umbraco Context and the generated model for the "Settings" doctype.

By using so-called .NET extensions this is made even easier and you could apply this to every view or partial.

It is possible to inject the so-called IUmbracoContextAccessor into each view. This is done by means of the following piece of code at the top of the view.

@inject IUmbracoContextAccessor_umbracoContextAccessor;

It is now possible to build an extension on the IUmbracoContextAccessor. The name of this extension is TryGetCurrentSettings() and returns the generated model of the "Settings" doctype which is probably called: Settings.cs. The implementation of this extension looks like this:

public static class UmbracoContextAccessorExtensions
{
    public static Settings? TryGetCurrentSettings(this IUmbracoContextAccessor umbracoContextAccessor)
    {
        using (var contextReference = umbracoContextAccessor.GetRequiredUmbracoContext())
        {
            //Trying to retrieve the homepage (root node)
            var homepage = contextReference?.Content?.GetAtRoot()?.OfType<Homepage>()?.FirstOrDefault();
            if (homepage == null)
                return null; //Homepage has not been found.

            //Trying to retrieve the settings page
            Settings? settings = homepage.FirstChild<Settings>();
            return settings;
        }
    }
}

The above solution will only work if the "Settings" doctype is located somewhere under the "Homepage" in the content tree. If the doctype "Global" is a root node itself it wont work. Please contact me if this is the case.

It is now possible to read the Settings in a view or partial by applying the following logic.

@inject IUmbracoContextAccessor _umbracoContextAccessor;
@{
   Settings? currentSettings = _umbracoContextAccessor.TryGetCurrentSettings();
   if (currentSettings == null)
      return; //Will not render
}

Let me know if this helps!

Greetings, Joppe

Here's how I access mine a lil different than Joppe...

SiteSettings siteSettings = (SiteSettings)Umbraco.Content("6214009f-38e1-408f-89b0-bc5dcc9254dc");

SiteSettings is the DocType, and that part between the "" is the id from the info tab on that content node. I reference that at the top of my TemplateMaster.cshtml and can use the siteSettings.AttributeName to access the various attribute values.

Hope that helps.

The solution that BH gave would indeed work. However, there are a number of reasons why I do not use this method.

• A hardcoded GUID string is used. If the pages are not staged between environments (by using uSync complete) but are created manually, the GUID of the pages would differ on each environment. This can be solved by using so-called "environment variables" but I do not see the advantage of this. Personally, I find it easier to directly look up the first node of the type "Settings" instead of directly referring to an ID.

• An explicit cast is done by using (SiteSettings). This is of course possible, but by using generics (

• The solution is not easy to maintain because the logic is not managed in 1 place. If you add this piece of code to every view and change the ID of the SiteSettings page (the GUID) then you will also have to adjust this in every view. It is easier to write the retrieval of the site settings in a function.

• The solution cannot be reused in any future solution within for example Services because the object Umbraco is not available outside views but the IUmbracoContextAccessor is (even available in the Core package of Umbraco).

I can imagine that the above may come across as "dramatic" and that this is not necessary for a relatively simple setup of an Umbraco site. If this is the case, I would definitely use BH's solution, but with one caveat: store the hardcoded GUID string in a static variable somewhere in the code so that it is easier to manage if it changes.

If you are interested in the other version of my solution, please let me know!

Greetings, Joppe

is working on a reply...