This seems to be part of it. I'm not sure if there is a sort_by fix in
there or not. It would be nice to be able to pass some of these fields
to the add user form. It would look much more uniform.

On Oct 31, 6:00 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> This just seems like a generalization of 
> this:http://code.djangoproject.com/ticket/3400
>
> On Oct 31, 7:28 pm, Cornbread <[EMAIL PROTECTED]> wrote:
>
> > I've ran into an issue I think that many will run into.
>
> > In our project we have a profile for each user and we have integrated
> > that inline with the user settings page. We have also added items from
> > the profile (address, city, state, zip, is_boss, etc) into the auth
> > users view.
>
> > The issue comes up when we want to filter through those users by our
> > user profile items.
>
> > I'm not extremely familar to the inner workings to django. I was
> > thinking that it would be nice in the admin when registering the
> > Profile maybe in Meta: show_user_profile. then user_profile_fields =
> > ('address', 'city', 'state', 'zip', etc).
>
> > Reported here:http://code.djangoproject.com/ticket/9463
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to