• Is there a known error for this setting? I can’t get it to restrict the hours for all next 24 hours.

    It removes timetable until the next day, but the user can also select times that are < 24 hours in advance. So basically this setting is the same as “Block same-day bookings”?

    Thanks, Thomas

    • This topic was modified 4 years, 2 months ago by hofercraft.
    • This topic was modified 4 years, 2 months ago by hofercraft.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support jaysupport

    (@jaysupport)

    Hello hofercraft,

    Thanks for contacting us. By any chance, are you making the booking as an administrator or booking manager? Note that Administrators and Booking Managers are not restricted by this setting.

    If not, could you provide the URL to your booking page so we can take a look at what’s going on?

    Thread Starter hofercraft

    (@hofercraft)

    Thanks for your quick reply. I have sent a support request yesterday for my problems also related to Premium.

    For now I can’t provide an up to date demo environment, because our servers are IP-locked or on local computer only (our live environment uses an older plugin version).

    I found out:

    “Late Bookings” do not work if the selected time span in this dropdown setting would reach midnight: Then all times of the current day are shown.

    8 pm, select “At least 1 hour in advance”: it works
    8 pm, Select “At least 4 hours in advance”: all (expired) times of the current day can be selected (if it’s an opening time)
    11pm, select “At least 1 hour in advance”: all (expired) times of the current day are shown (if it’s an opening time)

    “At least 24 hours in advance”: blocks the same day, behaves like “Block same-day bookings”

    (WordPress/server timezone is “Berlin”, eg. Universal time is 2020-09-18 20:00:00. Local time is 2020-09-18 22:00:00 )

    If you can’t reproduce I think about ask my company to turn off the ip-lock for our wordpress dev environment.

    Plugin Support jaysupport

    (@jaysupport)

    Hi hofer,

    To follow up just on the Late Bookings issue, is that still going on? If so, you mention midnight. Are you, by any chance, putting midnight as a closing time? If so, you’d need to change that, as 11:45pm is the latest available closing time, and what you’d be doing is actually setting a closing time that comes before the opening time.

    Thread Starter hofercraft

    (@hofercraft)

    Yes this is still a big problem for us. I also reported this to your Premium Support together with other bugs. Last reply was, that you are still testing this.

    – Tested with closing time 9pm and 11:45pm (opening is set to 10am).
    – “Late Bookings” works only, if the set time span (eg. At least 4 hours in advance) is still within the same day as seen from current time.

    – “At least 24 hours in advance”: blocks the same day, behaves like “Block same-day bookings”
    -> to have the current day blocked is fine. But the main problem here is that it ONLY blocks the same day-bookings. The earliest times on the next day are still available even if they are < 24h distant in time.

    Tested with newest plugin version / frontend booking form as admin and logged out (inkognito), same problem.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Early booking setting “At least 24 hours in advance” does not work’ is closed to new replies.