Created on 2008-05-19.13:26:27 by htgoebel, last changed 163 months ago by ced.
Fixed with changeset 093fa8487414
As issue10 showed, tracking down errors in server communication may be not that obviuos, since tryton does not print a trace back. Enclosed please find a patch wihich makes at least Bug reporting print the place, where the exception occured.
|2008-05-19 17:15:26||ced||set||status: unread -> resolved|
messages: + msg60
nosy: + ced