Or you can set up a custom template tag that returns settings values
if you only want the settings on particular pages, and don't want to
add boilerplate to each view, or have the overhead of a context
processor.
On Jan 18, 12:25 pm, phoebebright <phoebebri...@spamcop.net> wrote:
> Thanks - learning more every day!
>
> On Jan 18, 11:37 am, Malcolm Tredinnick <malc...@pointy-stick.com>
> wrote:
>
> > On Sun, 2009-01-18 at 03:26 -0800, phoebebright wrote:
> > > What is best practise if you want to use a variable defined in
> > > settings.py in a template?
> > > Pass it in via the view or call it directly in the template?
>
> > Since you can't access it directly in a template, that leaves only the
> > former option ("best practice" is not to attempt the impossible). Pass
> > it in. If you find yourself needing a particular setting regularly, you
> > could set up a context processor to populate context with the value(s)
> > you require, just like the media context processor does
> > (http://docs.djangoproject.com/en/dev/ref/templates/api/#django-core-c...)
>
> > Regards,
> > Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
