Hi, in that case could you send me a log file with every request performed including requests for synchronization? I can check that and find out exact order of performing ajax calls. Thanks Regards, Andrej Dňa 2. 5. 2014 17:14 Attila Asztalos wrote / napísal(a):
Hi, I'd love to, but as I already mentioned earlier in this thread this is not an internet-facing setup, it works on LAN only, and it's not even powered up most of the time. I'll happily run whatever test you can think of or send you any log / config file you might need, but making it externally accessible is not really an option right now. Anyway, it's a standard Baikal-on-Apache setup, nothing special about it. Regards, Attila
On 2-May-2014 15:34, Andrej Lezo wrote:
Hi Attila, it seems that your server supports Calendar-query reuqests but no sync-collection requests. It results in performing of PROPFIND requests so every event is loaded. Could you create a demo account for me and send credentials on my email? I can check whole behaviour and make potential fix. Thanks in advance Regards, Andrej Dňa 2. 5. 2014 13:55 Attila Asztalos wrote / napísal(a):
Hi, that's perfectly reasonable (and events with, say, less than a month past-due indeed do show up immediately). What is a bit confusing is that much earlier events do show up anyway after waiting a short time - just not immediately. Perhaps some consistency (either loading everything right from the start, or not loading events older than the 'globalEventStartPastLimit' limit at all - except maybe at a specific request of clicking a "load older/all todos" button) would be preferable? It's clearly not a big issue of course... Regards, Attila
On 23-Apr-2014 16:31, Andrej Lezo wrote:
Hi Attila, thanks for your attachment. The reason why you don't see your to-do from last year is because we use time range filtering for todo/event loading (Calendar-query) to minimalize server traffic. So we are loading todos which are after start of that time range. Unfortunately there is no such thing as using of time range filter in combination with STATUS=NEEDS-ACTION filter in logical "OR" relation (http://tools.ietf.org/html/rfc4791#section-7.8). But you can extend the start of your time range by setting globalEventStartPastLimit variable to bigger number in config.js file. Default value is 3. Regards, Andrej Dňa 22. 4. 2014 22:06 Attila Asztalos wrote / napísal(a):