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
Attendee contraints. E.g. Only x,y and z can register. | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Attendee contraints. E.g. Only x,y and z can register.

Attendee contraints. E.g. Only x,y and z can register.

Posted: February 6, 2014 at 12:29 pm

Viewing 1 reply thread


Nicole Tang

February 6, 2014 at 12:29 pm

Is there a possible way to enforce a list of allowed names for a certain field?

Current situation.
I have one main event which 350 people are attending.

I have a second event which all attendees (all individual… i.e each person in a group order) can optionally apply to attend this sub event.

My issue here is how do I limit it so that only people who have paid for the main event are allowed to register for this event? I need some kind of cross-referencing mechanism.

These attendees will be then subjected to my approval before receiving a ticket.

  • This topic was modified 10 years, 11 months ago by Nicole Tang.


Sidney Harrell

  • Support Staff

February 6, 2014 at 2:48 pm

You could take advantage of the post-save-attendee hook that is in place to add a custom function that would do the check that you are describing, and delete the attendee if it does not meet the criteria, as well as post a message to the user. Something similar to what I did here: https://gist.github.com/sidharrell/7163075.

Viewing 1 reply thread

The support post ‘Attendee contraints. E.g. Only x,y and z can register.’ 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.

Event Espresso - Staging Server