Search Results for 'booking form'

[Stephen Harris]

Hi Jan,

Currently the only way of doing this is to copy the eo-booking-form.php template into your theme and edit it. Specifically, it contains a call to eo_signup_form() (which can be found in includes / booking-form-handler.php). If you replace eo_signup_form() with the (edited) mark-up of eo_signup_form(), then you can add the necessary class and *.

At some point, these ‘sign-up’ fields will may become part of the customiser (with appropriate checks to ensure backwards compatibility).

[Jan Wildefeld]

I have a similar problem. The provided solution posted above makes the field “last name” a required field but it doesn’t indicate it with a star character ‘*’

Is there a solution to add span class “required eo-booking-form-required” to the field ‘last name’

Thanks in advance
Jan

[Stephen Harris]

Great, it is possible with the current release, but there are going to be a few API improvements (particular to the front-end booking form javascript), that will make this a lot easier in 1.5. This is scheduled for release early December, and I’ll write up a tutorial on how to modify the “checkout cart”, using VAT as an example, then.

If there’s popular demand it may be made into an extension.

[Stephen Harris]

Hi Michael,

Can I get back to you on this? I’m fairly confident that this is already possible (but the solution is quite involved, e,g, to get the VAT to be reflected at the booking form).

[Stephen Harris]

No worries! It’s great to get feature requests (even if occasionally we can’t fulfil them) – it indicates how the plug-in is being used (and how customers would like to use it) – and helps steer development :).

As for custom fields for the booking form, you already have it: http://wp-event-organiser.com/pro-features/booking-form-customiser/ :). You can download this data when you download the bookings as CSV.

There is even a reasonable amount of need for multi-attendee entries. (One ticket purchaser enters info for a number of people he/she represents).

This is something I’m looking into, that is “ticket meta” rather than “booking meta” which the existing form customiser caters for. The idea is that these fields would be duplicated in the booking form according to the number of tickets selected. There are still some decisions to be made on how to handle this in the plug-in, and also, how the user interface should work.

I imagine that a template system – where a number of event types/ticket types could be saved and reused– with as much administrative freedom as possible – would make my particular clients very happy.

1.5 will see a change in the user interface for ticket management (loosing the cramped modal in favour of something inline where options can be revealed / hidden). This is partly pre-empting the admin UI changes WordPress will be implementing in 3.8 (http://www.wptavern.com/breaking-new-features-selected-to-merge-into-wordpress-3-8-core), but also about giving the ticket-edit area more space. With that comes the possibility of providing more advanced options – so this will definitely be looked at post 1.5

(Feel free to email the links you referenced!)

Hey Stephen –

Sorry to be so present on these boards- you sound busy. Recently realized that custom form fields for event booking would be very helpful to us- I’d probably even pay a good deal extra for it.

The organization we work with has to collect vastly different info for many events. If we could give non-programmer administrators an easy way to collect data about event attendees, I know they would really appreciate it. They need to collect data like “Do you need to rent a tent?” “Will you have a chaparone?” “Do you prefer the color red or blue for your souvenir?” Etc… These questions change frequently, and they host many events annually.

There is even a reasonable amount of need for multi-attendee entries. (One ticket purchaser enters info for a number of people he/she represents).

I imagine that a template system – where a number of event types/ticket types could be saved and reused– with as much administrative freedom as possible – would make my particular clients very happy.

Not sure about precedent for this with other users of the plugin, however–but thought I’d ask

If possible, I’d like to email you a link with some examples of how this has been implemented elsewhere.

Hope you are well ! Thanks for your time!

CE @ WA

• This topic was modified 11 years, 7 months ago by  Ann/Caitlin Wiegand/Everett.

Hi Stephen,

EO Pro currently supports quite a few email placeholders, but is missing others that I’d like to use.

I’m particularly interested in displaying the venue name, address and links to the venue page and event page.

Is there currently a way of adding this information in emails (esp. booking confirmation emails), or would you consider adding these placeholders?

Thanks

Shortcode [eo_events] prints out a list of events. When clicking on one of them the expected behavior would be to jump to the detail page of this event and having the booking form selected with the event that has been clicked.

Now I’m using a reoccurring/multievents (not sure how it’s called in English) – when I pick out one of them from the [eo_events] list the click leads me to an overview of all recurrences of this events and no event is selected in the booking form. This is confusing.

Is there a way to jump into a specific event and select the chosen one in the detail page?

[Stephen Harris]

No problem 🙂

[Michael Waugaman]

Sorry – shouldn’t have bothered you with the second question as have already figured it out myself 😉

Again thanks for the quick response!

[Stephen Harris]

The plug-in only shows the booking form when there’s tickets to sell. But if you turn off the auto part as above then it’ll never show unless you call into in your theme via eo_get_booking_form() or via the shortcode.

(Even if using that function / shortcode, the form won’t appear unless their are tickets being sold).

[Michael Waugaman]

That’s great, Stephen

Moving the meta data was easy enough I just hadn’t clocked how you were calling up the booking form. just to clarify if I turn off the ‘auto’ part of the booking form will it ALWAYS show or only when appropriate (ie when there are tickets to sell 😉

thanks for the quick response.

[Stephen Harris]

Hi Michael,

Glad you like the plug-in. By default (for improved theme compatibility) event meta data is prepended to the event content. However if you create a single-event.php template in your theme, it will use that instead. So I’d recommend making a copy of single.php in your theme and then immediately after it displays the main content, add the following:

<?php eo_get_template_part('event-meta','event-single'); ?>

to display the event meta day (or completely customise how event-related details appear by using the available functions). At this point the booking form is still automatically appended to the content, so to stop that add the following to your functions.php:

 add_filter( 'eventorganiser_pro_get_option_disable_automatic_form', '__return_true' );

Then add

<?php echo eo_get_booking_form( get_the_ID() ); ?>

wherever you want the booking form to appear in single-event.php (e.g. immediately after eo_get_template_part... above.

Hi – great plugin!

I’m trying to roll this out quickly for a client who wants a custom single-event page. I’ve set up my own copy in the current theme folder and everything is fine except I can’t see how you are calling the booking form after the content.

Essentially we want to move the meta details (date, map, etc…) to after the main post content but BEFORE the booking form ……. help?