Hi,
SmileyChris schrieb:
> But whatever you use, it should be made easy to put this in all your
> template contexts without having to jump through the hoop of creating
> your own context_processor.
I'm -0 on this, I don't think it's necessary to replace such a tiny bit
of programming with just another setting (there are so many settings
even without new ones!)
'context processor' sounds more difficult than it is. That's how it's
actually done:
from django.conf import settings
def processor(request):
return {'MEDIA_URL': settings.MEDIA_URL}
... and then add it to TEMPLATE_CONTEXT_PROCESSORS.
Since you're probably going to need a context processor somewhere in
your code anyway, this is not even something you have to learn extra.
Just my 2c,
Michael
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
