I had the same problem and after many days of trying to figure it out it boiled down to a particular word that I was typing. I don't recall exactly, but I think it was something like the word "union" followed by a fullstop. As soon as I used another word it worked fine. rusty explained that it was something about the coding of the board software or something like that. Unfortunately, in my case, I literally pasted my entire reply into a Notepad document and then copied one sentence at a time, pasted into the reply box, and hit "preview." If it worked okay, I pasted the next sentence and so on, until I came to the sentence that was causing the problem. (You will probably find that hitting Preview also takes you back to the home page.) I then went word by word until I figured out what the problem was. Really painstaking, but I figured it out in the end.
D3PART3D wrote:Darn it schase! I was going to tell him after making him beg.
Oi, I went through the actual exercise and remember well how frustrating it was. I wouldn't willingly subject anyone to such treatment, with the possible exception of QBM.
it's pretty temperamental and probably requires that the preceding text hobble the parser somehow, (having zero knowledge around the parser i'm not going to sit here guessing but it would appear to present when 2 or more keywords are present), but the issue revolves around SQL keywords being used in posts... every once in a while the parser decides you're attempting an injection attack and bombs during posting..
i've seen it prang on DROP, DELETE, UNION, INSERT: as these are all sql keywords i'm happy in my assumption... removing the word 'and' from the above list allowed me to post this.. bombed otherwise...
Most people would sooner die than think; in fact, they do so - Bertrand Russel
it's pretty temperamental and probably requires that the preceding text hobble the parser somehow, (having zero knowledge around the parser i'm not going to sit here guessing but it would appear to present when 2 or more keywords are present), but the issue revolves around SQL keywords being used in posts... every once in a while the parser decides you're attempting an injection attack and bombs during posting..
i've seen it prang on DROP, DELETE, UNION, INSERT: as these are all sql keywords i'm happy in my assumption... removing the word 'and' from the above list allowed me to post this.. bombed otherwise...
Sounds to me suspiciously like Mugabe's media censorship. Next thing you know, we'll be kicked back to the homepage everytime we post the word "covergirls" in conjunction with any other word that might be construed as negative.
