diff options
| author | tschilling | 2014-07-16 22:37:07 -0400 | 
|---|---|---|
| committer | Aymeric Augustin | 2014-08-02 10:22:43 +0200 | 
| commit | e009bb394820c6753e6f6a36e9eb88fb61606248 (patch) | |
| tree | dfca111cc754efb2743db4ae697bd5830b57cf71 /docs/tips.rst | |
| parent | f6cae03e901d76331da73752f592dd7e1d5f1931 (diff) | |
| download | django-debug-toolbar-e009bb394820c6753e6f6a36e9eb88fb61606248.tar.bz2 | |
Added documentation around ProfilingPanel and problems with the middlware.
Closes #497
Diffstat (limited to 'docs/tips.rst')
| -rw-r--r-- | docs/tips.rst | 11 | 
1 files changed, 11 insertions, 0 deletions
| diff --git a/docs/tips.rst b/docs/tips.rst index b65c3d6..d2d88dd 100644 --- a/docs/tips.rst +++ b/docs/tips.rst @@ -13,6 +13,17 @@ requests and return responses. Putting the debug toolbar middleware *after*  the Flatpage middleware, for example, means the toolbar will not show up on  flatpages. +Middleware isn't working correctly +---------------------------------- + +Using the Debug Toolbar in its default configuration and with the profiling +panel will cause middlewares after +``debug_toolbar.middleware.DebugToolbarMiddleware`` to not execute their +``process_view`` functions. This can be resolved by disabling the profiling +panel or moving the ``DebugToolbarMiddleware`` to the end of +``MIDDLEWARE_CLASSES``. Read more about it at +:ref:`ProfilingPanel <profiling-panel>` +  Using the toolbar offline  ------------------------- | 
