Red Hat Bugzilla – Bug 804651
CalDAV backend doesn't respect "Copy for offline" option
Last modified: 2014-01-02 05:48:29 EST
Description of problem:
when CalDAV URI is unreachable, the calendar can't be enabled in spite of enabled offline cache. This makes offline cache pretty much useless.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. have a CalDAV calendar with Copy Calendar for Offline Use (or so) checkbox checked
2. turn on Offline Mode
3. quit Evolution, restart e-calendar-factory/evolution-data-server, start
4. reenable calendar
calendar can not be enabled again
calendar will be enabled
when user makes changes to calendar contents, he/she should be warned that it can not be pushed to calendar right away. During actual push of the changes, user should be asked how should be any conflicts resolved.
The CalDAV backend doesn't support real offline handling. The most it can show the cached events in offline mode, like On The Web calendars work, and when the server gets reachable then it'll use it in writeable mode again (if available for the user by server principals). Some such code is available in Fedora, thus enabling in offline mode is considered as a typo in the URL (not necessary offline mode initiated by a user, but kinds like VPN unexpected disconnect and such).
Created attachment 579827 [details]
I finally got to this and even I thought this will be significantly harder, then it turned out that the CalDAV backend didn't respect the "Copy calendar contents locally for offline operation" option, and always acted as it would be off. Having it on makes the calendar open in read-only mode while in offline, being able to read current offline cache from the disk.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
devel-acking, (upstream) patch available
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.