>
> Thank you for your help Andre
You're welcome!
> I've now worked out what the problem
> was. I was editing the wrong copy of the source code (it happens to
> everyone at some point!) so no wonder the changes were not
> happening...
Happens to me more often than I'd like to admit...
> In t
Thank you for your help Andre - I've now worked out what the problem
was. I was editing the wrong copy of the source code (it happens to
everyone at some point!) so no wonder the changes were not
happening... In the end I just created a completely new url path (i.e.
not 'accounts/register') and cal
My guess is that there's another module somewhere in your PYTHONPATH from
which django is importing these forms.
Also, don't edit registration.forms, subclass the form instead.
You can also try {{ form.as_p }} to make sure the problem isn't in the
template.
You can raise an exception somewhere i
OK I must have missed something fundamental. I installed v0.8 and
having started all over again, I only made one change - adding an
extra field to the basic RegistrationForm class in registration.forms
- this isn't showing up on my template either!
Looking over my code, I've found it's not just th
I think that's it! I'm using v0.7 and will upgrade now - thanks for
the heads up.
On Jul 8, 6:52 pm, CareerDhaba tech wrote:
> I believe you are using an older version of django_registration, since there
> is no reference to the backend in your code. The backend is an addition in
> the latest (0.
I believe you are using an older version of django_registration, since there
is no reference to the backend in your code. The backend is an addition in
the latest (0.8) version of django_registration.
Did you download the code from here?
http://readthedocs.org/docs/django-registration/en/latest/in
If I remember this correctly, there's a variable somewhere in
django-registration that defines the form to be used.
grep (or ack!) the source for RegistrationForm and see if you can find it
Cheers,
Andre
On 7/8/11, katstevens wrote:
> Thanks for your answer, but unfortunately that hasn't helped
Thanks for your answer, but unfortunately that hasn't helped - on
further investigation I think the problem is somewhere else, as the
original RegistrationForm class instance (in registration.forms)
doesn't seem to be being called correctly by registration.views (so no
wonder RegistrationFormTermsO
Hi Kat,
You have to tell the your registration view to use the
RegistrationFormTermsofService. First, import that class from forms and
change your form_call from None to to RegistrationFormTermsofService.
Hope this helps.
On Thu, Jul 7, 2011 at 5:34 PM, katstevens wrote:
> Hi - I'm new to Djan
9 matches
Mail list logo
