Hi I have just been using Django for the last 4 months, and the application I developed needed an extensive UserProfile module. It needed things such as
1. Ability to log in via both email and username 2. Ability to link multiple social accounts with the same user account (the social connections were primarily used for logging in, but they can be extended to store and use the social account information) 3. Ability to link multiple emails with the same account and having one email as the primary verified one These were some of the features that I needed. After a bit of looking around I resorted to using django-allauth<https://github.com/pennersr/django-allauth>for the registration part(also manages social connections) and made a custom UserProfile model. The result of this was that auth.user just reduced to a FK (I also didn't have much need of the permissions). Just to give a new user's perspective I would say, pluggable auth.user does not seem to be the correct way to go. A much better approach would be to BaseClass the auth.user and allow developers to subclass user model according to their needs. To maintain backward compatibility the existing fields need to be maintained. This does not solve the problem of smaller email field size, but then a lot of things would break. The problems of increasing email field length and maybe combining first and last name field to a single field can be solved incrementally. Regards Sachin -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/6mqH-9GnkqQJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
