Hello, there.
I am very much interested in this middleware stuff.
I have now a Python data processing script, which normally runs 2 to 3
minutes. I was trying to use feedback.py to call this external script
as a subprocess, firing it off to run, monitoring its progress, and
return an innerHTML
Oh my god the stupidity.
The error was in my 500.html template. NOTHING to do with my
middleware.
Sigh.
On Nov 20, 1:54 pm, jwpeddle <[EMAIL PROTECTED]> wrote:
> I've got a custom middleware class (nearly identical in function to
> the flat page fallback middleware). When I have DEBUG = True, i
Eliminated any possible issues in my urls conf. Even removing
everything from it doesn't change the situation.
On Nov 20, 1:54 pm, jwpeddle <[EMAIL PROTECTED]> wrote:
> I've got a custom middleware class (nearly identical in function to
> the flat page fallback middleware). When I have DEBUG = Tr
Ok, I've tried to dumb things down, and it turns out the built-in
flatpage fallback middleware ALSO doesn't have it's process_response
called. I can only assume a response is sent before the middleware is
reached, but I've got a pretty standard setup:
MIDDLEWARE_CLASSES = (
'django.middleware
I've got a custom middleware class (nearly identical in function to
the flat page fallback middleware). When I have DEBUG = True, it works
as expected. When I have DEBUG = False, I get errors stemming from
variables set by the middleware not existing for the templates. After
investigating, the onl
5 matches
Mail list logo
