Copied to clipboard

Flag this post as spam?

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


  • Kevin 18 posts 121 karma points
    Sep 08, 2022 @ 10:26
    Kevin
    1

    Upgrading v8 to v10 (uSkinned & cloud)

    Has anyone successfully upgaded a cloud project running uSkinned from v8 to v9/v10 ?

    The uSkinned guide: https://uskinned.net/support/how-to-upgrade-from-uskinned-site-builder-for-umbraco-8-to-umbraco-10/

    is quite different to the Umbraco guide: https://our.umbraco.com/documentation/Umbraco-Cloud/Upgrades/Migrating-from-8-to-10/)

    so i've been following the uSkinned one but can't get past the initial run where you log in for the first time.

    As the guides feel a bit incomplete in parts, the process I've followed is:

    1. Connect to live v8 database and export as .bacpac
    2. Import locally into SSMS
    3. Create a new v10 project within cloud and clone dev environment
    4. Open local v10 project and per the guide, install uSkinned and uSync
    5. Update the connection string in appsettings.Development.json to the local v8 database
    6. Per the guide, change the unattended upgrade and package migration settings
    7. Copy the /usn/updates/3.x contents to root
    8. Run the site.

    The front end shows a 404 as expected. The backend loads the login screen

    When i try to sign in though I get this error

    enter image description here

    Has anyone successfully upgraded a v8 > v10 cloud uSkinned site before? what am i doing wrong? what does the above error indicate?

    thanks

  • Marc Love (uSkinned.net) 431 posts 1669 karma points
    Sep 08, 2022 @ 11:13
    Marc Love (uSkinned.net)
    2

    It seems that Umbraco Cloud databases have 4 additional tables.

    Create copies of the following 4 tables based on the local database you cloned from the new Umbraco 10 Cloud Site.

    umbracoCreatedPackageSchema

    umbracoDeployDependency

    umbracoDeploySignature

    umbracoIdTockenCache

  • Kevin 18 posts 121 karma points
    Sep 08, 2022 @ 12:41
    Kevin
    0

    Thanks Marc, done that and its got me in :)

  • Kevin 18 posts 121 karma points
    Sep 08, 2022 @ 13:12
    Kevin
    1

    I stopped the site to carry on with the upgrade and now when i run it i just get the following error about a duplicate dictionary key

    enter image description here

  • Marc Love (uSkinned.net) 431 posts 1669 karma points
    Sep 09, 2022 @ 13:23
    Marc Love (uSkinned.net)
    0

    Cloned Umbraco Cloud environments will by default try to run package migrations. uSkinned Site Builder will run a package migration to create demo content and setup other settings. In this upgrade scenario you do not want the package migration to run again. You need to disable the default behaviour of Umbraco Cloud with the following settings:

    {
      "$schema": "https://json.schemastore.org/appsettings.json",
      "Umbraco": {
        "CMS": {
          "PackageMigration": {
            "RunSchemaAndContentMigrations": false,
            "AllowComponentOverrideOfRunSchemaAndContentMigrations": false
          }
        }
      }
    }
    
  • Kevin 18 posts 121 karma points
    Sep 09, 2022 @ 14:04
    Kevin
    0

    Thanks Marc,

    This helps and allows us to get further until... enter image description here

    The complete process to replicate this is

    1. Connect to live v8 database and export as .bacpac
    2. Import locally into SSMS
    3. run script to add missing cloud tables to database
    4. Clone v10 dev environment locally
    5. Update connection string to local v8 database
    6. Change unattended upgrade and package migration settings (including latest override setting)
    7. Build site (otherwise folder in next step does not exist)
    8. Copy /usn/updates/3.x contents to root
    9. Run site
    10. Go to backend > usync and import settings and content
    11. Stop project
    12. Start project {error}

    The v8 uSkinned project we're trying to upgrade is quite simple in structure so i'm surprised no one else has come across this so far. Would be great if someone else can try this to try and find a solution

  • Kevin 18 posts 121 karma points
    Sep 09, 2022 @ 15:10
    Kevin
    0

    To update: the above error is related to Umbraco Forms. Like someone else in the forum post below, I'd also decided not to migrate my v8 forms to the db as it would be easier to just rebuild them in the new v10 site.

    https://our.umbraco.com/forum/using-umbraco-and-getting-started/109436-umbraco-forms-upgrade-v8-to-v10

    Running this on the DB resolves it

    DELETE FROM umbracoKeyValue
    WHERE [key] = 'Umbraco.Core.Upgrader.State+UmbracoForms'
    
Please Sign in or register to post replies

Write your reply to:

Draft