Re: cut-and-paste traceback error actually the error from the time before --

Yeah -- I am using firefox. Thanks for the lead on that. On Apr 29, 2:05 pm, Mike H <[EMAIL PROTECTED]> wrote: > Are you using firefox? I think this is a "helpful" feature of firefox > where if you fill out a form and refresh the page, it remembers the > form content so you don't have to fill it

Re: cut-and-paste traceback error actually the error from the time before --

In this situation it might be helpful to use tamper data (or something similar) to examine the all of the requests / responses and see exactly what your server is sending and when Could at least determine if this is broswer behavior or if Django is really sending the incorrect trace. Colin

Re: cut-and-paste traceback error actually the error from the time before --

Are you using firefox? I think this is a "helpful" feature of firefox where if you fill out a form and refresh the page, it remembers the form content so you don't have to fill it in again. So if you get an error page, fix the problem, refresh and get a different error, firefox messes up t

cut-and-paste traceback error actually the error from the time before --

I thought this was "maybe it's just me" problems -- but it happens on every install of Django, in every environment I've dealt with Django (which is now up to six). When I get a Django error page, the error that's listed in the cut-and- paste traceback is actually the error that existed the time