Search Results for 'booking form'

In the booking settings there is an option to allow logged-out users to book an event but not sign them up for an account. I have that check but there is this small form (First Name, Last Name, and Email) appearing before the date picker and the rest of the form items I had created. I can not figure out where this is coming from to get rid of it.

Thanks

[Stephen Harris]

You could listen for when the user makes a ticket selection and then add/remove the field. However, if it’s ‘required’ in the form customiser then the server-side checks will reject the booking unless its has been filled in. You could around this by not making it a required field and then adding additional checks when the server validates the booking.

(Here’s an example of additional validation checks – in particular the second section).

[Stephen Harris]

I see – I’m afraid there isn’t a way of importing booking forms from another installation, but that is something I’ll definitely look into.

[JB Woodruff]

We are managing the site so users are booking as logged-out users. No, the user’s names are not correctly capitalised in the booking admin screen. It appears that it’s passing the correct information from the booking to the email; however, what the user is entering in the form is not being correctly being passed at the time of the booking.

User enters:
JB Woodruff

Booking Appears as:
jb woodruff

Email appears as:
jb woodruff

[Ann/Caitlin Wiegand/Everett]

I am hoping to take the forms out of one installation of wordpress/eo and into a new one (dif server, domain, etc). I can hand-copy the booking forms, but it would save me some time to be able to clone them- if they are saved as templates somewhere or something. Not hugely important, just wondered if there is an easy way.

[Stephen Harris]

Hi Caitlin,

The same booking form can be used by multiple events without any problems. Or do you have a booking form which you want mostly duplicated, but with a few alterations to it?

Hey Stephen!

I am hoping to use reuse a few rather complicated booking forms and wondered if there is an easy way to do this without importing/exporting all of the event data as well.

Hope you are well!

Caitlin

[Stephen Harris]

What Dario says is correct, but you can also do this for Stripe & Offline Payment Gateway (but slightly differently). The reason is that in those two gateways, the gateway is processed without taking the user away from the site, so you can essentially ‘jump in’ before the user is redirected back to the event page and redirect anywhere you want. With the PayPal gateway you tell PayPal where you want the user to end up after payment and PayPal takes them straight there.

The following will work for anyway gateway where the user remains ‘on-site’:

//This will work only for gateways where you don't leave the site.
add_action( 'eventorganiser_pre_gateway_booking_stripe', 'adrian_redirect_after_booking', 100, 4);
add_action( 'eventorganiser_pre_gateway_booking_free', 'adrian_redirect_after_booking', 100, 4);
add_action( 'eventorganiser_pre_gateway_booking_offline', 'adrian_redirect_after_booking', 100, 4);
function adrian_redirect_after_booking( $booking_id, $booking, &$errors, $form ){

    $total_price = eo_get_booking_meta( $booking_id, 'booking_amount' );
    if ( 0 == $total_price ) {
             eo_confirm_booking( $booking_id, true );
        }

     //Set redirect url and send them there
     $redirect = '';
     wp_redirect( $redirect );
     exit();
}

(A future update may well try to provide a ‘unified’ way of changing the gateway return url)

[Dario]

Yes it is possible as long as you are not using the offline payment gateway.

Firstly, create a new page on your site informing the user of successful payment & booking, etc. Make sure that this page doesn’t appear in your menu bar, sitemap, etc so users don’t navigate to it manually or though a search engine.

Once you’ve got that sorted out, see this blog post for code to add to your theme’s function file to enable the redirect.

Note that this code was written specifically for the PayPal payment gateway, but slight alterations should make it work with other gateways too (with the exception of the offline gateway which doesn’t redirect).

Hope this helps.

[Stephen Harris]

Hi Linda,

Currently only booking custom fields can be added. However, a feature in delopment (which may still be 1-2 months away) is to support attendee custom fields. These are a collection of form fields which are duplicated depending on the number of tickets being purchased, allowing, for example a name and e-mail address to be supplied for each ticket. As you can currently do with bookings and booking custom fields you will be able to download attendee (or ticket) custom fields along with the tickets. But currently, only booking custom fields can be added.

[Dario]

Usually the booking form is added automatically to the bottom of the_content() if tickets are currently available.

Try adding quotation marks on either side of the id attribute of the shortcode to see if that helps.
[event_booking_form event_id=”4″ ].

Also note that it asks for the event id and not the booking form id. Edit your event and select the correct form in the booking section and then copy the event id from that event into the shortcode.

[Rania Sayegh]

I have a problem viewing booking forms i have created inside the events. I used the the command :
[event_booking_form event_id=4 ]

Using this didn’t help when added it also inside the event and page. where I have used the ID number of the form created.

Is there a bug in this shortcode? I tried to use it in a page too, but didn’t work out either as it doesn’t show the form. Please advice.

Thanks.

[Stephen Harris]

Hi Arn,

1. You can add custom booking fields (see http://wp-event-organiser.com/pro-features/booking-form-customiser/)
2. You can have multiple ‘tickets’ available. And (unless in Simple Booking Mode) a single booking can contain any number of tickets (up to availability). In your case you could have multiple tickets: “Category 1”, “Category 2”, etc. And the bookee could set the quantity of tickets they want. It’s possible, with a bit of custom code, to prevent multiple categories to be used.
3. This isn’t done by default, but is certainly possible with some custom code.

I’d be happy to offer assistance with regards to the custom code. (In fact I’ll write up a tutorial on (3)).

The topic title mentions this is for a campsite. I should point out, in case of any confusion, that Pro is intended to allow you to sell tickets to events and not book an arbitrary period, e.g. a holiday booking.

[Stephen Harris]

Ah, I see. (Just a side note – you mentioned you’re implementing a custom gateway, there’s a class EO_Payment_Gateway in the gateways folder. I recommend extending that. Documentation is rather limited, but I can provide a ‘skeleton’ plug-in for creating an additional gateway. It handles almost everything but the gateway side of things).

Here’s perhaps one way of dealing with this. The above class I mentioned has a method (payment_form()) for adding HTML to the booking form which is only displayed when that gateway is selected (or if it is the only gateway). The intention for this is to support gateways where additional details are required (eg. Stripe requires the bookee provide a valid credit card). Any data sent in that section is ignored by the plug-in, unless the gateway itself choose to use it. (For instance PayPal Pro also requires a credit card number, but we don’t want the plug-in to save those details insecurely – in fact we don’t need to store it all).

You could use that method to conditionally display a name field (to logged-in users).

 ....

    function payment_form( $element ){
            if( is_user_logged_in() ){ ?>
                    <div class="eo-booking-field-row">
                            <label for="netbanx-name"> Name </label>
                            <input type="text" id="netbanx-name" name="netbanx" />
                    </div>
            <?php }
    }

 ....

When processing the booking you can use that field – or, use the stored name if not provided

    function process( $booking_id, $booking, $error, $form ){
          $stored_name = trim( eo_get_booking_meta( $booking_id, 'bookee_first_name' ) . ' ' . eo_get_booking_meta( $booking_id, 'bookee_last_name' )  );
          $name = ( empty( $_POST['netbanx'] ) ? $stored_name : sanitize_user( $_POST['netbanx'] );

          //Process payment
    }

(Obviously those two methods are part of a child class which extends EO_Payment_Gateway). A simpler method would be just to require a name – even though this may result in two name fields. A future update will allow fields to be visible only to logged-in / logged-out users which will allow to get around that.