GNOME Bugzilla – Bug 530205
Use CalDAV calendar read-only when server unreachable
Last modified: 2010-12-03 16:16:02 UTC
Please describe the problem: I checked the checkbox about the local-sync for offline operation but as soon as my server disappears all my appointments are gone. Steps to reproduce: 1. Create an appointment while server is reachable 2. Quit Evo 3. Make server disappear 4. Start Evolution Actual results: No appointments left in the CalDav calendars. Expected results: See all appointments available in the calendar. Does this happen every time? Yes. Other information: Debian SID, Evolution 2.22.1;
please don't file bugs as blockers by default. thanks.
evolution-caldav is not worked on anymore. Its functionality has been completely migrated to evolution itself, hence moving all open bugs to Evolution itself.
Hmm, there is a little difference between offline mode (File->Work offline) and unreachable server. Maybe not as that big, I do not know, just from my point of view it might be strange to work with the server like any other day, but have things saved on a local machine only, thus moving to the other machine and realizing all the events gone might surprise even regular users. There should be some indication you are working "without server", or some confirmation dialog that you want to work without the server, but evolution is not ready for such a thing, moreover I do not like the idea too, mainly because the above. Nonetheless, the offline support for CalDAV is not implemented yet. Thus confirming a bug report at least for this, as the option in calendar preferences is not relevant here at all.
Yes, the option in the Calendar Backend is quite confusing. I spent a lot of googling until I found out that it's obviously not implemented yet (please correct me if I'm wrong). It could be implemented the same way as the Offline Mode for LDAP contacts, i.e. have a read-only cache on the local harddisk, so no changes need to be sync'ed back to the server. Otherwise this option should be removed.
It works that way at the moment. What I meant with the previous comment about the difference between having evolution offline and server unavailable is that the offline mode for evolution itself makes caldav backend work as you want, but server unreachability is not the same, the isn't turning offline mode for itself only. I'll try to see what we can do with it.
Great, because from a user's perspective, there is no difference between these two.
Created attachment 175792 [details] [review] eds patch for evolution-data-server; This does that. It is trying to be clever, thus on each refresh (either the one on time out set in calendar preferences or by the forced one from the pop-up menu over the calendar) it tries to connect to the server. If it failed for the first time (aka it was reachable before), then it tells it to the user. And vice versa, it connects when the server becomes reachable, but doesn't tell it to anyone. The only restriction is that the server name should be resolvable, to avoid typos in server names.
Created commit 07f8955 in eds master (2.91.4+)