On Jan 4, 9:43 pm, Peter Rowell <[EMAIL PROTECTED]> wrote:
> > Well, if I can't get this working I suppose I can just stuff the
> > settings.MEDIA_URL variable into each template render by placing it
> > into the render dictionary myself each time.
>
> Nah, don't do that.
>
> I think your problem is that you are running 0.96 instead of trunk.
> I am on trunk/6688 and there is, in fact, a media processor and
> I'm even using it in a production site.
>
> I noticed you started off by saying:
>
> >Hi, I read that if I install a context processor, MEDIA_URL will
> >automatically be available to my templates.
>
> So the question is: where did you read that? Was it the online
> tutorial? Did it say 0.96 or .... SVN trunk?
>
> IMWTK! (Inquiring Minds Want To Know!)
OK, I got that bit from this website (after looking at many trying to
figure out how to set it up correctly):
http://www.jesselegg.com/archives/2007/11/08/serving-media-django/
where it says "If you use the RequestContext context processor in your
views, you get an automatic MEDIA_URL variable."...so I guess that's a
lesson not to take things you read on random web sites too literally.
I didn't think the media context processor was that new that it
wouldn't be in 0.96. Anyway, I will try the trunk version if I can
figure out how to get it installed. Thanks!
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
