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 On Tue, Apr 29, 2008 at 1: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 in again. So if you get an > error page, fix the problem, refresh and get a different error, > firefox messes up the textarea. Extremely unhelpful. I'm pretty > certain django is outputting the correct data. A random name and id > for the textarea would probably fix this, but it's really a firefox > problem from what I've seen. > > > > On 29 Apr 2008, at 19:49, Joe Murphy wrote: > > > > > 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 before. > > > > That means I get a page kind of like this: > > http://dpaste.com/47439/ > > > > Anybody else experience this? > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
