Events from CalDAV not taken into consideration when checking availability

[kuba-orlik]

Issue Summary

Appointment selector shows me as available even if I have a single day-long event for a particular date

Steps to Reproduce

1. Connect a CalDAV server
2. Pick a calendar & confirm
3. In a calendar app, create an event for a given date
4. Open the URL of meeting time picker
5. Select the day containing the event from step 3
6. See that all possible time slots are available, not affected by the event created in step 3

Technical details

• Browser version: Firefox 92
• Node.js version: 14

[femyeda]

Fixed in latest commit. Will let you know when deployed.

[jdaviescoates]

Really looking forward to this being deployed! I'm really loving Cal.com so far, but without CalDAV working properly I can't use it because my Nextcloud CalDAV calendar is my primary calendar.

[Kovah]

Is there any ETA when this will be deployed? It's basically the only issue holding me back from using Cal right now. :(

[jdaviescoates]

@Kovah it looks like there are quite a few CalDAV issues that need resolving see #956 - but I'm the same as you, as soon as CalDAV integration actually works I'll start using Cal :)

[natelindev]

cannot repoduce this now.

[jdaviescoates]

cannot repoduce this now.

Nor can I. Just tested on cal.com and it does now block out times from my CalDAV calendar!

[obstschale]

I just signed up on cal.com and connected my CalDAV Account. This bug is still present.

[jdaviescoates]

I just signed up on cal.com and connected my CalDAV Account. This bug is still present.

Works for me using Nextcloud Calendar. What CalDAV are you using @obstschale ?

[borishinzer]

Same issue here. Tested with Nextcloud 19 and 23

[obstschale]

I use Synology Calendar. I use CalDav on my MacBook, Android Devices and have no problem at all.

The screenshot shows that I have 1 meeting, but cal.com offers free slots

[amigasoc]

If it's significant, we're seeing this in our logs:

timeZoneName WARN [[lib] caldav_calendar Method not implemented. dateFrom: 2022-02-24T00:00:00+00:00, dateTo: 2022-02-24T23:59:59+00:00, selectedCalendars: [object Object]

We're connecting to a CalDAV server on Radicale.

[mathieugp]

I am seeing this problem too. My CalDav compatible server is NextCloud 20.x.

One difference maybe with the other cases above: for some reason, one particular event seems to be taken into account. That event was created by accepting an invitation sent from Google Calendar to my CalDav calendar, while the others were created by me manually. I am using Thunderbird 78.x on Ubuntu 20.04 on the client side.

I will be happy to share any (non personal) information if it can help. :-)

[KierenB]

Commenting to note that I am also seeing this issue - connecting to Fastmail via caldav.

[lionux2]

The same issue with Apple Calendar ... tested today, and failing too.

[ykktrcb7]

Same issue with Baikal server

[PeerRich]

has this not fixed the bug? https://github.com/calendso/calendso/pull/1649 if not, @natelindev can take a look!

[jdaviescoates]

I just re-checked and this works fine for me using a Nextcloud calendar. Events on my Nextcloud calendar are taken into consideration are those time slots are not available to book via Cal.com

[KierenB]

I just checked using cal.com, it's not fixed there yet (not sure if the fix has been deployed there yet or not?)

Edit: using Fastmail caldav account

[lionux2]

Just checked and not working for me either. Based on jdaviescoates, it works, so maybe his configuration on Nextcloud calendar works. I have multiple ' calendars', such as personal, work, etc... so maybe cal.com does not go through any of them if many exists?

[PeerRich]

Just checked and not working for me either. Based on jdaviescoates, it works, so maybe his configuration on Nextcloud calendar works. I have multiple ' calendars', such as personal, work, etc... so maybe cal.com does not go through any of them if many exists?

can you record a loom.com and @natelindev can you take a look?

[borishinzer]

from our cal server's /var/log/messages:

Feb 21 14:59:38 cal yarn[3102337]: #033[90m13:59:38.149 timeZoneName #033[39m#033[1m#033[93mWARN#033[39m#033[22m CalendarManager
Feb 21 14:59:38 cal yarn[3102337]: #033[1m#033[97m#033[41m TypeError #033[49m#033[39m#033[22m Only absolute URLs are supported#033[1m#033[4m
Feb 21 14:59:38 cal yarn[3102337]: error stack:#033[24m#033[22m

I would guess Nextcloud and Cal timezones are not matching?

[haccg]

Tried it with Synlogy CalDav-Server.

Works ONLY with the primary calendar.
All other calendars are not working with the collision check.

If you could fix this, it would be very good.

[restuccia]

I encounter a similar issue, probably due to time zones as well. My CalDAV server is SOGo 2.3.12.

[jdaviescoates]

Just checked and not working for me either. Based on jdaviescoates, it works, so maybe his configuration on Nextcloud calendar works. I have multiple ' calendars', such as personal, work, etc... so maybe cal.com does not go through any of them if many exists?

Just to add, I don't have many but it is checking again two separate Nextcloud calendars (my primary work and personal calendars). And it's still working nicely for me (just checked again - seems to have got a lot faster too). I'm currently on Nextcloud 24.0.1

[jdaviescoates]

And it's still working nicely for me (just checked again - seems to have got a lot faster too). I'm currently on Nextcloud 24.0.1

Well, it works in that CalDAV events are taken into consideration, and appointments created via Cal.com to added to the calendar selected in the options under https://app.cal.com/apps/installed

However, if I e.g. edit the location of the booking then instead of editing the previously created event a whole new event is added to the calendar. I guess I should create a new issue about that...

[alishaz-polymath]

@jdaviescoates Yes, please create a new issue about that. I'm going ahead and closing this ticket as I have tested that CalDAV events are taken into consideration to block double booking, as you have confirmed as well. 🙏