: Single Full Name field in registration form user submits only first what to enter in my backend as last? On a registration form I have a single input called Full Name. The strings are parsed
On a registration form I have a single input called Full Name. The strings are parsed with code.google.com/p/php-name-parser/ so if a person enters their full name middle or any quantity of strings it's handled just fine and the app creates the user in a billing system with it's API.
The form validates and checks for two strings in the field otherwise it won't post. I'd like to remove this validation but a last name is required by the API. You cannot post an empty last name to the API.
Users are signing up for a trial so I don't want them having to deal with many form fields. The only place the last name shows up visible to the user is in their account settings page. If they end their trial and start a paid plan they'd have to enter their billing details which asks with two fields for their First, Last, and other billing information.
What is an alternative to submitting "Doe", "Default", "Empty" in place of them not filling in their last name?
More posts by @Si4351233
2 Comments
Sorted by latest first Latest Oldest Best
Are your visitors going to have a user/account name in addition to their "proper" name? If so, get a username only for trial purposes(or even just use their e-mail address) and only ask for full profile information once they decide they want to actually move to a paid plan. This is less invasive all around(since they may not even come back), and doesn't manufacture extra work for you. Plus, if you use the e-mail address option, you have a bit of contact information for them if you want to send a reminder poke later on for marketing purposes or whatever. (Anybody who really don't want you to do this will probably just lie about the address.)
[Adding after response to my comment above]
I figured you were earlier in the development. It wasn't clear you were already more or less locked into an implementation. As far as having to put something in the field, I'm not sure there's any pretty solution. Given the situation as you mention, I'd actually lean toward putting some kind of gibberish in the field, just to be absolutely sure it won't collide with a real name. (So, eg. "sdafasaddsafds") Then you'd have to build in logic to always hide that value from users. This way, if they choose to stay with you and edit the field they won't see any weird value but can still provide their own on the edit form. It's a nasty solution, but should be kinda safe.
Ask them for "name or id" and if they just full in ID, use that as the last name.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.