Signup UX issue on Name field position

AI-generated summary

A user, wendellverli, reported a signup issue where a user was unable to sign up due to a “Password too common” error, despite trying multiple passwords. Moin suggested that the issue might be due to the password being the same as the name, which was entered in the “Full Name” field. wendellverli argued that the issue is due to the “Full Name” field being placed at the end of the signup form, which is an unconventional flow that can confuse users into thinking it’s a “confirm password” field. This issue was corroborated by Vaping_Community, who had a similar experience. pmusaraj acknowledged the issue and stated that a change is planned to address this, including adding a site setting to make the “Full Name” field optional or required.

One of our users tried MANY passwords, with and without their new account user name resemblance… with special characters… all of them said “common” password and she could NOT signup … has anyone received or seen any bug on the latest update?



“Password too common” – I mean? wow? Anyone can help? Ideas?

I think the problem is that the password is the same as the name.

When your name was “fl0rentef0t0gr4f4!@?)(” I could guess that this is your password and you accidentally entered that into the name field as well.

2 Likes

@Discourse please IA is not correct on the Signup flow

Full Name
Email
Screen Name
Password

Having the “full name” as the last field confuses users into thinking it’s a “confirm password” and it’s just never a normal flow to add your “Full Name” at the end of a signup form.

#pleaseadvise

4 Likes

I did the exact same thing today while signing up a test account on my site, just assumed it was a verify password box :man_facepalming:t2:

2 Likes

Yes, we’re with you on this. We will be working on a change here soon. The plan is to add a site setting that lets admins choose whether to show the Full Name field on the signup form, and whether it should be optional or required.

4 Likes