July 2, 2005 at 10:42 pm
So I just spent 15 minutes or so writing a witty and erudite response (well, it answer their question and covered the salient points nicely), and hit "Post New Topic". The screen flashed, the text entry form reappeared, and all my text disappeared--utterly wiped and gone for good. Sorry, Joe Anonymous, but I am no way going to write it all out again. (Blame it either on my limited attention span, or my severe dislike of doing the same piece of highly detailed work over and over and over again.)
This is by no means the first time this has happened to me over the past few years of (admittedly infrequent) postings. It does not happen at all often or frequently, but when it does occur it drives me up the wall. Yes, I should cut n' paste it to a "side-window" before hitting post, but I only think of doing that for a week or so after it happens, and then forget until the next time a post vanishes.
What gives? Do I have something misconfigured? Is it sunspot activity?
Philip
July 5, 2005 at 8:00 am
This was removed by the editor as SPAM
July 5, 2005 at 2:15 pm
I've been bitten by the same problem and my behavior matches yours... I'll copy and paste to a side window for about a week after getting burned, but after that I stop doing that... until it happens again.
K. Brian Kelley
@kbriankelley
July 5, 2005 at 2:24 pm
Maybe it would be possible to write the post to a cookie and redisplay it if the session has ended.
July 8, 2005 at 7:38 am
Sometimes I'm able to hit the BACK option and go back one or two screens and see what I typed....I just highlight it, copy, go back to the original thread, select reply and paste it in.
-SQLBill
July 8, 2005 at 7:55 am
Phillip,
Apologies for that and I'm not sure what it is either. I know since I've switched to FireFox it doesn't happen to me, but I suspect there'e something in the ASP.NET code that refreshes the page and it explodes.
We haven't been able to reproduce it to track it down. I'm only about 50 posts a week, but I never see it, or I haven't in close to a year. Unfortunately we bought this code from someone and they have moved a few versions past. With all the customizations we've done to integrate this into the site, we're slightly stuck until we're ready for another major change.
July 8, 2005 at 7:58 am
Did you read my idea about a cookie (javascript). Shouldn't be too hard to install.
As for making it happen, start a reply, wait an hour (15/20 minutes seems to be enough sometimes) and hit post .
July 11, 2005 at 1:40 pm
It is a known problem with web based editors the serialization is not stable. I use note pad to keep a copy until the post is live. Hope this helps.
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie
July 11, 2005 at 1:43 pm
Is there any known fix?
July 11, 2005 at 2:24 pm
It may be a session expiration issue. I don't use the WYSWIG editor but instead use the plain text box and I get the behavior. Of course, it's always a response I've either had to walk away from or one I've spent a lot of time writing.
K. Brian Kelley
@kbriankelley
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply