There have been recent bug-fix releases for Pro and FES extensions. Both of these fixes an issue with the select, radio and checkbox fields in the booking / event submission forms. Specifically users can modify the HTML of those fields in the browser to submit whatever value they like. While there is no security implications …
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 …
Event Organiser Pro 1.6 has just been released. It contains a few major feature enhancements, as well as fixes for a number of minor bugs. Here’s a breakdown of this latest release: Booking Status API With 1.6 you can now create custom booking statuses to allow you to better organise or track the progress of …
The 1.5 update added the filter eventorganiser_booking_form_gateways, this allows you to filter the gateways that appear on the booking form (and also to do so by event). Lets suppose you have multiple events and want to accept offline payments on some, and PayPal on others. You can do that from 1.5 with a bit of …
Gateway settings (merchant account details etc) must be the same across all events – but it is possible to restrict which gateways appear on which events – for instance to allow PayPal purchases only on some events To do this we use the eventorganiser_enabled_gateways hook, which filters the enabled gateways. Step 1: Specify which gateways …
1.1 is about be released this week so I’d share with you some of the updates that shall be included: What’s in 1.1 Guest booking options 1.0 gave you the option of only allowing logged in users to place bookings. Or you could allow guests to place bookings, but they would be created an account. …
