|
Nick
|
November 16, 2017 at 4:12 am
Hi
It’s often the case that people register for an event without paying for it and, when they are ready to pay, register again, rather than using the links from their original registration email to pay. This means I get duplicate bookings that I don’t need.
I am wondering if there’s a way with EE4 of preventing people from signing up again with the same name and email address combination (if there is already a booking in with this combination), or at least warning/reminding them of the previous booking when they attempt to book again?
From a search on this forum I can see that Dean created a script for EE3 to warn customers of this, but is there anything similar for EE4?
Thanks,
Nick
|
|
Josh
|
November 16, 2017 at 7:54 am
Hi Nick,
The closest ready-made script is this one:
https://gist.github.com/joshfeck/51c2ef122616b48cc4846b1f44384859
It’s not exactly the same though because it relies on the WP User integration add-on and requires the user to log in before buying a ticket.
|
|
Nick
|
November 16, 2017 at 9:16 am
Ah. my events are open to the public, so that wouldn’t work. It would be great if something like this could be written in to the core, as I imagine it’s a fairly common issue.
Thanks Josh.
Nick
|
|
Josh
|
November 16, 2017 at 9:26 am
Hi Nick,
I’m afraid this is not something that will be added to core because some users actually need to allow multiple registrations with the same name and email address. I can advise contacting one of the pros listed here and they may be able to give you a quote to build an extension to your specifications:
https://eventespresso.com/developers/event-espresso-pros/
|
|
Nick
|
November 16, 2017 at 9:54 am
Sure. I suppose I was thinking of it as an option that people could enable. And if it was only a warning, it wouldn’t actually stop any registrations. I only ask because I spend quite a lot of time deleting multiple registrations, some of which are locked because someone has attempted to pay, and I’d rather not have to do so!
|
|
Josh
|
November 20, 2017 at 7:49 pm
One of the pros listed in the directory may be able to build in and extension for adding some additional on-the-fly validation that would include comparing the submitted form to the attendee information in the database for that event and check for a match and if there’s a match, stop the registration process (or add an additional step that warns the user they’ve already registered for the event).
|
