Hello Support
User fields are still showing up in sign up page even with tickbox not ticked:
The discussion revolves around the issue of user fields still showing up in the signup page despite not being marked as required. Nrsinga_Dasa reports the issue and shares screenshots of their settings. codinghorror initially responds that itâs not a bug, but rather the intended behavior, as ârequiredâ means the field must be filled out. However, tshenry and Nrsinga_Dasa argue that the expected behavior should be to only display the fields if âRequired at signup?â is checked.
Nrsinga_Dasa points out that the fields can still be accessed via the membersâ preference section after signup, so thereâs no need to show them on the signup page. Stephen chimes in, stating that the behavior has been this way for a long time and that ticking the ârequiredâ box only adds a red asterisk, making the field optional at signup.
The discussion concludes with codinghorror suggesting that there might be a misunderstanding about what ârequiredâ means, and Stephen questioning the value of hiding user-edited fields during signup, arguing that it might not add friction if theyâre optional.
This is not a bug. Required means âmust be filled outâ.
Can you repro this @tshenry?
I can repro! The user field shows up on the signup modal with all boxes unchecked. The expected behavior should definitely be to only display if âRequired at signup?â is checked. Unless user fields were always intended to show on the signup modal, and the setting is only to enforce that the field is filled before a user can sign up.
It should not show up on signup page it not ticket. Because it can still be access via members preference section after signup. So definitely needs to edit code to not show.
@nbianca can you investigate a fix here. This sounds very odd to me.
It has behaved this way for as long as I can recall, I know several sites built on this behavior. Ticking required adds the red asterisk to the field and registration canât be completed unless itâs provided.
Previously I took that unchecked box to mean âoptional at signupâ. If the behavior of that box is going to change, as I know several places where providing additional data is optional and relies on those fields.
Yes, this, so different communities could ask for social media handles, etc. Asked, but not enforced.
Aha yes, that is what I remembered as well. So this is a misunderstanding about what ârequiredâ means. Or maybe we need two options here, not sure.. I donât favor a lot of extra work at this time though.
I guess it depends if thereâs any value in hiding user-edited fields during signup. If theyâre optional then they arenât adding friction.
I know from experience with customer environments that thereâs a stark difference in the completion rate on optional fields against the date of their implementation. Asking later just doesnât have the same takeup.