Search Results for 'booking form'

[Stephen Harris]

Hi Dan,

I think I emailed someone about this – I’ll dig that code up and write a tutorial.

As for hiding the amount – no not yet. I’m about to release 1.2, and 1.3 will focus on the booking form in which it’ll be a lot more flexible to do things like that. (although you could just hide it with some CSS).

[Stephen Harris]

… I have noticed you need to edit each booking separately. … it would good to do this in bulk from the main booking page just by ticking the ones you want to confirm and selecting “change status to confirmed”

I agree, will add this (but after 1.2) :).

The offline payment instructions will appear on the booking form. There is a filter which allows you to change the ‘thank you’ message which you could use to add the payment details (I’ll write up a tutorial) or you could include it in the email you send out immediately after the booking is placed (article pending 🙂 ).

[Stephen Harris]

Yes, I don’t see why not :).

On the ‘bookings’ settings tab there’s an option to require that the user be logged-in to ‘purchase’ tickets. If you’re just registering attendance then set the tickets price to 0, and disable the gateways (as they won’t be needed).

The only downside is that the ticket table still appears – I’ll be focussing on the booking form in the 1.3 update, and aim to make it easier to structurally change it (as opposed to just add/remove forms). (1.2 is due out this week in case you’re wondering 🙂 ).

[Stephen Harris]

Hi Ian,

If you only have one gateway enabled, you won’t see an option – but it should automatically use the only available payment gateway option. I release that if the only option is the offline payment then the method of payment is hidden – I’ll fix this.

If you book a ticket it is booked on the back end but the person doesn’t receive an email

The user won’t recieve an e-mail until payment is confirmed (there should be a booking confirmation notice once they submit the form – but there is a bug with this which will be fixed in the next few days).

I enabled PayPal and there is still no choice of payment until after you book the ticket.

I can only assume that the page was refreshed from the cache and so didn’t reflect the updated settings.

Also, is it not possible to choose different payment methods for each event.

Currently its not possible but I’ll add a filter in for this (in the next update) and write up quick snippet that does something like this. The gateway settings cannot be changed for each event, but with this filter you can prevent certain gateways from appearing.

All the best,

[David Musgrove]

Thanks for the prompt response Stephen. No, no gateway response section, no transaction numbers. I’m using the Responsive theme, and quite a number of plugins:

Archives for a category / Better WordPress Minify / Better WordPress reCAPTCHA / Contact Form 7 / Contact Form 7 reCAPTCHA extension / Event Organiser (+ Pro) / Google Analytics / Google XML Sitemaps / Map Categories to Pages / Member Access / Meteor Slides / NextGEN Gallery / NIVO slider light / Page Links To / Query Posts / Really simple Facebook Twitter share buttons / Remove Dashboard Access / SEO Slugs / SoundCloud Shortcode / UK Cookie Consent / Video Sidebar Widgets / W3 Total Cache / WordPress Backup to Dropbox / WordPress SEO

Any of those ring immediate alarm bells with you? I’d obviously prefer not to set up another clean site to test these one by one if I don’t have to…

[Stephen Harris]

Sorry to hear you’re having trouble

If you view the booking’s admin page does it include a ‘Gateway response’ section, or is there a transaction number under the booking ID in the bookings admin table?

Could you include the plug-ins and themes you are using (you may want to try the plug-in on a fresh install of WordPress, or with all other plug-ins & themes disabled to rule out (or identify) the possibility of it being a plug-in/theme conflict.

(It might be easier to go to wp-admin/edit.php?post_type=event&page=debug and copy the information there into an e-mail.)

[David Musgrove]

Hi Stephen

This isn’t working for me at all I’m afraid. I can complete the transaction on both Sandbox and Live PayPal, but in neither environment does the booking end up as confirmed, so confirmation emails don’t get sent out without manual intervention.

When PayPal returns to my site, all I get is an empty booking form again, no confirmation message, which looks awful. All the expected PayPal emails are there, and I can see in Chrome developer tools that PayPal is posting a valid set of data back to WordPress. When I try to access the site with the querystring you suggested earlier directly, I get the empty page with the error box that I should do.

Any advice?

David

[Stephen Harris]

I didn’t do this last time because I didn’t want to add in a fourth option :).

R.e. templating the booking form – this is what I’m planning for 1.3 (1.2 due out in the next 1-2 weeks) which will be focussing on improving the booking forms (and booking form customiser). With that update you could hide the ‘register an account’ checkbox (you could also filter the received input from the user just to be safe) – and that will prevent any accounts being created.

The name & email fields fields are required anyway.

Hi Stephen!
Would like to know if it’s possible in some way to hide the ‘account’ options in the booking form. I’m usintg ‘Allow logged-out users to place bookings? Yes, account is optional’ but really I don’t need the users to create an account, and in any case maybe I don’t want them to. So, since with the new version is possible to make a booking without creating an account, I would like not to offer this option to the users. Any idea or workaround about how to get this?
Thank you in advance!
Ricardo

[Stephen Harris]

Bookings are just a CPT of type eo_booking, so the entire post API (specifically update_post_meta(), get_post_meta() is available to you. eo_get_booking_meta() is specifically for ‘core’ meta / booking form as its essentially a wrapper for get_post_meta(), but ensures the plug-in prefix is added to the meta key.

So yes, a WP_Query() call to get bookings could exclude by meta value, and the approach you describe is the one I would use. I’d recommended writing it as a shortcode which you can then embed in a page. I’d also recommend that you prefix ‘hidden’ meta data with an underscore. This doesn’t really matter in this case, but its convention (such meta data wouldn’t appear in the a post’s custom fields, for example).