Projects Thu, 26 May 2016 12:34:11 +00:00 umbraco Latests packages from the forum on en SVG Icon Picker A picker, for picking icons from an SVG spritesheet.

How to use

Pick SvgIconPicker as the editor for your desired icon property.

Type the path to your SVG spritesheet in the configuration.

On the document where you put the editor, it works just like the built in media picker mixed with the icon picker. You can filter icons, by searching the icons id. Select an icon by clicking it.

The selected icons id is saved as a string in the property value.

You can then render it in your frontend using a snippet like this:

<svg viewBox="0 0 100 100">
<use xmlns:xlink="" xlink:href="/assets/svg.svg#@Model.Content.GetPropertyValue("icon")"></use></svg>

Søren Kottal Tue, 24 May 2016 18:30:58 +00:00
Umbraco Properties Generator Umbraco Properties Generator lets you create complex ui for marco by defining json properties for fast development

This package is intended for developers.

Start here:

1) Install package

2) Include  "App_Plugins\PropertiesGenerator" folder in your project and build it

3) Add a json file in folder App_Plugins\PropertiesGenerator\properties\, look at the file "demo.json" for structure examples

4) Create a new macro with a new property that it's type is "Properties generator" and the alias of that property is the json file name

5) Use the macro :)


* It was tested on Umbraco 7.4.x

* Demonstration here:



Elad Fri, 20 May 2016 10:59:13 +00:00
VirtualNodes This package lets you specify one or more document types that will be excluded from Umbraco-generated URLs, thus making them "invisible". Those can be used as grouping nodes and they will not appear as part of the URL.


After you install the package, you will have to add one appSettings entry to your web.config file, as follows:

<add key="virtualnode" value="docTypeToMakeVirtual"/>

Where docTypeToMakeVirtual is the document type alias you want to be treated as a "virtual" node.

You can define more than one "rules" for docTypes by separating them with commas, as follows:

<add key="virtualnode" value="docTypeToMakeVirtual,anotherDocType"/>

You can also use wildcards at the start and/or the end of the document type alias, like this:

<add key="virtualnode" value="dog*,*cat,*mouse*"/>

This means that all document type aliases ending with "dog", all document types starting with "cat" and all those containing "mouse" will be treated as virtual nodes.


Advanced: Auto numbering of nodes

Consider the following example:






Supposing that groupingNode1 and groupingNode2 are virtual nodes, the path for article1 will be /articles/article1. Okay, but what if we add a new article named "article1" under groupingNode2?

The plugin checks nodes on save and changes their names accordingly to protect you from this. More specifically, it checks if the parent node of the node being saved is a virtual node and, if so, it checks all its sibling nodes to see if there is already another node using the same name. It then adjusts numbering accordingly.

So, if you saved a new node named "article1" under "groupingNode2" it would become:






    article1 (1)

And then if you saved another node named "article1" again under "groupingNode1" it would become "article1 (2)" like this:





    article1 (2)


    article1 (1)

This ensures that there are no duplicate urls. Of course, to keep things simple, I've implemented checks only a level up - if you have multiple virtual nodes under each other and multiple nodes with the same name in different levels, better be careful because no checks there. (Yes, I'm lazy).



Sotiris Filippidis Wed, 18 May 2016 07:37:58 +00:00
Merchello Bazaar Merchello Bazaar Starter Kit for Merchello.


This starter kit is now being maintained by the Umbraco community.

This package requires that be installed BEFORE installing.

Please post questions about this project in the main Merchello forum

Rusty Swayne Tue, 17 May 2016 19:53:20 +00:00
RankOne - SEO Toolkit

RankOne is a collection of SEO tools for Umbraco that aim to optimize your content according to the latest SEO standards.

RankOne currently contains 4 different tools for Umbraco:

  • A doctype composition with title, meta description and meta keywords
  • Dashboard property editor: Score based list of seo improvements
  • Summary property editor: A list of seo improvements
  • Result preview property editor: A google search result preview

How to install

  1. Install the package
  2. Create a doctype or composition
  3. Create a new tab
  4. Create a new property with the RankOne - Dashboard datatype
  5. Save it all and you're ready to go

How to add a focus keyword

  1. In the content tree click the node(s) where the dashboard is installed on
  2. Go to the seo tab
  3. On the right hand corner click on the cog
  4. Fill in your focus keyword and click save
  5. Click save and publish on the node to save the keyword and reload the dashboard

For suggestions, corrections and bugfixing please contact me on github or send a pm

Mark Wemekamp Sat, 14 May 2016 11:17:32 +00:00
Custom Login Page Custom Login Page


Plugin for Umbraco 7.4.3+


This is a tweak for the login page, changing the visual of the layout. It adds a custom css and javascript injections into the Login page.

It also adds a "loading" after clicking login, and it changes the background image for the screen.

To customize it, you should open ~/App_Plugins/Custom.Login.Page/css/style.css and change the style to fit your needs.


Carlos Casalicchio Fri, 13 May 2016 17:49:31 +00:00
"Omit Segments" Url Provider (a.k.a. URL Sniper)

Makes Umbraco omit URL segments from a node's URL, based on rules specified in web.config. The URLs generated are native Umbraco URLs, i.e. no rewriting, urlAlias or redirects.

Works with document types, e.g. omits the URL segment for doctype A if found in the path which has doctype B as parent.

Simply put, sometimes you want to omit parts of URLs created by Umbraco (which are based on a node's path).

For example, you'd like the URL:


to become:




You can make Umbraco omit URL parts from the default url it constructs from a page by excluding it from the path. All you have to do is add entries (as many as you like) in the appSettings section of your web.config file like this:

<add key="omiturlsegments:ParentDocTypeToLookFor" value ="DocTypeToOmitFromUrl,AnotherDocTypeToOmitFromUrl"/>


ParentDocTypeToLookFor is the parent document type alias that will trigger the plugin to alter the node's URL and

DocTypeToOmitFromUrl (as well as any additional doctypes, comma-separated) is(are) the doctype(s) that will be omitted from the URL path. Those docs with the specified doctypes must be children of the document with "ParentDocTypeToLookFor".



Let's suppose that you have a document of type "CarPage" which is used to display car data. You add a child of type "Parts" which is used to group various car parts detailed descriptions, and under it you add multiple documents of type "PartPage".

So, for example, you may have a structure like Peugeot 208/Parts/Engine, where "Peugeot 208" is the CarPage doctype, "Parts" is the Parts doctype and "Engine" belongs to the "PartPage" doctype.

But you don't want the url to say "Parts" or whatever the name of this interim node is. It's just a grouping node and you need this URL segment to go away, so that your Url can be something like:


instead of:


In order to achieve that, you will simply have to create an entry in the appSettings section of your web.config, like the following:

<add key="omiturlsegments:CarPage" value ="Parts"/>

which will tell the plugin to produce Urls for CarPage doctypes that will IGNORE any segment that comes from "Parts" doctypes under it.



Make sure that the URLs generated after applying your rules are still unique! Use this plugin only to omit "grouping" nodes or nodes that will not alter the uniqueness of the URL.

Sotiris Filippidis Wed, 11 May 2016 16:33:50 +00:00

This is a simple plugin that automatically creates new child nodes in the Umbraco back end upon publishing a node, based on a set of user-defined rules.

Usage (using configuration file in /config folder)

In your /config folder, you will find autoNode.config with a commented example of a rule.

Here's an example rule:

    nodeName="Dummy Name" 
  • createdDocTypeAlias: The document type alias of the document being published. IF the document being published has the specified doctype alias, then the rule will execute.
  • docTypeAliasToCreate: The document type alias of the document that will be automatically created as a child document.
  • nodeName: The name of the newly created node.
  • bringNodeFirst: If set to true, will bring the newly created node first in the Umbraco back-end.
  • onlyCreateIfNoChildren: This, naturally, regards republishing. If set to true, then republishing a node that already has child nodes (including any already automatically created nodes) will NOT run the rule. If set to false, the rule will run even if the node being published already has children. Note: If this setting is set to false and there are already automatically created nodes under the node being published, then they won't be created again. (The check is performed on both doctype and node name as defined in rules - if such a node is found, it will not be created again)

Usage (using code)

You can also register one or more rules for the package on application start. All you need to do is get the AutoNode instance (it's a Singleton) and use the RegisterRule method. You can use both a configuration file and code if you like. All rules will be added.

  AutoNode au = AutoNode.Instance;

  au.RegisterRule(new AutoNodeRule(
    createdDocTypealias: "TextPage",
    docTypeAliasToCreate: "Dummy",
    nodeName: "Dummy Auto Inserted Node",
    bringNodeFirst: true,
    onlyCreateIfNoChildren: false));

You should use this call in the ApplicationStarted event handler, in a new class you can create in your App_Code folder like below:

using Umbraco.Core;
using Umbraco.Core.Events;
using Umbraco.Core.Models;
using Umbraco.Core.Services;

    public class AutoNodeEvents : ApplicationEventHandler

        protected override void ApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)
            base.ApplicationStarted(umbracoApplication, applicationContext);

            AutoNode au = AutoNode.Instance;

            //This is an example rule, put your own here
            au.RegisterRule(new AutoNodeRule(
                createdDocTypealias: "TextPage",
                docTypeAliasToCreate: "Dummy",
                nodeName: "Dummy Auto Inserted Node",
                bringNodeFirst: true,
                onlyCreateIfNoChildren: false));

Limitations / Warnings

You should not specify circular rules (i.e. one rule for creating doc B when A is published and one rule for creating doc A when B is published - this will cause an endless loop and leave you with a huge tree if you don't stop it on time :). You can, however, create multiple rules for the same document type. That is, you may want docs B, C, and D to be automatically created when A is published, so you will have to create 3 rules.

The plugin creates the subnode only if there isn't any child node of the same doctype with the same name as defined in the rule.

The plugin works for new nodes as well as existing nodes (if they are published and there is a rule in place and no subnode of the given doctype already exists).

This plugin works only with doctypes, so it's not possible at the moment to have any other criteria for automatic document creation. IF you need this, I'll be happy to add more logic.

This plugin was made to cover very specific, simple needs, like having a "Files" grouping node created automatically under each new "Article" node. It doesn't do miracles, so don't expect any :)

Sotiris Filippidis Mon, 09 May 2016 19:40:55 +00:00
uWhiteLabel Easily add your brand to your Umbraco backoffice


  • Add your logo to the Umbraco login screen
  • Custom backoffice welcome screen for your Umbraco editors.


It’s important to stay “top of mind” with your clients if you are building long term business relationships.

This little package allows anyone to quickly and easily create a completely custom welcome screen that is shown when content editors log into the Umbraco backoffice.

You can add any image & (optionally) override the default welcome message that Umbraco displays.

Something as simple as showing your company logo and a reminder of contact details can help to polish your professional image.

uWhiteLabel allows you to do this in minutes without having to waste time digging into the Umbraco internals.

More info:

v1.0.22: fixes issue with support for v7.3 Umbraco

v1.0.24: Bug fix

Barry Sat, 30 Apr 2016 23:12:38 +00:00
UmbracoSocialPluginAdapters UmbracoSocialPluginAdapters adds Facebook and Twitter adapters for the jQuery Social Stream Plugin to your site!

The excellent jQuery Social Stream Plugin unfortunately comes only with a PHP file that is necesary for Twitter and Facebook authentication. This plugin is a rewrite of the original adapters from PHP to C#, so that your Umbraco site can natively support this the social stream plugin.

Ondrej Pialek Sat, 30 Apr 2016 01:04:54 +00:00
Tabulate Tabulate manages instances where content authors are maintaining large, generally well-structured data sets in the Umbraco back office.

Getting started
- Install the package and create a new datatype using the Tabulate editor. Simple.
- Add the data type to a document type. Obviously.
- The editor can be configured to either use a custom view defined in code, or through the settings dialog on content node - add or remove columns of the desired type, set the label format, set pagination, import and export data and so on.

Data is stored as a JSON blob so what you do with it is entirely up to you.

For a full rundown, check the GitHub repo at

On the sound advice of Chief Unicorn Hartvig, icon is no longer a burger, it's much more appropriately, a table.

Nathan Woulfe Thu, 28 Apr 2016 02:54:58 +00:00
Our.Umbraco.OpeningHours An Umbraco v7 property editor for handling opening hours

Bo Damgaard Mortensen Thu, 14 Apr 2016 20:04:44 +00:00
BootEasy - Client Bundling This is a addon for the BootEasy for Umbraco framework ( that will allow easy bundling and minifaction of client side assets like css and javascript using the Microsoft Asp.NET optimization framework (

To use this package you will first need to install the BootEasy package using the Umbraco package.

The package will allow configuration of your style and script files using a config file instead of coding it in a application start event. For more information see :

This package is also available as nuget package :

Dave Woestenborghs Mon, 11 Apr 2016 06:32:24 +00:00
Whodunit Whodunit adds a changelog as a new dashboard. You can export the changes to CSV.

It tracks both content and media changes.

Nicholas Westby Fri, 08 Apr 2016 00:37:19 +00:00
Styled Textbox Simple styled textbox property editor to let you apply a little flare to the standard text boxes.Great for things like Page Titles and headings and it works as a direct replacement for the built in textbox.

I keep finding myself reaching back into old projects to pull this simple styled textbox property editor out, so i've stuck it in a package to make it even easier for me to find. 

Allows you to create textboxes, with styles, character limits or warnings and placeholders.

either install from the package below, or via NuGet

Install-Package Jumoo.StyledTextbox

Release Notes:

  • 1.2 - Added Textare support - you can pick multiline and get a textarea, instead of a textbox.
  • 1.0 - initial release


Kevin Jump Fri, 01 Apr 2016 15:17:12 +00:00
Insert Ipsum A simple package for inserting Lorem Ipusm using the NLipsum Library for the .NET Framework:

1. Insert the 'Insert Ipsum' macro in a richtexteditor.
2. Specify the number of paragraphs to insert.

The Lorem Ipsum text in generated on pageload, which gives a bit more life to pages during development, instead of doing a traditional static copy/paste from

No magic, just a simple macro surrounding the awsome NLipsum Library.

Dennis Adolfi Thu, 24 Mar 2016 14:22:10 +00:00
BootEasy BootEasy is a small framework to help hooking in to the Umbraco startup events.

Instead of implementing a class that inherits from Umbraco.Core.ApplicationEventHandler and hooking into the different startup events, with BootEasy you will implement a class inherting one of the base classes provided by BootEasy to hook in to these events. For more information see

This package is also available as a nuget package :



Dave Woestenborghs Mon, 14 Mar 2016 07:51:34 +00:00
Export Umbraco Members to Word Documents, OpenDocument, PDF and Image formats using Aspose.Words Export Umbraco Members to Word Documents, OpenDocument, PDF and Image formats using Aspose.Words

Aspose.Words for .NETExport Members to Word is an Add-on for Umbraco which allows you to export members from your Umbraco CMS to a Word Document, OpenDocument, PDF and Image formats using Aspose.Words. A new node titled Export Members To Word appears under Members tree in Umbraco backend after installation where you can simply select members to export and output format to get members in selected output document format.

free downloadvideo demoopen source


This initial version of the Add-on have the following features:

  • Export members to Microsoft Word Documents (.doc, .docx, dot, dotx, docm, and dotm)
  • Export members to Portable Document Format (*.pdf)
  • Export members to OpenDocument Format (*.odt)
  • Export members to Tiff Image/s (*.Tiff)
  • Export members to JPEG Image (*.Jpeg)
  • Export members to PNG Image (*.Png)
  • Option to select desired output format before exporting
  • Option to export all or selected members to selected output document format.
  • Works with all .NET versions starting from .NET 4.0.
  • Exported document is automatically sent to browser for downloading
  • If selected a copy of the exported document is saved in App_Data folder on the server for later use.
  • Compatible with a wide range of Umbraco versions 7.x+

Umbraco Member Export To Word

Download, Installation and Usage

Please check the links below to find instructions on downloading, installing, configuring and using Export Members To Word Add-on.

Start a Free Trial Today

Start a free trial today – all you need is to sign up with Aspose. Once you have signed up, you are ready to try powerful file processing features offered by Aspose file format APIs.

Customer Feedback

Your feedback is very important to us. Please feel free to provide feedback and raise feature requirements. We are keen to implement customer driven features since we are a 100% customer driven company.

Aspose Marketplace Thu, 10 Mar 2016 18:40:23 +00:00
CM Umbraco Tools This package contains a set of tools for the developer and the administrator of an Umbraco site.

Nuget install


In order to enable the backoffice tools for an administrator, the CM Umbraco Tools section has to be checked for the user.

This package contains the following tools for Umbraco.

  • Settings
  • Appication Pool Restart
  • Log Viewer
  • Robots.txt
  • Sitemap
  • Permanent Redirect (301)
  • Examine Manager
  • Data Annotations for dictionary

Version History

Version 1.0.0 (2016-03-02) - NuGet package only

  • Added Settings management tool
  • Added Applcation pool restart tool
  • Added Log Viewer tool

Version 1.1.0 (2016-03-06)

  • Added Sitemap generation tool
  • Added Robots.txt generation tool
  • Changed Log Viewer tool in order to allow the administrator to delete log files

Version 1.2.0 (2016-03-08) - NuGet package only

  • Changed some ajax calls from GET method to POST
  • Added Permanent Redirect (301) tool

Version 1.3.0 (2016-06-15)

  • Added Examine Manager tool

Version 1.4.0 (2016-06-16)

  • Added Data Annotations for dictionary


Aristotelis Pitaridis Sun, 06 Mar 2016 14:56:01 +00:00
Terabyte CSS Picker A Visual CSS Picker for Umbraco 7


Download the zip file from github, copy Terabyte.CssPicker folder to your App_Plugins folder.

We would like to make a nuget package for this project, but have not done so yet.


You need to supply 2 PreValues:

cssFile: the path to your css file where your selectors can be found

cssPrefrix: any selector that begins with this value will be shown in the picker.

The css class is saved to the DataValue (including prefix) ready to be output in your markup.

Questions, Bug Reports, Feature Requests

Please use github issues for these.

Murray Roke Thu, 03 Mar 2016 01:19:19 +00:00