Posted on Wednesday May 5, 2010

Umbraco hacks for developers

A lot of the tips here are relevant for Umbraco 3.0, issues such as the debug builds have been resolved in 4.0

Sitemap XSLT

The XSL below is the source used for Sitemap on It’s taken from the Umbraco book, and modified to display the Dublin Core description alongside each page’s url.

Changing the content type of a document

I’ve had to do this quite often on when I realised I’ve created something as a Textpage (a built in document type) but then need some code highlighting which comes from a different content type.
I haven’t got round to making a tool to do it, but it’s simple to do when access to SQL Enterprise Manager/Management Studio.

First of all, backup the content of the document you are going to change. This is important, as changing the content type wipes the content. I don’t know why, the developers will know the reason for that. But the bodyText and the properties dissapear. Changing the contentType is straight forward, simply run

UPDATE cmsContent SET contentType={Your ContentTypeID} WHERE nodeId={Your document ID}

in SQL Server Management studio. You can get a list of contentTypes from the contentType table. nodeId holds the ID (rather than the pk column).

Once you have done this, publish your document. It will probably show a null reference exception when you click on the node in the editor. This will go once it has been published.

Moving multiple documents

If you need to move a lot of documents at once to a new parent, it’s painful doing it inside the editor. A SQL Script for doing this is below, just change the @oldParentId and @ParentId accordingly. Make sure you backup your database first.

Performance issues with Umbraco

Since installing Umbraco and running on it since December 2006 I’ve noticed a few ways of making it go faster. Most of them are out of the box with Umbraco, like using the XML cache however there’s a few others worth a mention:

Truncate your umbracoLog table regularly

The table contains all exceptions and warnings plus a host of other information from the Umbraco system. Most of this you don’t need and can clog up the database. The table can grow very large quickly, particularly if you’re creating the website for the first time and testing. This image shows an example

umbraco tables

Before this the site was 500,000 records strong before I noticed. The backups become large too. So simply run truncate on it:

TRUNCATE TABLE [dbo].umbracoLog

There’s not point saving the deletes to the transcation log with DELETE FROM, as the data is never used by Umbraco except for your information.

Make sure tracing and debug is turned off

Find the following lines in your web.config file and make sure the attributes are set to false, it makes a noticeable difference:

<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />
<compilation defaultLanguage="c#" debug="false">
<add key="umbracoDebugMode" value="false" />

GZip your HTML output

I’ve written a small HttpModule based on some code by Bart De Smet that’s very simple to install. It GZIP’s your HTML output, reducing the bandwidth your site uses and page load time. It’s aimed at people using shared hosting or pre-IIS 5 servers.

Changing templates on multiple documents

Like moving lots of documents at once, this is also a pain in the editor. The code below (for version 3.03) does this for you. You’ll need to turn it into a webservice and make a calling application to use it.

Database schema

This shows the schema of the Umbraco database, imported into Visio and organised so the tables are grouped together.

umbraco schema

Download the original Visio file

Data export

This tool came from having troubles backing up an Umbraco database on - who didn’t allow user backups of SQL databases or remote SSIS packages. The host has now been switched but for users of similar hosts like the tool is useful. Find it here (it needs Visual Studio to compile it, which you can get for free).

These links are included to supplement the ones on the site.

  • V2 docs:
  • Old docs:
  • Wikibooks
  • Official utilities:package