5 ms·
You should probably set DEBUG at False. This is very undesirable in a production environment as it will probably leak sensitive information that attackers can u
by mmq 14y ago
You should probably set DEBUG at False. This is very undesirable in a production environment as it will probably leak sensitive information that attackers can use against your site. Unless, of course, if you use only the Django ORM.
- cookingrobot 14y agoSeconded - I tried to participate but wasn't willing to give access to my twitter account. It gave me a very verbose error page.
- jessratcliffe 14y agoThank you. I've tried setting debug to false but it causes a problem with the template. Do you know how I set it to false without affecting the design? I've tried a couple of ways as suggested on SO but all seem to return a server error.
- mmq 14y agoHow is your design affected? For the case when the user isn't willing to give access to his/her twitter account. The error returned is KeyError, since you are trying to access : user = User.objects.get(username = authorized_tokens['screen_name']) I see that you have put a try, except blocks. But you are not catching the KeyError exception. You are only making an exception when the user doesn't exist. you should add a block : except KeyError. And figure out the logic for this particular case. (probably just redirecting the user to the home page)