
Stephen Harris
Hi Warwick,
The booking form customiser is in the plug-ins settings page under ‘Booking Form’ tab. From there you can create multiple forms if needed. Then on an event page there’ll be a drop-down in the ticket metabox, allowing you to select a booking form to use for the event.
If there are tickets available the booking form is automatically added to the bottom of the event page. This can be prevented, but until 1.4 (due out this weekend) there is no shortcode to place the booking form elsewhere on the event’s page, or on another page.
Please note, that [registration_form]
seems to be a theme’s provide registration form shortcode – and completely unrelated to event registration. The booking form settings however do allow you to restrict bookings to logged-in users, or allow (or force) users to create a (user) account when placing a booking. In 1.4 there’s an option to prevent users from creating a user account when placing a booking.

Stephen Harris
Hi Sue,
I’m about to launch 1.4-beta which will allow you to prevent account creation on the booking form and copy a booking form template into your theme and edit it there (to, for instance, remove the log-in form). If you’d like I can send you a copy?
But otherwise, yes those are the appropriate bits to remove, but your changes will be lost when you update, so I advise against editing the core plug-in files.

Stephen Harris
Hi Barak,
This will be much easier in 1.4 which will hopefully be hitting beta over the weekend. There are two ways to hide this, the first is to hide the notice with CSS, in your the theme’s style.css
.eo-booking-notice-logged-in{ display: none }
But that just hides, rather than removes it, to remove it add the following to your functions.php
:
add_filter( 'eventorganiser_booking_form_notices', 'my_remove_are_you_logged_in' );
function my_remove_are_you_logged_in ( $notices ){
$dom = new DOMDocument;
$dom->loadHTML( $notices );
$xpath = new DOMXPath( $dom );
$pDivs = $xpath->query("//*[contains(@class, 'eo-booking-notice-logged-in')]"); //->query(".//div[@class='']");
foreach ( $pDivs as $div ) {
$div->parentNode->removeChild( $div );
}
return preg_replace( "/.*<body>(.*)<\/body>.*/s", "$1", $dom->saveHTML() );
}
In 1.4 you’ll be able to edit the templates to remove this template, and that’s a much easier and nicer approach.

barak kassar
On Event details page ( for single event) under bookings heading (just after the event text) there is a line that says:
You are logged in as admin@wpnew.com. Not you?
If you hit not you..it logs you out of wordpress (if you are logged in) and show 2 forms side by side (one with option to create an account and other to login to wordpress)
Is there a way to get rid of that line (You are logged in as admin@wpnew.com. Not you?) under bookings subhead in event details page? If yes, how?
Please adivce.

Stephen Harris
Hi Alf,
Pro does indeed allow you to create a page with a user’s “booking history”, via the booking history shortcode: http://wp-event-organiser.com/pro-features/shortcodes/booking-history-shortcode/
I would say yes, what you describe can be achieved using Pro. There would be some differences – most notably the fact that there would no longer be a ‘product’ page – and the associated booth could instead be displayed/advertised on the event page itself (perhaps that’s the intention).
Event Organsier Pro does allow you to add custom fields to the booking form – for example, a drop-down selection for size. However, if you need to limit the number of bookings made with any particular size (i.e. you have 15 booths: 5 of each size), then the custom field does not allow you to limit how many times a particular option is chosen. (E.g. with 15 bookings, all users could select the ‘small’ option).
If you need to do that then I’d recommend creating a seperate ticket for each size, which would allow you to limit the number of times a small booth (for example) is selected when booking.
Event Organiser Pro also supports offline booking payment, so there is no problem there.

Stephen Harris
Thanks Markus. .mo
files were corrected in the 1.3.2 release too.

Stephen Harris
Not currently I’m afraid. But it is on the roadmap (1.5 maybe). Because there are multiple booking forms there will need to be a way of identifying fields on different forms to ‘mean’ the same thing. E.g. you may want a contact phone number, and you’ll add this field to all your booking forms. In the email you’ll want a tag to represent that field in each of the forms, so that the entered phone number can be displayed, regardless of which form they actually used.

Erica Eide
Is there a way to display the selections that a user made on the booking form in the confirmation e-mail?

Stephen Harris
That will be quite difficult currently I’m afraid. But 1.4 will hopefully make it easier to edit the booking form. This is still being worked out, mind.

Omayr McAdam
Thanks Stephen,
I now realise the payment gateway wont show up for free tickets. As all events are free I wanted to take it a step further by hiding any reference to price so I ended up reading through all the includes and functions files.
In the end I managed to make the booking form NOT display the price (and total price) fields for bookings so now it only shows Ticket Name and Quantity.
Still looking at how this can be saved so that when updates happen I wont loose what I changed.

Markus
Thanks. Updating the mo file fixed the issue.

Stephen Harris
Hi Markus,
This affects users using the plug-in with one of the available translations enabled. There is an error in the .mo file, and I’ll be updating shortly.
Oddly this behaviour did not occur in pre-release testing. So I suspect that the distributed copies had an out-of-date .mo files. In the unlikely event that the problem persists after 1.3.2 please use this form so I can give you a corrected copy of the .mo/,po files and investigate further.
Apologies for any inconvenience.

Markus
Hi Stephen,
after upgrading to wp 3.6, eo 2.2.1 and eo pro 1.3.1 respectively, I get my DOM messed up in the booking form. When a user is logged in, they get the “You are logged in as x, not you?” message with logout link but this link is repeated a total of 4 times, spanning across all the elements of the booking form (so that when you click anywhere in the booking form you are being logged out).
Also, one of the “strong” tags does not appear to be closed as any text that comes after the booking form will be rendered in bold. Since this glitch is rather obvious and disabling I suspect that not everyone is experiencing it. What could be causing this and how do I fix it?
Best,
Markus
-
This topic was modified 11 years, 10 months ago by
Markus.
-
This topic was modified 11 years, 10 months ago by
Markus.