Author: carljm
Date: 2012-01-12 14:17:22 -0800 (Thu, 12 Jan 2012)
New Revision: 17370
Modified:
django/branches/releases/1.3.X/docs/intro/tutorial03.txt
Log:
Fixed #17538 -- corrected the section in tutorial 3 about the handler404
default. Thanks matt at brozowski dot com for the report.
Backport of r17369 from trunk.
Modified: django/branches/releases/1.3.X/docs/intro/tutorial03.txt
===================================================================
--- django/branches/releases/1.3.X/docs/intro/tutorial03.txt 2012-01-12
22:03:34 UTC (rev 17369)
+++ django/branches/releases/1.3.X/docs/intro/tutorial03.txt 2012-01-12
22:17:22 UTC (rev 17370)
@@ -365,17 +365,16 @@
format the normal URLconf callbacks use. A 404 view itself has nothing
special: It's just a normal view.
-You normally won't have to bother with writing 404 views. By default, URLconfs
-have the following line up top::
+You normally won't have to bother with writing 404 views. If you don't set
+``handler404``, the built-in view :func:`django.views.defaults.page_not_found`
+is used by default. In this case, you still have one obligation: To create a
+``404.html`` template in the root of your template directory. The default 404
+view will use that template for all 404 errors. If :setting:`DEBUG` is set to
+``False`` (in your settings module) and if you didn't create a ``404.html``
+file, an ``Http500`` is raised instead. So remember to create a ``404.html``.
- from django.conf.urls.defaults import *
+A couple more things to note about 404 views:
-That takes care of setting ``handler404`` in the current module. As you can see
-in ``django/conf/urls/defaults.py``, ``handler404`` is set to
-:func:`django.views.defaults.page_not_found` by default.
-
-Four more things to note about 404 views:
-
* If :setting:`DEBUG` is set to ``True`` (in your settings module) then
your
404 view will never be used (and thus the ``404.html`` template will
never
be rendered) because the traceback will be displayed instead.
@@ -383,15 +382,6 @@
* The 404 view is also called if Django doesn't find a match after checking
every regular expression in the URLconf.
- * If you don't define your own 404 view -- and simply use the default,
which
- is recommended -- you still have one obligation: To create a ``404.html``
- template in the root of your template directory. The default 404 view
will
- use that template for all 404 errors.
-
- * If :setting:`DEBUG` is set to ``False`` (in your settings module) and if
- you didn't create a ``404.html`` file, an ``Http500`` is raised instead.
- So remember to create a ``404.html``.
-
Write a 500 (server error) view
===============================
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
