|
TSpinde
|
January 16, 2024 at 1:37 pm
Dear support team,
we have an issue with registrations. If a person registers three tickets for an event, but by accident puts his own name in for all three tickets, then the participant list in the frontend adds one person, but there are three attendendants. How can I make sure a non-registered participant can buy multiple tickets, but only if he/she enters multiple names (As long as it’s the same ticket)?
|
|
TSpinde
|
January 16, 2024 at 2:17 pm
Just an addition: Another alternative would be showing an error message in case one person registers for the same event + same ticket multiple times with the same name.
|
|
TSpinde
|
January 17, 2024 at 5:33 am
Topics are getting responded to, but there are no reactions on my question here: https://eventespresso.com/topic/change-event/. Can you take a look? It’s a bigger issue that one person can register for the same event multiple times, entering his name multiple times. It’s required to check that a person doesnt double book the same ticket.
|
|
Tony
|
January 17, 2024 at 5:48 am
Hi there,
I’ve merged your 2 threads together, there’s no need to post multiple threads on the same question/issue as it just means more cleanup time for us. Some questions will take longer than others and your original thread has been posted for less than 24 hours.
Officially EE does not limit registrations based on the ticket selection/registrant data entered into the registration form. We don’t have any options for it so out of the box this is not something we support at this time.
However, the reason I delayed replying to your thread was to be able to spend a little time checking into hooking into the registration form and adding some additional processing. The closest snippet we have available would be to force the email address used of ALL registrations to be unique, which is available here:
https://github.com/eventespresso/ee-code-snippet-library/blob/master/checkout/tw_ee_force_unique_emails_for_registrations.php
The requirement of “(As long as it’s the same ticket)” complicates this a little more so I’m not sure if the above would work for you, however, it would help a developer towards creating a custom function specifically for your requirements.
|
|
TSpinde
|
January 17, 2024 at 8:42 am
Hi, thank you very much, and sorry for the re-asking (Was not sure if it got missed). I implemnted it, however, this also prevents one user to book different dates of the same event, which he could (you can test it here https://marktvolk.de/veranstaltungen/kaltenberg-2024/). From a logical perspective this does not seem reasonable, since I do want one person to book different tickets for the same event on different dates, but I dont want one person attend one event at one date 10 times (since it is only one person).
Did you encounter this before? Can you aid in fixing it? Maybe this is even a general problem of the snippet.
|
|
Tony
|
January 17, 2024 at 2:45 pm
Hi there,
I implemnted it, however, this also prevents one user to book different dates of the same event, which he could (you can test it here https://marktvolk.de/veranstaltungen/kaltenberg-2024/).
Well, yes, it will, because your hiding the email field and setting them all to be test@test.com?
The snippet specifically checks for match email address submissions and prevents those so if your setting all of the email fields to the same value that’s going to happen.
From a logical perspective this does not seem reasonable, since I do want one person to book different tickets for the same event on different dates, but I dont want one person attend one event at one date 10 times (since it is only one person).
We don’t limit how people register onto the events as this allows EE to cover the most use cases, if we limited EE registrations to ALL require unique contact details we limit the number of use cases EE can work with.
Did you encounter this before?
This specific use case, I have not had before. Generally, people add details to the registration form to inform the registrant to use unique details for each person as it wouldn’t be expected for the same person to register onto the same event and be 10 different people with the same name.
Can you aid in fixing it?
For your specific use case your going to need some custom development
Maybe this is even a general problem of the snippet.
Sort of, this is a conflict of your use case and the snippet.
That snippet is doing exactly what it is intended to do, force all registrations on the registration form to use a unique value. Your manually setting all of the email fields to be the same value, so it triggers the snippet (which is expected).
This is why I mentioned above that it may not suit your use case but can be used as a base to work out your custom code.
|
|
TSpinde
|
January 17, 2024 at 2:59 pm
Hi,
thank you for the response! I did not hide the mail before and tested your snippet with the regular mail registration, understanding that it only works based on that and doesn’t make sense otherwise; sorry for not clarifying this earlier. Hiding the mail happened later and for other test purposes. However, the issue remained the same, also with the mail. The view of an event such as here (https://demoee.org/use-cases/event-category/churches-and-ministries/) – which is different times for the same church service – relates to the same event. However, your snippet prevents a user to register for the same event with the same mail address. For example, if added to your church demo, the user with one mail address would not be able to attend the church service at 9 and at 11, but only one of them.
This is what I meant: The snippet prevents users from booking the same EVENT twice, but the same event can have different TICKETS (with varying times and dates), and I would like to have users be able to attend the same event on different occasions, but not buy the same ticket for the same event at the same date and time.
I’m happy to revert the hiding of the mail if it aids your support. If you have recommendations on how to address this, it would help a lot :). Thank you already!
|
|
TSpinde
|
January 20, 2024 at 12:09 am
I found a fix to solve this. Can be closed.
|
