"correct" way to add name to the registration form

[nateworthy]

I'm excited to have found this package for its core purpose of using email address as Django username. I'm also interested in collecting the user's name during registration. Do you have any advice on how to alter the form, but still be able to incorporate future versions of django-registration-email?

[mbrochh]

I have updated the README for you: https://github.com/bitmazk/django-registration-email#how-to-use-a-custom-form

If you have further questions, just post them into this issue.

[nateworthy]

Thanks Martin! I've read through your instructions and they make sense. I also just remembered I intend to ask for zip code and political party, so I will add that in. I'm working on a politics-related app - I plan to map zip code to elected representatives. I expect political party will lead to using a related model like User Profile, which I think I understand how to include in the architecture you've so kindly laid out. On Mar 3, 2013 7:51 PM, "Martin Brochhaus" notifications@github.com wrote:

I have updated the README for you: https://github.com/bitmazk/django-registration-email#how-to-use-a-custom-form

If you have further questions, just post them into this issue.

— Reply to this email directly or view it on GitHubhttps://github.com/bitmazk/django-registration-email/issues/6#issuecomment-14362912 .

[mbrochh]

Sure the process will be exactly the same. Just add all the fields you need to your CustomForm and make sure you save the additional request.POST data in your signal handler.

[nateworthy]

notes for others:

• make sure you "import settings" in your urls.py for the getattr() call to succeed
• I think the instructions intend url(r'^accounts/register/$', rather than url(r'^register/$', so consider the url pattern you desire.

[mbrochh]

@nanthony you are right, it should be accountrs/register/, sorry for that. I updated the README.