Posted: March 24, 2020 at 6:44 am
Dear Event Espresso Team,
1. An event can be set to “1 ticket per user”. However the same user could still get more tickets by clicking the registration button again. We’re confused that even with the people addon, we don’t seem to be able to lock the registration button if the user already has a seat in the event. Is that correct or are we missing something obvious?
2. There are different kinds of status for events in Event Espresso. (e.g. cancelled, approved, etc…) and we are trying to read the status of a specific event (like you read the user name from the wp_user object). Is it possible to access a status of a course in this way via PHP for reading its value?
3. It seems for users it is not possible to cancel a participation by themselves? We only have non-profit / free courses, so we skip the pay process always and would like to make it possible for users to cancel a registration by themselves (or at least an easy way to request a cancellation). But also we didn’t find a functionality (except for “contact admin”) sadly.
We appreciate any help in these matters. Thank you very much, we do love EE so far. 🙂
That’s correct, EE doesn’t currently have a limit of 1 registration per user.
It can be set to allow 1 registration per order, but that doesn’t prevent a user from placing multiple orders.
If you are using the WP user integration add-on and force users to log into the site before registering then it is possible to remove the ticket selector from an event if the user has a registration on that event.
Will that work for you?
Yes, this is possible using our models system, you can find the docs for that here:
What object do you have to work with currently?
If you have an EE_Event object you can use something like:
Or to echo directly:
Assuming you are using the WP User integration add-on and require users to log in before they add a registration you can use a snippet to add a cancellation feature into the My Event section.
Note that the above is not officially support by Event Espresso so should be thoroughly tested to make sure it suits your needs.
You can add that to a custom functions plugin on your site, we have some documentation on creating one here: