Truly bizzarre forum problem

[sloanjh]

Like in quotes Creates problems. Try That word in quotes with either a space after the e or any words after it.

"Don't say that word"
....
"How can we not say the word if you don't tell us what it is"
"Aaaaaah"

John

[Erik L]

I removed a couple of unused mods. Have to see if that has any effect.

[MarcAFK]

"like " Still giving the same error, from what I gathered on google it's some kind of security setting from your webhost which SMF forums doesn't like.

[Erik L]

"like"

[MarcAFK]

put a space after like :p

[Erik L]

It's an SQL thing. = and like are SQL operators and something makes the software think that it's performing a select query instead of an insert/update.

[MarcAFK]

It's an SQL thing. = and like are SQL operators and something makes the software think that it's performing a select query instead of an insert/update.

I thought so but have no idea what a select query or an insert update is, I just know that like and from are codey things :p

[Theodidactus (OP)]

*assembles cunning SQL injection protocol*

*Destroys forum*

http://xkcd.com/327/


Can't believe I  didn't think of that before.

[boggo2300]

I thought so but have no idea what a select query or an insert update is, I just know that like and from are codey things :p

That knowledge alone puts you in the top 10% of Java programmers world-wide!

[MarcAFK]

That knowledge alone puts you in the top 10% of Java programmers world-wide!

Well I suppose it helps that I read a book about javascript and spent about 2 hours attempting a webpage. Oh and a few hours on whatever scripting language MIRC uses.  I also know java isn't javascript which is probably news to half the internet.....

[boggo2300]

Well I suppose it helps that I read a book about javascript and spent about 2 hours attempting a webpage. Oh and a few hours on whatever scripting language MIRC uses.  I also know java isn't javascript which is probably news to half the internet.....

Sorry,  unemployable,  too overqualified

 

[Erik L]

The host gave me a snippet to override the behavior, but that didn't work. Now they will put me in a white list so hopefully that will work. If not, I'll put in cuss word replacements for like, =, and where so the issue will seem to disappear

[Vandermeer]

Thanks for the tip with the cursive, because that really helped me out today, so I didn't have to rewrite 4 paragraphs. I also have new information gathered by this, that finally shows some structure in the errors: All the paragraphs that caused a problem today always started with "Then", and the next word in line would here cause the issue and need to be cursiv(-ied?). Maybe "Then" means something special in SQL that causes this, but anyway, it can be avoided.

[Erik L]

I've also seen it when I include one of the verboten words as the only content in the post.

[Erik L]

Good news is the host has been able to replicate the error. Bad new is they need to escalate it to their engineers.