World is now on Opti ID! Learn more


Aug 4, 2014
  3380
(0 votes)

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.

 image

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:

http://world.episerver.com/Documentation/Items/Installation-Instructions/Installing-EPiServer-updates/

[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.

Release Notes:

EPiServer.Commerce 7.10
EPiServer.Commerce.UI 7.10

Aug 04, 2014

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |