Re: Best practise for using settings in templates

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 wrote: > Thanks -

Re: Best practise for using settings in templates

Thanks - learning more every day! On Jan 18, 11:37 am, Malcolm Tredinnick 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

Re: Best practise for using settings in templates

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 practise for using settings in templates

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? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users"