I'm one of those people who uses a custom template context processor to access settings in virtually all of my templates. Specifically, I use this code [1] to access SITE_URL and MEDIA_URL so that my templates can build absolute links within my sites.
However, I don't believe that this functionality needs to be Django proper. It would be nice, but you don't *need* this to make a Django project work. But if you do want to access settings. Seriously. Make your own library. Stick your custom template context processor in it. And import your library in all your projects. Simple. Bryan :) [1] http://www.verdjn.com/browser/verdjnlib/context_processors On 8/18/06, SmileyChris <[EMAIL PROTECTED]> wrote: > > Way back in ticket http://code.djangoproject.com/ticket/1278, Adrian > declared that a settings context processor was not going to happen. The > reason being that it could give template authors direct access to the > db password / secret key. > > Recently I coded up > http://code.djangoproject.com/wiki/SafeSettingsContextProcessor, which > uses the same get_safe_settings which the debug error page shows. > > Is this still too dangerous? As long as it's off by default, isn't it > safe enough? > > On a side note, most people just want access to media_url, so I > actually would be happy with just > http://code.djangoproject.com/ticket/2532. Every web site wanting to > use static CSS will need to access this variable somehow, won't they? > Otherwise it has to be hard coded and that's not very Djangoish... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
