From 8928823b135b9ce2c7b18f4da0d2602b113a247e Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 31 Mar 2016 13:41:06 -0400 Subject: [PATCH] Fixed #26436 -- Added a link to the settings filtering in the error reporting howto. Thanks mlissner for the suggestion. --- docs/howto/error-reporting.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/howto/error-reporting.txt b/docs/howto/error-reporting.txt index fc043375d4..9ae194d4e0 100644 --- a/docs/howto/error-reporting.txt +++ b/docs/howto/error-reporting.txt @@ -143,10 +143,12 @@ exception raised, each `traceback frame`_’s local variables, and the However, sometimes certain types of information may be too sensitive and thus may not be appropriate to be kept track of, for example a user's password or -credit card number. So Django offers a set of function decorators to help you -control which information should be filtered out of error reports in a -production environment (that is, where :setting:`DEBUG` is set to ``False``): -:func:`sensitive_variables` and :func:`sensitive_post_parameters`. +credit card number. So in addition to filtering out settings that appear to be +sensitive as described in the :setting:`DEBUG` documentation, Django offers a +set of function decorators to help you control which information should be +filtered out of error reports in a production environment (that is, where +:setting:`DEBUG` is set to ``False``): :func:`sensitive_variables` and +:func:`sensitive_post_parameters`. .. _`full traceback`: https://en.wikipedia.org/wiki/Stack_trace .. _`traceback frame`: https://en.wikipedia.org/wiki/Stack_frame