diff options
| author | Thomas Güttler <hv@tbz-pariv.de> | 2015-04-01 13:16:42 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-04-06 19:50:27 -0400 |
| commit | 5f8016cdfec0db5e03aa54bee7b2667fac140e2e (patch) | |
| tree | 52622fc8d8c88fca6e69caac2243a7cbfe15516b | |
| parent | 69f00f00915f0f96f0e72268796edc2ebc840c5e (diff) | |
[1.7.x] Added admonition about reusable apps and AUTH_USER_PROFILE.
Backport of 566c9362363f4b65cc64a35f907c2d6c39d0289e from master
| -rw-r--r-- | docs/topics/auth/customizing.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 2c54cc48af..e5b8a1839e 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -401,6 +401,14 @@ use as your User model. have a ForeignKey to each other and seeing how ``makemigrations`` resolves that circular dependency if you want to see how it's usually done) +.. admonition:: Reusable apps and ``AUTH_USER_MODEL`` + + Reusable apps shouldn't implement a custom user model. A project may use + many apps, and two reusable apps that implemented a custom user model + couldn't be used together. If you need to store per user information in your + app, use a :class:`~django.db.models.ForeignKey` or + :class:`~django.db.models.OneToOneField` to ``settings.AUTH_USER_MODEL`` + as described below. Referencing the User model -------------------------- |