Is there a way to find and delete double entries/attendees?

[Jack]

It seems that for this site where people can get free tickets, there have been double entries, so people are getting more than one free ticket which is not allowed. Can this be prevented somehow, and how can I find the double entries in the list with attendees?

[Andras]

Hello again Jack,

Thanks for the great question!

I’m sorry to say that out of the box it is not possible to limit RSVPs / tickets. However, there are some things you can do.

E.g. Create a template override that limits the number of RSVPs done at a time.

These 2 guides should help you get started:

https://theeventscalendar.com/knowledgebase/themers-guide/
https://theeventscalendar.com/knowledgebase/template-overview/

You will need to override this file:

wp-content\plugins\event-tickets\src\views\tickets\rsvp.php

Create a copy it here:

wp-content\themes\twentysixteen-child\tribe-events\tickets\rsvp.php

And change the max value of the input field to 1 (Line 54). Or you can make the field readonly and set the value to 1.

 

It would be pretty difficult to stop people from submitting again. With some further customization it could be done that if someone has already registered / RSVPd, then they cannot any more, but it’s impossible to stop them from doing it with a different email address / name.

I’m sorry I don’t have a better solution at this time. Let me know if the above helps or if you have another question.

Cheers,
Andras

[Jack]

I now realize this is/might be closely related to another topic where Nico is helping me out: https://theeventscalendar.com/support/forums/topic/only-one-ticket-per-person/

When I copy and modify the rvsp.php file it indeed gives me one ticket max, but for ALL the tickets on the page (several tickets for different time periods). The code of Nico at this moment prevents that, but still allows for manual entering a larger number in the input field. Setting the input field to read only could prevent that, but that also means that the arrows can’t be used to set one of the input fields/tickets to 1.

So a combination of these suggestions/solutions could just be what I need 😉 Perhaps something like when the focus is set on one of the input fields it is set to 1 (the only value possible), and that the other fields/tickets are set to 0.

About this: With some further customization it could be done that if someone has already registered / RSVPd, then they cannot any more, but it’s impossible to stop them from doing it with a different email address / name. You are right, the latter cannot be prevented, but the first would be a great option/addition to the plugin!!! Most people won’t bother to try and use another computer, so if the IP and/or email address could be checked to see if someone already ordere a ticket, that would be fantastic!

[Andras]

Hey Jack,

Just scanned through the other thread with Nico as well.

An idea that came to my mind was to change the quantity fields to radio buttons. That will only let you choose 1 from all. That’s fairly easy to do with RSVPs.

For the ticket fields you would need to dig into some WooCommerce code. Maybe the Woo guys or the community can help you with that if you think this would be a solution for you. I’ll also ask Nico, maybe he has an idea.

Would this be a good solution for you?

Cheers,
Andras

 

[Jack]

Hi András,

That sounds exactly what I need (radio buttons), but we are only giving away free tickets, so we don’t use Woocommerce. So the change has to be made in a file from the tickets plugin.

[Andras]

Then you need to edit the file I referenced above, the rsvp.php

Copy it here (sorry, there was a typo before)

wp-content\themes\[your-theme]\tribe-events\tickets\rsvp.php

You will need to change the input type to radio (instead of number) and the name to $event->ID (instead of $ticket->ID). I haven’t tested this, just writing how I would do it.

Give it a try and let me know if you get stuck.

Cheers,

Andras

[Jack]

Hi András,

This looks very promising, thanks. Radio button works. The only thing is that now the name and email fields were to send the tickets have disappeared.

[Andras]

Hey Jack,

I see what you mean. Since we are limited on doing customizations I will need to pull some strings for this and can require couple days to get a solution – if at all. Let me check what I can do and I’ll get back to you asap. Hang in there.

Cheers,

Andras

[Jack]

Hi András. I understand. Well, it works with the solution from Nico, although not error free. Some people just don’t understand the way it works 😉 so we have to explain it to them by email. Using a radio buttons would make it much simpler en without possible mistakes by users.

On the other hand, a plugin that gives you an option to ‘sell’ or give away free tickets most of the time means people can only order 1 ticket. This limitation is quite logical, because you don’t want someone to be able to order 200 tickets at once. When tickets cost 10 dollars, someone is not going to order 200 tickets because they have to be paid for, but with free tickets this limitation should be possible.

So, if you can’t do anything about it now, that’s ok. But we will be doing these kind of events a lot more in the future, so a solution for this would be great.

Thanks for your help so far 🙂

Jack

[Andras]

Hello Jack,

I created an override (kindofa hack) that overrides the number selectors with radio buttons. Currently one of my teammates is checking it if all is good. If yes, then I might be able to share it with you.

Cheers,
Andras

[Jack]

Thanks András. Looking forward to trying it out on the site, and thanks for this extra work.

[Andras]

Hey Jack,

Good news, some team members checked it and said it’s good enough a hack to share. 🙂

So here is the file, which is an override. Place it in wp-content\themes\[your-theme]\tribe-events\tickets\rsvp.php and you should see the radio buttons. Note, that I didn’t take into account the additional meta fields that can be set up. Only the basic RSVP name / email / (not) going stuff.

Also note that this is an unsupported and unofficial template override.

Check it out and let me know how it works.

Cheers,
Andras

[Jack]

Hi András and thank you for doing this.

One more question before I’m going to test this, because the actual tickets are online and people are registering, will extra fields not be visible when I add the new file?

Now I have this: http://pix.toile-libre.org/upload/original/1481186241.png

Will those fields still be visible? Otherwise moving those options to the bottom of the form in case of one ticket limitation would be an option, but I guess that would be too difficult to do right now?

[Andras]

Hi Jack,

I didn’t do thorough testing with the extra fields, so I cannot confirm it works well with those. I would suggest to test it out on a dev / staging site first, if you can, before the live one.

At the moment my hands are a bit full and we usually do not support customization like this, so I cannot promise you that I can take a look at it this week. I’ll try, but will take some time.

Cheers,
Andras

[Jack]

I understand. I will install a test site and check it out that way. Thanks so far 🙂

[Author]

Posts