Hi,
Suddenly a good working configuration came to a halt.
Symptomes: InfCloud gets stuck at "Loading 1 of 1".
Reproducible with InfCloud 0.13.1 and 0.13.2.rc1, and with CardDAVmate 0.13.2.rc1.
The problem seems to be in the contacts, since CalDAVzap works properly.
The last command executed (from the http log): "REPORT /caldav.php/jv/addresses/ HTTP/1.1" 207 8404356 "http://localhost/carddavmate/"
I can fetch the contacts w/o problems (using wget), and I tried reloading the contents from the VCF (using the DAViCal web UI). No change.
I probably did something stupid, but I do not have the faintest idea what...
-- Johan
Hi Johann,
it is often caused by invalid XML 1.0 data returned from the server. There is a list of characters not allowed in XML 1.0, but lot of server (e.g. DAViCal) accept these characters in vCard/vCalendar and then the resulting XML response is invalid (so the browser "crashes" on the data parsing). The HTTP response code in these cases is always 207, but the result is simply not valid ... see: http://en.wikipedia.org/wiki/Valid_characters_in_XML http://en.wikipedia.org/wiki/Valid_characters_in_XML
See also: https://www.inf-it.com/mlmmj/davclients/2013-07/0000079.html https://www.inf-it.com/mlmmj/davclients/2013-07/0000079.html
If the links above not help you then please send me a private email with demo credentials and I will debug it ...
Cheers,
JM
On 07 Dec 2015, at 15:45, Johan Vromans jvromans@squirrel.nl wrote:
Hi,
Suddenly a good working configuration came to a halt.
Symptomes: InfCloud gets stuck at "Loading 1 of 1".
Reproducible with InfCloud 0.13.1 and 0.13.2.rc1, and with CardDAVmate 0.13.2.rc1.
The problem seems to be in the contacts, since CalDAVzap works properly.
The last command executed (from the http log): "REPORT /caldav.php/jv/addresses/ HTTP/1.1" 207 8404356 "http://localhost/carddavmate/"
I can fetch the contacts w/o problems (using wget), and I tried reloading the contents from the VCF (using the DAViCal web UI). No change.
I probably did something stupid, but I do not have the faintest idea what...
-- Johan
Hi Ján,
I verified the contacts data in the davical database, and it does not contain invalid XML characters. I even used the more strict 1.0
[\x{0009}\x{000a}\x{000d}\x{0020}-\x{007e}\x{0085}\x{00a0}-\x{d7ff}\x{e000}-\x{fffd}\x{10000}-\x{10ffff}]
The debugger shows that CardDAVmate crashes in
TypeError: variables.forEach is not a function getContactDataColumn (http://localhost/carddavmate/interface.js:2150:12) AddressbookList.getSortKey (http://localhost/carddavmate/addressbook.js:138:13)
I turned out that I had my globalCollectionSort still as [ 'last', 'first', 'middle' ] while the newer functionality requires an array of arrays.
However, this change was introduced in 0.13, and I've been running 0.13.1 since september... I cannot explain why it stopped working today...
Anyway, I know what to do now.
Thanks for the suggestions that helped me out!
-- Johan
Hi Johan,
yes we changed lot of things between 0.12 and 0.13 ...
It is worth to read the changelog.txt before each upgrade ... especially the "note" and "configuration" lines ;-)))
Cheers,
JM
p.s.: to clean-up all your settings (stored as DAV property on the server) you can use SHIFT+login (keep holding the SHIFT + click to the login button) ...
On 07 Dec 2015, at 20:57, Johan Vromans jvromans@squirrel.nl wrote:
Hi Ján,
I verified the contacts data in the davical database, and it does not contain invalid XML characters. I even used the more strict 1.0
[\x{0009}\x{000a}\x{000d}\x{0020}-\x{007e}\x{0085}\x{00a0}-\x{d7ff}\x{e000}-\x{fffd}\x{10000}-\x{10ffff}]
The debugger shows that CardDAVmate crashes in
TypeError: variables.forEach is not a function getContactDataColumn (http://localhost/carddavmate/interface.js:2150:12) AddressbookList.getSortKey (http://localhost/carddavmate/addressbook.js:138:13)
I turned out that I had my globalCollectionSort still as [ 'last', 'first', 'middle' ] while the newer functionality requires an array of arrays.
However, this change was introduced in 0.13, and I've been running 0.13.1 since september... I cannot explain why it stopped working today...
Anyway, I know what to do now.
Thanks for the suggestions that helped me out!
-- Johan
userauthOn Mon, 7 Dec 2015 21:04:56 +0100 Ján Máté jan.mate@inf-it.com wrote:
yes we changed lot of things between 0.12 and 0.13 ... It is worth to read the changelog.txt before each upgrade ... especially the "note" and "configuration" lines ;-)))
If a problem like this occurs after upgrade to a newer release I know where to look... But this only occurred several weeks after the upgrade.
p.s.: to clean-up all your settings (stored as DAV property on the server) you can use SHIFT+login (keep holding the SHIFT + click to the login button) ...
Oh, but I do not login :) ...
-- Johan
-
Johan Vromans -
Ján Máté