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.
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
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.
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.
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)
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:
Hope anybody can help with this error. We went back to V9.5 wich works for now.
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.
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
Ive run into this issue with other packages too....
Looks like the breaking change is the method sig in the migration :
from v9:
to v10:
This would break a LOT of packages. You would think this should be backwards compatible...
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.
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.
@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/
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!
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_pluginsanymore - 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)
is working on a reply...