52
edits
Calendar:QA CalDAV Support: Difference between revisions
→Google Calendar Notes: both old and new URL
(→Google Calendar Notes: Changed URL for Google CalDAV) |
(→Google Calendar Notes: both old and new URL) |
||
| Line 283: | Line 283: | ||
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. | 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. | ||
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/> https:// | 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/> https://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> https://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: Neither CalDAV nor the GDATA provider support tasks. | No Tasks: Neither CalDAV nor the GDATA provider support tasks. | ||