summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJames Bennett <ubernostrum@gmail.com>2008-05-28 20:31:03 +0000
committerJames Bennett <ubernostrum@gmail.com>2008-05-28 20:31:03 +0000
commitbd73eaf952b65b17580498fee846e8fddace68db (patch)
treede7c8f5e42d155859a9cdb2fc428b6e6677ffe1c
parent4d79a9588a6fcd14509218ab73d0ffcdc74a4be2 (diff)
Big glaring warning in docs/flatpages.txt to remind people how response middleware works
git-svn-id: http://code.djangoproject.com/svn/django/trunk@7555 bcc190cf-cafb-0310-a4f2-bffc1f526a37
-rw-r--r--docs/flatpages.txt11
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/flatpages.txt b/docs/flatpages.txt
index b6fa8e035f..a538217642 100644
--- a/docs/flatpages.txt
+++ b/docs/flatpages.txt
@@ -66,6 +66,17 @@ resort.
For more on middleware, read the `middleware docs`_.
+.. admonition:: Ensure that your 404 template works
+
+ Note that the ``FlatpageFallbackMiddleware`` only steps in once
+ another view has successfully produced a 404 response. If another
+ view or middleware class attempts to produce a 404 but ends up
+ raising an exception instead (such as a ``TemplateDoesNotExist``
+ exception if your site does not have an appropriate template to
+ use for HTTP 404 responses), the response will become an HTTP 500
+ ("Internal Server Error") and the ``FlatpageFallbackMiddleware``
+ will not attempt to serve a flat page.
+
.. _SITE_ID: ../settings/#site-id
.. _RequestContext: ../templates_python/#subclassing-context-djangocontext
.. _middleware docs: ../middleware/