These are the changes you'll have to make to django-registration, if you are using AUTH_USER_MODEL in django 1.5 and inheriting from AbstractUser:
https://bitbucket.org/prjts/django-registration/commits/ba31fc3053bfca7eb7a19d912882e50e295adc55 On Friday, 19 April 2013 11:52:55 UTC+3, Paul Walsh wrote: > > James Bennet says above that it is compatible, but the latest > django-registration code is not compatible with custom user models. > > RegistrationProfile, for example, still refers directly to User, whereas > the new custom user implementation in Django 1.5 require this to be changed > in order to work when AUTH_USER_MODEL is actually being used. > > See the docs here > https://docs.djangoproject.com/en/dev/topics/auth/customizing/#referencing-the-user-model > > Seeing as in Django, we can't override fields when we subclass models, we > cannot "subclass the provided stuff" in this case. Of course, we can > override forms and views. > > In a current django app I am working on, and indeed in every Django app I > have worked on, the I was happy with the default user model, and extended > it with a profile that included language settings, for example - I didn't > replace functionality. > > The Django 1.5 docs refer explicitly to my use case: > > > https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-django-s-default-user > > But, django-registration does not work with this use case. > > > > > On Wednesday, 17 April 2013 10:51:44 UTC+3, James Bennett wrote: >> >> Current hg tip is actually 1.5-compatible, in the sense that if you want >> to use your own User model, you just subclass the provided stuff and plug >> in your model, either importing directly or using the helper function in >> Django 1.5. >> >> django-registration does not do this itself because >> >> 1. Using Django 1.5's helpers requires either extra complication of the >> imports, or a break with Django 1.4 compatibility, and >> 2. If you're using a custom User model, you will by definition be wanting >> to subclass and override the default fields, validation logic, etc., since >> only a User model identical to django.contrib.auth.models.User works with >> the defaults. >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
