From ffa5a7550d95f7fd0d0add1e9599a797b2eb60f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=BCttler?= Date: Wed, 1 Apr 2015 13:16:42 +0200 Subject: [PATCH] [1.8.x] Added admonition about reusable apps and AUTH_USER_PROFILE. Backport of 566c9362363f4b65cc64a35f907c2d6c39d0289e from master --- docs/topics/auth/customizing.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 1a5e33f3ba..6a56d542d3 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -407,6 +407,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 --------------------------