Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Limits registrations or avoid duplicate registrations | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › Limits registrations or avoid duplicate registrations

Limits registrations or avoid duplicate registrations

Posted: October 22, 2013 at 4:21 pm

Viewing 1 reply thread


rosorio

October 22, 2013 at 4:21 pm

We have a free event on my installation (using Event Espresso is 3.1.35.1.P).

We would like to send to our attendees the URL for register their asistance with one more attendee.

So, when this attendeed register, will receive their ticket and their guest his own ticket (using Ticketing system for Event Espresso Ver. 2.0.10.2.p).

Can we avoid to have duplicated persons for this event? i mean, validating the name or mail, or another new field?

Thanks in advance


Garth

  • Support Staff

    •

October 22, 2013 at 8:30 pm

Hi Rosorio,

Right now Event Espresso doesn’t have a check for duplicate registrations. The only thing that would allow you to restrict registrations is using the pre-approval feature (available in the Event Espresso General Settings as an option.

I assume you’d only compare emails or a combination of first name, last, name and email address?

Viewing 1 reply thread

The support post ‘Limits registrations or avoid duplicate registrations’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Status: closed

Updated by Garth 11 years, 3 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server