Ok, I see what happens. So it basically runs through its own code until it gets to forms.save_contact where it imports the registration model and then proceeds to create the appropriate user. So why the apparent duplication? Django registration handles most if not all of the features I can see in the accounts module of Satchmo and this way just creates unnecessary complexity (and I imagine greater maintenance burden).
On Jan 13, 11:07 pm, Cromulent <[email protected]> wrote: > I've spent a fair bit of time going through the Satchmo source code > and can't get my head around where it makes use of the Django > Registration module. > > The accounts stuff seems to happen in satchmo_store.accounts but none > of that actually imports Django Registration anywhere as far as I can > see. I think I am missing something really simple here but it is > evading me at present. > > So how do I get my customisations I have made directly to Django > Registrations to start working. All I have done is change a couple of > functions (whilst keeping the API the same) and then replaced the > default one with my own one. But the changes have no effect, if this > is the case what is the point of having Django Registrations as a > requirement of Satchmo if it never actually uses it (as far as I can > tell)? > > I'd be extremely happy to hear that I have been doing something > increadibly stupid here as it is 11pm right now :). > > Thank you for any help. -- 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.
