Words that cause problems...
Brandon that does it voodoo, spirit and myself are on our way for the second intervention. The firsttime itwas the fat chicksand support your local single mothers thing, now it has escalated to this [:@]lol [sm=lol.gif]
ORIGINAL: chainstretcher
Whoever said the site is possessed is the big weiner!!! Sometimes it gives me the error then I post the same thing more spread out and it works. If any of you break the rhyme and reason for our issues I'll give you $100 outta my pocket ...
Whoever said the site is possessed is the big weiner!!! Sometimes it gives me the error then I post the same thing more spread out and it works. If any of you break the rhyme and reason for our issues I'll give you $100 outta my pocket ...
S E L E C T
*
F R O M
tblForum AS f W I T H ( N O L O C K )
I N N E R J O I N tblMember AS m W I T H ( N O L O C K ) On f.MemberID = m.MemberID
W H E R E
f.MessageID = 591968
O R D E R BY
tblForum.AddDate
I conjecture, that something is improperly modifying the text and causing these particular words to appear incorrectly to the SQL backend. Something else that leads to this conclusion is the conversion of the single quotation marks to 2 single quotation marks (not the double quote character). Single quotation marks are used to denote the beginning and ending of a string (in layman's terms). Basically the computer needs to know what needs to be treated as text and what is the actual programming code. Since single quotes are used for the text identifiers, then in order to get the single quote to actually appear in the text, you need to type the single quotes twice.
Again, without seeing the code, this only my best guess. I personally thing you should disable the profanity filter for now and see if things improve. Beyond that you might want to try toggling the quoted identifiers feature in SQL.
I or one of the other programmers on the forum can take a gander at the code, (but might not find the problem if it's in a compiled exe or dll).
Is postpro new?
woo that's been my finding as well... any post problem I've had has turned out to be an SQL reserved word. As you say - it's probably related to anti-sql injection code...
well...i will interject as well and say that this is my finding as well....if i can find the word and remove it my post goes through fine...however...that being said...it doesn't make sens why some people are not having issues when others do not...
in the morning yesterday one post that didn't work, worked perfectly fine later that day...the posts were identical...it's pretty odd..
in the morning yesterday one post that didn't work, worked perfectly fine later that day...the posts were identical...it's pretty odd..
ORIGINAL: ffingers
omit the periods - have to have them to post the word
u.s.e
w.h.i.l.e
l.i.k.e
h.a.v.i.n.g
compare (sometimes)
now some of these words work SOMETIMES...but if you are not able to post see if these words are there and change them...might help out...feel free to add to the list
omit the periods - have to have them to post the word
u.s.e
w.h.i.l.e
l.i.k.e
h.a.v.i.n.g
compare (sometimes)
now some of these words work SOMETIMES...but if you are not able to post see if these words are there and change them...might help out...feel free to add to the list
kicking back to top cuz W-HILE and LI-KE are kicking my *** and they didn't used to in case others H-aving same problem need a reminder.


