asked 2016-07-24 13:12:04 +0300
I tried to add a CalDAV account in my Jolla C and it was succesful. However, it only appeared to sync entries at most about one year old to my Jolla calendar. Is this a property of the Jolla caldav client or the caldav server?
answered 2017-09-26 10:59:05 +0300
I'm proposing a MR on Gitlab adding two settings in the Buteo profile. There is no UI for this, but at least time limit values can be adjusted by user by modifying entries in ~/.cache/msyncd/sync/caldav-sync-XX.xml. These two values should be added or changed in the client profile:
<key value="12" name="Sync Next Months Span"/> <key value="6" name="Sync Previous Months Span"/>
Note that the actual key names may changed after discussion in Gitlab.
It is not released yet, still under testing.
You can add these entries in the file I mentioned. It is a priviledged file, so you need to devel-su.
Damien Caliste ( 2017-11-06 20:24:18 +0300 )editAsked: 2016-07-24 13:12:04 +0300
Seen: 320 times
Last updated: Sep 26 '17
It's a property of the plugin. That setting is currently not exposed in any way, so it's not user configurable, unfortunately. See https://git.merproject.org/mer-core/buteo-sync-plugin-caldav/blob/master/src/caldavclient.cpp#L454 for the place where that's defined. Patches are welcome, if you want to make it configurable via an account setting.
chris.adams ( 2016-07-25 07:53:45 +0300 )editOK, thanks. As a quick'n'dirty fix I just changed the hardcoded # of months from 6 to 60 in a local modification, worked perfectly for me. Will have a look on making this configurable when I have the time (which might not be too soon, seeing as it took me two months to find the time for the dirty hack ;) ), did get an account to merproject git for the purpose :)
elakim ( 2016-09-13 23:07:48 +0300 )editI've created a MER bug to track this: https://bugs.merproject.org/show_bug.cgi?id=1671
Feel free to submit patch or simply ask questions there on how to solve this.
Damien Caliste ( 2016-10-12 17:56:06 +0300 )edit