Hi André, Thanks for the feedback.
Here is the relevant code: registration_form view: http://dpaste.com/564165/ my views.py file directly from the django_registration app code: http://dpaste.com/564166/ Here is my form class: http://dpaste.com/564167/ - Harshil On Thu, Jul 7, 2011 at 3:52 AM, Andre Terra <andrete...@gmail.com> wrote: > Start by pasting relevant code. Views, forms and possibly the backend > logic. Use dpaste.com > > And quit bumping or you'll never get an answer, not from most of us. > > Regards, > André Terra > > On 7/6/11, CareerDhaba tech <t...@careerdhaba.com> wrote: > > Bumping once more. Can anyone shine some light on this issue? Would be > > extremely helpful. > > > > > > On Wed, Jul 6, 2011 at 6:24 PM, CareerDhaba tech > > <t...@careerdhaba.com>wrote: > > > >> Bump - anyone has any insight into this? > >> > >> I am happy to post my code, just not sure where I am going wrong. > >> > >> On Wed, Jul 6, 2011 at 2:35 PM, CareerDhaba tech > >> <t...@careerdhaba.com>wrote: > >> > >>> Hey folks, > >>> > >>> Django newbie here and I need some help. I am using django_registration > >>> v0.8 and using the docs here: > >>> http://readthedocs.org/docs/django-registration/en/latest/index.html > >>> > >>> I have successfully installed the app, and I am using the default > backend > >>> for my registration purposes. > >>> > >>> I have tested this and I can get the form to show up properly at > >>> '/accounts/register' > >>> > >>> However, one problem is that if I try and break the form input > (different > >>> password1 and password2 or improper username), no validation errors are > >>> being invoked. > >>> > >>> The issue also, is that the username, email, and password data is not > >>> being stored in auth_user, and the activation email isn't being sent. > >>> > >>> From the default backend doc, "During registration, a new instance of > >>> django.contrib.auth.models.User is created to represent the new > account, > >>> with the is_active field set to False. An email is then sent to the > email > >>> address of the account, containing a link the user must click to > activate > >>> the account; at that point the is_active field is set to True, and the > >>> user may log in normally." > >>> > >>> I believe this new instance of django.contrib.auth.models.User is not > >>> being created. > >>> > >>> I have also included the necessary email settings: > >>> EMAIL_USE_TLS = True > >>> EMAIL_HOST = "smtp.gmail.com" > >>> EMAIL_HOST_USER = "Email" > >>> EMAIL_HOST_PASSWORD = "Password" > >>> EMAIL_PORT = 587 > >>> > >>> Any help on getting this straight? I am pretty sure I am missing > >>> something > >>> simple, but been trying to figure it out without any progress. Any help > >>> is > >>> greatly appreciated. > >>> > >>> Thanks, > >>> Harshil > >>> > >>> > >> > > > > -- > > 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. > > > > > > -- > Sent from my mobile device > > -- > 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. > > -- 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.
