Fixed #22874: Document that AUTH_USER_MODEL must be in first migration
This commit is contained in:
parent
9f4852f649
commit
08221d1b5c
|
@ -2377,7 +2377,9 @@ The model to use to represent a User. See :ref:`auth-custom-user`.
|
|||
.. warning::
|
||||
You cannot change the AUTH_USER_MODEL setting during the lifetime of
|
||||
a project (i.e. once you have made and migrated models that depend on it)
|
||||
without serious effort. It is intended to be set at the project start.
|
||||
without serious effort. It is intended to be set at the project start,
|
||||
and the model it refers to must be available in the first migration of
|
||||
the app that it lives in.
|
||||
See :ref:`auth-custom-user` for more details.
|
||||
|
||||
.. setting:: LOGIN_REDIRECT_URL
|
||||
|
|
|
@ -392,6 +392,14 @@ use as your User model.
|
|||
fix your schema, port your data from the old user table, and possibly
|
||||
manually reapply some migrations.
|
||||
|
||||
.. warning::
|
||||
|
||||
Due to limitations of Django's dynamic dependency feature for swappable
|
||||
models, you must ensure that the model referenced by :setting:`AUTH_USER_MODEL`
|
||||
is created in the first migration of its app (usually called ``0001_initial``);
|
||||
otherwise, you will have dependency issues.
|
||||
|
||||
|
||||
Referencing the User model
|
||||
--------------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue