Show a warning if the database is in a non-upgradable state

[OwainJ]

Currently, if the database is in an non-upgradable state, e.g. the migration step GUID in umbracoKeyValue does not exist in the migration plan), then Umbraco will simply show the Umbraco installer screen and prompt an upgrade. (it will fail with an error if you click continue, but this initial screen can cause confusion)

How can the database be in an "non-upgradable" state?

Let's say you have a Umbraco 12 website, and someone accidentally connects to it's database with a v13 project and upgrades it, then you will suddenly be greeted with the upgrade screen which states you need to upgrade to your current version of v12:

In the screenshot above (taken from this forum post: https://our.umbraco.com/forum/using-umbraco-and-getting-started/113543-umbraco-12-automatic-upgrade) the website is running Umbraco 12.3.3, but the database has seemingly been upgraded to v13; and as the v12 migration plan does not contain the v13 migration steps, it simply prompts to run an upgrade (which will fail and show a migration not supported error).

This is quite confusing to the user/dev who encounters this, as the migration plan GUID shown 6158F3A3 is completely meaningless unless you have prior knowledge of how Umbraco's migration plan works.

There's currently no way of knowing that 6158F3A3 correlates to a v13 migration step, unless you search the Umbraco source code.

What should happen instead?

It would be much better if Umbraco could somehow check if the migration step exists in the current migration plan and, if it does not, display some kind of warning to inform the user that the database is non-upgradable.

Something like this:

I thought I should bring this up as I have seen a few posts on our where people have encountered this situation:

• https://our.umbraco.com/forum/using-umbraco-and-getting-started/113543-umbraco-12-automatic-upgrade
• https://our.umbraco.com/forum/using-umbraco-and-getting-started/113539-issues-with-umbraco-1200

[jbreuer]

Great idea! I've also run into this issue myself. See this forum post: https://our.umbraco.com/forum/using-umbraco-and-getting-started/108170-the-migration-plan-does-not-support-migrating-from-state

[naepalm]

I really like this idea! I've run into this issue multiple times and then we have to dig through the database to figure out what the version mismatch is and why.

I think some more helpful text would be super useful. Also I wish the GUIDs were somewhere easy to find that wasn't digging through the source code. When all you want to know is what a version means, it'd be great to have some easily sortable/parseable/searchable table somewhere.