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
Nickname shows up in the First Name field of a registration. In the Registration Template > Registration form, the Person Field labeled as "First Name" is being used. However, during the registration process, the Nickname field is displayed instead of the First Name. This creates confusion because users see the Nickname on the form and thinking they are seeing the Firstname. This became evident when using Electronic Signature documents and LAVA {{ Registrant.FirstName }}.
Actual Behavior
The Registration Template uses the Person Field = First Name. The registration shows the nickname in the first name field but does not save in the database that way.
Expected Behavior
I would expect the First Name to be displayed as the First Name and the Nickname to be an optional Person Field to display on the registration form.
Steps to Reproduce
Create an Event Template containing the First Name person field.
In the Registration template details, check "Show Family Members".
Make sure you have a profile you can login with to complete the registration, as well as someone in the family with a different nickname.
Complete the registration with the selected family member and see their Nickname pop up in the First Name field.
Issue Confirmation
Perform a search on the Github Issues to see if your bug or enhancement is already reported.
Reproduced the problem on a fresh install or on the demo site.
Rock Version
16.6 and 16.8
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered:
Description
Nickname shows up in the First Name field of a registration. In the Registration Template > Registration form, the Person Field labeled as "First Name" is being used. However, during the registration process, the Nickname field is displayed instead of the First Name. This creates confusion because users see the Nickname on the form and thinking they are seeing the Firstname. This became evident when using Electronic Signature documents and LAVA {{ Registrant.FirstName }}.
Actual Behavior
The Registration Template uses the Person Field = First Name. The registration shows the nickname in the first name field but does not save in the database that way.
Expected Behavior
I would expect the First Name to be displayed as the First Name and the Nickname to be an optional Person Field to display on the registration form.
Steps to Reproduce
Issue Confirmation
Rock Version
16.6 and 16.8
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: