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
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
Hi Martin,
if an event is not processed you will get a warning in the browser/javascript console. If there is a javascript error you also get it in this console.
First please try to use the latest release candidate from:
http://www.inf-it.com/CalDavZAP_0.9.1-rc2.zip
and then send me the result.
JM
On Jul 24, 2013, at 8:59 AM, Martin Egge mailinglists@martin.egge.info wrote:
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
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@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
-- Rudolf Graf von Roit zu Hoya E-Mail: graf.roit@gmail.com
Hello,
the only thing related to the "problem" calendar i found:
Zeitstempel: 24.07.13 12:24:58 Fehler: nicht wohlgeformt Quelldatei: https://calendar.server.tld/caldav.php/username/cal1994-1996/ Zeile: 2008, Spalte: 3 Quelltext: u
followed by:
Zeitstempel: 24.07.13 12:24:58 Fehler: nicht wohlgeformt Quelldatei: https://calendar.server.tld/caldavzap/ Zeile: 2008, Spalte: 3 Quelltext: u
This two errors occur five times.
There are many other errors before and after like this:
Zeitstempel: 24.07.13 12:24:56 Fehler: Nicht übereinstimmendes Tag. Erwartet: </input>. Quelltext: <div><input></div>
But i think, this doesn't matter. And the css warnings, too.
Hope this helps.
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@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
--
Rudolf Graf von Roit zu Hoya *E-Mail:* graf.roit@gmail.com
Hello,
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/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': 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@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
--
Rudolf Graf von Roit zu Hoya *E-Mail:* graf.roit@gmail.com
Hi Rudolf,
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)
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
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)
JM
On Jul 24, 2013, at 12:49 PM, Graf von Roit zu Hoya graf.roit@gmail.com wrote:
Hello,
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/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': 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@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
-- Rudolf Graf von Roit zu Hoya E-Mail: graf.roit@gmail.com
-- Rudolf Graf von Roit zu Hoya E-Mail: graf.roit@gmail.com
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/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': cannot parse vCalendar webdav_protocol.js:1919
Error: 'https://username@calendar.server.tld/caldav.php/username/calendar/0400000082...'': 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@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
Hi Rudolf,
On Jul 24, 2013, at 5:54 PM, Graf von Roit zu Hoya graf.roit@gmail.com wrote:
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.
I understand
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.
JavaScript is not Java (personally I really hate Java but really love JavaScript) ... and sorry but I have no exact idea howto debug it - I just see that this is not CalDavZAP bug ... here is the documentation for the problematic call: http://api.jquery.com/jQuery.ajax/
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?
If the difference is only in dates then no, one example is enough.
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?
No, you are OK, but I've got lot of private messages with events as inline text. It is not problem if the sender is experienced and knows that the problem is related to specific part of event, but lot of users cannot distinguish between syntax/logical errors in VEVENT and processing errors.
JM
- Rudolf
Hello Jan,
Am 24.07.13 18:12, 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.
I understand
I've got an ics-File containing the problematic calendar. It is dumped via wget direct from the davical database. Uncompressed 116k. Not so big as i thought. Would this help?
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.
JavaScript is not Java (personally I really hate Java but really love JavaScript) ... and sorry but I have no exact idea howto debug it - I just see that this is not CalDavZAP bug ... here is the documentation for the problematic call: http://api.jquery.com/jQuery.ajax/
Neither Java nor JavaScript are my profession. I'm only a admin. Shell and Perl are my world.
If the difference is only in dates then no, one example is enough.
The dates and one character in the subject line: (1/20xx), (2/20xx) and so on.
-Rudolf
Hi,
On Jul 24, 2013, at 7:21 PM, Graf von Roit zu Hoya graf.roit@gmail.com wrote:
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.
I understand
I've got an ics-File containing the problematic calendar. It is dumped via wget direct from the davical database. Uncompressed 116k. Not so big as i thought. Would this help?
I don't think that this can help to debug the issue, because this problem is related to calendar-multiget REPORT (we get raw data from the server without processing the content). Data processing is performed ONLY if this request is successful ...
JM
Hello,
Am 24.07.2013 um 21:25 schrieb Ján Máté jan.mate@inf-it.com
I've got an ics-File containing the problematic calendar. It is dumped via wget direct from the davical database. Uncompressed 116k. Not so big as i thought. Would this help?
I don't think that this can help to debug the issue, because this problem is related to calendar-multiget REPORT (we get raw data from the server without processing the content). Data processing is performed ONLY if this request is successful ...
It's a standard DAViCal with latest patches from you. Postgresql 8.4.13, CentOS 6.4. Nothing unusal...
On Jul 24, 2013, at 10:21 PM, Graf Roit graf.roit@gmail.com wrote:
Hello,
Am 24.07.2013 um 21:25 schrieb Ján Máté jan.mate@inf-it.com
I've got an ics-File containing the problematic calendar. It is dumped via wget direct from the davical database. Uncompressed 116k. Not so big as i thought. Would this help?
I don't think that this can help to debug the issue, because this problem is related to calendar-multiget REPORT (we get raw data from the server without processing the content). Data processing is performed ONLY if this request is successful ...
It's a standard DAViCal with latest patches from you. Postgresql 8.4.13, CentOS 6.4. Nothing unusal...
I understand, but "something" is wrong between your server and CalDavZAP ... and it is very probably the jQuery (library we use). The problem is that your bug looks very specific (browser/version, browser/version + OS/version, browser/version + OS/version + jQuery/version, ...).
JM
Hello,
Hello,
Am 24.07.2013 um 21:25 schrieb Ján Máté jan.mate@inf-it.com
I've got an ics-File containing the problematic calendar. It is dumped via wget direct from the davical database. Uncompressed 116k. Not so big as i thought. Would this help?
I don't think that this can help to debug the issue, because this problem is related to calendar-multiget REPORT (we get raw data from the server without processing the content). Data processing is performed ONLY if this request is successful ...
It's a standard DAViCal with latest patches from you. Postgresql 8.4.13, CentOS 6.4. Nothing unusal...
I understand, but "something" is wrong between your server and CalDavZAP ... and it is very probably the jQuery (library we use). The problem is that your bug looks very specific (browser/version, browser/version + OS/version, browser/version + OS/version + jQuery/version, ...).
Ok. Tomorrow i try to load the calendar into a test account, but i mean to remember DAViCal's import function is not very reliable.
I give you info on success.
Hi Rudolf,
finally we found where is the problem. The result from the server is successfully received (207 code) but the XML from your server is NOT VALID.
And the problem is, that one of your events (see the output from XML validator below) contain a special character (0x12) which not allowed in XML 1.0 (check: http://en.wikipedia.org/wiki/Valid_characters_in_XML).
So this is a very rare a very specific bug and needs a fix in DAViCal.
JM
On Jul 24, 2013, at 10:46 PM, Graf Roit graf.roit@gmail.com wrote:
Hello,
Hello,
Am 24.07.2013 um 21:25 schrieb Ján Máté jan.mate@inf-it.com
I've got an ics-File containing the problematic calendar. It is dumped via wget direct from the davical database. Uncompressed 116k. Not so big as i thought. Would this help?
I don't think that this can help to debug the issue, because this problem is related to calendar-multiget REPORT (we get raw data from the server without processing the content). Data processing is performed ONLY if this request is successful ...
It's a standard DAViCal with latest patches from you. Postgresql 8.4.13, CentOS 6.4. Nothing unusal...
I understand, but "something" is wrong between your server and CalDavZAP ... and it is very probably the jQuery (library we use). The problem is that your bug looks very specific (browser/version, browser/version + OS/version, browser/version + OS/version + jQuery/version, ...).
Ok. Tomorrow i try to load the calendar into a test account, but i mean to remember DAViCal's import function is not very reliable.
I give you info on success.
Hello Jan,
thank's a lot. So my problem is defined. Could this be the same to Martin?
I will correct the concerned event.
--Rudolf
Am 25.07.13 13:11, schrieb Ján Máté:
Hi Rudolf,
finally we found where is the problem. The result from the server is successfully received (207 code) but the XML from your server is NOT VALID.
And the problem is, that one of your events (see the output from XML validator below) contain a special character (0x12) which not allowed in XML 1.0 (check: http://en.wikipedia.org/wiki/Valid_characters_in_XML).
So this is a very rare a very specific bug and needs a fix in DAViCal.
JM
On Jul 24, 2013, at 10:46 PM, Graf Roit <graf.roit@gmail.com mailto:graf.roit@gmail.com> wrote:
Hello,
Hello,
Am 24.07.2013 um 21:25 schrieb Ján Máté <jan.mate@inf-it.com mailto:jan.mate@inf-it.com>
I've got an ics-File containing the problematic calendar. It is dumped via wget direct from the davical database. Uncompressed 116k. Not so big as i thought. Would this help?
I don't think that this can help to debug the issue, because this problem is related to calendar-multiget REPORT (we get raw data from the server without processing the content). Data processing is performed ONLY if this request is successful ...
It's a standard DAViCal with latest patches from you. Postgresql 8.4.13, CentOS 6.4. Nothing unusal...
I understand, but "something" is wrong between your server and CalDavZAP ... and it is very probably the jQuery (library we use). The problem is that your bug looks very specific (browser/version, browser/version + OS/version, browser/version + OS/version + jQuery/version, ...).
Ok. Tomorrow i try to load the calendar into a test account, but i mean to remember DAViCal's import function is not very reliable.
I give you info on success.
-
Graf Roit -
Graf von Roit zu Hoya
-
Ján Máté -
Martin Egge