Search Results for 'booking form'

[Markus]

Thanks and no worries. The error messages are now properly translated.

Things still not being properly localised:
Upon successfully booking a free ticket it says “Thank you for registering”
The dates in the confirmation mail are not localised. A simple fix would be to add the format string (‘jS F Y’) from includes/email.php to the po files. However, there seems to be a lack of general consensus throughout the template files as well as to how to deal with date and time format strings. Might be nice to have that streamlined, e.g. by adding an option for DateTime output format to your plugin settings and defaut to the format set in the WP general settings.

Best,
Markus

[Stephen Harris]

I should have posted an update here. The booking form templating was proving too big a task for 1.3, was holding up the other features and would involve a lot of reorganising code (which itself would need to be tested). For that reason, this was pushed back to 1.4 and the features that had been completed, released in 1.3 (and which in part is why 1.3 deviated from its original scope).

The plan for 1.4 is to reorganise the booking form customiser ‘under the hood’ (so no changes to the UI), make it possible to have booking forms on non-event pages and to use (and make customisable) a template for booking form (excluding the custom fields added by users via the customiser – for the time being at least).

[Markus]

I second this feature request of having the option not to create accounts at all. It would be nice if the values for name and email could optionally be stored in long term cookies for a next booking.

1.3 did not seem to include booking form templating after all, but it is good to see (in the 1.3 release post) that it is still planned for the near future.

• This reply was modified 11 years, 11 months ago by  Markus.

Hello again,

it appears that some of the booking messages are not being localised. For example, when submitting a booking without selecting a ticket, it will state in a friendly red box: “Please select a Ticket.” rather than using the translation.

A couple of notes:
There are a couple of other occurences of this, such as other form errors or the message box stating that the user is currently logged in.
Other translated strings, e.g. the “book” button or the headline do translate properly.
Updating the mo file correctly changes affected strings – except the ones in question.
The message box stating that I have already booked an event is, unlike the others, properly translated.
The problem persists despite having most other plugins disabled.

Could this be a bug? What is different about these messages that could be causing this behavior?

[Stephen Harris]

Hi Jakov,

Absolutely! – Event Organiser is good at handling frequent or infrequent and regular or irregular events. If your course run over several dates then you’ll want to ‘book by series’ in the booking options, rather than ‘book by date’. (See this page for more details).

In short the answer to all three questions is yes. The plug-in allows you to create your own booking form – e.g. create a drop-down which requires the user to select a choice. So you could have a field related to meal choice. This data can be exported in CSV along with the bookings if required.

The plug-in is fully translatable (If I’ve missed some text, then that will be fixed in a bug-fix release).

Hope that helps! If you have any more questions, just ask!

Stephen

[Stephen Harris]

Sorry, so “Workshop Essential” is an event – or a ticket?

In both cases the name of the event and ticket(s) purchased appear in the bookings admin screen. You can also include these in e-mails via the provided tags: http://wp-event-organiser.com/pro-features/e-mailing-bookees/

This information will appear in the booking/ticket CSV export too (ticket names only appear in the ticket export).

Sorry if I’ve misunderstood you!

[Stephen Harris]

So are you’re booking events ‘by series’ or ‘by date’? If the former the user has booked for all events in a series, if the latter they are booked on for the specific date they chose. – Could you explain how that fits with your use case?

They repeat almost every month but may differ by country/venue.

Recurring event’s can only occur at particular venue – so are each of these different events. (Sorry, I’m having trouble picturing your use case and how it relates to EO’s handling of events!)

[Stephen Harris]

HI Miho,

The title is filtered using eventorganiser_booking_title:

add_filter( 'eventorganiser_booking_title', 'miho_change_booking_form_title' );
function miho_change_booking_form_title( $title ){
   return 'Registration'
}

Similarly the ‘Book’ text is filtered via eventorganiser_booking_button_text.

[Stephen Harris]

Great suggestions Jeff,

Display if tickets remain available for a specific event based on the confirmed booked tickets. …

This will be in 1.3: I’ll be introducing a function for displaying ‘spaces’ remaining. And may consider a template tag for the event shortcode too.

From the admin panel: possibility to book for an event on the behalf of a user…

I like this idea: I’ll look into the best way to implement this, as ideally I’d like it to be possible to search user’s email / name / event title or event jump to a specific booking given its ID.

Admin panel / list of bookings: For the pending bookings, for a better productivity, add booking confirmation link whitout having to open them individually.

This something someone else has requested. I’m aiming to have this in 1.3. Though it’ll probably take the form of ‘bulk confirm’ (via the drop-down) to save space on the rows.

Send a confirmation mail when a booking is in pending

Again, something someone else requested, I also wrote this tutorial. But I hope to bring it into the core plug-in as an ‘offline gateway’ option.

…and when a pending booking is cancelled by the admin (Mails are actually sent only for confirmed bookings)

This is in the pipe-line, but I’ll write up a tutorial for how to add this. in the time being.

Give the possibility to the user to cancel a booking with a field to let them explain the cancellation reason…

This might work best as an add-on – since I’m not convinced that the vast majority of users wouldn want this (I could b be wrong) and I’m keen to avoid bloat. Also, ‘cancelling’ a booking involves deleting it permanently. I plan to support ‘trashing’ bookings in a later version, where I also plan to support custom status’ for bookings. The idea being that you could have a more complex workflow than pending -> confirmed (maybe pending -> payment confirmed -> tickets posted -> confirmed, for example)

Possibility to duplicate an event (or a “Save as new” button when editing an event ?)

I don’t plan to implement a ‘duplicate’ feature. The reason being is that you can effectively duplicate events by adding / removing occurrences. If you want an event which is almost identical to the given the one (but differs say in venue) you can always break that occurrence from the parent event. There are plug-ins which allow you to duplicate post types, but they’ve not been tested with EO.

Presence follow-up. Provide the possibility to the admin to flag the bookings of an event

This is another feature that might be best as an add-on. Its lower priority at the moment, but I will look at adding attendance logging.

---

Thanks for your suggestions – I look forward to implementing some of them for 1.3 :).

[Ian Gray]

Hi, it’s taken me a while to get round to testing this. I added the code and this is what was outputted:

require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, _eo_booking_form_submission_listener, do_action(‘eo_booking_form_submission’), call_user_func_array, _eo_booking_form_submission_handler, EO_Booking_Form->process_form, do_action_ref_array, call_user_func_array, _eo_process_booking_submission, do_action(‘eventorganiser_pre_gateway_booking_offline’), call_user_func_array, email_booking_receipt, eventorganiser_email_template_tags, eo_get_schedule_start, eo_format_datetime
Fatal error: Call to a member function format() on a non-object in /home/USER/public_html/wp-content/plugins/event-organiser/includes/event-organiser-utility-functions.php on line 38