101
edits
m (clarify zimbra note) |
(use log to determine if server claims to support scheduling or auto-scheduling) |
||
| Line 213: | Line 213: | ||
===Diagnosis hints=== | ===Diagnosis hints=== | ||
To narrow possible causes of CalDAV problems in <i>small</i> | To narrow possible causes of CalDAV problems in <i>small</i> calendars, (1) set both preferences <tt>calendar.debug.log</tt> and <tt>calendar.debug.log.verbose</tt> to true, and (2) click right on calendar in the Calendars pane to reload it. (Set pref via Options / General / Config editor, right click New / Boolean to add it.) | ||
calendars, (1) set | |||
true, and (2) click right on calendar in the Calendars pane to reload it. The | The xml CalDAV messages will be shown in the error console (and in the startup command line shell) with verbose logging. | ||
xml CalDAV messages will be shown in the error console (and in the | |||
startup command line shell). | The kind of scheduling a server claims to support can also be found with verbose logging. | ||
Look for something like | |||
CalDAV: Error getting DAV header, status 404 | |||
CalDAV: Server does not support CalDAV scheduling. | |||
Or | |||
CalDAV: DAV header: 1, 2, access-control, calendar-access, calendar-schedule | |||
CalDAV: Server generally supports calendar-schedule | |||
Or | |||
CalDAV: DAV header: 1, 2, access-control, calendar-access, calendar-auto-schedule | |||
CalDAV: Server supports calendar-auto-schedule | |||
===SOGo Notes=== | ===SOGo Notes=== | ||
edits