Tonight I attempted to register a new account on bugs.python.org and encountered a bug.
* I visited http://bugs.python.org/user?@template=register and filled it out with the username "ryanpetrello"
* I received a confirmation email and clicked on the link provided (on the bugs.python.org domain). I can provide the exact link from my email if necessary.
* Upon clicking the link, I was taken to bugs.python.org and was shown an error that said, "Invalid URL scheme in homepage URL". From here, I was unable to confirm my registration and login.
* I attempted a second registration (with a different username, ryan.petrello). This time I did *not* provide a homepage URL, and was able to confirm my registration and login.
I suspect that on my original user registration (ryanpetrello), the homepage URL I specified must have omitted an http:// or https://
The fields (email address, homepage, roles) are validated (by detectors/userauditor.py) only once the user is being created, and that happens while clicking on the confirmation link. I can't think of any simple way to validate them beforehand on the server side, however if you get an error, no user should have been created and you should be able to reregister with the same username and with correct information.
A user here https://github.com/python/peps/pull/517 got the same "issue".
I explained him the issue, so he can fix the URL in his profile, but the issue is more like:
- The message is hard to understand, it should help point to the profile so the user can fix the URL
- The URL should be checked before, not during validation, so they have the error right after typing it, not a few days later
Yep, I am that user, and changing the URL worked. I guess that the site doesn't try to map strings like about.me/james.ray to http://about.me/james.ray or https://about.me/james.ray, while my browser does. And yes, as mdk mentioned on the page, failing doing that outputting an error straight after typing the URL or submitting the form would be the next best option.
I ran into the same issue of the "homepage" validation - but failed to notice the error message amongst all the other information.
I suggest if an error occurs in the confirmation, the error should be (virtually) the only thing displayed - giving the current issue list as well is confusing and unnecessary. If the confirmation succeeds a dedicated screen is displayed - the same should be true if it fails.