>> As far as I can tell the way to do this is to modify *every*
>> *view* *in* *my* *project* to pass either the user or a
>> RequestContext.
>
> The link I gave you is to not do that, but add a processor that will add the
> user to the context.
I think you might be missing the bit that says:
"F
> On the linked thread have you checked:
> http://www.b-list.org/weblog/2006/06/14/django-tips-template-context-processors?
> You can use a context processor to make {{ user }} available on all
> templates.
Unless I'm missing something, that link says the same as what I'm
saying, namely that you
Ok, here's an attempt to elicit some kind of response, having failed
last time I asked this question:
http://groups.google.com/group/django-developers/browse_frm/thread/5b5b9070f8ca36d7
If I submit a reusable app, should its views pass a RequestContext to
the templates or not? If they don't, the
SmileyChris wrote:
> According to the docs:
>
> "The semantics of one-to-one relationships will be changing soon, so we
> don't recommend you use them. If that doesn't scare you away, keep
> reading."
>
> It scares me a bit. Can anyone expand on the "changing semantics" or
> point me to an existin
Nope, still broken here.
--~--~-~--~~~---~--~~
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
5 matches
Mail list logo
