Re: 500 displayed instead of 404

2008-10-31 Thread janedenone
On 29 Okt., 14:00, Thomas Guettler <[EMAIL PROTECTED]> wrote: > > Thanks to all who answered, now I'll go looking for the person who > > messed with the development machine. > > Everybody can make mistakes. The root of the problem is (or was) > that you don't see tracebacks if

Re: 500 displayed instead of 404

2008-10-29 Thread Thomas Guettler
> Thanks to all who answered, now I'll go looking for the person who > messed with the development machine. > Everybody can make mistakes. The root of the problem is (or was) that you don't see tracebacks if settings.DEBUG=False. I see them in the apache error log. I use mod_wsgi. Thomas

Re: 500 displayed instead of 404

2008-10-29 Thread janedenone
Hi all, I found the solution. Someone (not me!) changed the django.views.defaults.page_not_found(). The first line of the method definition read def page_not_found(request, template_name='404_default.html'): instead of def page_not_found(request, template_name='404.html'): Thanks to all who

Re: 500 displayed instead of 404

2008-10-28 Thread Karen Tracey
On Tue, Oct 28, 2008 at 4:08 PM, janedenone <[EMAIL PROTECTED]>wrote: > > Hi Karen, > > I did that, but the message was never sent to me. > That's the first problem I'd be working on fixing, then. Long term you are likely to want that mechanism working, you've got a problem to solve right now

Re: 500 displayed instead of 404

2008-10-28 Thread janedenone
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

Re: 500 displayed instead of 404

2008-10-28 Thread Karen Tracey
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.

Re: 500 displayed instead of 404

2008-10-28 Thread janedenone
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: # urls.py: urlpatterns = patterns('myproject.myapp.views', (r'^test/$', 'test'), ) # views.py: def test(request): raise

Re: 500 displayed instead of 404

2008-10-28 Thread Thomas Guettler
Hi, I guess that you get 500 because there is an unhandled exception. Can you see a traceback in your error log? What happens if you write "return django.http.HttpResponse('OK')" instead of raise Http404? Thomas janedenone schrieb: > Hi, > > I use the following simple view > > def

Re: 500 displayed instead of 404

2008-10-28 Thread Steve Holden
janedenone wrote: > Hi, > > I use the following simple view > > def index(request, page_id, current_subpage=1): > try: > current_page = get_object_or_404(Page, pk=page_id) > except: > # if anything else goes wrong, display the 404 anway >

Re: 500 displayed instead of 404

2008-10-28 Thread Ronaldo Zacarias Afonso
Hi Jane, Are you sure your index view is being executed? It just seems that django can't find a URLconf rule defined for your view. []s Ronaldo. On Tue, Oct 28, 2008 at 11:36 AM, janedenone <[EMAIL PROTECTED]> wrote: > > Hi, > > I use the following simple view > > def index(request, page_id,

500 displayed instead of 404

2008-10-28 Thread janedenone
Hi, I use the following simple view def index(request, page_id, current_subpage=1): try: current_page = get_object_or_404(Page, pk=page_id) except: # if anything else goes wrong, display the 404 anway raise Http404 In debug mode,