Hi, I logging in with admin privileges and get this error while logging out. Page not found (404) Request Method: GET Request URL: http://greenchilly.in/admin/admin/logout/ And a long traceback from Django. Kenneth, something needs to be done to take care of errors gracefully without the default action of the Python traceback being printed. How does typical Django sites take care of this? I would think that they would have specific error templates for handing most web page errors. There is one more error when I try to log out from http://greenchilly.in/admin/sites/site/admin/logout/ . ValueError at /admin/sites/site/admin/logout/ invalid literal for int() with base 10: 'admin/logout' Request Method: GET However these are admin errors and not priority since they don't directly affect user experience. Still I am reporting it. Anyway, the error management should be more graceful than now, since tracebacks are being printed for user level errors also. Regards, -- -Anand
On Sun, May 31, 2009 at 12:04 PM, Anand Balachandran Pillai <abpillai@gmail.com> wrote: [..]
Kenneth, something needs to be done to take care of errors gracefully without the default action of the Python traceback being printed. How does typical Django sites take care of this? I would think that they would have specific error templates for handing most web page errors.
I think it's running in 'development' mode and so prints tracebacks and application innards. In production mode, it'll probably show an HTTP Error 500 or something like that. -- ~noufal
Anand Balachandran Pillai wrote:
Kenneth, something needs to be done to take care of errors gracefully without the default action of the Python traceback being printed. How does typical Django sites take care of this? I would think that they would have specific error templates for handing most web page errors.
There is one more error when I try to log out from http://greenchilly.in/admin/sites/site/admin/logout/ .
I too have been facing this error. I think the Debug mode has been set to True so that bugs product Tracebacks, like the one you we see when logging out. This might be because it is in development mode currently for people to test and report bugs, and hopefully will be turned off when going live. And yes, Django allows you to have custom error templates so that you can handle errors more gracefully. This is done by having a custom template dir and overriding default error templates using the custom templates placed in this. Am sure Kenneth knows about it, may be someone can volunteer and write some custom error templates with InPyCon logo and some nice error message ;) -- With Regards, Parthan SR "technofreak" GPG Key 2FF01026 Fingerprint 5707 ECBD 8D8D 8E6E 28F8 DFA5 938B D861 2FF0 1026 Weblog http://blog.technofreak.in
On Sunday 31 May 2009 12:04:14 Anand Balachandran Pillai wrote:
Page not found (404) Request Method: GET Request URL: http://greenchilly.in/admin/admin/logout/
And a long traceback from Django.
Kenneth, something needs to be done to take care of errors gracefully without the default action of the Python traceback being printed. How does typical Django sites take care of this? I would think that they would have specific error templates for handing most web page errors.
There is one more error when I try to log out from http://greenchilly.in/admin/sites/site/admin/logout/ .
ValueError at /admin/sites/site/admin/logout/
invalid literal for int() with base 10: 'admin/logout'
Request Method: GET
However these are admin errors and not priority since they don't directly affect user experience. Still I am reporting it.
Anyway, the error management should be more graceful than now, since tracebacks are being printed for user level errors also.
debug is on for testing - when the site goes live this will be set to off and no error messages will be seen. -- regards Kenneth Gonsalves Associate NRC-FOSS http://nrcfosshelpline.in/web/
participants (4)
-
Anand Balachandran Pillai -
Kenneth Gonsalves -
Noufal Ibrahim -
Parthan SR