Umbraco 6 RC is here

Monday, January 21, 2013 by Niels Hartvig

Gentle(wo)men start your engines - Umbraco 6 RC has landed!

After more than 500 downloads and loads of feedback of the beta, we’ve worked hard on getting the last issues fixed and as the baby passed all the items on the release checklist this morning, we’re proud to mark it the Release Candidate, which is fancy lingo for “we think it’s ready and if you don’t prove us wrong really fast, this will be the release”.

In other words - Umbraco 6 is here and real.

But what is Umbraco 6 - 159 great reasons?

Umbraco 6 is everything you loved about Umbraco 4, but with a whole new - and super fast - data layer as well as a new Public API. If this sounds very technical, it simply means that Umbraco is now much faster and more stable in the way it fetches and stores your content and that developers have a much nicer way to interact with Umbraco that follow best development practices.

Umbraco 6 also brings true MVC support (as well as continuous Webforms support), native Razor support and a lot of bug fixes and polish. Like support for master Media types, filtering of what Document Types can be allowed in the root of your site and a bunch of new razor templates to make you work faster. All in all, Umbraco 6 is the product of 159 work items.

But I know and love Umbraco 4 - do I have to learn everything again?

No. Umbraco 6 is 99% compatible with Umbraco 4 and you can work the exact same way that you’re used to and use (most of) the packages you can’t live without. The core team have even made sure that legacy code and packages will be automatically enhanced as well, as usage of the old API will automatically be re-wired to the new APIs behind the scenes.

So while Umbraco 6 brings you true MVC support, native Razor support and a whole new shiny API, if what you love is your XSLT, your webforms and the weird API that I originally made, you can keep doing it in Umbraco 6. But of course we’ll strongly recommend learning the new free toys right in front of you. We’ll even relaunch Umbraco.TV in February with loads of new content to help you get up to speed.

But why are you even reading this, when you can play with Umbraco 6 instead. Go download now!

24 comment(s) for “Umbraco 6 RC is here”

  1. Gravatar Imagesun Says:

    When you say something like that Umbraco is now much faster. You should give some data to explain this.
    I can remember that When V5 is released, you said V5 is faster, but it's not.

  2. Gravatar ImageSebastiaan Janssen Says:

    @sun I think you misunderstood the "v5 is faster" thing, we didn't claim v5 was faster than v4. We did improve the speed of v5 in the later releases and that's where those blog posts came from.

    The v6 backoffice will be faster because we're not saving each property on your documents individually. Instead, we're now updating the whole document plus all of the properties in one go. That's where you'll see the of speed improvement.

  3. Gravatar Imagekim Says:

    Congrats on the release candidate. I'm looking forward to explore the new options availble, especially changes regarding strong types instead of dynamics.
    Can't help smiling at the comment and reply regarding 'This is much faster', think the user is asking for data comparing latest v4 to v6 RC. Quantification through a simple use case will help get the point through :)

    Where do I find the documentation for the new features? having the documentation ready and published along with the final release is sort of necessary. No point in releasing V6 if nobody can use it except for HQ. A link would be just fine.

    Good work

  4. Gravatar ImageSebastiaan Janssen Says:

    Hey kim, a blog post was already in the making, have a look here:

  5. Gravatar ImagePinal Bhatt Says:

    gr8 news..... waiting for documentation for new APIs.

    Also will their be an upgrade path form U6 RC to U6 RTM?

  6. Gravatar ImagePhill Says:

    I tried to upgrade a test site from to RC 6.0 and followed instructions here It always wants me to start with a blank database, no upgrade option available. What am I missing?
    Thanks in advance, looking forward to giving v6 a test.

  7. Gravatar ImageWilliam Burnett Says:

    Unable to upgrade from 4.x to 6.x SQL.

    There are no primary or candidate keys in the referenced table 'cmsContentType' that match the referencing column list in the foreign key 'FK_cmsPropertyTypeGroup_cmsContentType_nodeId'.
    Could not create constraint. See previous errors.

    Really guys... how does stuff like this happen? A release candidate that 90% of us can't use due to a bug thet prevents us from upgrading a 4.x site to 6.x and nobody has noticed (or fixed) the issue yet? anybody paying attention to the important details or is it an open source free-for-all with all indians and no chief?

    There really is no excuse.... at least from my perspective.

  8. Gravatar ImageMorten Christensen Says:

    @Phil You should enter the details of your existing database. The reason why it pops up with that screen is because we are moving away from the old way of having the connection string as an appSetting and having it as a real connection string, so it needs to be rewritten. We are aware of the quirks of this, and its something we're improving.

    @William You are more than welcome to file a bug report on Upgrades has been tested against versions 4.8.0 - 4.11.3 to v6, and we have not seen this error before.

  9. Gravatar ImageNiels Hartvig Says:

    @William What version of v4 is this - as Morten mentioned we've tested a tonne of upgrades. We'd love more details - with or without rage.

  10. Gravatar Imagerm34 Says:

    @William Is this your Umbraco installation?:

    If yes, you should first upgrade to 4.8.x before going for v6. You're still using the old XML schema which is deprecated since nearly 3 years!

  11. Gravatar ImageWilliam Burnett Says:

    @Niels and Morten

    I have an email I am responding to from Niels and Sebastiaan regarding the issue:

    That said, my "upgrade" is not recognized as an upgrade and instead (posted in the installation forum) proceeds as a "blank" install where I get the error posted above.

    Maybe I am missing something, but I don't see documentation anywhere obvious that the connection string needs to be moved or changed from appsetting to perform an upgrade....

    So Morten you posted reasoning, but where are the details for those of us upgrading? Part of my "rage" (I have no rage, just frustration) is the fragmentation and.or lack of clear concise information at almost every turn.

  12. Gravatar ImageWilliam Burnett Says:


    I (clearly) indicated that my issue is upgrading a 4.x site to 6.0. The site you posted the stack trace link to is clearly a 3.x site :) So no... it is not the site in question. Btw, it is not very responsible to post a direct link to a site that has debug enabled. I am preparing that site for upgrade all the way to 4.11 as we speak.

    The site is the site in question and is running 4.11.2

    In any case: Niels, Sebastiaan... whoever. Feel free to take my "critical" post down. I had hoped to get some attention and did not realize there was not an "edit" feature here in the blog.

  13. Gravatar ImagePhill Says:

    @morten, thanks for your help. I went through process of clean RC6 install so I could grab the format of the connection string. I added this to my 4.11.3 site web.config file and I was able to get past install this time. However the upgrade still didn't work. Under developer, "Packages" has become "PackagesPackages" and there are also two sets of "PackagesPackages" both listing installed components. The same happend to "Relation Types". Naturally this has corrupted the site and I can't access any content that use doc types that require an installed package. When forums are back up I'll add screen shot of end result. Suffice to say the Upgrade process obviously wasn't tested much.

  14. Gravatar ImageWilliam Burnett Says:


    After hours of fiddling around, I stumbled upon something that worked.

    It would appear that A) the installer moves and rewrites the connection string... so you don't need to do that yourself?

    Secondly, in the past I have had a lot of issue with the web.config umbracoConfigurationStatus key. In this case a BLANK "" key results in the error! You must leave the key as "4.11.2". In previous versions, this was not an issue and in fact I have had to erase the key to get the installer to perform the upgrade.

    In this case, they key was present, but I think it may have been blank. with simply an opening and closing quote "".

    At least, after numerous attempts that is what allowed the priocess to continue. Note that even though the prevuious attempts failed, the DB connection string was moved in web.config and I did not move it back to appsettings.

  15. Gravatar ImageFunka! Says:

    This sounds very exciting, thank you to everyone who helped bring this to a reality. As I do not have full-time to commit to testing/developing with Umbraco, I've been looking forward to squeezing in some time to test this out but haven't quite yet. My worry is that RTM will be rushed out the door sooner than I have a chance to play with this RC. Although, with a few issues already seeming to crop up with problematic upgrades, maybe there might be a few more RC's beforehand? Thanks again everyone!

  16. Gravatar ImageHartvig Says:

    @Funka: The upgrade issues can be isolated to some very specific scenarios and we'll be working on resolving those. Rest assured that an RTM will not be released until we've tested those edge cases fully and updated the upgrade process to give better instructions on what's going on.

  17. Gravatar ImageMax Says:

    Fresh installation, installer does not work with IE 9, "Lets get started" button does not act on click event. In FF and Maxthon it works this far. After entering database connection settings for SQL Server 2008 R2, it stays at "Connecting to database", 5% progress.
    Ok, it should at least work with the SQL CE edition, I thought. But it still hangs at the same step.
    Are you serious?

  18. Gravatar ImageMax Says:

    Sorry, SQL Server connectivity was my fault. The SQL Server user had too less permissions. The 4.11 installer gave feedback about missing permissions, so I was able to figure this out. 6.0 stalls.

  19. Gravatar ImageMax Says:

    There is still the question about SQL CE - why didn't it work? I will do another test installation, maybe later this week.
    But: Umbraco still is the best CMS I got in touch with! Great work, I think you are on a very good way!

  20. Gravatar ImageNileZ Says:

    I succesfully upgraded 3 sites from v. 4.11.3 to 6.0.0, following the normal upgrade procedures. Everything went smooth, loving it!!
    One thing, though; Merging web.configs is ALWAYS a pain.. Would be awesome with a few notes on whats new in the web.config, maybe a diff between versions, so its easier to figure out whats new and what needs to be changed.

  21. Gravatar Imagesc Says:

    stuck at "connecting to database 5%" ... and has been there for an hour... this sucks...

  22. Gravatar ImageSebastiaan Janssen Says:

    @sc That sure does suck! I'm sure there's more than a few kind souls willing to help you out at though! :-) Make sure to have a look in your log file in App_Data/Logs as well, that should give you a clue.
    Also, hopefully you're installing Umbraco 6.0.2 and not the RC mentioned here. :-)

  23. Gravatar ImageRoger Says:

    The web matrix and installers all download and install Vesion 4. For new installs are we expected to install 4 then upgrade to 6?

  24. Gravatar ImageEric Herlitz Says:

    I'm upgrading from 4.9 to 6.1.1 and are also getting the same error as William.

    The database configuration failed with the following message: There are no primary or candidate keys in the referenced table 'cmsPropertyTypeGroup' that match the referencing column list in the foreign key 'FK_cmsPropertyTypeGroup_cmsPropertyTypeGroup'. Could not create constraint. See previous errors. Please check log file for additional information (can be found in '/App_Data/Logs/UmbracoTraceLog.txt')

    I followed the guidelines here but nothing seem to work, the umbracoConfigurationStatus is set to 4.9.0

Leave a comment