1. BookingWP Avatar BookingWP
  2. Plugins
  3. WooCommerce Appointments
  4. Issues

gCal recurring event blocking out the wrong time

Issue #847 resolved
Valentina R created an issue

When creating an event in gCal from 10:00 to 13:00, the staff is unavailable at that time. But if you change this event (or create a new one) with the same time repeating weekly, the blocked out time is from 8:00 until 11:00. Can be easily reproduced.

Reported here.

‌

Comments (18)

  7. Valentina R reporter

    Another report here. It’s urgent.

    This case is a bit different because the synced event shows the correct time in WP UI and in ajax code and it’s almost blocking out the right time.

    To reproduce: set duration to 1h, interval to 30min, set availability daily from 08:00 to 20:00, then create a recurring gCal event on a Wednesday 09:00 - 10:30. It’s possible to book at 08:30, but shouldn’t be. The rest is blocked fine.

  11. Valentina R reporter

    I just tested on my site with the global calendar and same timezone for gCal and WP (Paris timezone). With single event it only blocks the necessary hour. But with the repeating event, it blocks 2 hour, the correct one and one hour before. This is no mater how long the duration of the event is (1 or 2 hours makes no difference)..

  12. Valentina R reporter

    It gets even worse. To reproduce I create a product with 15min duration and interval. I set the product daily availability 9:00 - 16:00. I have 2 global recurring events:

    The availability for Tuesday in April 2023 is missing the slots from 12:00 to 13:00 (wrong) and the slots from 14:00 to 15:00 (correct).

    The availability for Thursday in April 2023 is missing the slots from 12:00 to 16:00 (wrong). The only missing slots should be from 14:00 to 16:00.

    When adding a single event, it works fine. The recurring events were not changed before.

    I tried adding a new repeating event on:

    • Mondays from 14:00 to 17:00 and it blocks the 12:00 - 17:00. Again, two hours (12:00-14:00) are blocked that should not be.
    • Mondays from 11:00 to 12:00 and it blocks the correct time only.
    • Mondays from 14:00 to 15:00 and it blocks the 12:00 - 13:00 (wrong) and 14:00 - 15:00 (correct). Same as in the initial example with an event that was created before the DST change (thought that might play a role, but apparently it doesn’t).
    • Mondays from 15:00 to 16:00 and it blocks the correct time only.
    • Mondays from 15:00 to 17:00 and it blocks the 13:00 - 17:00. Again, two hours (13:00-15:00) are blocked that should not be.

    ‌

  17. Valentina R reporter

    another report.

    I did a test on the latest version and it’s getting even worse than it was, blocking out random times and lengths of time. It also happens that slots are shown but not bookable with the “slot cannot be booked“ msg.

  19. Log in to comment
Assignee
–
Type
bug
Priority
blocker
Status
resolved
Votes
2
Watchers
2