-
-
Notifications
You must be signed in to change notification settings - Fork 403
Description
Description
When creating the registration template, I added first name and last name. I locked these values. However, the person is able to change them on the event registration which then creates a duplicate person record.
Actual Behavior
ER is set to locked for first name and last name:

The person is required to login:

ER allows me to change it anyway:

Upon changing it, it creates a second person record:

Expected Behavior
The first and last name fields, while they can be changed on the screen (according to the Rock documentation), it will not save to the person record. However, I don't think it should create a duplicate person record. Something about this functionality is not right when a person is simply registering himself and we don't want them to edit their name.
Steps to Reproduce
- Create a simple event registration and lock the value of the first and last name field. Require a login so that these fields populate.
- Login as the person without any security roles (not a rock admin or any other security role)
- Go to the event registration = the first and last name fields are editable.
I recreated this on rmslatest.
Issue Confirmation
- Perform a search on the Github Issues to see if your bug is already reported.
- Reproduced the problem on a fresh install or on the demo site.
Rock Version
Rock McKinley 17.6 (17.6.1)
Client Culture Setting
en-US