Event Organiser Pro will be released shortly, and is now available for beta-testing. If you want to get hold of a copy early then fill out the form at the bottom of this page. Here’s a summary of what you can expect in 1.6:
Booking Status API
You can now easily create custom booking statuses to allow you to better track the progress of a booking. This is useful if you have additional steps you wish to track before or after a booking is made or confirmed. For example, you may wish to create a booking status to indicate that a confirmed booking has had its tickets dispatched to the bookee’s address, or that an unconfirmed booking has had a reminder sent.
The booking status API simply allows you to register addition booking statuses, and indicate whether bookings of that status should have tickets reserved and whether the booking should be deemed ‘confirmed’.
add_action( 'init', 'my_custom_booking_status_register', 500 );
function my_custom_booking_status_register(){
eo_register_booking_status( 'deposit-paid', array(
'label' => 'Deposit paid',
'label_count' => _n_noop( 'Deposit Paid <span class="count">(%s)</span>', 'Deposit Paid <span class="count">(%s)</span>'),
'reserve_spaces' => true,
'include_in_confirmed' => false,
));
eo_register_booking_status( 'tickets-sent', array(
'label' => 'Tickets sent',
'label_count' => _n_noop( 'Tickets Sent <span class="count">(%s)</span>', 'Tickets Sent <span class="count">(%s)</span>'),
'reserve_spaces' => true,
'include_in_confirmed' => true,
'show_in_admin_status_list' => true,
'show_in_admin_all_list' => true,
));
}Documentation for the eo_register_booking_status() function can be found here.
As hinted in the first example this would make it easier to implement ‘part payments’ or deposits for events.
Cancelled bookings can be retrieved
Prior to 1.6, cancelled bookings were irrevocably deleted. Now cancelled bookings remain in the database, but largely ignored by the plug-in. Cancelled bookings can be re-instated, or permanently deleted.
Booking CSV export options
Additional options setting the delimiters used in the CSV file have been added. The aim here is to provide a greater degree of flexibility in the format the file takes, making compatibility with various CSV readers much easier.
Javascript checkout API improved
This change is almost entirely under the hood, and won’t be noticeable. But with recent extensions such as VAT and discount codes, this API overhaul aims to make extending booking form interaction a lot easier. There are some exiting plans for seat allocation extension which will integrate with Seats.io.
Minor tweaks to the booking form styling
There’s been a few alterations to the styling applied to the booking form. These all very minor, including fixing some conflicts which may occur with themes using a common ‘reset’ styling (used to remove default styling applied by browsers). The labels of booking forms have also been given display:block and the <br> tags removed.
Improved performance
The front-end stylesheet has been linted, condensed and then a compressed version used for live sites. It’s a minor change, but a very welcome one!
“No gateway enabled” error message
Currently if you create an event with some non-free tickets, but neglect to enable any of the payment gateways the booking form does not appear. In 1.6 admins will see an error message where the form would appear explaining this. The error does not appear to non-admins.
Of course, if your tickets are free you do not need to enable any gateway.
Various bug fixes
Various minor bugs have been addressed in this update. Including a bug with the postcode and state components of the ‘address’ form field remaining visible regardless of form field options.
Want to get hold of 1.6 early?
Great! Just fill out the form below and I’ll be in touch!
Sorry, Beta-testing for 1.6 has now closed.