Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Reggie Roberts 13 posts 33 karma points
    Nov 20, 2012 @ 16:13
    Reggie Roberts
    0

    Upgrade path from v4.6.1 to v4.9.1

    I have inherited an umbraco site that has not been upgraded since it's initial installation.  What is the best upgrade path from 4.6.1 to 4.9.1? 

  • Lee Kelleher 4026 posts 15836 karma points MVP 13x admin c-trib
    Nov 24, 2012 @ 03:15
    Lee Kelleher
    1

    Hi Reggie,

    The safest upgrade path would be: v4.6.1 » v4.7.0 » v4.7.2 » v4.8.1 » v4.9.0 - that would cover any config & database changes.

    I believe it would be possible to go straight from 4.6.x to 4.9.x, but I honestly think the number of config changes would be overwhelming.

    If you need any of the in-between versions, they should be available on CodePlex, or failing that I've got an "unofficial" archive.

    Good luck!

    Cheers, Lee.

  • Reggie Roberts 13 posts 33 karma points
    Nov 27, 2012 @ 19:34
    Reggie Roberts
    0

    Lee, thanks for your response.  I followed your upgrade path.  When I went from 4.7.2 to 4.8.1.  The admin page did not load correctly.  I found a post that recommended adding the "debug=false" to the compilation tag of the web.config file.  I made the change and the admin page did load with the following errors.  Any ideas on what is causing these errors?

    Webpage error details

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
    Timestamp: Tue, 27 Nov 2012 18:31:37 UTC


    Message: ASP.NET Ajax client-side framework failed to load.
    Line: 40
    Char: 34
    Code: 0
    URI: https://localhost/umbraco/dashboard.aspx?app=content


    Message: 'Sys' is undefined
    Line: 56
    Char: 1
    Code: 0
    URI: https://localhost/umbraco/dashboard.aspx?app=content

    Webpage error details

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
    Timestamp: Tue, 27 Nov 2012 18:33:26 UTC


    Message: ASP.NET Ajax client-side framework failed to load.
    Line: 40
    Char: 34
    Code: 0
    URI: https://localhost/umbraco/dashboard.aspx?app=content


    Message: 'Sys' is undefined
    Line: 56
    Char: 1
    Code: 0
    URI: https://localhost/umbraco/dashboard.aspx?app=content

     

     

  • Lee Kelleher 4026 posts 15836 karma points MVP 13x admin c-trib
    Nov 27, 2012 @ 19:44
    Lee Kelleher
    0

    Hi Reggie,

    I'm sure the 'Sys' namespace is an ASP.NET JavaScript library... strange that it isn't loading.  Difficult for me to guess what it might be... could be either that a copy-over of the "dashboard.aspx" got corrupted, or there is another server-side error that is further down and hidden by this JavaScript error.

    The ASP.NET JavaScript libraries are loaded in using a dynamic handler called "ScriptResource.axd" ... if you're comfortable with HTML, see if you can "view-source", dig out the "ScriptResource.axd" references and try to view those in your web-browser.  Hopefully you'll find a 500 Server Error - which will pinpoint the underlying problem.

    Good luck!

    Cheers, Lee.

  • Funka! 398 posts 661 karma points
    Nov 28, 2012 @ 19:35
    Funka!
    0

    When upgrading from 4.7.2 to 4.8.0 or higher, be sure you remember to delete /bin/App_global.asax.dll when you do; this is one thing I'ev forgotten once or twice and it can cause the whole site not to load.  Not sure if this is your problem here.

    We also always diff the entire config folder against the "stock" config folder (as well as /web.config itself!) you'll find supplied with the new version. Each change is reviewed to make sure we don't lose anything custom from before, and as you noted, sometimes other changes as well need to be carried forward.

    Best of luck!

  • Reggie Roberts 13 posts 33 karma points
    Dec 13, 2012 @ 18:48
    Reggie Roberts
    0

    I finally figured out the issue.  We use url rewriting on our web site.  One of the URL Rewrite rules was causing the issue.   This posting help me identify the problem.

    http://weblogs.asp.net/lkempe/archive/2007/08/04/asp-net-ajax-and-url-rewriting-issue.aspx

Please Sign in or register to post replies

Write your reply to:

Draft