That's it. That's exactly it, and I remember doing it, now that you put it that way. All right, now that I know what's going on, maybe I can figure out where the error's coming from. Thank you. I like this explanation way more than the possiblility that I was going mad.
On Jan 10, 9:47 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Jan 10, 2008 9:14 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Unless I've gone utterly mad, it IS django-registration. I remember > > installing django-registration, and most all of the code looks just > > like django-registration, albeit an older version. Not that any of > > that explains the error, or where line 35 or 36 came from (they differ > > from the current django-registration code). I don't remember putting > > them in. I DO remember changing the import paths. > > And yet you must have added those lines (presumably to set up the > automatic login on activation, which django-registration doesn't > support and never has); the problem is that you're not checking > whether the activation actually did anything -- 'account' can and will > be the boolean False if the activation failed. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
