Umbraco 4.11.4 Released

Friday, February 1, 2013 by Sebastiaan Janssen

We've just released Umbraco 4.11.4 and an additional package to fix a serious issue in all versions of Umbraco between 4.10.0 and 4.11.3.

In v4.10.0, when you move a node to a different parent, the path property did not get updated properly. This, in turn, led to a bug where Examine could not index the nodes. It would result in a "yellow screen of death" saying or "value can not be null 'attribute'". To make matters worse, the node could never be edited again, you kept seeing this error.

We identified the bug and fixed it in 6.0.0, so moving nodes updates the path correctly in 6.0.0. Now, we've also fixed the same move issue in 4.11.4, so from 4.11.4 onward, moving a node will work fine again.

"Path Fixup" package

If your site was ever of version 4.10.x or 4.11.x (up until it is possible that this bug has caused problems for you. You can easily fix these problems by installing the fixup package made by Shannon.

The package will install an extra dashboard in your Developer section. Once it starts fixing, it will look at all of the nodes in your website and determine if the path is correct. If it is not correct, it will fix the path and publish the node.

To make it very clear:

  • if your site was ever of a version between 4.10.x and 4.11.x (anything lower than 4.11.4) you should run this package. 
  • if you have just upgraded to 6.0.0 and your site was ever of version 4.10.x or 4.11.x you should run this package.
  • new installs of 4.11.4 are fine
  • installs of 4.9.x and lower are fine
  • new installs of 6.0.0 are fine

What else is new?

Previewing nested unpublished pages now works and when in preview mode, macro's won't be cached.
Other than that, w
e fixed 36 issues for your enjoyment and we highly recommend you upgrade to this version. No breaking changes, so no need to worry.

Download your copy today!

22 comment(s) for “Umbraco 4.11.4 Released”

  1. Gravatar ImagePhill Says:

    Upgraded my site to 4.11.4 and all seems ok. Tried installing Fixup Package to verify all my nodes and got YSOD during install (after accepting license and clicking install package button).
    Server Error in '/' Application.
    Could not load type 'System.Runtime.CompilerServices.ExtensionAttribute' from assembly 'mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

    Source Error:
    Line 39:

    Source File: c:\pathtosite\Umbraco\masterpages\umbracoPage.Master Line: 39

  2. Gravatar ImageShannon Deminick Says:

    Think this is a .Net 4.5 issue, I'll check the source and ensure that it's working against 4.0.

  3. Gravatar ImageSean Says:

    Is the .net4.5 vs 4.0 issue fixed yet?

  4. Gravatar ImageStephen Says:

    I have upgraded to 6.0.0 and ran the FixPath but it hangs on Fixing content recycle bin. I had noticed before this that when I empty recycle bin it says there is one item but it will not delete it and no items are visible within the recycle bin node.

  5. Gravatar ImageSebastiaan Janssen Says:

    Sean: Yes, please redownload the package.

    Stephen: Interesting, it does everything else first though, right? Please create an issue on and attach your log file from /App_Data/TEMP/Logs so we can diagnose and help.

  6. Gravatar ImageTed Jardine Says:

    Upgraded 4.11.3 to 4.11.4 and then ran the Path Fixup package, but five minutes later it's still "Fixing". Assuming it's either hung or...but a little hesitant to interrupt it.

    Not a very large site (again 4.11.4 upgraded from 4.11.3 which was previously upgraded from 4.6'ish?) running ASP.NET 4.0.

  7. Gravatar ImageTed Jardine Says:

    ...and log file has nothing pertinent. Posting here as it's the first place people will look regarding this "path fixup" package. Restarted it and second time around doing the same (almost as if nothing was happening behind the scenes).

    Will post to if continue to have issues.

  8. Gravatar ImageSean Says:

    When I run the Path Fixup package, it is also hanging, but on the recycle bin. Been waiting for a while now, and there is not a lot of content in it. I might just manually change the DB myself if it keeps hanging. But for the content, looks good!

  9. Gravatar ImageBjarne Fyrstenborg Says:

    After I have installed the package and click "Fix paths" button it's executing for a while and then stop at this message:

    " INVALID PATH DETECTED. Path for 1113 changed to: -1,1088,1215,1106,1113 "

    I am using Umbraco v. 4.11.1

    I had tried it with a smaller Umbraco installation on v. 4.11.0 .. but with a few attempts I got the green success message.

    In this installation it doesn't seem to continue after this message.

  10. Gravatar ImageChris Evans Says:

    I'm also getting a situation where the Fix Paths tool hangs and crashes.

    I my instance, I ran it with the console opened and noticed it was throwing this exception:

    No Document exists with Version 'd5d37b67-b8aa-4947-ba02-386d329ce9ce'

    I created an issue on YouTrack, with the full stack trace and a description of the installation etc:

  11. Gravatar ImageJonatan Cortes Says:

    Be careful with the Fixup Package! This morning I got the same error as Chris Evans, after the typical "INVALID PATH DETECTED".
    Plenty of node have been automatically moved to Recycle bin.

    I used this workaround:
    - Seek the register within table CMSCONTENTVERSION using the version in the error message.
    - Delete that register.

    For whatever reason, there was a partial created version that existed in cmsContentVersion but didn't exist in cmsDocument

  12. Gravatar ImageShannon Deminick Says:

    Hi Jonatan, The fixup package doesn't actually 'move' nodes, the problem is that they would have already been moved but the bug that existed in 4.10+ would not have updated their paths properly so they may not have been seen in the recycle bin. That said, if people are using this package they should definitely be careful as it does modify data in the database and should be sure to have a backup before proceeding.

    I've just released a new version (1.0.1) with some better error checking so it won't hang when exceptions like: "No Document exists with Version 'd5d37b67-b8aa-4947-ba02-386d329ce9ce'" are thrown. I believe these exceptions are being thrown because there may be orphaned documents in the database. This could also have been a side affect from the bug that existed in 4.10+ due to paths/levels not being updated after a move.

    Thanks for all of the feedback so far, if there are more issues with this package or with the database data inconsistencies caused by this bug in 4.10+ please log the issues on the tracker (it's much easier to track bugs, feedback, etc... on there than it is here :)

  13. Gravatar ImageMike Says:

    I have installed Fix Path package but I can't seem to run it I click the button nothing, checked the Umbraco log file checked mc application log and still nothing. I Uninstalled the package and made sure it was unblocked reinstalled it and still nothing.

    I am using Umbraco 4.10.1 on iis7 .net 4.5 any help appreciated.


  14. Gravatar ImageSebastiaan Janssen Says:

    @Mike as Shannon said above, please file a bug report at so we can have a look, attach the log file from App_Data/Logs

  15. Gravatar ImageMike Says:

    Can Umbraco multy sites, means 1 Umbraco installation for multy domains?

    What about
    - laguage packages, e.g. German?
    - extensions, e.g. eShops?
    - forms, e.g. for emails, polls

    Is Umbrco really free of charge? I saw in the homepage prices up to 3.000 €.

  16. Gravatar ImageSebastiaan Janssen Says:

    @Mike Yes it can do that, for specific questions, please head on over to the forum:

    Umbraco is 100% free! We ask money for support contracts and a few specialized packages, but they are not a requirement for you to buy.

  17. Gravatar ImageDavid Says:

    Umbraco version 4.11
    I would like to use filedownload methos in umbraco razor macro script to download pdf files stored on the same server with the umbraco application (not in the umbraco folder).
    Can you let m eknow the right way?

  18. Gravatar ImageSebastiaan Janssen Says:

    @David Make sure to post your questions to instead.

  19. Gravatar Imageblake Says:

    Question about the path fix up package (sorry if this is a stupid question & possible answered). I've got a couple 4.11.1 & 4.11.3 umbraco sites. I HAVE successfully run the path fixup package (thank you for that) but do I need to re-run that package if I don't upgrade umbraco? Just curious if running it once is enough to fix the bug and database paths. Thanks!

  20. Gravatar ImageSebastiaan Janssen Says:

    @Blake Most likely, yes. As soon as someone starts moving nodes around, the paths will get corrupted again so you'll have to re-run it regularly. An workaround could be to disable the move / copy functions for editors.

  21. Gravatar Imageblake Says:

    Thank you @Sebastiaan for the reply. Looks like we have a few client sites to upgrade. :)

  22. Gravatar Imageblake Says:

    Would anyone happen to know if this works on version 4.11.8? I just upgraded a 4.11.3 site that i ran the package on before but after the upgrade it just stays on fixing. Thx!

Leave a comment