8👍
Your error is caused by the order you run the migrations. Since many apps depend on the user model existing, you must run the initial migrations for your custom user app before those other apps.
If you change the default user model in an existing project, it might be easier to discard all existing migrations (and the database) and rebuild from scratch. The order to apply migrations would be:
- The core
django.contrib
apps. - Your custom user app.
- Other custom apps and third party apps.
You can use django-admin showmigrations
to see which migrations exists and are planned.
25👍
You have to delete the migrations folder and then, you should do
python manage.py migrate --run-syncdb
python manage.py migrate --fake appname
- 'WSGIRequest' object has no attribute 'get'
- Django load local json file
- Django-rest-swagger: how to group endpoints?
- Django: prefetch related objects of a GenericForeignKey
0👍
FYI-
I had this problem, and to resolve it I had to comment out all references to views.py in my urls.py and url_tenants.py files. Then, I ran makemigrations and got the database tables to create, then run migrate_schemas, and later uncomment the url files. Hope this helps someone.