Ok...nevermind. Jake is righttemplate context processors are my
friend. Thanks!
On Sep 12, 10:06 am, Ryan K <[EMAIL PROTECTED]> wrote:
> Ok...so how do I pass my 'site_context' dictionary (which is just a
> dict with URL prefixes in it for static media) to the default 404
> handler?
>
> On Se
Ok...so how do I pass my 'site_context' dictionary (which is just a
dict with URL prefixes in it for static media) to the default 404
handler?
On Sep 12, 4:24 am, Collin Grady <[EMAIL PROTECTED]> wrote:
> You don't need a custom 404 handler in order to use RequestContext -
> the default handler a
You don't need a custom 404 handler in order to use RequestContext -
the default handler already does.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to djang
from django import http
from django.template import RequestContext, loader
from urls import site_context
def display_404(request):
custom_dict = {'request_path': request.path}
custom_dict.update(site_context)
t = loader.get_template('404.html')
return http.HttpResponseNotFound(t.
hi ryan,
how about a context processor?
http://www.djangoproject.com/documentation/templates_python/#writing-your-own-context-processors
-jake
Ryan K wrote:
> Hi. All URLs in my templates are preceded by variables I added to the
> settings file so I could easily deploy my site on many differen
Hi. All URLs in my templates are preceded by variables I added to the
settings file so I could easily deploy my site on many different URLs,
this includes CSS file URLs. When the custom error 404 page comes up,
there is obviously no style because I can't pass the setting to it. Is
there a way to h
6 matches
Mail list logo
