Umbraco 6.0.2 released

Monday, March 04, 2013 by Sebastiaan Janssen

Only two days after releasing 6.0.1 we already have to do a new patch release, with a big Mea Culpa from the core team. As mentioned in the 6.0.1 release blog post, we fixed some problems in the document type editor that popped up in the 6.0.0 version. Unfortunately, the upgrade script for 6.0.1 was not entirely correct and caused tabs and/or properties to disappear from your document types.

Who's affected?

If you've put a property on an inherited tab, the upgrade from 6.0.0 to 6.0.1 would have caused problems for you.

So let's say you have a "Page Settings" document type, with a tab called "Navigation". As a child document type of "Page Settings" you have "Homepage". If you've put one or more properties on the "Navigation" tab on the "Homepage" (inherited from "Page Settings"). See the picture below (click it for a larger version):


What can you do to fix?

Unfortunately, some properties and tabs might have gotten deleted. We hope you've used the usual precaution and made a backup of your database. Make sure to restore the database in which your document type structure was fine (the 6.0.0 version). The installer of the 6.0.2 version will now properly upgrade your database without deleting properties/tabs.


We're very sorry that this has happened. We were focused too much on making sure that document type editing worked as expected in 6.0.1 and didn't pay enough attention to people who were upgrading. For future releases we'll make sure to test the upgrade path thoroughly as well. 

For this 6.0.2 release we've upgraded a bunch of sites that were previously affected and they all worked as expected after doing the upgrade from 6.0.0 to 6.0.2.

6.0.2 is available from CodePlex and NuGet now!

18 comment(s) for “Umbraco 6.0.2 released”

  1. Gravatar Imagemike Says:

    CMS upgrades are a myth...

  2. Gravatar ImageMartin Says:

    CMS upgrades are damn difficult but not a myth we've taken major projects from to 4.11.5 and upgraded Contour and Courier too! The benefits in doing this, despite the difficulty level are enormous.

  3. Gravatar ImagePinal Bhatt Says:

    Thanks a lot Umraco Team.

  4. Gravatar ImagePeter Says:

    So how do we fix those ones that have been screwed up already? Sadly, we can't revert back to a backup because we have 10 days worth of content, and one page that throws a duplicate sequence error.

    Pretty disappointed about this.

    Sequence contains more than one matching element
    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 more than one matching element

    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 more than one matching element]
    System.Linq.Enumerable.SingleOrDefault(IEnumerable`1 source, Func`2 predicate) +2537270
    umbraco.controls.ContentTypeControlNew.BindDataGenericProperties(Boolean refresh) +1633
    umbraco.controls.ContentTypeControlNew.SetupGenericPropertiesPane() +291
    umbraco.controls.ContentTypeControlNew.OnInit(EventArgs e) +90
    System.Web.UI.Control.InitRecursive(Control namingContainer) +134
    System.Web.UI.Control.InitRecursive(Control namingContainer) +290
    System.Web.UI.Control.InitRecursive(Control namingContainer) +290
    System.Web.UI.Control.InitRecursive(Control namingContainer) +290
    System.Web.UI.Control.InitRecursive(Control namingContainer) +290
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +489

  5. Gravatar ImageAndreas Iseli Says:

    @Peter: I receive the same error after upgrading to 6.0.2. This does not seem to be a simple 6.0.1 bug.

  6. Gravatar ImageMorten Christensen Says:

    @Peter The issue revolves around PropertyTypes and PropertyTypeGroups (Tabs), so if you restore your backup in a different setup, run the upgrade to 6.0.2 then you *should* be able to copy the content over. Easiest thing would probably be to script it.
    The Ids of the PropertyTypes, which are referenced from the Properties within your Content hasn't changed, but merely been updated with a PropertyTypeGroupId. So it should still be possible to fix your solution with the backup you have, as long as the PropertyTypes and Tabs are correct in that backup of course.

    We know that its unfortunate situation, which is why we were quick to fix the issue and release 6.0.2.

    @Andreas I commented on the issue you reported here:

  7. Gravatar ImageOwen Says:

    I agree with Andreas Iseli. I have tried upgrading from 6.00 to 6.02 twice now, both times I have run the installer, and both times my document properties were all mixed up.

    I'm going to try packaging everything and importing it all into a fresh install of 6.02. If that doesnt work, I'm going back to 4.9.

  8. Gravatar ImageOwen Says:

    The document property issue is not fixed in the upgrade. I tried upgrading twice, then I created a package with all my doc types, installed a fresh version of umbraco 6.02, imported the package, and all the documents have their properties mixed up.

    Umbraco 6.00 and 6.02 are reading the documents tables differently.

  9. Gravatar ImageMorten Christensen Says:

    Hi Owen, sorry to hear you are seeing issues after the upgrade to 6.0.2. We have seen a one cases were some Property Type Groups (tabs) were saved incorrectly in v6 which caused problems for the upgrade process. If its possible for you to post a backup of your database (.bak or scripted of the 6.0.0 db) I'd be happy to take a look to see if its possible to make any kind of correction before upgrading. Please use this issue on our issue tracker (you can set visibility to HQ so only we can see the attached files - alternatively email them to me).

  10. Gravatar ImageJoey Kincer Says:

    I started a few new projects with clean installs of 6.0.1 (skipped over 6.0.0 completely to avoid the worst of the inevitable bugs). Is there any benefit to updating from 6.0.1 to 6.0.2 or would I be better off waiting for the next maintenance release?

  11. Gravatar ImageMorten Christensen Says:

    @Joey The only difference between 6.0.1 and 6.0.2 is the ugprade script + 3 minor issues (U4-1814, U4-1816 and U4-1818), so if you started fresh there won't be any noticeable difference.
    Should you hit any issues along the way we always have the nightly builds for 6.0.3, which we always aim to have as stable as the latest patch release, so that its safe to use while waiting for the final release.

  12. Gravatar ImageOwen Says:

    Just thought I'd leave a note saying that the upgrade to 6.02 from 6.00 does work after all. If you're doing it, dont make my mistake and forget about the umbracoConfigurationStatus. Make sure you keep this line here set to 6.00:

    Make sure you keep your connection string in the web.config.

    Then run the installer.

    Thanks for your help Morten!

  13. Gravatar Imagehabibbasha Says:


    Page not found No umbraco document matches the url 'http://localhost/UmbracoCms/about.aspx'. This page can be replaced with a custom 404. Check the documentation for "custom 404".

    i have found this error while i publish a page

    please give me ur reply

  14. Gravatar ImageMark Bowser Says:

    We found a quick solution. You have to dig into the umbraco DB, but for those of you who have a lot of content you don't want to merge, this might be a good option:

    We basically went into the database, located the duplicate tabs, and deleted them. Give it a try and tell us how it goes. Make sure to back everything up before you do this.

    Good luck!

  15. Gravatar ImageMark Bowser Says:

    It looks like the issue is more than just duplicated tabs and properties. Some tabs and properties were deleted. If you try a fix like the one I presented above, make sure to glance over all of your doc types for missing properties. Remember, if a tab was deleted, some of your properties may show up under the 'Generic Property' tab.

  16. Gravatar ImageJørgen Bakke Eriksen Says:

    We have problems upgrading from 6.0.1 to 6.0.2. That is, we don't get the install screen when starting the application after following the upgrade guide on

    We have copied the four folders from the zip mentioned here but nothing happens. Are we missing something?

  17. Gravatar ImageJørgen Bakke Eriksen Says:

    I can force the install screen to appear by changing to


    from 6.0.1 to 6.0.2 but after the installation is done the key is set back to 6.0.1

  18. Gravatar ImageJørgen Bakke Eriksen Says:

    Found the solution. It was of course our organization of the binary files. Sorry for the fuzz :-)

Leave a comment