Copied to clipboard

Flag this post as spam?

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


  • Vincent 1 post 71 karma points
    18 days ago
    Vincent
    0

    Upgrade to V10-RC1 Error

    Hi,

    Newbie here, We have a new Umbraco project that we would like to launch in 2 or 3 months. We saw that it was a good option to use V10-RC1 for that. At the moment the project is running 9.5 but when we upgrade it to V10 and follow the steps we get the following Error:

    Method not found: 'Umbraco.Cms.Infrastructure.Migrations.ExecutedMigrationPlan Umbraco.Cms.Infrastructure.Migrations.Upgrade.Upgrader.Execute(Umbraco.Cms.Core.Migrations.IMigratiowatch : Exited with error code 134

    Hope anybody can help with this error. We went back to V9.5 wich works for now.

  • Mike Isaacs 1 post 71 karma points
    1 week ago
    Mike Isaacs
    0

    I had this same issue on a project upgrade to v10. For me, the issue was USync - once I'd removed the package the project started up fine.

    I just tried installing the latest USync version on a clean Umbraco 10 project (straight from the dotnet template) and I get the same error.

  • Jamie Pollock 174 posts 853 karma points c-trib
    1 week ago
    Jamie Pollock
    0

    Hey Mike, This is hilarious. I was upgrading our project this morning to v10-rc1 and stumbled on this thread earlier today. Found the issue was uSync about 30 minutes ago and was going to report back.

    For now v9.3.2 should work with v10-RC1. The issue is v9.4.0 came with the new FirstBoot feature which adds a migration and migrations changed in v10 ever so slightly. I've created an issue for this here: https://github.com/KevinJump/uSync/issues/390

  • Carlos Rey 9 posts 103 karma points
    1 week ago
    Carlos Rey
    0

    Ive run into this issue with other packages too....

  • Carlos Rey 9 posts 103 karma points
    1 week ago
    Carlos Rey
    0

    Looks like the breaking change is the method sig in the migration :

    from v9:

     public ExecutedMigrationPlan Execute(IMigrationPlanExecutor migrationPlanExecutor, ICoreScopeProvider scopeProvider, IKeyValueService keyValueService)
    

    to v10:

     public ExecutedMigrationPlan Execute(IMigrationPlanExecutor migrationPlanExecutor, IScopeProvider scopeProvider, IKeyValueService keyValueService)
    

    This would break a LOT of packages. You would think this should be backwards compatible...

  • Jamie Pollock 174 posts 853 karma points c-trib
    1 week ago
    Jamie Pollock
    0

    To be fair this is a major release which is allowed breaking changes. Also this is a RC1 not the final release. It will give developers some time to update their packages should they choose to support v10 in the future.

  • Simon Justesen 63 posts 175 karma points
    1 week ago
    Simon Justesen
    0

    I'd advise strongly against using RCs in production. There might still be breaking changes awaiting. Also it usually takes a while for package maintainers to update their code and dependencies.

  • Marc Goodson 1682 posts 11099 karma points MVP 6x c-trib
    1 week ago
    Marc Goodson
    0

    @all There is a beta of usync for V10 released today that would be worth giving a spin with the v10 RC:

    https://blog.jumoo.co.uk/2022/v10-betas/

  • Carlos Rey 9 posts 103 karma points
    1 week ago
    Carlos Rey
    0

    It stops the BO crashing and does actually sync when run. The UI seems to be broken though with placeholders for labels & text. But it works!

  • Kevin Jump 2115 posts 13361 karma points MVP 5x c-trib
    1 week ago
    Kevin Jump
    1

    Hi,

    If you have had a older version of uSync installed on the v10 release and then updated, you should remove all uSync folders from app_plugins, and then rebuild.

    the newer vesion doesn't use the files in app_plugins anymore - but if they are there they might take priority over the ones it does use.

    (i think for the next v10 release we will put in a clean to remove them incase people do this)

Please Sign in or register to post replies

Write your reply to:

Draft