ProgrammingError: relation "auth_user" does not exist about cookiecutter-django HOT 8 CLOSED

@raushanraj did you run python manage.py migrate (for Django 1.7) or python manage.py syncdb and then python manage.py migrate (for Django 1.6)?

from cookiecutter-django.

@benregn yes,I run python manage.py migrate.nothing to migrate now.

from cookiecutter-django.

I follow step by step from documentation.Every thing is working fine.User Login,User Regestration.But When Admin add user it throws error mentioned aboved.I tried two times the documentation but is not working

from cookiecutter-django.

https://code.djangoproject.com/ticket/19353 please see this issue.some problem in users admin.py .

from cookiecutter-django.

I ran into the same trouble. With the help of this blog post, I managed to fix it. My admin.py looks now like this:

# -*- coding: utf-8 -*-
from django.contrib import admin
from django import forms
from django.contrib.auth.forms import UserCreationForm, UserChangeForm
from django.contrib.auth.admin import UserAdmin as AuthUserAdmin
from .models import User


class MyUserCreationForm(UserCreationForm):
    def clean_username(self):
        username = self.cleaned_data["username"]
        try:
            User._default_manager.get(username=username)
        except User.DoesNotExist:
            return username
        raise forms.ValidationError(self.error_messages['duplicate_username'])

    class Meta(UserCreationForm.Meta):
        model = User


class UserAdmin(AuthUserAdmin):
    add_form = MyUserCreationForm
    update_form_class = UserChangeForm


admin.site.register(User, UserAdmin)

from cookiecutter-django.

thanks!

from cookiecutter-django.

I had the same issue with a Django project.
I created the superuser through manage.py createsuperuser which worked out fine, but when I tried to log in via the web interface, I got the described error.
The reason was that I was using production settings when I ran the server, but development settings when using manage.py. So the superuser was created to the development Sqlite database, while the server tried to access the production Postgres database where no migrations had been performed yet.

In case anybody runs into the same issue:

1. use manage.py the_command --settings the.real.settings
2. or set the DJANGO_SETTINGS_MODULE to hold the right settings.

from cookiecutter-django.

I encountered the same errors as described in this post, but in my case, the issue was that I was using from django.contrib.auth.models import User instead of from django.contrib.auth import get_user_model. After some investigation, I realized that the cause of the error was related to my custom User model, which I had created by subclassing AbstractUser. Once I made the change to use get_user_model(), the errors were resolved.

from cookiecutter-django.