| T O P I C R E V I E W |
| Jamallo Kreen |
Posted - 02 Jun 2008 : 22:02:33
I have found that when the server is somewhat busy, and I use the "quick reply" option instead of the "reply to topic" option, I am much more likely to receive an error message and generate multiple posts. I haven't compiled any statistics on it, but that's my general impression. "Reply to topic" will also tend to post immediately when the other won't.
|
| 4 L A T E S T R E P L I E S (Newest First) |
| Jamallo Kreen |
Posted - 04 Jun 2008 : 04:39:13
It's alive, I tell you! Alive! ... and it ... hates us. <insert emoticon for lightning flash and thunderclap>
|
| Alaundo |
Posted - 03 Jun 2008 : 18:51:26
Aye, oddly, the Quick Reply does seem to be less robust.
As Kajahase states, it's wise just to copy the text of your post before hitting submit, until we get this sorted once and for all. |
| Kajehase |
Posted - 03 Jun 2008 : 12:42:27
I've found that the best way to avoid maiking multiple replies in this situation is to copy the message every time I use the "Quick Reply" function; and if I then provoke an ASP error, I check the thread before posting again rather than repost, repost, repost until I see it come up. |
| The Sage |
Posted - 03 Jun 2008 : 01:38:30
Aye. I've discussed this with Alaundo before. It's a curious aberration, and something that may be connected to the overall problems Candlekeep's been experiencing. The "Quick Reply" function is often fickle. Once, not too long ago, I was having plenty of success getting around the ASP errors when "Replying to Topic" by using the "Quick Reply" function. Other times, it would quickly lead to the ASP error screen. |
