I hate you.

[Sch3mat1c]

Ok, not really. But I did just type at least 50 lines of reply, only to have it killed when it refused to post the >800x1200 attachment.

Tim

 

[halojoy]

Ok, not really. But I did just type at least 50 lines of reply, only to have it killed when it refused to post the >800x1200 attachment.
Tim

Yes, this is terrible!
Imagine you have put a lot of work in to a nice post
and it is all lost.

It has happend to me.
Now I sometimes, COPY & PASTE into Notepad,
before Pressing the Submitt.
At least on the longer posts - just in case ...

I guess this problem has happend to most of us.

halo - did not SAVE this

 

[Brian Donaldson]

I too have pecked my heart out only to have it thrown out like the days rubbish. And I can never put the same effort on the second try. I often write a short post, then edit it until I'm happy. So if you see crap post from me, try again in 10 minutes. I may not be finished.

 

[SkinnyBoy]

I have found the same thing too, perhaps its why all my posts are short, and bad...

 

[EC8010]

This has happened to me too. I now don't attempt posting graphics with more than 780 pixels in any direction, and I copy to the clipboard before attempting anything clever like adding a graphic. Surely this shouldn't be necessary?

 

[AudioFreak]

IIRC,

The limitations on graphics are 100KB file size and no larger than 800 pixels wide by 600 pixels high.

 

[pinkmouse]

Certainly in IE5 on the Mac, you can just use the browser's back button to get back to your original message if the post is rejected. I do it all the time

 

[SkinnyBoy]

Certainly in IE5 on the Mac, you can just use the browser's back button to get back to your original message if the post is rejected. I do it all the time

You used to be able to do that, but I have found that now when I click back, the message box is empty (except perhaps of a quote script)

 

[AudioFreak]

Yes,

That wont work at present, we are working on this.

 

[pinkmouse]

test of backing up...

Yup, just tried it, it still works fine for me...

 

[Jason]

The problem with turning on the "no cache" headers to stop pages being cached, is that then clicking back will cause the page to reload.

Combine this with the way myriad different browsers and versions use headers, and the multiple page refresh options in IE, and worst of all the way certain ISP proxies decide to cache (compressed) pages, and you have a incredibly complex problem worthy of the most experienced http expert.