Hello Jan,
Am 24.07.13 17:26, schrieb Ján Máté:
there are 2 different errors in your e-mail:
1.) netLoadCalendar ... => unsuccessful "calendar-multiget" REPORT ...
looks very interesting because we cannot do anything here - we simply
say JavaScript/jQuery to perform the request and waiting for the
result ... the interesting part is that jQuery executes the "error"
callback, but then it returns 207 (2xx = success) ... you can try to
experiment with jQuery (maybe jQuery bug) and report more details
about this error (or create a temporary access to your server and send
me a private message with credentials)
This error only occurs on one of the nine
calendars in this account. It
would be possible to create an own account for you on the server, but
unfortunately i'm not allowed to gain access to this account and the
other calendars, as these contain high secret future appointments and
events.
If there is a chance to export and re-import the faulty calendar to a
new account, i will do so. This calendar isn't so confidental.
Also if you give me instructions for deeper debugging of jQuery, i will
do so, too. But i'm not a java programmer.
2.) if it is possible please download all problematic
events as files
(for example download them using wget) and send me them for further
investigation
The other ones are similar to them and differ only in the
dates/times.
All of them seem to be sent from an exchange server. Do you want the
other ones too?
For everybody: if you find any problematic events,
please send them us
as text files and not as inline e-mail text (nearly all errors are
caused by white or special control characters and these are very often
deleted by e-mail clients)
Hmm, attached it to Thunderbird as files. Did you
receive them inline?
- Rudolf
>
> Safari talks a little more:
>
> Error:
> [netLoadCalendar:
> 'https://calendar.server.tld/caldav.php/username/Cal1994-1996/']
> code: '207'
> webdav_protocol.js:1847
>
> Error:
>
'https://username@calendar.server.tld/caldav.php/username/calendar/040000008200E00074C5B7101A82E0080000000050D2FC76587BCB0100000000000000001000000098700104D4D5F347AB0530C1DF56078A.ics'':
> cannot parse vCalendar
> webdav_protocol.js:1919
>
> Error:
>
'https://username@calendar.server.tld/caldav.php/username/calendar/040000008200E00074C5B7101A82E0080000000090A3269F547BCB0100000000000000001000000025C7D94BDF05964DA2F5013FDE2D0F68.ics'':
> cannot parse vCalendar
> webdav_protocol.js:1919
>
> Error:
>
'https://username@calendar.server.tld/caldav.php/username/calendar/040000008200E00074C5B7101A82E00800000000D0E4D2AC557BCB0100000000000000001000000025C7D94BDF05964DA2F5013FDE2D0F68.ics'':
> cannot parse vCalendar
> webdav_protocol.js:1919
>
> Error:
>
'https://username@calendar.server.tld/caldav.php/username/calendar/040000008200E00074C5B7101A82E0080000000040D23D43567BCB0100000000000000001000000025C7D94BDF05964DA2F5013FDE2D0F68.ics'':
> cannot parse vCalendar
> webdav_protocol.js:1919
>
> Error:
>
'https://username@calendar.server.tld/caldav.php/username/calendar/040000008200E00074C5B7101A82E00800000000F015701C577BCB0100000000000000001000000025C7D94BDF05964DA2F5013FDE2D0F68.ics'':
> cannot parse vCalendar
> webdav_protocol.js:1919
>
> Error:
>
'https://username@calendar.server.tld/caldav.php/username/calendar/040000008200E00074C5B7101A82E0080000000090E58C909414CC0100000000000000001000000025C7D94BDF05964DA2F5013FDE2D0F68.ics'':
> cannot parse vCalendar
> webdav_protocol.js:1919
>
> Error: [netLoadCalendar:
> 'https://calendar.server.tld/caldav.php/username/Cal1994-1996/']
> code: '207'
> webdav_protocol.js:1847
>
> The calendar which ist NOT loaded ist "Cal1994-1996", the calendar
> "calendar" is displayed corretly (as long as i can check)!
>
>
>
> Am 24.07.13 11:51, schrieb Ján Máté:
>> 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".
>>
>>
>> JM
>>
>>
>> On Jul 24, 2013, at 9:15 AM, Graf von Roit zu Hoya
>> <graf.roit(a)gmail.com <mailto:graf.roit@gmail.com>> wrote:
>>
>>> Hello,
>>>
>>> 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,
>>> Rudolf
>>>
>>> Am 24.07.13 08:59, schrieb Martin Egge:
>>>> Hello,
>>>>
>>>> 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,
>>>> Martin