views:

111

answers:

2

This is starting bug me: whenever I use the django admin to add or edit a record, I hit save and expect a confirmation page, but the result is a page that tells me the website is experiencing an error (it's not a Django page with a traceback, just a default view in my browser). If I hit reload or back in the browser, it takes me back to the user form. Even though the confimation page doesn't display, it never fails to save my entry in the database, so it's apparently just a problem generating/serving the confirmation page.

Has anyone else had this problem? Am I missing something obvious?

My server: Django dev server My browser: Internet Explorer 7 (but same problem occurs with any broswer I use) My OS: Windows XP

A: 

This is certainly not how it's supposed to work! Have you been messing around in the Django codebase at all? The first thing that comes to mind here is a "pdb.set_trace()" left by mistake somewhere in the change_list codepath. Off-hand I can't think what else would cause the server to simply not respond.

Carl Meyer
Nope, haven't messed with the codebase (that's beyond me). You know it's wierd, the server responds ok if I reload the page or go back in my browser, but it's just that initial submit that seems to missfire. I wish I knew more about how the server works. And it does this on both my work computer and my home computer.
twneale
+1  A: 

I got such a behaiviour when I overwrote __init__ incorrectly. Or to be more precise when switching to a new version of Django with these worng __init__s. That was the day I started to love signals :D.

Can you post your models?

vikingosegundo