|
shoreshdavid
|
April 24, 2022 at 4:27 pm
Greetings,
Some people, despite warnings and pleadings, think it’s still okay to purchase multiple tickets using their first and last name. Then when we print an attendee list or make name badges, we must waste time contacting each offender to try and get unique names for each ticket that they purchased.
Is there a code snippet somwhere that, during registration, compares each attendee first/last name and displays an error if duplicates are found?
We also need to use the “copy attendee” feature but without copying first name, last name, email, or custom question fields. As the code snippet for that doesn’t seem to work, we have a thread open for that one.
With both of those solutions in place, we should be able to alleviate this common problem at the beginning, before it becomes a larger problem later.
Regards,
Chris
|
|
Joao Victor
|
April 27, 2022 at 11:14 am
Hi Chris!
Thanks for contacting EventEspresso support today.
I am afraid that’s a requirement that needs a custom development since it’s not available in EventEspresso by default. It seems would need to hook into the registration form submission and add your own data. Please, take my note as simple advice, not an instruction to hack the CORE. We have a couple of partners that may assist you with this: https://eventespresso.com/developers/event-espresso-pros/
Let us know if you have any further questions!
|
|
shoreshdavid
|
April 27, 2022 at 7:00 pm
Joao,
Below is a link to a gist on Josh’s github which already does email field input validation (basically compares all email addresses and issues an error if there is a match).
https://gist.github.com/joshfeck/7eddc3977ed0ff480fc60a2b00d796aa
Given a common complaint in the forums is about purchases not providing unique names for multiple registrations, I figured there must be a similar code snippet that compares each fname + lname combination and also issues an error if there is a match.
All I know is that each time we have a big event, I have to keep a weather eye on my email, or the list of attendees, looking for complacency in following directions. It should not be this way. For events, unique email addresses isn’t quite as important as getting a unique name for each attendee to facilitate check in and name badges.
Regards,
Chris
|
|
Joao Victor
|
May 2, 2022 at 12:25 pm
Hi there!
Thanks for getting back to me.
Your request is still a custom development case since we need to think in the following scenario: A person (called Joao Angeline) purchases four tickets for himself and their siblings but decided to keep them in his name because he can decide to give the ticket to another person and not keep it exclusive per person. In this case, the First and Last names should be allowed. In your case, you basically want an event option that each ticket must belong to a different person.
Let me know if it makes sense!
|
|
shoreshdavid
|
May 2, 2022 at 3:52 pm
Joao,
I believe you are over complicating my request.
When the SPCO “finalise” button is clicked, form validation kicks in. The function referenced above compares Email field inputs for duplicates. What we (and others in this forum) need is the same thing only comparing Names instead.
Since it was found on Josh Feck’s github, please forward this request to him. I would very much like to know what he thinks of this request. Thank you.
Best Regards,
Chris
|
|
Joao Victor
|
May 5, 2022 at 5:24 pm
Hello Chris!
Thanks for waiting!
We have created a custom snippet that will implement the “Names can’t match” rule on the Singe Page Checkout like:
You can find the snippet available in our public Event Espresso Code Snippet Library: https://github.com/eventespresso/ee-code-snippet-library/blob/master/checkout/ee4-names-cant-match.js
Just make sure to follow the instructions commented at the top of the file to enqueue this script correctly:
Please, let me know if it works!
We are happy to help!
|
|
shoreshdavid
|
May 5, 2022 at 7:12 pm
Hi Joao,
I appreciate the effort, however, there seems to be an understandability issue here as to what we (and others) in this forum require.
We are not having a problem with people entering the same information in both first and last name fields:
Attendee1
First: Joao
Last: Joao
The problem that we keep having is when people use their own first/last name for all attendees. For example:
Attendee1
First: Joao
Last: Victor
Attendee2
First: Joao
Last: Victor
Attendee3
First: Joao
Last: Victor
As I said, we aren’t the only paying EE4 customers experiencing this issue in which registrants fail to follow directions.
If the code snippet from Josh Feck’s github can compare emails for each attendee in SPCO and display an error when there’s a match… then it should be possible to compare first/last names in SPCO and display an error if there’s a match.
We ask that you please have Tony or Josh take a look at this thread so we can get this sorted. We truly believe that such a code snippet will be of great benefit to many, as having unique names for each attendee is vitally important for printing conference badges.
Thank you.
Best Regards,
Chris
|
|
Tony
|
May 10, 2022 at 2:13 pm
Hi Chris,
Joao asked if I could take a look into this for you and Josh’s snippet can indeed be extended to check the First and Last name fields for matching values and then display something like:
“* Duplicate! Please use a unique value”
It could also change the message depending on the specific field with further development. However, it’s important to note here that the snippets we provide aren’t officially supported so the way I would adjust the above would be like this:
https://gist.github.com/Pebblo/be8ff8e94c7f4d21127f0b9712ad7c39
That uses the exact same method Josh did but just extended for the 3 system field, First Name, Last Name and Email.
Does that work for you?
|
|
shoreshdavid
|
May 10, 2022 at 7:30 pm
Hi Tony,
Thank you for having a look at this.
Unfortunately the code snippet isn’t working quite right, as it errors even if we register the following combinations:
Attendee1
First: John
Last: Marks
Attendee2
First: Donna
Last: Marks
…or
Attendee1
First: John
Last: Doe
Attendee2
First: John
Last: Paddleton
…or
Attendee1
First: John
Last: Paddleton
Attendee2
First: Benjamin
Last: John
What’s needed is to ensure that each attendee First Name + Last Name is unique on a registration. So if someone tried to register:
Attendee1
First Linda
Last Steele
Attendee2
First Michaela
Last Steele
Attendee3
First Linda
Last Steele
…they would get a warning about the duplicate “Linda Steele” entered for more than one attendee.
Hopefully there is a way to do this! When it comes to event registration, unfortunately, this kind of validation is necessary as there are just too many people out there who can’t seem to read directions properly. Their duplicate attendee names then end up creating larger problems later on for Event Coordinators and the Badge Coordinators.
Kind Regards,
Chris
|
|
Joao Victor
|
May 17, 2022 at 5:19 pm
Hi Chris!
We are sorry the snippet did not work.
Josh’s snippet was made to work with the email field which must need to be equal. I have checked with our development team and your request requires a more complex code. As we are not currently taking custom development services, we recommend you hire a third-party service in order to accomplish this.
I hope you understand!
|
|
shoreshdavid
|
May 31, 2022 at 7:18 pm
Joao,
Because it failed to work, we ended up paying nearly $200 USD for a programmer on codeables.io to make a code snippet. He finished it rather quickly and basically issues a warning whenever someone tries to register multiple attendees with the same First & Last Name (together), including pseudonyms like “John Doe” and “My Guest”. The registrant is literally disallowed from proceeding to the payment page until they enter a real and unique FirstName & LastName for each of their attendees.
You know… for the price we pay Event Espresso, we shouldn’t have to pay a 3rd party just to ensure our attendees have unique names (i.e. keep people from playing games at registration). Such a thing is essential to any organisation using event registration software, especially when conference badges are printed and/or security is a concern. This is something that has been queried many times within the EE support forum.
Thank you for your assistance. You’ve been helpful.
Best Regards,
Chris
|
|
shoreshdavid
|
May 31, 2022 at 7:32 pm
This reply has been marked as private.
|
|
Joao Victor
|
June 2, 2022 at 2:23 pm
Hi David!
Thanks for getting back to us.
I understand is not great to spend $200 for a custom job, but our development team is not available to accept custom implementations (mainly when it requires a plan to implement). However, I am glad you were able to figure this out and have your Registration form working as expected.
|
|
Joao Victor
|
June 2, 2022 at 2:26 pm
This reply has been marked as private.
|
|
shoreshdavid
|
June 2, 2022 at 2:59 pm
My name is not Chris.
|
|
Joao Victor
|
June 3, 2022 at 12:08 pm
Hi there!
Your account is under the ________. We are sorry your name is not Chris, we just take it from your account.
|
|
shoreshdavid
|
June 3, 2022 at 3:08 pm
This reply has been marked as private.
|
|
Joao Victor
|
June 5, 2022 at 7:42 pm
This reply has been marked as private.
|
