So I've heard a few comments from various members saying that the forum is eating posts, having problems with comments not being able to be posted, etc.
None of this ever happens to me - there are no SQL errors logged, no PHP errors logged - nothing.
So to me, that leads me to believe its weird browser thing.
Now, this editor that's in use here gives you all the nice formatting options, image insertion, bla de bla.. but if its being a problem, it can be disabled - just need to know :)
So looking for some feedback, or some information on what happens when the site eats your post.
Thanks!
chomp
Symptom: you write a long post and hit <post comment>. The system comes back with an error. I don't remember the error text, but i think i remember the word "time" in it. You hit the back button which returns you to the editor and all your stuff is gone.
Possibilities that occur to me are browser or web page timeout while typing and editing a long post, or a timeout on how long it takes to process posting the comment. The server does occasionally run very slow. I don't think it's the editor with all the gee whiz editing features. .
I tend to notice the issue when i do a long post. Typing it takes a while and tweaking the words to say exactly what i want takes a while. Hit the button and error. It may happen on short posts too. But I notice it after a long post bacause I'm annoyed that i've lost the work.
The workaround is to copy to the clipboard or to another editor before posting. Then if it craps out, you paste it back in and try again.
Kalb- druid
Lizztoo- lock
Chamu- Chaman
scripts
If you want to see what I'm talking about, write something in the "Subject:" box, and something in the "Comment:" box, go 'back' then 'forward'. If you have scripts enabled the "Comment:" box will be empty while the "Subject:" field, being a normal text box, will still retain whatever you put in there.
No one uses the formatting the Subject box provides, it seems to cause more harm than good.
Hmm neat.
Based on Kalb's comment, I'm not convinced that the editor is the problem, but I know it's been an issue in the past.
As for the timeout issue that he wrote about - the site shouldn't be logging anyone out, except after.. 55 hours. Or you forcibly log yourself out.
But thanks for the input. I can't say that I had ever noticed that the data in a text box is persistent through page navigation.
Just to be safe