Thx for the links, but I don't think that middleware is a nice
solution. My logic is simple - why not to provide a simple way to
debug errors raised during ajax calls _by default_? Serving full 500
page when requested via ajax is kind of wrong default way of doing
things.
On May 9, 2:47 am, Ramir
Hello, unfortunantly I am unable to find anything except
http://groups.google.com/group/django-developers/browse_thread/thread/526dd3fd0e21a04e/e4c95e59ffc6b82f?hl=en&lnk=gst&q=ajax#e4c95e59ffc6b82f
can you please point me to that topics?
On May 9, 2:26 am, Ludvig Ericson wrote:
> On May 8, 20
On Fri, May 8, 2009 at 6:25 AM, OverKrik wrote:
>
> Hello, I am working on heavy-AJAX-based website and use firebug alot
> to check responces from server, in case of 500 error Django sends full
> 500 page which is not very easy to use. I've made a simple patch to
> provide light version of 500 pa
On May 8, 2009, at 11:25, OverKrik wrote:
> Hello, I am working on heavy-AJAX-based website and use firebug alot
> to check responces from server, in case of 500 error Django sends full
> 500 page which is not very easy to use. I've made a simple patch to
> provide light version of 500 page in cas
Hello, I am working on heavy-AJAX-based website and use firebug alot
to check responces from server, in case of 500 error Django sends full
500 page which is not very easy to use. I've made a simple patch to
provide light version of 500 page in case of ajax request.
I know that everybody is in ru
