Umbraco's MultiNode TreePicker (MNTP) data type has a couple of tokens (or, more precisely, "context-aware placeholders") that can be used in the XPath query defining the starting node for the picker and represent the current or parent node - but these tokens behave differently when creating a new node than when editing an already published node. In this post we will see why and how we can make MTNP behave consistently regardless of whether the node being edited is new or existing.
We are happy to announce our first version of a Starter Kit for Umbraco 7.4 and onwards, based on the Mazel HTML theme. It is actually the same kit we are using on our web site here. This starter kit features a lot of functionality both in the front-end and the back-end and is FREE to use for personal or commercial purposes.
We created a quick-and-dirty solution for when you don't want to (or can't) use the new Umbraco strongly-typed models (Models Builder) but you still need IntelliSense for your property names.
A plugin we created that automatically adds predefined child nodes when a node is published.
In this very blog, all posts are grouped under a node called "Posts". That's good, but "/blog/posts/a-blog-post" doesn't look as good as "/blog/a-blog-post". That's right, if only there was a way the "/posts/" part could be omitted.
Imagine this: You've got a setup where a specific node has to have a maximum of, let's say, 4 children. It can be a slider, a pricing section, a set of counters, whatever, but let's suppose it's not designed to work with more than this number of items. What do you do?