Search Results for 'booking form'

[Stephen Harris]

You could create different ticket types: sponsorship, ticket or donation. You would have to be careful here though, as ‘donation’ and ‘sponsorship’ would be considered tickets by the plug-in. This might seem confusing for the user who receives an e-mail with their “tickets”.

Additionally, you can’t set an event wide limit – as donations and sponorships will count towards that. So you would just have to rely on the limit placed on the individual ticket (this is fine, unless you want more than one ticket type that you are actually treating as a ticket).

Lastly, it’s possible to allow the user to add a donation, but it’s a solution that would have to be developed. I would proceed as follows:

1. Add a field via the form customiser or (preferably) the Form API. The number type would work, but only allows integer values.

2. Load some javascript that listens for a value that has been entered, and alters the ‘cart’ total. There is an example of how this is done in the VAT plugin – the difference is, that is adding a fixed percentage, rather than a dynamic amount. That plug-in also adds a row with the VAT amount, which you could include for the donation amount if required.

3. Then server-side, you alter the booking total based on the value stored against your donation field (see the tutorial on the Form API on retrieving that value). The VAT plug-in also adds rows to the e-mail

4. Lastly, for PayPal, you will need to alter the cart object set to Paypal: https://github.com/stephenharris/Event-Organiser-VAT/blob/02c7aeda3e881ceb082ce60f83576394481b7be4/includes/vat.php#L151-L179. If you inspect the $cart variable you’ll see the individual items in the cart, you can add an additional ‘donation’ item.

Hi,

So I’ve created a new event, with everything exactly the same as an old event, except for all the dates (which now lie in the future).
However, for some reason the ‘old’ event does show the booking form, and the new event not.. What’s going wrong?

http://www.demoweek.nl/?event=evenement-4 (does work)
http://www.demoweek.nl/?event=test (doens’t work > not even the shortcode for the form..)

All the best,

Elise

[Stephen Harris]

Hi Sam,

Unfortunately, this not possible (without creating a second event for the 12-3pm timeslot). The reason is largely due to user-interface constraints. Namely, in the booking form (when not using the drop-down), and in the booking and event admin – a datepicker is used for selecting a bookable occurrence. This assumes that a bookable occurrence can be mapped to a date.

Once a more suitable UI is found for searching, selecting and creating datetimes rather than just dates, then it would be possible to lift this restriction. (The plan is do just that, but I cannot give any concrete timelines for this feature).

[Ron]

Stephen,

Thanks a lot for your comprehensive answer. Good news to me regarding most of the requested features.

Let me kindly digg deeper with two of my previous scenarios:

a) You pointed out that there’s no waiting list feature at the moment. Could you please kindly outline a way, how you’d add this waiting list feature if necessary? Imagine talking in pseudo code, what steps would be needed? Plus, is it an official option to place a commercial order of such an add-on to you? If so, how much would it be?

b) Export of lists of participants from WP Admin: I understand the user role and capability stuff. My question is, if a list of participants for a particular event is exported, not only data from the booking form is needed but data from the wp_usermeta table, too. Again just like with part a) How would you approach this requirement? For example, which hooks would be needed to loop through other tables data with each participant’s user_id?

I know, that’s a lot I’m asking for. So I appreciate any help very much. Also, I’m happily willing to pay for stable, reliable and update proof solutions that match these requirements.

Thanks and a Happy New Year!
Ron

[Stephen Harris]

Hi Ron,

1 & 2 – yes, you can configure whether a user has to be logged-in or not to place a booking. By default, for logged-out users, they’ll be able to log-in from the booking form.

3 – there’s a shortcode for this. It displays all the bookings for the current (logged-in) user, so you’ll just need to create a page with that shortcode.

4 – Events can be free. If they are free you do not need to configure a payment gateway, nor the user need to proceed through a payment gateway. You can have multiple ticket types, each with their own limit, plus a global capacity limit.

If all spaces for a given event are booked, booking shall still be possible for users, but those who come late should be assigned to a waiting list for this event

There is no waiting-list feature.

User can also cancel a booking

There’s an option with the booking history shortcode that allows users to cancel bookings.

5 – There are no custom roles by default in Event Organiser, but you can assign capabilities to any role and allow users of that role to manage theirs (or other’s bookings) and create/edit events. Those that can manage bookings can view these in the bookings admin page. From there you can filter by event and export the bookings to CSV (along with any information collected on the booking form). Additionally you can export the individual tickets.

Please note that users who can manage their bookings but not manager bookings of other users will only be able to edit / export bookings for their events. This means they will need to filter by (their) event before exporting.

By default bookings for other users’ events will appear in the Bookings admin screen, but are not exportable / editable by that user (unless they have the”‘manage others’ bookings” capability). I can provide a snippet if you want these hidden from that user.

Merry Christmas!

[Stephen Harris]

Hi Ron,

1 & 2 – yes, you can configure whether a user has to be logged-in or not to place a booking. By default, for logged-out users, they’ll be able to log-in from the booking form.

3 – there’s a shortcode for this. It displays all the bookings for the current (logged-in) user, so you’ll just need to create a page with that shortcode.

4 – Events can be free. If they are free you do not need to configure a payment gateway, nor the user need to proceed through a payment gateway. You can have multiple ticket types, each with their own limit, plus a global capacity limit.

If all spaces for a given event are booked, booking shall still be possible for users, but those who come late should be assigned to a waiting list for this event

There is no waiting-list feature.

User can also cancel a booking

There’s an option with the booking history shortcode that allows users to cancel bookings.

5 – There are no custom roles by default in Event Organiser, but you can assign capabilities to any role and allow users of that role to manage theirs (or other’s bookings) and create/edit events. Those that can manage bookings can view these in the bookings admin page. From there you can filter by event and export the bookings to CSV (along with any information collected on the booking form). Additionally you can export the individual tickets.

Please note that users who can manage their bookings but not manager bookings of other users will only be able to edit / export bookings for their events. This means they will need to filter by (their) event before exporting.

By default bookings for other users’ events will appear in the Bookings admin screen, but are not exportable / editable by that user (unless they have the”‘manage others’ bookings” capability). I can provide a snippet if you want these hidden from that user.

Merry Christmas!

[Daniel Cooksey]

function my_add_element( $form, $event_id ){    
//Create element to add to the field
$element = EO_Booking_Form_Element_Factory::create( array(
     'type'     => 'email',
     'id'       => '_email2', //a unique ID
     'required' => 0, //make this field optional
     'label'    => 'Confirm Email'
));
  //Add the field element, optionally specify where
$form->add_element( $element, array( 'at' => 4 ) );
 }
add_action( 'eventorganiser_get_event_booking_form', 'my_add_element', 10, 2 );

• This reply was modified 8 years, 7 months ago by  Daniel Cooksey.

[Daniel Cooksey]

Thanks, it seems to have something to do with the fact I have the booking form on a separate page.

I tried disabling plugins one at a time, no result.

Switching from the Sports theme I am using to 2016 fixed the problem

But , while using the Sports theme the error no longer appears if I disable the extra code to move the booking form to a separate page.

I followed the instructions in this post to use a separate booking page –

https://wp-event-organiser.com/forums/topic/separate-booking-page/.

I made one change though. In event-meta-event-single.php<br />
[page-url]/?event_id[event-ID]
didn’t work so I changed it to [page-url]/?event_id=<php echo (get_the_ID))?>

So the Sports theme obviously has something to do with it but do you think there is a workaround to get the booking form on a separate page without causing the error?

[Daniel Cooksey]

That’s perfect. Unfortunately it throws the booking form error I mentioned in another thread, even when the email addresses match, and which I have confirmed is related to the theme I am using.

[Stephen Harris]

Not by default, but you could add an additional e-mail field

Let’s suppose you gave that field the id _email2, then you can add a validation check as follows:

function my_validate_email_match( $form ){

    if ( is_user_logged_in() ) {
          return;
    }

    $email = $form->get_element( 'email' )->get_value();    
    $email2 = $form->get_element( '_email2' )->get_value();

     if ( $email !== $email2 ) {
          $form->get_element( '_email2' )->add_error( 'email-mismatch', "Sorry, your e-mail does not match" );
     }

}
add_action( 'eventorganiser_validate_booking_form_submission', 'my_validate_email_match', 10 );

• This reply was modified 8 years, 7 months ago by  Stephen Harris.
• This reply was modified 8 years, 7 months ago by  Stephen Harris.

Hi
Is there an option to confirm email address in the booking form where the customer enters their email address twice and a check is made ?
Thanks
Daniel

[Stephen Harris]

Hi Daniel,

The booking form uses the 'name' query variable to store the bookee’s name. The values entered will populate $_POST['name']. The error you see refers to this line: https://github.com/WordPress/WordPress/blob/4.6/wp-includes/query.php#L1609 – WordPress is trying to trim the 'name' query variable – which it expects to be string, but isn’t.

My guess is that it’s an array, and that $_POST['name'], populated by the booking form, is being passed to a WP_Query instance. This doesn’t happen by default, so you presumably have a plug-in that’s causing this.

If you can identify that plug-in then it maybe possible to workaround the issue. I suspect it’s a bug in another plugin, because I can’t see a reason why you would want to blindly pass $_POST to WP_Query instance.

It doesn’t seem that the terms and conditions element has any bearing on the bug. I suspect, if the booking is successful then the user is redirect to PayPal before the bug is reached – and not checking the terms and conditions was just one way of preventing the booking from being successful.

[Daniel Cooksey]

Version 4.6.1
http://pivotnetball.com.au/index.php/booking-form/?event_id=42

[Stephen Harris]

Hi Daniel,

It’s not possible to change the ticket selection to a dropdown, but you can change them to radio buttons. You’ll need to edit the ticket template, and using the following: https://wp-event-organiser.com/forums/topic/limit-one-ticket-per-person/#post-10052

As for the applying a discount based on a dropdown value this is possible. I’d recommend you add the field via the API rather than the UI customiser – simply because it gives you a concrete (HTML) ID to work with. It’s less fragile then using the auto-assigned IDs the form customiser gives you, which will change if you remove and re-add the element.

As for discount logic, you’ll need to this mostly yourself, but I have just published an un-tested ‘skeleton’ plugin: https://gist.github.com/stephenharris/6b80f310a107e8aca9ce93508e5b5934

There are two places where you’ll need edit it to handle your discount.

Firstly, on the frontend – you’ll need to determine the value currently selected in the field and assign a float value to the discount accordingly.

Since that only deals with displaying the discount on the front-end, you’ll need to effectively replicate that logic in PHP here: https://gist.github.com/stephenharris/6b80f310a107e8aca9ce93508e5b5934#file-bulk-discount-php-L109. You can get the value that was selected from the dropdown via:

 $selected_value = eo_get_booking_meta( $booking_id, 'meta_{element ID}' ); 

Similarly to before, you’ll need to use that value to decide what $discount_amount should be.

I hope that helps but please note that the plug-in I linked to hasn’t been tested yet.

Hi
Is there a way of including a “register another” button on the booking confirmation page to direct customers back to the same event booking form to complete another registration ?
Thanks
Daniel