Comment 1 for bug 583069

Revision history for this message
Mitja Pagon (sect2k) wrote :

Looks like more JSON decoding issues, the thing is, I can't reproduce this one. Is there anyway you could find out what part of JSON returned by zimbra causes the error (located at chat 25299 in your case).

To do that, try this. Login into zimbra web client, open a new tab in browser and type this url

https://<email address hidden>/?fmt=json&query=is:unread

copy the content of that page into text editor and look at what is at char 25299.

That would probably help a lot. You breaking my stuff, helps me improve it so keep on breaking ;-)

Cheers,
Mitja