I’m not opposed to doing some development & on the plus side, the only way to sign up for the events I have planned are if you’re a member of my site.
Actually checking whether somebody is already registered is pretty easy to do (a simple query), what I’m not clear on – since the filter documentation is a bit thin IMHO – is which filter to use to both prevent an event instance from being listed if the user is already booked that day as well as how to deny the booking if they’re listed.
Lastly, I’d love to be able to make the # of attendees per event limited by start time (and not the actual event), but can’t find an action to hook into that would let me do that?
In the case of modifying the list so it does not display the event in the list if the user has already registered for the event, you could add to the query that is in the event-list.php template. Or you could also copy the entire “event_espresso_get_event_details” function with its modification into custom_functions.php and it will load from there.
Making the # of attendees per event limited by start time isn’t something that Event Espresso 3 handles well. While there is an option in ee3’s general settings that lets you “Use registration limits on time slots?”, the way the database is set up in EE3 this feature cannot account for group registrations.
In Event Espresso 4 you’ll be able to do this out of the box. You’re more than welcome to sign up for Event Espresso 4 alpha access if you’d like to test this new feature out:
The support post ‘Limit number of events per day a user can sign up for’ 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.
Support forum for Event Espresso 3 and Event Espresso 4.