UPDATE: OK, I installed the trunk version and it worked right away, so
I guess 0.96 does not support the media context processor.
Thanks again for the help.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django use
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 probl
On Jan 4, 4:19 pm, Peter Rowell <[EMAIL PROTECTED]> wrote:
> > (3) Imported the RequestContext object in my views.py file:
>
> > from django.template import Template, Context, RequestContext
>
> I know this is a silly question, but did you *use* RequestContext, or
> just import it?
>
> E.g.
> r
Hi, I read that if I install a context processor, MEDIA_URL will
automatically be available to my templates. However, it's not. Here's
what I've done:
(1) Added the image files to my ftp server here:
myserver.com/sites/myapp/images/
(2) Added this to settings.py (TEMPLATE_CONTEXT_PROCESSORS
Those solutions make sense, that was just what I was looking for,
thanks! That should be in the docs somewhere...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send ema
Hi, I think I understand modeling, and user/session authentication.
But, what I don't understand is how to use these together to tie some
object instances (stored in the database) to a specific user. For
example, I want each authenticated user of the application to have a
single instance of my mod
Aren't you duplicating information with the newforms, violating the
DRY principle? What I mean is, aren't we separately creating most or
all of the same fields for a form as for the model whose data will be
bound to the form? Why can't a form be instantiated automatically when
passed a model (mayb
7 matches
Mail list logo
