Unable to Register

[CrashNBurn71]

Unable to Register, attempted with user Crash and CrashNBurn. Both get a "Fatal Error" when login is attempted.

Fatal Error Invalid value - method [post] type [string] name [password]

There was also another similar Fatal Error when attempting to copy-paste the emailed confirmation code into the page form, instead of clicking on the emailed link.

[zenbi]

Hmmm... the "Invalid Value" error should only occur when an invalid character is in the input string. The password can be up to 64 characters and use pretty much any of the keys on a English keyboard including: "[A-Z][a-z][0-9]`~!@#\$%^&*()_+-=[]{}|;':\",./<>? "

A fix is being worked on for the confirmation code bug, until then, like you've already found click the link in the email.

Let me know if you have any further problems, since I just now (few hours ago) changed mail servers and I'd like to make sure registration still works!

[CrashNBurn71]

Ah, so you only allow typeable characters....My password generator uses the full 255 character ANSI-set except for the various spaces and control-codes, ~225 characters.

So it would of been something like this: qu’8Xœ3&CZåƒí2Ð+2F(8(âkX4â¦ÑÇÑV0 I would of expected UNICODE compatibility. The page source for pipedot.org claims to be UTF-8.So the site is not UTF-8, if you are filtering passwords to only be allowed to use ~50 characters.

CB

On Wednesday, October 12, 2016 1:23 PM, Bryan Beicker <notifications@github.com> wrote:

Hmmm... the "Invalid Value" error should only occur when an invalid character is in the input string. The password can be up to 64 characters and use pretty much any of the keys on a English keyboard including: "[A-Z][a-z][0-9]`~!@#\$%^&*()_+-=[]{}|;':\",./<>? "A fix is being worked on for the confirmation code bug, until then, like you've already found click the link in the email.Let me know if you have any further problems, since I just now (few hours ago) changed mail servers and I'd like to make sure registration still works!— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.