Ricardo, I don't know that it is a usual task for Satchmo users, but I guess it could be. At the least, it could be a pretty common practice among people who are using django-registration.
I would advise against your current solution because you've modified Satchmo code & may risk a less smooth upgrade path. The proper way to do this in my opinion, as with anything else in a Django project, would be to make your own extension part of a separate app that is included in your Django apps. I'd recommend your own forms.py & views.py code that did what you wanted it to do and pass things off to the appropriate Satchmo views where necessary. So, in your forms.py, you would import the Satchmo form & extend it. In your views.py, you would do whatever extra work you want to do with your extended form, calling out to the satchmo view where needed and likely returning that view's result after finishing your extra processing. In your urls.py, you would ensure that the url for registration goes to your custom view. Finally, in the template, you would modify accordingly to include your extra field(s). Bob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
