eventespresso / event-espresso-core

Event Espresso 4 Core for WordPress: Build an Event Ticketing Website Today!
https://eventespresso.com
GNU General Public License v3.0
121 stars 87 forks source link

disable the option to change the autofill data #4173

Open minkah1 opened 2 months ago

minkah1 commented 2 months ago

At Arnes we organize a free, 3-day conference with many lectures and workshops. This conference is organized for teachers who receive a certificate of attendance at the end of the conference. To obtain this certificate, they must register through the single sign of one. At the same time, this conference is also organized for researchers who do not have the option of single sign one, so they are not logged into Wordpress when registering and do not need this type of certificate.

To avoid confusion regarding the issuance of certificates, we would like to disable the option to change the autofill data from sso in the registration form.

garthkoyle commented 2 months ago

To avoid confusion regarding the issuance of certificates, we would like to disable the option to change the autofill data from sso in the registration form.

Can you specify what autofill data you are referring to, or which autofill data you want to exclude from being able to edit?

minkah1 commented 2 months ago

For example, e-mail, first and last name, which are automatically written in the registration form when the user is logged into worpress.

garthkoyle commented 2 months ago

So, in this case, the WP User integration would be used to require people to login via SSO before having access to the events, and then pull the first name, last name, and email address into the registration form and disable the ability to edit those fields?

garthkoyle commented 2 months ago

Please note that this option works best if you do not collect personal information for additional registrants (a per-event setting). This ensures that all tickets are associated with a single user and prevents the person registering from providing contact information for others.

Conversely, when the event is set up to collect information for each attendee (including primary and additional registrants), this snippet does not prevent users from entering different information for the additional registrants during the registration process.

This should work great for events that require login because the registration form will only create registrations for one person, not different or multiple people, only the person logged-in.