Closed GoogleCodeExporter closed 8 years ago
Original comment by will.abson
on 11 Sep 2012 at 11:17
I could not reproduce this issue on the latest Community release (4.2.a) but
Enterprise 4.0.2 did suffer the problem.
The cause is that the web script framework in that version does not properly
catch the exception that is thrown and therefore information on the problem
that has occurred is not returned in the JSON response (in fact the response
format is changed to HTML and contains no useful information).
Adding a custom failure handler to the dialog seems to fix the problem, so that
in the event of no failure info being returned, a generic message is now
displayed.
Original comment by will.abson
on 17 Oct 2012 at 5:34
Fixed in r1315 / v2.0.1
Original comment by will.abson
on 17 Oct 2012 at 5:39
Original issue reported on code.google.com by
tahirjuv...@gmail.com
on 3 Sep 2012 at 2:44