Umbraco 6.0.3 and 4.11.6 released

Wednesday, March 27, 2013 by Sebastiaan Janssen

Toot Your Own HornThe v6 release is being picked up by more and more people and we're very happy with the uptake and the relatively few bug reports for it, all in all it's looking like v6 is very solid indeed!

Okay, enough tooting of our own horn, we're not perfect and there were bugs:

The first thing we missed was strictly v6 related, and it was a total oversight on our part: when fixing the document type related issues for version 6.0.2, we forgot that the package installer is happily doing it's own thing. Oops, sorry!

So when you were installing a package with nested document types similar problems to the ones we fixed in 6.0.2 cropped up. We've now addressed these issues and tested over 30 of the most popular packages PLUS most packages that we could find that would install a nested node structure.

Another bug fix, in both v4 and v6, was because we accidentally broke a feature in Razor. If you had properties that store something other than text (like a date or an integer), querying those suddenly returned strings, instead of a date or an integer. This is now fully working again.


One new thing (in both v4 and v6 releases!) is that you now have much better control over how macro errors are handled. We had help from Adam Nelson who sent in a pull request for this.
The default behaviour for macro error is the same: just show an error inline in the html. However, in your umbracoSettings.config you can now set the MacroErrors behaviour to be completely silent or you can throw an error.
These errors can now also be handled through Application_OnError or the umbraco.macro.Error event. So if you want an email or an SMS whenever a macro fails, no problem, just write a few lines of code! Thanks Adam, #h5yr!

 He's not the only one to contribute though: Steven Lemmens, Andy Butland, Stephen RobertsAsbjørn Riis-Knudsen and Brian Powell also offered their fixes for various issues. Awesome work, thank you. A big #h5yr to you too AND to the people reporting bugs and responding to our follow up questions, our community is on fire!

Go forth..

Other than that, there's a big number of small(er) bugfixes, mostly relating to MVC and updates to document type editing. Of course you can find a full list of bug fixes on our progress pages:

 The downloads are now available on CodePlex and NuGet and we hope that Microsoft accepts 6.0.3 in the Web Application Gallery soon so it will also show up in the Web Platform Installer.

So with that.. Go forth and download the shiney new bits for your easter enjoyment!

Ps. Sorry, we didn't have time to put any easter eggs in there.. ;-)

13 comment(s) for “Umbraco 6.0.3 and 4.11.6 released”

  1. Gravatar ImageSebastiaan Janssen Says:

    Warren, you can start with something like this, that should get you going in the right direction:

  2. Gravatar ImageAdam Nelson Says:

    A slightly more complex example showing how you can detect specific macros and also change the default behaviour on a per-macro basis:

  3. Gravatar ImageLee Kelleher Says:

    Great work on the latest releases!

    Very happy about the new `macro.Error` event, #h5yr to Adam & co!

  4. Gravatar ImageTommy Says:

    Warren, added a comment to Sebastiaans gist. Maybe worth something :)

  5. Gravatar ImageSteven Lemmens Says:

    Hey guys,

    I just checked out the source code from Codeplex and I'm getting build errors on Macro.CS. It's all ambigious references between Umbraco.Core.Events.MacroErrorEventArgs and umbraco.cms.businesslogic.MacroEventArgs and some calls to a missing method "GetControlForErrorBehavior". Perhaps the wrong version is online or something?

  6. Gravatar ImageSebastiaan Janssen Says:

    Works fine on my machine (VS2012).
    Got source from (download button), unzipped, opened the umbraco.sln, hit F5 and I was good to go.
    You may need to do a rebuild or get a fresh copy. The nightlies are (automatically) building fine as well, so it's not a problem in the source code.

  7. Gravatar ImageLaurence Gillian Says:

    When upgrading from 6.0.2 -> 6.0.3, can we assume that their are only changes to the DLL's?

    Thanks, Laurie

  8. Gravatar ImageSebastiaan Janssen Says:

    Laurence, no, there are changes to /umbraco and /umbraco_client as well. And an addition to the umbracoSettings.config (though if you don't add the MacroErrors element it defaults back to the current behavior, so it's not required to have that element).

    So, as mentioned in the release notes, follow the general upgrade guide:

  9. Gravatar ImageSelcuk Says:

    Downloaded the latest version from

    Tried to compile

    And I get a lot of that kind of error:
    Error 638 'MacroErrorEventArgs' is an ambiguous reference between 'Umbraco.Core.Events.MacroErrorEventArgs' and 'umbraco.cms.businesslogic.MacroErrorEventArgs'

    How sad...

    Does any of you have an idea to get rid of that message?
    or should I download that version:

  10. Gravatar ImageSebastiaan Janssen Says:

    Selcuk that's the source of the default branch. If you want the source for 4.11.6 or 6.0.3 then go to their release pages, there's links to 4.11.6 ( and 6.0.3 source code (

    But if you need to just install umbraco make sure to download the binaries from the release page: (Umbraco.Cms).

  11. Gravatar ImageStephen Says:

    I am trying to understand the difference between v6.0.3 and v4.11.6. Where can I get more information?
    We are currently using v4.5.2, should we upgrade to v4.11.6 or v6.0.3?


  12. Gravatar ImageSebastiaan Janssen Says:

    @Stephen Refer to the v6.0.0 blog post for more details:
    If your site is running fine then there's no need to upgrade.
    If you need new features in v4.11 or v6 then it's up to you to decide.
    v6 is still fairly young, so we might not have found all the minor bugs yet (but it's very stable now, all of the bigger problems have been ironed out).

  13. Gravatar Imagesawe Says:

    i get an error when installing the

    Server Error in '/' Application.

    Sequence contains no elements

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.InvalidOperationException: Sequence contains no elements

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [InvalidOperationException: Sequence contains no elements]
    System.Linq.Enumerable.First(IEnumerable`1 source) +269
    umbraco.cms.businesslogic.packager.Installer.InstallBusinessLogic(Int32 packageId, String tempDir) +2305
    umbraco.presentation.developer.packages.Installer.ProcessInstall(String currentStep) +208
    umbraco.presentation.developer.packages.Installer.Page_Load(Object sender, EventArgs e) +425
    System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +51
    System.Web.UI.Control.OnLoad(EventArgs e) +92
    umbraco.BasePages.BasePage.OnLoad(EventArgs e) +14
    System.Web.UI.Control.LoadRecursive() +54
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +772

    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18034

Leave a comment