I don't believe Satchmo defines the Contact model as AUTH_PROFILE_MODULE. I could be wrong, but can't recall seeing it defined there.
Note, it is AUTH_PROFILE_MODULE that you add to your settings.py, not AUTH_PROFILE_MODEL. Just give it a shot on a local dev machine, fire up your Satchmo instance, and you should see if any odd behavior exists. Moreover, to be certain right now, you could use the python manage.py shell command on your project, import the Django User model, and try the following: >> u = User.objects.get(pk=1) >> p = u.get_profile() If Contact is setup as the AUTH_PROFILE_MODULE by Satchmo, `p` in the code above should be a Contact instance. If it is not, you won't have any trouble defining a custom profile module. On Mon, Oct 26, 2009 at 11:08 AM, captainmish <[email protected]> wrote: > > Hello > > I am busy implementing profiles for users with django-profiles, and > need to add AUTH_PROFILE_MODEL = myapp.MyUser to settings - will this > break Contacts? I cant seem find that this will break (I can create a > new user/contact on checkout), but just in case anyone has tried and > found something I didnt! > > I would prefer to keep this as a separate thing instead of extending > satchmo's contact if possible, so there will be 2 places where > extended user info is kept. > > Thanks in advance for any tips :) > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
