From 19ac8b2fe156088eb005343b9f46dc47bcfc9689 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 25 Jul 2015 09:30:54 -0400 Subject: [PATCH] [1.8.x] Fixed #25166 -- Clarified how auth permissions are created. Thanks Baptiste Mispelon for report and review. Backport of 217f173be025d2cce6484c760ea6ec77436f26a1 from master --- docs/topics/auth/customizing.txt | 11 ++++++----- docs/topics/auth/default.txt | 3 ++- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 1d2daed333..d1c4cabe49 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -281,11 +281,12 @@ can or cannot do with Task instances, specific to your application:: ) The only thing this does is create those extra permissions when you run -:djadmin:`manage.py migrate `. Your code is in charge of checking the -value of these permissions when a user is trying to access the functionality -provided by the application (viewing tasks, changing the status of tasks, -closing tasks.) Continuing the above example, the following checks if a user may -view tasks:: +:djadmin:`manage.py migrate ` (the function that creates permissions +is connected to the :data:`~django.db.models.signals.post_migrate` signal). +Your code is in charge of checking the value of these permissions when a user +is trying to access the functionality provided by the application (viewing +tasks, changing the status of tasks, closing tasks.) Continuing the above +example, the following checks if a user may view tasks:: user.has_perm('app.view_task') diff --git a/docs/topics/auth/default.txt b/docs/topics/auth/default.txt index 51b4cf35db..02d68e4056 100644 --- a/docs/topics/auth/default.txt +++ b/docs/topics/auth/default.txt @@ -207,7 +207,8 @@ These permissions will be created when you run :djadmin:`manage.py migrate will be created for all previously-installed models, as well as for any new models being installed at that time. Afterward, it will create default permissions for new models each time you run :djadmin:`manage.py migrate -`. +` (the function that creates permissions is connected to the +:data:`~django.db.models.signals.post_migrate` signal). Assuming you have an application with an :attr:`~django.db.models.Options.app_label` ``foo`` and a model named ``Bar``,