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
One user - One event max | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › One user – One event max

One user – One event max

Posted: February 21, 2014 at 4:03 am

Viewing 3 reply threads


Federico Bertaina

February 21, 2014 at 4:03 am

Hi,
it is possibile to deny user registering at more than one event, even if it scheduled in different days?


Anonymous

February 21, 2014 at 4:27 am

Hi Federico,

Currently Event Espresso does not check if a user is already registered onto an event.

It is possible to add a check to see if a user has registered onto the current event they are registering onto or possible multiple events, however it is not a part of Event Espresso core.

Does that help?


federico bertaina

February 23, 2014 at 3:53 pm

Yes. How can i add the check?


Dean

  • Support Staff

    •

February 24, 2014 at 5:05 am

Hi,

We have a list of available hooks in EE3 here http://staging.eventespresso.com/wiki/event-espresso-3-1-action-hooks/

You could use one of those to do a database check and stop registration if needed.
Viewing 3 reply threads

The support post ‘One user – One event max’ 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 Dean 10 years, 11 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server