Tim, no worries on the delay for me -- whenever you have time.
Well yes and no on the code location...
Granted, it might not matter, but the "flow" of that handling was unexpected since the login was technically invalid.
I would have expected:
[Login] => [Invalid Login]
Instead of:
[Login] => [DB Update] => [No Session Error] (nothing about a bad login)
So, rethinking the picture, even my suggested move may not be enough to achieve the invalid login first, before DB upgrade, as it should flow.
This may be something to fix post-release?
I won't dwell on it, only an observation during testing. (and would only take the DB Upgrade flow if admin, I believe)
