On 6/6/06, Steven Armstrong <[EMAIL PROTECTED]> wrote:
> Wouldn't that be a use case for djangos built in (but hardly documented)
> AUTH_PROFILE_MODULE setting?
This was just written up over here:
http://www.b-list.org/weblog/2006/06/06/django-tips-extending-user-model
:)
On 06/06/06 17:11, Todd O'Bryan wrote:
> On Jun 6, 2006, at 11:03 AM, Adrian Holovaty wrote:
>
>>
>> On 6/6/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>>> Here's the problem: How do I get to those in a template? I know
>>> there's only one UserInfo object per User object, and ideally I'd
>>>
On 6/6/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> Why is it that you can't find stuff until after you send an email
> asking about it?
>
> I actually implemented a context processor, added a
> TEMPLATE_CONTEXT_PROCESSORS to my settings.py and then noticed the
> line I had missed about list
I've extended User by providing extra fields (a middle name,
preferred nickname, etc.) in a UserInfo model with a User foreign
key. I've also written methods for UserInfo for things like formalName
() and informalName().
Here's the problem: How do I get to those in a template? I know
4 matches
Mail list logo
