Copied to clipboard

Flag this post as spam?

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


  • Gordon Saxby 1271 posts 1498 karma points
    May 23, 2019 @ 15:07
    Gordon Saxby
    0

    Upgrading Umbraco many versions

    I am working on a large Umbraco project which was based on 7.4.2 - I have successfully updated it to 7.4.3 and am just working on 7.5.0.

    I am trying to get to the latest v7, if possible, and am wondering if I need to go step by step (version by version), or if I can make bigger steps?

    Any ideas and/or suggestions?

  • Marc Goodson 887 posts 5809 karma points MVP 4x c-trib
    May 23, 2019 @ 16:49
    Marc Goodson
    0

    Hi Gordon

    In theory you can go all the way, in practice it 'depends' on your solution, and plugins and history of your database table index names, and whether all db migrations have run in past... and whether you have hundreds of backoffice users... etc etc the list goes on

    The version specific guide is your friend:

    https://our.umbraco.com/documentation/getting-started/setup/upgrading/version-specific

    But essentially in 7.7.0 the concept of User Groups were introduced and lots of database stuff related to user permissions were changed, you need those migrations to run...

    consequently I've found in the same circumstances you are in, that leaping to 7.6.13

    is a useful interim step to take.

    then to 7.7.13...

    then should be fine to move to 7.14 (although I've only ever gone as far as 7.13.2 recently)

    regards

    Marc

  • Gordon Saxby 1271 posts 1498 karma points
    May 24, 2019 @ 07:51
    Gordon Saxby
    0

    Thanks Marc.

    There are a number of breaking changes between 7.5.0 and 7.6.13 - did they not cause you any problems? 7.6.0, for example, seems to have a lot of breaking changes.

  • Marc Goodson 887 posts 5809 karma points MVP 4x c-trib
    May 24, 2019 @ 14:07
    Marc Goodson
    0

    Hi Gordon

    No, issues I had with going from 7.4 and 7.5 directly to 7.12 and more recently 7.13 have centred around not being able to login to authorize the upgrade which will trigger the database migrations to run, but the database migrations include the database changes that allow you to login... if that makes sense!

    So when I've had this issue, upgrading to 7.6.13 is the magic step that makes it work...

    What I would suggest is get a vanilla version of Umbraco that you are aiming to upgrade to, and point the connection string at a copy of your site - keep the umbracoConfigurationStatus appsetting blank. keep useLegacyEncoding the same, and see if when running the site, you can login and trigger the database upgrade. If you can and upgrade completes, then you know you can go directly to that version with your solution - if not, then 7.6.13 is likely the interim step to take.

    In the last two months, I've upgraded 9 sites, only 2 needed to go via 7.6.13 - then I tend to use the version specific guide to make sure settings that have changed, and dlls that can be removed are manually removed - and use source control for comparing config changes with existing site and upgraded version....

    if that makes sense!

    regards

    marc

  • Gordon Saxby 1271 posts 1498 karma points
    May 24, 2019 @ 14:33
    Gordon Saxby
    0

    then I tend to use the version specific guide to make sure settings that have changed, and dlls that can be removed are manually removed - and use source control for comparing config changes with existing site and upgraded version

    I'm using the command "Install-Package UmbracoCms -Version 7.n.n" in Visual Studio. It usually asks whether to overwrite the config files - should I answer Yes or No? The upgrade guide seems a little confusing over that!?

  • Gordon Saxby 1271 posts 1498 karma points
    20 days ago
    Gordon Saxby
    0

    Hi Marc, can you point out where DLLs that are no longer required are listed please?

    I decided to make the interim step to 7.6.13 ... I'll get that sorted and released to live, then come back and update to the latest v7.

  • Ricardo Marcelino 13 posts 71 karma points
    20 days ago
    Ricardo Marcelino
    0

    Hello!

    I too have done around 7 updates to existing websites, and did a similar approach to Marc Goodson's. But in my case with more baby steps.

    I have updated to the latest version of each of the versions indicated on the Version Specific upgrades documentation page, so when it says 7.7.0, I updated to 7.7.13.

    So my path of upgrade ended up being:

    1. 7.3.8
    2. 7.4.3
    3. 7.6.13
    4. 7.7.13
    5. Latest version (at time of writing, 7.14.0, with no version specific upgrades in between)

    This way it ended up being easier to test and with no issues whatsoever.

  • Ricardo Marcelino 13 posts 71 karma points
    20 days ago
    Ricardo Marcelino
    0

    can you point out where DLLs that are no longer required are listed please?

    They are pointed out in the Version Specific upgrades page, being 7.3.0 an example!

  • Gordon Saxby 1271 posts 1498 karma points
    20 days ago
    Gordon Saxby
    0

    Ah, OK. I started from 7.4.3, so the removals as of 7.3.0 don't apply. I will check the other info though, for the later releases.

  • Marc Goodson 887 posts 5809 karma points MVP 4x c-trib
    May 25, 2019 @ 09:01
    Marc Goodson
    0

    Hi Gordon

    If I have the existing config of the site commited into a git repo then yes I let the nuget install overwrite the config.... Then for each config file you can see in your git client exactly what has changed... Eg settings added or settings removed... Or settings you want to keep that will be overwritten by the fresh upgrade set of config! - the git client makes it easy to see and merge the configs... so that you end up with your Umbraco implementation specific config settings along with any new config added for specific version...

Please Sign in or register to post replies

Write your reply to:

Draft