You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: