diff options
author | Tim Graham <timograham@gmail.com> | 2013-06-30 14:48:15 -0400 |
---|---|---|
committer | Tim Graham <timograham@gmail.com> | 2013-06-30 14:56:10 -0400 |
commit | 3493f18d7850236dcb6292ebb1b949d6aeed7a9c (patch) | |
tree | 82dae7fefa4abf85a478eb193e3af9d1f60feef5 /docs/intro | |
parent | 02976a46c926880e78eb64424a9c8aa28d8be48a (diff) | |
download | django-3493f18d7850236dcb6292ebb1b949d6aeed7a9c.tar.gz |
[1.6.x] Fixed #20667 - Removed discussion of DEBUG from tutorial.
Backport of 0d642aac86 from master.
Diffstat (limited to 'docs/intro')
-rw-r--r-- | docs/intro/tutorial03.txt | 45 | ||||
-rw-r--r-- | docs/intro/whatsnext.txt | 5 |
2 files changed, 5 insertions, 45 deletions
diff --git a/docs/intro/tutorial03.txt b/docs/intro/tutorial03.txt index 91409848cf..777b8ef23b 100644 --- a/docs/intro/tutorial03.txt +++ b/docs/intro/tutorial03.txt @@ -454,51 +454,6 @@ just as :func:`~django.shortcuts.get_object_or_404` -- except using :meth:`~django.db.models.query.QuerySet.get`. It raises :exc:`~django.http.Http404` if the list is empty. -Write a 404 (page not found) view -================================= - -When you raise :exc:`~django.http.Http404` from within a view, Django -will load a special view devoted to handling 404 errors. It finds it -by looking for the variable ``handler404`` in your root URLconf (and -only in your root URLconf; setting ``handler404`` anywhere else will -have no effect), which is a string in Python dotted syntax -- the same -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. If you don't set -``handler404``, the built-in view :func:`django.views.defaults.page_not_found` -is used by default. Optionally, you can create a ``404.html`` template -in the root of your template directory. The default 404 view will then use that -template for all 404 errors when :setting:`DEBUG` is set to ``False`` (in your -settings module). If you do create the template, add at least some dummy -content like "Page not found". - -.. warning:: - - If :setting:`DEBUG` is set to ``False``, all responses will be - "Bad Request (400)" unless you specify the proper :setting:`ALLOWED_HOSTS` - as well (something like ``['localhost', '127.0.0.1']`` for - local development). - -A couple 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. - -* The 404 view is also called if Django doesn't find a match after checking - every regular expression in the URLconf. - -Write a 500 (server error) view -=============================== - -Similarly, your root URLconf may define a ``handler500``, which points -to a view to call in case of server errors. Server errors happen when -you have runtime errors in view code. - -Likewise, you should create a ``500.html`` template at the root of your -template directory and add some content like "Something went wrong". - Use the template system ======================= diff --git a/docs/intro/whatsnext.txt b/docs/intro/whatsnext.txt index a677bc9efd..638d219afe 100644 --- a/docs/intro/whatsnext.txt +++ b/docs/intro/whatsnext.txt @@ -66,6 +66,11 @@ different needs: where you'll turn to find the details of a particular function or whathaveyou. +* If you are interested in deploying a project for public use, our docs have + :doc:`several guides</howto/deployment/index>` for various deployment + setups as well as a :doc:`deployment checklist</howto/deployment/checklist>` + for some things you'll need to think about. + * Finally, there's some "specialized" documentation not usually relevant to most developers. This includes the :doc:`release notes </releases/index>` and :doc:`internals documentation </internals/index>` for those who want to add |