Hello everyone, I need to discuss in context with the feature request https://bugs.launchpad.net/postorius/+bug/1432383. The point is to make the fields like irc handle, first-name, last-name etc. editable in the user profile.
User registration is currently done using *django-browserid *with the default *User Model. *There are no schema rules for these *extra *fields in the *auth_user *table of the underlying Postorius database due to the use of the default *User Model*. I am thinking of using a CustomBackend class overriding the BrowserIdBackend class for adding customisation *[1]*. Also, I think it would be required to have a *new *User model for these extra fields which can be used by django-browserid for the initial user registration. Initially, these *extra *fields can be set to *empty*. Later on, with the help of an update view users can be asked to update their profiles when they login. This would require the use of database migrations. Other option is to use to create an extra table for these fields and for it the default *User model *would be suffice. In this case, an extra form would do the job. I want to ask whether my approach is correct ? Or it would be more meaningful to take input for these fields during the first time when the user registers by using Persona ? ( I guess it would require some ugly tweaks ) Waiting for your opinion on it ! Thanks, Ankush Sharma IIT-BHU, Varanasi India *github.com/black-perl <http://github.com/black-perl>* [1] : http://django-browserid.readthedocs.org/en/latest/user/customization.html#automatic-user-creation _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
