Clarify that handler404 and handler500 only applies to project

[Martin Vilcans <martin@…>]

The documentation states that you can define handler404 and handler500 in your URLconf, but it doesn't say that this only works in the project-level URLconf, not inside an app.

I think it should be mentioned in these sections:

​http://docs.djangoproject.com/en/dev/topics/http/urls/#handler404

​http://docs.djangoproject.com/en/dev/intro/tutorial03/#write-a-404-page-not-found-view

There are several questions about this at Stack Overflow (for example ​http://stackoverflow.com/questions/3309076/is-it-possible-to-include-a-custom-404-view-for-a-django-app-without-changing-any), so if the documentation could just say that it's impossible, it would save time for a lot of people.

[Aymeric Augustin]

Where is the patch? Resetting flags.

[Martin Vilcans <martin@…>]

Documentation patch

[Julien Phalip]

See also #16214.

[Julien Phalip]

This was addressed in [16449].

[anonymous]

I disagree. [16449] does not address this problem. The documentation still doesn't say anything about that the handlers only work in the project-level URLconf.

[Julien Phalip]

Well, it now says that the handlers have to be declared in the "root URLconf". More clarification can always be added. In that case, the same type of clarification should be made for handler500. Please also generate your patch from the root of the source tree. Thanks!

[James Bennett]

In [16804]:

Fixed #16079: Clarified (for real this time) how handler404 and handler500 work, and that they only work in a root URLconf.

[James Bennett]

In [16805]:

[1.3.X] Fixed #16079: Clarified (for real this time) how handler404 and handler500 work, and that they only work in a root URLconf. Backport of [16804] from trunk.