The swear filter has failed us

So I noticed two places that the swear filter doesn't work if a thread title contains a swear word.
1. The expletive appears in the URL. Probably to avoid generating filenames containing ":skull::skull::skull::skull:"
2. The other place is at the bottom of the thread where it links to the next and previous threads. If either the previous or next thread title contains a swear word, it's printed. Ostensibly, these are separate SQL queries, in which case it would be easily remedied.

See <a href="http://forums.eyesonff.com/eyes-each-other/109592-alright-smurf.html">this thread</a> for an example. I don't know if it's even an issue, just something I noticed. :p

We are aware of it but apparently are doing nothing.

Heh, cool. I figured it was going to be something about how obvious the swears are as fuck and :skull::skull::skull::skull: are different and all.

don't care don't care la la la

Hmm. let's turn VB SEO off!

I better get my swearing in now before they decide to do something about it!

I for one welcome our new cheesecake based overlords.

I'm using the skin Sosumi right now, and the swear filter isn't on at all in that skin. I wrote fuck in another thread and it didn't filter it, then I changed to EoFF Classic and it was filtered. Evil skin.

I'm using the skin Sosumi right now, and the swear filter isn't on at all in that skin. I wrote smurf in another thread and it didn't filter it, then I changed to EoFF Classic and it was filtered. Evil skin.

Paid membership feature :p?

I'd pay for that.

By joves, it really is unfiltered, and on all of the new skins. The S-word is still filtered though. :p

well googlebots can't exactly use those skins! or can they.

Then it must be "Replacement Variables" setup on the default skin. All someone has to do is set them up for the new skins. Or leave it like it is so we premium members can say !@#@#@# at everything :D

Yeah, when we were given the chance to test out the new skins I noticed that there was swearing, but no filtering! :jess:

Clearly the solution is to ban everybody, fix the issue, then reopen the board ?