|
Miguel
|
July 19, 2012 at 8:08 am
Hi!
Is there any way to prevent double registration for events? forcing visitor to become registered users… would it be a solution? Is there any way that EE check the provided email to inform that user is already registered?
Thanks in advance!
|
|
Josh
|
July 19, 2012 at 8:19 am
So are people signing up for the same event twice? The only way I could imagine preventing people from being able to do this would be to use the Attendee pre-approval feature. This puts each registration into a queue that the admin will have to approve before allowing the registration to go through. Look under “Event Options” for the “Attendee pre-approval required?” option.
|
|
emarienborg
|
August 26, 2012 at 10:16 am
I have a similar problem. But I don’t need to force the users not to register multiple times, I simply want to ask them if they have already registered if their email address is already registered for the event they’re trying to register for. (Our users sometimes forget they have signed up for events.)
I thought this would be easy, as there already is a “Please double check your entered information before submitting”-page. My plan was to simply add a database call to see if the submitted email had already been registered at the same event, and print a warning text if it had, at that point in the registration process.
But as all our events are free, it appears that that page has no function, because the attendees are added to the database before they even get to that page. So, I also loose the possibility to add my question to that page.
Where in the registration process could I add a “halt” to check like this? Or is there any other way to do this?
|
|
Chris Reynolds
|
August 27, 2012 at 10:33 am
In either case, the data isn’t stored until the user enters their information, and, by the time they do that, it’s too late — the attendee record is already created. Even if they abandon the form right there, it will still show up as an incomplete registration.
For free events, this is compounded by the fact that everyone is basically auto-approved because there’s no payment involved. In non-free events, there’s at least the additional step of confirming that the submitted information is correct (which is where I imagine you could put a warning “did you sign up already?” message — even though, as I said before, in either case the record is already created, so doing so is sort of moot).
The only way I can think of that would interrupt the process before the record was created is if there was an interrupt as the data was being written to the database, but that’s not currently something that’s supported (elite hackers can take a look at includes/process-registration/add_attendees_to_db.php and good luck and godspeed to you for trawling through that mess — much of that is being or has been rewritten for 3.2 and this may be possible (or at least easier) in 3.2). OR, you could load all the attendees for that event into an array and then do a check in the array via a jQuery hack (probably) after the email address was entered (which presumably would be possible with WP User Integration as well), but that’s a level of javascript voodoo that goes far above my head.
|
|
Joel Rey
|
September 24, 2012 at 2:29 am
I have also the same problem. For unregisterd visitors, this is not a problem. They have a rate for visitors. But I have non paying members (wordpress member with WP User Integration installed) who do not pay. If they are able to register several times, they will use several seats while they can only have one !!! And obviously, we do not control if they have paid as there is no payment for them.
-
This reply was modified 12 years, 2 months ago by
 Joel Rey.
|
