Copied to clipboard

Flag this post as spam?

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


  • Iain Waddell 15 posts 125 karma points
    Jul 28, 2021 @ 14:21
    Iain Waddell
    0

    How to manage edits to files during upgrade

    Recently tried upgrading a number of Umbraco sites from v8.11.1 to v8.14.0.

    One of the many issues I had was the change from Url to Url(). This involved updating files which had other site specific edits, so I couldn't just update copy the changes from our git repository.

    I was wondering how other people managed these migrations. Am I doing something wrong making my task particularly difficult?

  • Marc Goodson 1584 posts 10551 karma points MVP 6x c-trib
    Jul 30, 2021 @ 09:29
    Marc Goodson
    1

    Hi Iain

    I think the change from Url to Url() isn't mandatory? I think they just marked Url as obsolete and will remove it in V9... to give people a heads up that a change was coming... but maybe this was accidentally a breaking change?

    https://github.com/umbraco/Umbraco-CMS/pull/7550

    How to manage changes like this... I tend to read the version specific upgrade guide - for specific things that won't be automatically handled by the upgrade:

    https://our.umbraco.com/Documentation/Fundamentals/Setup/upgrading/version-specific

    (you can see with V8 this is a lot less than before!)

    and then I look at the version comparisons:

    https://our.umbraco.com/download/releases/compare?from=8.11.1&to=8.14.0

    which will list anything specifically identified as a breaking change.

    Each release usually has an accompanying blog post: https://umbraco.com/blog/umbraco-814-release/

    and when there is something accidentally breaking there is usually noise on the issue tracker / discussions / twitter in the days just after a release! and it's worth holding out for the point release that fixes the thing.

    But nowadays it's rare-ish to get a big breaking change like you describe on the same version series (largely because upgrades on Umbraco Cloud need to be as automatic as possible - although obsoleting MediaPicker2 was such a thing that has now been reverted) - which makes me think it's just an advisory for future obsoletion rather than something you needed to change in order to complete the upgrade.

    regards

    Marc

  • Iain Waddell 15 posts 125 karma points
    Jul 30, 2021 @ 09:55
    Iain Waddell
    0

    Marc,

    Thanks for the response. As I build with no warnings I suspect it was a breaking change for me.

    Just like Umbraco Cloud, our IT manager wants the upgrades to be fairly automatic and this one involved quite a bit of manual work.

    So perhaps this was a one off, but when changes are made to files that are also modified by customers (e.g. views), it gets quite tricky.

    Iain

  • Marc Goodson 1584 posts 10551 karma points MVP 6x c-trib
    Jul 30, 2021 @ 11:22
    Marc Goodson
    0

    Yes putting obsolete on the Url property would have created warnings but all should have worked "as before'...

    It will be removed in v9...

    So choosing to refactor now will save on the effort when you migrate to v9!

Please Sign in or register to post replies

Write your reply to:

Draft