This tutorial is very similar to this tutorial on limiting bookings to one ticket. At the time of writing, the above article uses an outdated, but still available API. That tutorial shall shortly be updated to reflect this. This tutorial uses the current API. Restricting bookings by user role To prevent bookings by users with …
With most payment gateways you receive payment almost immediately – and so its pointless to send an e-mail reminding users of their booking / how to pay, if they will receive another moments later thanking them for their payment. However with the ‘offline’ gateway, it could be hours or even days before their payment is …
You may wish to detect when a booking’s status changes, so that you can perform some action (for instance, e-mail the bookee that their booking has been cancelled). To detect when a booking changes status you can whose one of three hooks: {$old_status}_to_{$new_status} – to detect when a booking goes from one specific status to …
Event Organiser (& Pro) use a lot of custom hooks. Hooks, if you don’t know what they are, allow a third-party plug-in or a theme to modify the behaviour of WordPress – or, in this case, Event Organiser (& Pro). As an example, in this tutorial I’ll be demonstrating how you can email the venue …
In some situations you’ll only want to limit bookings to one ticket and/or prevent bookees from making additional bookings for events for which they have already placed bookings for. In this article I’ll walk you through how you can achieve that. First let’s look at the function we’ll be making use of: eo_user_has_bookings(). You can …