Revision history [back]
Try to use the default values.
This is a common problem - how to allow different apps to have their custom user profiles. Django did it one way until version 1.4, now switched to another approach in 1.5.
In askbot we just added fields to auth_user.
IMO - if you are integrating a number of applications into one project, then it's better to have one table for the user profile and maintain it accordingly, which requires some custom database maintenance, otherwise there may be several fields for the same thing like "website", "homepage_url" etc., depending on the app, and then you'd need to synchronize those values.
Maybe something can be improved in askbot code to make maintenance of the user profile table easier.
Try to use the default values.
This is a common problem - how to allow different apps to have their custom user profiles. Django did it one way until version 1.4, now switched to another approach in 1.5.approach.
In askbot we just added fields to auth_user.
IMO - if you are integrating a number of applications into one project, then it's better to have one table for the user profile and maintain it accordingly, which requires some custom database maintenance, otherwise there may be several fields for the same thing like "website", "homepage_url" etc., depending on the app, and then you'd need to synchronize those values.
Maybe something can be improved in askbot code to make maintenance of the user profile table easier.