Umbraco 4.11.2 Released

Thursday, January 10, 2013 by Sebastiaan Janssen

It's been brewing for a while now, we have the last few remaining issues for 4.11.2 fixed and it's up on CodePlex now! As we promised earlier the nightlies for patch releases are very stable and it's been fun to see people have picked them up and used them, leading to a few more fixes.

The upgrade is really easy and does not break anything, we've even managed to sneak a few things we had to for for v6 into this one. If you're on 4.10.x or 4.11.x it's a highly recommended upgrade, have a look at the list of fixes on the issuetracker.

As you can see, 4.11.2 mainly fixes some publishing problems that have cropped up, so make your editors happy and upgrade as soon as possible. The download is ready for you on CodePlex and of course NuGet has also been updated.

We're not forgetting about you v4 lovers and we're dedicated to providing more bugfixes to v4 in the future.

And yes, a v6 beta is on track to be released very, very soon, hold that thought!

Update: I made some mistakes during the release, oops! Version is all good though. :-)

13 comment(s) for “Umbraco 4.11.2 Released”

  1. Gravatar Imagesun Says:

    Can I update umbraco from 4.9 to 4.11.2 directly?

  2. Gravatar ImageSebastiaan Janssen Says:

    @sun should work just fine but make sure to back up and read about breaking changes in 4.10 and 4.11 before you do so.

    There's also some extra config changes and files in 4.10 that you'll want to consider:

  3. Gravatar Imagesun Says:

    I don't know very much about umbraco, I update it by some steps:
    1. uninstall all packages, it is in order go back to original 4.9
    2. copy 4.11.2 file into my site and run update steps.
    3. reinstall all packages. this will make all config right. So i don't need to know how to modify config files.
    Do you have any nice idea?

  4. Gravatar ImageSebastiaan Janssen Says:

    You don't need to uninstall the packages (and you shouldn't you could loose important content and other information!).

    The upgrade instructions are always clearly noted on CodePlex and if you are not sure what to do then the safest thing is to update each version and not attempt a direct upgrade. That way you can read and follow the upgrade instructions on each version so you won't miss anything important.

    I recommend you read this forum post as well:

  5. Gravatar ImagePinal Bhatt Says:

    On Nuget, for Umbraco Cms Core Binaries 4.11.1 i can see dependency on Microsoft.AspNet.Mvc (= 3.0.20105.1) but in Umbraco Cms Core Binaries 4.11.2 I dont see any dependency.

    Does that measn 4.11.2 works with MVC 4 ?

  6. Gravatar ImageSebastiaan Janssen Says:

    It has always been possible to upgrade to MVC4, just follow the upgrade notes on:

  7. Gravatar ImageSebastiaan Janssen Says:

    @sun I've created new documentation for upgrading Umbraco installs, go have a look over here:

  8. Gravatar ImageJesper Haug Karsrud Says:

    Hi there,

    It seems there are some issues with the new version. UmbracoCms.Core doesn't have a dependency to ASP.NET MVC, which means you don't get a Global.asax etc. That means things won't work as expected. Could you deploy a fix for this? :)

  9. Gravatar ImageKoos Mikael Says:

    I updated my umbraco 4.11.1 to 4.11.2 but I had an error when I rebuilded my project : Could not load type 'Umbraco.Web.UI.Umbraco.Create.PartialViewMacro'
    I excluded partialViewMacro.ascx and it solved my problem but I don't know if it is the good thing to do.

  10. Gravatar ImageSebastiaan Janssen Says:

    Sorry Jesper, the NuGet version we released yesterday was missing some things! It's all fixed now, make sure to get the latest version!

    @Koos That's fine!

  11. Gravatar Imagesun Says: can't create Macro. If you create a Macro and click it. It will give you YSOD.

  12. Gravatar ImageMihai Osvat Says:

    Indeed, you cannot create a blank Macro (as for an ASCX), it throws error "Object reference not set to an instance of an object.". I installed the version by using the NuGet package, and it was version

  13. Gravatar ImageSebastiaan Janssen Says:

    @sun, @Mihai Ouch! Just released to fix this, sorry. :-)

Leave a comment