Hi Graf,

please try to increase the timeout in config.js to check if the problem is really the calendar "size".

In 0.10 we will add support for "interval synchronization" - it will solve all problems with "too big calendars".


On Jul 24, 2013, at 9:15 AM, Graf von Roit zu Hoya <graf.roit@gmail.com> wrote:


me too. But i thought it is a timout as this particular calendar is a very big archive of old events (years 1994 to 1997). I didn't investigate further, as this is one of the calendars i would like to disable to load on regular startup of CalDAVZap.

When i can help debugging, i stand by.

Best regards,

Am 24.07.13 08:59, schrieb Martin Egge:

I started using CalDavZAP a few days ago. It works fine with one of my
calendars but does not show any events of my other calendar. There is an
attention sign (exlamation mark) after the calendar name.

I suppose there is at least one event that breaks the calendar parsing.
Is there any way to debug?

Kind regards,


Rudolf Graf von Roit zu Hoya
E-Mail: graf.roit@gmail.com