Calendar:QA CalDAV Support: Difference between revisions

← Older edit

Calendar:QA CalDAV Support (view source)

Revision as of 18:39, 6 April 2017

550 bytes added , 6 April 2017

add notes on Xandikos

Jelmer

2

edits

@@ Line 42: / Line 42: @@
 |-
 | [http://www.davical.org/ DAViCal]
-| 0.9.5
+| 0.9.7
+| http://www.reinit.net/rc1-ok.png
+| http://www.reinit.net/rc1-ok.png
+| http://www.reinit.net/rc1-ok.png
+| http://www.reinit.net/rc1-ok.png
+| http://www.reinit.net/rc1-ok.png
 | http://www.reinit.net/rc1-ok.png
-| http://www.reinit.net/rc1-broken.png
-|
-|
 | http://www.reinit.net/rc1-ok.png
 |
-|
+| [http://rscds.sourceforge.net/clients.php?client=Mozilla DAViCal docs] [http://wiki.davical.org/w/CalDAV_Clients/Mozilla_Calendar Mozilla on DAViCal Wiki]
-|
-|
 |-
 |
@@ Line 66: / Line 66: @@
 |-
 | [http://www.kerio.com/kms_home.html Kerio MailServer]
-| 6.6
+| 6.7
-|
+| http://www.reinit.net/rc1-ok.png
-|
+| http://www.reinit.net/rc1-ok.png
-|
-|
-|
-|
-|
 |
 |
+| http://www.reinit.net/rc1-ok.png
+| http://www.reinit.net/rc1-ok.png
+| http://www.reinit.net/rc1-failed.png
+| [[Calendar:QA_CalDAV_Support#Kerio_Notes|here]]
+| [http://support.kerio.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=481 KB Article]
 |-
 |
@@ Line 173: / Line 173: @@
 |
 |-
-| [http://www.chandlerproject.org/bin/view/Projects/CosmoHome Chandler Server (Cosmo)]
+| [http://chandlerproject.org/Projects/CosmoHome Chandler Server (Cosmo)]
 | 1.1.0
 | http://www.reinit.net/rc1-ok.png
@@ Line 183: / Line 183: @@
 | http://www.reinit.net/rc1-broken.png
 | [[Calendar:QA_CalDAV_Support#Chandler_Server_(Cosmo)_Notes|here]]
-| [http://chandlerproject.org/Projects/ChandlerServerEndUserManual#Supported%20Clients Client configuration]<br/>[https://hub.chandlerproject.org Hub Server Accounts]
+| [http://chandlerproject.org/Projects/CosmoWithLightning Using Lightning With Chandler Hub and Chandler Server]<br/>[https://hub.chandlerproject.org Hub Server Accounts]
 |-
 |
@@ Line 225: / Line 225: @@
 'Access' refers to [http://tools.ietf.org/html/rfc4791 CalDAV-access (rfc4791)], which permits creating, reading, editing, and deleting events and tasks (todos) in calendars.
-'Scheduling' refers to [http://www.ietf.org/internet-drafts/draft-desruisseaux-caldav-sched-06.txt CalDAV-sched (draft)], which permits retrieving participants' free-busy info, proposing a meeting time to participants, and gathering the participants' accepts and declines.
+'Scheduling' refers to [http://tools.ietf.org/html/draft-desruisseaux-caldav-sched-08 CalDAV-sched (draft)], which permits retrieving participants' free-busy info, proposing a meeting time to participants, and gathering the participants' accepts and declines.
 Server Legend:
@@ Line 263: / Line 263: @@
 ===Chandler Server (Cosmo) Notes===
-The WebUI does not show dates of tasks, but the server does store dates of tasks edited in Sunbird, and preserves the dates even when the task is edited by the webUI.
+The Web interface to Chandler Server offers a limited view of data that may be stored by CalDAV and other clients. Using this limited UI for edition of events or notes should have no adverse effect on underlying/background data.
-The WebUI creates 'notes' by default and stores them as undated tasks (todos).
-The WebUI 'Add to calendar' button then allows you to add dates to a note, and when you click 'save' it will turn it into an event.
-Clicking the collection (calendar) name in the WebUI causes it to reload.  It's useful if you make a change via Sunbird and want to see it in the WebUI.
 ===Zimbra Notes===
@@ Line 287: / Line 281: @@
 ===Google Calendar Notes===
-CalDAV vs. GDATA:  Google Calendar's CalDAV protocol support is an early prototype and is not recommended; users who just want to access their Google Calendar are much better off using the [https://addons.mozilla.org/en-US/sunbird/addon/4631 GDATA provider].
+CalDAV vs. GDATA: Most of Google Calendar's features can be accessed via the CalDAV protocol, for which Lightning has built-in support, making GDATA optional. In the past, CalDAV access was bugged, causing alarms (reminders) to sync improperly, but this has been fixed ([http://code.google.com/p/google-caldav-issues/issues/detail?id=25 Google CalDAV issue 25], Sunbird/Lightning {{bug|451821}}). Reminders set in Lightning now sync properly via CalDAV and will appear as pop-ups in the web interface and as notifications in the Android calendar app. Only the ability to set up SMS or email reminders is missing.
-Reminder alarm loop:  Google Calendar's CalDAV server does not preserve Sunbird/Lightning alarm properties ([http://code.google.com/p/google-caldav-issues/issues/detail?id=25 Google CalDAV issue 25], Sunbird/Lightning {{bug|451821}}), so Sunbird/Lightning will get into an infinite alarm loop.  (Events are created with an alarm by default, disregarding Sunbird/Lightning preferences, so just creating an event starts the loop.) The workaround is to tell Sunbird/Lightning to ignore these alarms: in the Calendars tab, popup the menu on the Google calendar, click 'Properties', and uncheck the checkbox "show alarms".
 Location URL: As described in the [http://www.googlewatchblog.de/2008/08/02/calendar-mit-via-webdav-mitsunbird-oder-thunderbird-synchronisieren/ instructions (in German)], the CalDAV URL is of the form<br/>&nbsp;&nbsp;https&#x3a;//www.google.com/calendar/dav/<i>CALENDAR_ID</i>/events<br/>
-where <i>CALENDAR_ID</i> for your initial calendar is your full email@address.  The calendar URLs end with <tt>/events</tt>, not <tt>/user</tt> (<tt>/user</tt> identifies the user account, not the calendar, and is used in Apple iCal).  For other calendars, extract the calendar id from the URLs in the calendar settings page of the webUI.
+where <i>CALENDAR_ID</i> for your initial calendar is your full email@address.  The calendar URLs end with <tt>/events</tt>, not <tt>/user</tt> (<tt>/user</tt> identifies the user account, not the calendar, and is used in Apple iCal).  This URL only works when you have enabled access for less secure apps in your Google account settings. You can also use the newer API using the following URL, which also works when you haven't enabled access for less secure apps:<br>&nbsp;&nbsp;https&#x3a;//apidata.googleusercontent.com/caldav/v2/<i>CALENDAR_ID</i>/events<br/>For other calendars, extract the calendar id from the URLs in the calendar settings page of the webUI.
-No Tasks: Google Calendar does not support tasks (todo's).
-More known limitations are listed at [http://www.google.com/support/calendar/bin/answer.py?answer=99355 Google Calendar CalDAV Support].
+No Tasks: Neither CalDAV nor the GDATA provider support tasks.
 ===Yahoo Calendar Beta Notes===
@@ Line 335: / Line 325: @@
 email with short reply corresponding to the button.)
+===Kerio Notes===
+CalDAV calendars and tasks work fine. Free/busy support doesn't currently work (see {{bug|456380}})).
+===Xandikos Notes===
+CalDAV calendars and tasks work. Scheduling isn't currently implemented.
+When running Xandikos behind an Apache server, make sure to disable HTTP/2 either in Thunderbird or in Apache. This is because of {{bug|1106727}}.
 [[category:calendar|QA Links]]