> It isn't at all clear to me from what you have posted what difficulty you > are having in using your own auth profile module. I do not understand why > the presence of the django-registration table would be causing any trouble. > At any rate, since you are already using django-registration, you may want > to consider also using django-profiles, there is a link to that project on > the page I linked to above.
I've loaded django-profiles and can't manage to get it to work after many hours of attempts, and after much thought of the small scale of our user/ profile database and the limited scope of our website would prefer to simply the process by bringing more control of the profiles into our own coding. So my idea at this point was if the AUTH_PROFILE_MODULE declares a constant object that has built in functions for it, then I just wanted to build my own profile, views and model and take it from there. I'm not building a large site by any stretch of the imagination, in fact most of the activation, profile maintenance and so on we do manually, including account activation and can do direct on the data via phpAdmin, via data importation or some other interface. With registration working, all we need from Django is a simple hook to initiate the AUTH_PROFILE_MODULE via the related field/row of user during registration, so we can then build our own models, forms and views for our user profiles. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
