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

First Name/Nickname in Registrations #6160

Open
2 tasks done
tpeera opened this issue Jan 23, 2025 · 0 comments
Open
2 tasks done

First Name/Nickname in Registrations #6160

tpeera opened this issue Jan 23, 2025 · 0 comments
Labels
Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be.

Comments

@tpeera
Copy link

tpeera commented Jan 23, 2025

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.

Image
Image
Image

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

@sparkdevnetwork-service sparkdevnetwork-service added the Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be.
Projects
None yet
Development

No branches or pull requests

2 participants