Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Contact: When multiple instances of the field type "name" are used, only the last field will be sent. #156

Open
AlexGStapleton opened this issue Mar 28, 2016 · 2 comments

Comments

@AlexGStapleton
Copy link
Member

issue reported here

When multiple instances of the field type "name" are used, only the last field will be sent while still having all "name" fields visible on the frontend.

All of the name fields should be visible in the email, but it would be ideal if all name fields could be merged.

Use case: User adds two fields both set to name. One for first name and one for last name. Only the last name field is sent.

e7ab9c8c8-45

@braamgenis
Copy link
Contributor

The current assumption is that users will use a single field for name, to input name, surname, middle names etc. To solve this quickly we can take a convention-based approach, where users will have to know that the name fields are expected to be in a certain order. A more user-friendly solution is to implement the suggestion in GH-155, but that will be more complicated and take longer to get out.

@Misplon
Copy link
Member

Misplon commented Jun 11, 2019

Greg estimates that changing the logic of the widget to allow for the sending of multiple single-use fields like "Name" would take 2-3 hrs. It's quite hard to assign that time given the low number of requests for this change. I'm going to document the limitation and will leave this as p3 for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants