I don't think this is performance related. Looks like some kind of timeout on a page or cookie or stuff like this.
It is frustrating because sometimes I just don't realize how long did it take me to write the post or get distracted... and I wish there was a way to figure out how to get rid of this problem on your side instead of going thru the copy and paste in case I went over the time limit.
Do you get a log entry if someone gets 'blanked out' when replying to a post?Maybe the problem happens more often then the posts would suggest.
Was just looking to post about this problem but did a search first. It's been a year and this is still happening Seems to me that this would be a quick killer of a good forum. Why is it still happening? Personally if I loose a post (it has happened) I will not bother retyping it unless I remembered to copy and paste the text before submiting it. This is happening to me on a regular basis.
i have been bitten by this bug 6 times this week; some of my posts couldn't have taken me over 3 minutes to type, others were huge detailed answers....I'm a damn decent web developer, if you need someone to trace the code and find the timeout issue, I'd volunteer; change the code to look for a cookie or something so that this doesn't happen.
Like Carl said, because of that, i didn't try to retype my answers....too much trouble.
No problem Steve; just wanted you to know; i bet it has something to do with the high traffic your site gets; i love this site and spend a lot of time on it every day.
i think this can be fixed simply by adding some code to either the button that submits the data, or the Sub Page_Load event; the page will have all the values that were submitted, so it would be something like this: i suspect that the submission page either explictly sets the current values to be blank on_load, or simply allows them to be initialized, and they have no value..... by not init-ing them on IsPostBack, the data would remain in place...similar to when you submit username/password, and the password is bad, and you leave the username in place, awaiting a change to the password...
Behind the scenes, an error like invalid viewstate is probably being raised because the session timed out (or the application was restarted...same effect);
simply find the block of code that handles the submit button and in the Try..Catch...don't allow the objects to be initialized, or maybe assign the fields back their value... it's either the submit button or page load events that are wiping the data.
in Page_Load :
If IsPostBack then
'don't init, let the values remain....or assign or ave the values and reassign them? hard to say without the code.
'initing the textboxes to be blank?
I certainly wouldn't say it's Steve's fault Clearly these are very busy forums and something is causing a problem over time. For the upcoming revision of SqlServerCentral we will be moving to the latest version of the forum software and will try and prove that this problem is no longer there during testing, or fix it if it is.
Lowell - thanks for your suggestion. I think it would be a great fix except for a bit of extra magic that is going on internally to keep the ASP and ASP.NET sides of the site running together. This is effectively converting the POST to a GET so the ultimate destination page has no concept of the previous conversation - it is no longer a postback.
We're looking at a couple of potential fixes/workarounds that should prevent the annoyance of losing your post and we'll keep you posted!