SmileyChris wrote:
> But Ivan, you need to access the STYLE_URL setting. Having access to
> settings via SafeSettings could be useful still, right?
Not much. Adding couple of needed settings in my own project's context
processor (which I already have anyway) is not a big deal. SafeSettings
then
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 functional
Ok, I agree that if we start putting individual settings it will lead
to a bit too much pollution.
But Ivan, you need to access the STYLE_URL setting. Having access to
settings via SafeSettings could be useful still, right?
--~--~-~--~~~---~--~~
You received this
SmileyChris wrote:
> 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?
No, I asked my two sites and they
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/SafeS
