For Those Who Had Issues Updating to Commerce 7.10
Last Friday, new updates were released for the Commerce NuGet packages. The version numbers are now 7.10.1. I am aware that many who tried to update to the older 7.10 packages were greeted with a new migration page which forced a database update. Unfortunately, it seemed that those who attempted to update to 7.10 got migration failures instead.
I am happy to note that the migration issues should be fixed in 7.10.1 and I was able to update a base Commerce 7.5 site with sample templates to 7.10.1. Via NuGet console, I installed EPiServer.Commerce and then ran “update-epidatabase” to get to the migration page on my Commerce site.
Migration completed. Yay!
Clicking on “Go to start page” should direct you to your newly updated 7.10.1 site.
Information specific to what’s new in Commerce 7.10 can be hard to find, so here’s some quick links to get you in the right direction:
[New in 7.10.0] An update may have one or more migration steps that need to be executed in order for the site to work correctly. If so, any request to the site will be redirected to a migration page. In order to access it you need to be part of the "CommerceAdmins" role. From there it is possible to run the migration steps and track the progress. Once all steps have been completed successfully the redirects will stop, and the site will be back to normal.
[New in 7.10.0] It is possible to have the migration started automatically during the sites initialization. That is done by adding an app setting called "AutoMigrateEPiServer" and setting the value to "true". However, until all steps have been completed, any requests will still be redirected to the migration page, where it is possible to track the progress.