Post by CrashNBurn » 17 Jul 2014, 13:37
In this case, it might be once you've used a wrong (illegal) name, what gets submitted is (as lexikos indicated) is no name/blank. And at the stage where you need to correct that, there seems to be a something preventing the corrected name from being accepted.
Perhaps, when an illegal name is detected, the page should just redirect back to the previous form where the captcha is, so the 'unique code' can be regenerated? Although to prevent undue frustration, would need to make sure the forms' fields are repopulated.
Another option would be to use JS to prevent illegal names (easy), or prevent already existing usernames from being submitted (not as easy, AJAXy interaction JS/PHP).
Another workaround/option would be to have a "validate-name" button beside the Username input field, and not let the form itself be submitted until the name has been validated as unique and not using illegal chars. Which could be fairly straight forward - disable the [submit] button until the username has been validated.
One Bonus: the password field accepted my lengthy password, that looks something akin to:
ÐßÇ5¹Æé–½ö›àè°œßbâþÂo‹íß6n²ù0
In this case, it might be once you've used a wrong (illegal) name, what gets submitted is (as lexikos indicated) is no name/blank. And at the stage where you need to correct that, there seems to be a something preventing the corrected name from being accepted.
Perhaps, when an illegal name is detected, the page should just redirect back to the previous form where the captcha is, so the 'unique code' can be regenerated? Although to prevent undue frustration, would need to make sure the forms' fields are repopulated.
Another option would be to use JS to prevent illegal names (easy), or prevent already existing usernames from being submitted (not as easy, AJAXy interaction JS/PHP).
Another workaround/option would be to have a "validate-name" button beside the Username input field, and not let the form itself be submitted until the name has been validated as unique and not using illegal chars. Which could be fairly straight forward - disable the [submit] button until the username has been validated.
One Bonus: the password field accepted my lengthy password, that looks something akin to:
ÐßÇ5¹Æé–½ö›àè°œßbâþÂo‹íß6n²ù0
