On 25 fév, 17:06, Margie Roginski wrote:
> Hi - thanks for your responses. Was on vacation and forgot to check
> back on this thread. The idea of middleware is good. I'm not sure,
> however, if the views.py code generates an exception, that it can be
> caught by the
Possibly useful tip:
Note that if you use request.is_ajax() in your django views, you can
also use e.g. the "Modify Headers" firefox plugin to simply pretend to
django that an ordinary request you've e.g. typed into your browser
address bar is an "ajax" request, with a rule e.g.
Action
Hi - thanks for your responses. Was on vacation and forgot to check
back on this thread. The idea of middleware is good. I'm not sure,
however, if the views.py code generates an exception, that it can be
caught by the middleware? I guess the question is how to catch
exceptions. The views.py
On Feb 11, 10:27 pm, Margie Roginski wrote:
> I have a question about debugging django server side code in the case
> where the request is an ajax request.
>From the server-side POV, a request is a request is a request. Truth
is : there's no such thing as an "ajax
On Thu, Feb 11, 2010 at 4:31 PM, Javier Guerra wrote:
> unfortunately, it doesn't render HTML responses...
i'm glad to report i was wrong! it _does_ render content as HTML on a new tab.
--
Javier
--
You received this message because you are subscribed to the Google
On Thu, Feb 11, 2010 at 4:27 PM, Margie Roginski
wrote:
> In the case of an ajax request, what happens to the error
> from the server code and is there any way to see it?
i use firebug. it lets you see every http interaction. with contents and all.
unfortunately, it
I have a question about debugging django server side code in the case
where the request is an ajax request. For example I have an
autocomplete widget. It makes a request to a particular url that
takes me to one of my views.py functions, get_users(request). If I
have some sort of error in that
7 matches
Mail list logo