Hi Mark,
Sorry for the late reply. There are two ways the Late Bookings setting is applied.
The first is done in the browser, with JavaScript, and prevents visitors from selecting the current day in the datepicker. However, this is entirely dependent on the system clock on the computer of the visitor. So if your clock is different from the restaurant’s, you’ll be able to select any day that fits the parameters of your system clock.
That’s why a second layer is also implemented on the server. The time of the booking request is checked against the Late Bookings rule according to the time as set in WordPress. You can check that this is correct and set this under WordPress’s general Settings page.
So, if you’ve set the Late Bookings setting to 1 day but are still able to select the current day in the booking form, that’s probably because of a system clock issue. If you find you’re able to actually make the reservation too, there’s probably an issue with the time setting in WordPress.
If that doesn’t solve your problem, please send a link to your site. I know that some themes tamper with the booking form quite a lot and so may break this setting completely.
Hi Nate,
Having the same issue here…
I’ve tested by checking using <?php echo date(“D M d, Y G:i a”); ?>
which gave me the right local time.
Also Under general it says (in Dutch)
UTC tijd is 23-12-2015 20:04:19 Lokale tijd is 23-12-2015 21:04:19,
where UTC is set to UTC+1. The local time equils php echo date.
Late reservation is set to 1 day, but still i’m able to make a booking for today, or even for a time yet past 4 hours ago…
Any suggestions are welcome. Credentials are available.
Thanks! D.
Hi daniel,
Have you tried testing when logged out from the site? Administrators and Bookings Managers are allowed to bypass the Early and Late Bookings restrictions. This is so that if you need to edit a booking (eg – a last-minute change of party size) you can do that in the admin area.
:-)))))))))))
If i only new this earlier …;-) (RTFM?)
Actually it’s not in the documentation. I should put it there! It’s a common source of confusion.
Hi Nate,
That would be a great idea 😉
Perhaps is it also possible to combine the ‘phone required’ add-on in the same plug-in and have it create an option to make it required or not? I’ve tried to LOCOlize the ‘phone required’ text into Dutch but it won’t shop up in the front-end. Feature request 😉 Thanks !