Closed adrianbanks closed 9 years ago
I've not looked at the code yet, but I think we may be able to mitigate this a little. Can we chat about it before the end of the day? I'm keen to get this fixed before submissions open if possible.
Sure. I'm open to any ideas.
Can't be merged until the build is fixed - there's some kind of NuGet error:
"The build restored NuGet packages. Build the project again to include these packages in the build. For more information, see http://go.microsoft.com/fwlink/?LinkID=317568"
Wow, DotNetOpenAuth really likes screwing with your Web.config...
:+1: for the changes beyond the one pretty minor refactoring.
This fixes #333.
This is a bit of a pig. I've fixed the logging in behaviour, but there is an outstanding issue that I can't fix. Any user who has already logged in via Google, when logging in again will get a new account. There isn't an upgrade path for these logins.
To mitigate it, I've added a warning message asking people to contact us. I think that is pants however.
Anyone got any better ideas?
(There is supposedly an upgrade path, but I can't get through the confusion of the docs to figure out how to make it work correctly.)