You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have 8000+ (?) usernames already reserved. We'll have people that want to use them. (JPbarlow comes to mind). Thus, when someone is trying to login, we should check to see if that username is already reserved, check that the email addr they supply matches, and then record their (double entered) password.
The text was updated successfully, but these errors were encountered:
We're live on postgres now. Pre-reservation forms work. If anyone does register on test.hypothes.is that's the same DB and they'll have in-use errors if someone has reserved the name.
Any users migrated over are unable to log in until we send them an activation code, pending completion of the last issue on this milestone.
js-polyfills v0.1.15 used to install the polyfill on
`this.URL`, where `this` was set to module.exports in
the context of a Browserify bundle. Consequently the result
was available as `require('js-polyfills/url').URL`.
As of v0.1.16 however, it installs the polyfill on `self`,
which is the Window object in the context of the browser
and so `require('js-polyfills/url').URL` is undefined.
Fixes#63
We have 8000+ (?) usernames already reserved. We'll have people that want to use them. (JPbarlow comes to mind). Thus, when someone is trying to login, we should check to see if that username is already reserved, check that the email addr they supply matches, and then record their (double entered) password.
The text was updated successfully, but these errors were encountered: