Hi Karen,
I did that, but the message was never sent to me.
Anyway, when I create a new project with a single app, containing
nothing but a single view which raises a Http404, along with a
urlpattern which refers to that view – the 500 template is still
displayed when I request the URL.
This must be easily reproducible on any machine using the following
code:
# urls.py:
urlpatterns = patterns('myproject.myapp.views',
(r'^test/$', 'test'),
)
# views.py:
def test(request):
raise Http404
The same thing happens when I try any other URL: in debug mode, I get
the well-known
"Using the URLconf defined in djangoanke.urls, Django tried these URL
patterns, in this order:
^test/
The current URL, teste, didn't match any of these."
But with DEBUG = False, Django sends the 500.html template.
Clueless,
Jan
On 28 Okt., 20:09, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 28, 2008 at 2:58 PM, janedenone <[EMAIL PROTECTED]>wrote:
>
>
>
> > Hi,
>
> > it must be some kind of unhandled exception, but I fail to see where
> > it might occur. I now boiled down the app to a single URL pattern and
> > a single view:
>
> [snipped]
>
> If you configure ADMINS and EMAIL_HOST, etc. so that Django can successfully
> send email, then the traceback from the uncaught exception will be mailed to
> whatever email address you include in ADMINS. Much easier than guessing
> what might be happening.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
