Closed
Bug 748245
Opened 12 years ago
Closed 10 years ago
No free/busy status in Invite Attendees window with CalDAV after enabling cache
Categories
(Calendar :: Provider: CalDAV, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: krissn, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [CalDAV server: DavMail][calconnect31])
I'm using Lightning to access my Exchange calendar via the DavMail gateway (using CalDAV). When creating a new event I'm using the Invite Attendees window to add participants to the meeting. Unfortunately in the recent Lightning versions the Invite Attendees window doesn't show free/busy status of any of the participants (all rows are red). However when I disable cache for the Exchange calendar in Lightning the free/busy status display starts working again. If I enable cache again it still works, however only until I restart Thunderbird. After that it doesn't work again (until I disable the cache again of course). This has been reproduced on Thunderbird 11.0.1 with Lightning 1.3 (both Linux and Windows).
Comment 1•12 years ago
|
||
Reproduced on Thunderbird 13.0.1 Windows. Lightning 1.5 Lightning 1.5.1 Lightning 1.5.2 Reproduced on Thunderbird 12.0 Mac (Snow Leopard) Lightning 1.5.1
Same problem here Thunderbird 15 on Windows, Lightning 1.7, DavMail 3.9.9-1976. Turning off "Cache" and restarting TB works around this problem.
Comment 3•12 years ago
|
||
Same problem here Thunderbird 15 on Ubuntu, Lightning 1.7, DavMail 4.0.0-2016
Updated•12 years ago
|
Whiteboard: [CalDAV server: DavMail][calconnect25]
Comment 4•12 years ago
|
||
Confirmed on: Thunderbird 17, Lightning 1.9, Zimbra CalDAV server
Updated•10 years ago
|
Whiteboard: [CalDAV server: DavMail][calconnect25] → [CalDAV server: DavMail][calconnect31]
Comment 5•10 years ago
|
||
I've tested this on the latest nightly with Zimbra 9.0 prerelease and it works for me. If the issue persists, please reopen this bug, providing additional details.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•