[Fixed]-Custom user model in django

by

9👍

✅

I did this in one of my project. I was surprised to see that you extended User because the doc says something else 🙂 You can extend Django User model, but if you only want to add new fields (not change its behavior), you should use a OneToOneField.

If you wish to store information related to User, you can use a one-to-one
relationship to a model containing the fields for additional information.

So, as you can see in the link, your code should look like:

from django.contrib.auth.models import User

class MyUser(models.Model):
    user = models.OneToOneField(User)

    # Or a ForeingKey to the College table?
    college = models.CharField(max_length=40)

    other_data = ...
👤Nil

3👍

It is a good practice to keep your code generic by using get_user_model() (to get the User model that is active in your project. Defined in django.contrib.auth) and AUTH_USER_MODEL (to reference the User model) rather than directly referring to the User model.

from django.conf import settings

class MyUser(models.Model):
    user = models.OneToOneField(settings.AUTH_USER_MODEL)

    # Or a ForeingKey to the College table?
    college = models.CharField(max_length=40)

    other_data = ...
👤harishkb

1👍

try removing this line in models.py:

admin.site.register(Users, UserAdmin)

I figured out your error, You have the INSTALLED_APPS in the wrong order they should be the next: 

INSTALLED_APPS = (
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    #'django.contrib.sites',
    #'django.contrib.messages',
    'django.contrib.staticfiles',
    # Uncomment the next line to enable the admin:
    'django.contrib.admin',
    # Uncomment the next line to enable admin documentation:
    # 'django.contrib.admindocs',
    'login',
    'forms',
)

AUTH_USER_MODEL = "login.User"

Why?

looking at the source code admin uses the User model so maybe you can think:

But my user model is into login app and this one is before admin app, therefore login is installed before admin, why it does not work?. That’s because django.contrib.auth is swappable (the model can be replaced for another one in your case has been swappable by login.User) so as you created a new User Model therefore django has to change its user Model to the new one and then you have to install the rest.

How must be at the moment of run syncdb:


1.- django.contrib.auth is installed, then this see if has been swapped, if yes it adds the new field or override completely the User Model (in your case only you add a field).

2.- admin, contentypes.... your apps, are installed and all works.

How you had it:

1.- login is installed (where the new User Model was, you put the AUTH_USER_MODEL in settings)

2.- Then forms.

3.- Then django tries to install the admin app but it can't because auth_user table hasn't been added that's because django.contrib.auth was after admin, therefore there is no User Model, this one isnt's swapped and this throws the error  **admin.logentry: 'user' has a relation with model login.users, which has either 
not been installed or is abstract.**

So accordingly first you always have to install the django.contrib.auth app and then all the apps that depends from.

👤Victor Castillo Torres

Leave a comment