Full 24 hours
Hi! I think that I found a bug. We use the calendar to log in to events with duration 24 hours and 30-minute slots. 48 slots in total.
When "Connection" is 0:00 - 23:59 (for example 0:00 - 0:00 on is not possible) then lastone time slot (23:30-24:00) will never close for another reservation.
I think it's just that the time slot exceeds the Connection. Unfortunately, there is no other way to do this, because you cannot enter a time longer than 0:00:00 - 23:59:59. And that one missing second at the end of day makes the last slot on that day always appear as free.
When "Connection" is 0:00 - 23:59 (for example 0:00 - 0:00 on is not possible) then lastone time slot (23:30-24:00) will never close for another reservation.
I think it's just that the time slot exceeds the Connection. Unfortunately, there is no other way to do this, because you cannot enter a time longer than 0:00:00 - 23:59:59. And that one missing second at the end of day makes the last slot on that day always appear as free.
1 Answers
Hi Karel, this is not a bug but limitation by the system. So it will work only with bookings within one day. So you can have it only as 00:00 - 23:59. You can set it as 00:00 - 00:00 it will not work correctly in that case.
Best regards,
Nikola
Hi Nikola. Thanks for the reply. Well, assuming that 23:59:59 is limitation. If I create a Service with time slots by 30 minutes and Connection for example 23:00 – 23:35 with 1 allowed registration. I would expect that:
a) system won’t let me do it.
b) there will be only one slot (23:00-23:30) because the other (23:30-24:00) will not fit there.
And what will happen in reality? Two slots are created (23:00-23:30 and 23:30-24:00). First one (23:00-23:30) with limit 1 registration. Second (23:30-24:00) with no limit at all. But maybe I’m just a special kind of user. 🙂
Best regards,
Karel
Please login or Register to submit your answer