Our.Umbraco.TagHelpers 0.8.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package Our.Umbraco.TagHelpers --version 0.8.0
NuGet\Install-Package Our.Umbraco.TagHelpers -Version 0.8.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Our.Umbraco.TagHelpers" Version="0.8.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Our.Umbraco.TagHelpers --version 0.8.0
#r "nuget: Our.Umbraco.TagHelpers, 0.8.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Our.Umbraco.TagHelpers as a Cake Addin
#addin nuget:?package=Our.Umbraco.TagHelpers&version=0.8.0

// Install Our.Umbraco.TagHelpers as a Cake Tool
#tool nuget:?package=Our.Umbraco.TagHelpers&version=0.8.0

Our Umbraco TagHelpers

A community project of C# ASP.NET TagHelpers for the Open Source CMS Umbraco


Add the following Nuget Package to your Umbraco website project Our.Umbraco.TagHelpers with Visual Studio, Rider or with the dotnet CLI tool as follows when inside the directory with the .CSProj file for the Umbraco website project.

cd MyUmbracoProject
dotnet add package Our.Umbraco.TagHelpers


With the Nuget package added you need to register the collection of TagHelpers for Razor views and partials to use them. Browse to /Views/_ViewImports.cshtml in your Umbraco project and add the following line at the bottom

@addTagHelper *, Our.Umbraco.TagHelpers


This is a tag helper element <our-dictionary> that will use the current page's request Language/Culture to use a dictionary translation from the Umbraco translation section.

  • Find dictionary key
  • Find translation for Current Culture/Language of the page
  • If no translation found see if we have fallback attribute set fallback-lang or umb-dictionary-fallback-lang
  • Attempt to find dictionary item for that ISO language fallback
  • No translation found - leave default/value inside tag untouched for final fallback
<h3><our-dictionary key="home">My Header</our-dictionary></h3>
<h3><our-dictionary key="home" fallback-lang="da-DK">My Header</our-dictionary></h3>


This is a tag helper attribute that can be applied to any DOM element in the razor template or partial. It will include its element and children on the page if the expression inside the our-if attribute evaluates to true.

Simple Example

<div our-if="(DateTime.UtcNow.Minute % 2) == 0">This will only render during <strong>even</strong> minutes.</div>
<div our-if="(DateTime.UtcNow.Minute % 2) == 1">This will only render during <strong>odd</strong> minutes.</div>

Example Before

@if (Model.ContentPickerThing != null)
    <a href="Model.ContentPickerThing.Url()" class="btn btn-action">

        @if (Model.LinkMediaPicker != null)
            <img src="@Model.LinkMediaPicker.Url()" class="img-circle" />

Example After

<a our-if="Model.ContentPickerThing != null" href="@Model.ContentPickerThing?.Url()" class="btn btn-action">
    <img our-if="Model.LinkMediaPicker != null" src="@Model.LinkMediaPicker?.Url()" class="img-circle" />


This tag helper element <our-macro> will render an Umbraco Macro Partial View and will use the current page/request for the Macro rendering & context.

If you wish, you can modify this behaviour and pass the context/content node that the Macro will render with using an optional attribute content on the <our-macro> tag and passing an IPublishedContent into the attribute. This allows the same Macro Partial View Macro code/snippet to work in various scenarios when the content node/context is changed.

Additionally custom Macro Parameters that can be passed through and consumed by Macro Partial Views are specified in the following way. The key/alias of the Macro Parameter must be prefixed with the following bind:

So to pass/set a value for the macro parameter startNodeId then I will need to set an attribute on the element as follows bind:startNodeId

<our-macro alias="ListChildrenFromCurrentPage" />
<our-macro alias="ListChildrenFromCurrentPage" Content="Model" />
<our-macro alias="ListChildrenFromCurrentPage" Content="Model.FirstChild()" />
<our-macro alias="ChildPagesFromStartNode" bind:startNodeId="umb://document/a878d58b392040e6ae9432533ac66ad9" />

BeginUmbracoForm Replacement

This is to make it easier to create a HTML <form> that uses an Umbraco SurfaceController and would be an alternative of using the @Html.BeginUmbracoForm approach. This taghelper runs against the <form> element along with these attributes our-controllerand our-action to help generate a hidden input field of ufprt containing the encoded path that this form needs to route to.



@using (Html.BeginUmbracoForm("ContactForm", "Submit", FormMethod.Post, new { @id ="customerForm", @class = "needs-validation", @novalidate = "novalidate" }))

    <div class="input-group">
        @Html.TextBoxFor(m => m.Name)
        @Html.ValidationMessageFor(m => m.Name)
        @Html.TextBoxFor(m => m.Email)
        @Html.ValidationMessageFor(m => m.Email)
        @Html.TextAreaFor(m => m.Message)
        @Html.ValidationMessageFor(m => m.Message)
    <input type="submit" name="Submit" value="Submit" />


<form our-controller="ContactForm" our-action="Submit" method="post" id="customerForm" class="fneeds-validation" novalidate>
    <div asp-validation-summary="All"></div>

    <div class="input-group">
        <input asp-for="Name" />
        <span asp-validation-for="Name"></span>
        <input asp-for="Email" />
        <span asp-validation-for="Email"></span>
        <textarea asp-for="Message"></textarea>
        <span asp-validation-for="Message"></span>
    <input type="submit" name="Submit" value="Submit" />


This tag helper element <our-lang-switcher> will create a simple unordered list of all languages and domains, in order to create a simple language switcher. As this produces alot of HTML markup that is opionated with certain class names and elements, you may wish to change and control the markup it produces.

With this tag helper the child DOM elements inside the <our-lang-switcher> element is used as a Mustache templating language to control the markup.


    <div class="lang-switcher">
            <div class="lang-switcher__item">
                <a href="{{Url}}" lang="{{Culture}}" hreflang="{{Culture}}" class="lang-switcher__link {{#IsCurrentLang}}selected{{/IsCurrentLang}}">{{Name}}</a>

<div class="lang-switcher">
    <div class="lang-switcher__item">
         <a href="https://localhost:44331/en" lang="en-US" hreflang="en-US" class="lang-switcher__link selected">English</a>
    <div class="lang-switcher__item">
         <a href="https://localhost:44331/dk" lang="da-DK" hreflang="da-DK" class="lang-switcher__link ">dansk</a>

If you do not specify a template and use <our-lang-switcher /> it will use the following Mustache template

<ul class='lang-switcher'>
            <a href='{{Url}}' lang='{{Culture}}' hreflang='{{Culture}}' class='{{#IsCurrentLang}}selected{{/IsCurrentLang}}'>


This tag helper element <our-svg> will read the file contents of an SVG file and output it as an inline SVG in the DOM. It can be used in one of two ways, either by specifying the src attribute to a physcial static file served from wwwRoot or by specifying the media-item attribute to use a picked IPublishedContent Media Item.

<our-svg src="/assets/icon.svg" />
<our-svg media-item="@Model.Logo" />


This tag helper element <our-fallback> uses the same fallback mode logic that is only available on the Value() method of the IPublishedContent interface that uses a string for the property name to lookup. In addition if the fallback value from a language or ancestors is not available we are still able to fallback to the content inside the tag.

@* Current way *@
@Model.Value("Header", fallback:Fallback.ToLanguage)

<h3><our-fallback property="Header" mode="Fallback.ToLanguage" culture="da-DK">I do NOT have a DK culture variant of this property</our-fallback></h3>
<h3><our-fallback property="Header" mode="Fallback.ToAncestors">I do NOT have a Header property set on ANY parent and ancestors</our-fallback></h3> 


This tag helper element <our-version> prints out version number for a given Assembly name loaded into the current AppDomain or if none is given then the EntryAssembly version is displayed, which would be the Umbraco website project you are building.

<our-version />

<our-version assembly="Our.Umbraco.TagHelpers" />

our-member-include and our-member-exclude

This is a tag helper attribute that can be applied to any DOM element in the razor template or partial. It will show or hide its element and children on the page when passing a comma seperated string of member groups that the current logged in member for the exclude or include variants.

There are two special Member Groups you can use:

  • * - All anonymous users
  • ? - All authenticated users
<div our-member-include="Staff">Only members of Staff Member Group will see this.</div>
<div our-member-include="Staff,Admins">Only members of Staff OR Admins member group will see this.</div>
<div our-member-include="*">Only logged in members will see this.</div>
<div our-member-include="?">Only anonymous members will see this.</div>

<div our-member-exclude="Staff">Only Staff members can't see this (Including anonymous).</div>
<div our-member-exclude="?">Everyone except Anonymous members will see this.</div>
<div our-member-exclude="*">Everyone except who is authenticated will see this.</div>

our-user-include and our-user-exclude

This is a tag helper attribute that can be applied to any DOM element in the razor template or partial. It will show or hide its element and children on the page when passing a comma seperated string of user groups that the current logged in Umbraco backoffice user is in, for the exclude or include variants.

There are two special User Groups you can use:

  • * - All anonymous users
  • ? - All authenticated users

Use the alias of the User Group

<div our-user-include="admin">Only users in the Admin group will see this.</div>
<div our-user-include="admin,editor">Only users in the Admin or Editor user group will see this.</div>
<div our-user-include="*">Only logged in users will see this.</div>
<div our-user-include="?">Only anonymous users will see this.</div>

<div our-user-exclude="editor">Only Editor users can't see this (Including anonymous).</div>
<div our-user-exclude="?">Everyone except Anonymous users will see this.</div>
<div our-user-exclude="*">Everyone except who is authenticated will see this.</div>

This is a tag helper element which renders an edit link on the front end only if the current user is logged into umbraco and has access to the content section.

The link will open the current page in the umbraco backoffice. You can override the umbraco url if you are using a different url for the backoffice.

Simple example

This is the most basic example. The link will render wherever you put it in the HTML.


It will output a link link this, where 1057 is the id of the current page:

<a href="/umbraco#/content/content/edit/1057">Edit</a>

Use Default Styles example

If you add an attribute of use-default-styles, it will render the link fixed to the bottom left of the screen with white text and a navy blue background.

<our-edit-link use-default-styles>Edit</our-edit-link>

Change the edit url

Perhaps you have changed your umbraco path to something different, you can use the edit-url attribute to change the umbraco edit content url:

<our-edit-link edit-url="/mysecretumbracopath#/content/content/edit/">Edit</our-edit-link>

Open in a new tab

As the edit link is just an a tag, you can add the usual attributes like target and class etc. If you want the edit link to open in a new tab, just add the target="_blank" attribute.

<our-edit-link target="_blank">Edit</our-edit-link>


This is a tag helper attribute that can be applied to <a> element in the razor template or partial. It will use the value inside the attribute and append it to the class attribute of the <a>. If the link inside the href attribute can be found by its route as a content node, if so then it will check with the current page being rendered if its the same node or an ancestor.

This allows for the navigation item to still have the class added to it when a child or grandchildren page is the currently page being rendered.

Simple Example

@foreach (var item in Model.Root().Children)
    <a href="@item.Url()" class="nav-link" our-active-class="nav-link--active">@item.Name</a>

Alternatively you can use the our-active-class attribute in conjuction with our-active-href attribute to apply this to any HTML DOM element on the page.

    @foreach (var item in Model.Root().Children)
        <li our-active-href="@item.Url()" our-active-class="selected">
            <a href="@item.Url()" class="nav-link">@item.Name</a>

This tag helper element <our-link> will create a simple anchor tag using the Umbraco Multi Url Picker property editor that uses the C# Model Umbraco.Cms.Core.Models.Link

Note if the link set is an external link and you set the target of the link to be _blank, then the link will have the noopener attribute added to the link.

Simple Example

    <h2>Hi There</h2>

Alternatively if you use the <our-link> without child DOM elements then it will use the Title property of the link in the Multi Url Picker property editor to create the anchor tag.


With this tag helper the child DOM elements inside the <our-link> is wrapped with the <a> tag


This tag helper element <our-cache> is a wrapper around the DotNet CacheTagHelper - it operates in exactly the same way, with the same options as the DotNet CacheTagHelper, except, it is automatically 'not enabled', when you are in Umbraco Preview or Umbraco Debug mode.

Without this tag helper

Essentially this is a convenience for setting

<cache enabled="!UmbracoContext.IsDebug && !UmbracoContext.InPreviewMode">[Your Long Running Expensive Code Here]</cache>

With this tag helper

<our-cache>[Your Long Running Expensive Code Here]</our-cache>

Clearing the Cache 'on publish'

The Umbraco convention with other Cache Helpers, eg Html.CachedPartial is to clear all memory caches whenever any item is published in the Umbraco Backoffice. By default the our-cache tag helper will do the same, however you can turn this part off on an individual TagHelper basis by setting update-cache-key-on-publish="false".

<our-cache>[Your Long Running Expensive Code Here]</our-cache>

is the same as:

<our-cache update-cache-on-publish="true">[Your Long Running Expensive Code Here]</our-cache>

But to turn it off:

<our-cache update-cache-on-publish="false">[Your Long Running Expensive Code Here]</our-cache>

(NB if you had a thousand tag helpers on your site, all caching large amounts of content, and new publishes to the site occurring every second - this might be detrimental to performance, so do think of the context of your site before allowing the cache to be cleared on each publish)


All examples will skip the cache for Umbraco preview mode and debug mode, and evict cache items anytime Umbraco publishes content, media or dictionary items.

<our-cache expires-on="new DateTime(2025,1,29,17,02,0)">
     <p>@DateTime.Now - A set Date in time</p>

<our-cache expires-after="TimeSpan.FromSeconds(120)">
     <p>@DateTime.Now - Every 120 seconds (2minutes)</p>

    <partial name="Navigation" />

This example will turn off the automatic clearing of the tag helper cache if 'any page' is published, but still clear the cache if the individual page is published:

<our-cache update-cache-on-publish="false" vary-by="@Model.UpdateDate.ToString()">
     <p>@DateTime.Now - A set Date in time</p>

Video 📺

How to create ASP.NET TagHelpers for Umbraco


The logo for Our.Umbraco.TagHelpers is made by Freepik from flaticon.com

Product Compatible and additional computed target framework versions.
.NET net5.0 is compatible.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Our.Umbraco.TagHelpers:

Package Downloads

Custom forms add-on for UmBootstrap

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.2.0 16,654 5/12/2023
1.1.0 610 5/5/2023
1.0.0 13,333 11/17/2022
0.8.0 6,315 9/6/2022
0.7.0 2,797 8/5/2022
0.6.0 5,646 2/24/2022
0.5.1 2,933 11/21/2021
0.5.0 1,029 11/19/2021
0.4.0 1,377 11/16/2021
0.3.0 1,027 10/28/2021
0.2.0 1,063 10/27/2021
0.1.0 1,215 10/19/2021