Percent Sign
 

It can't be posted by most people it seems. Bad request.

However, some people can ;o

weird

%%%%%%%%%

-_-

Ya, it seems completely random... but does it more often than not.

%

Seems to work when using quick reply but not advanced ;o

EDIT: AND NOW IT DOESNT o.o

Heh... the worst part is it always happens when you're not expecting it. It ALWAYS happens when posting scripts and tidbits, which is the worst part.

I've posted about this before, they don't seem too interested in even giving a damn.

Yeah it's doing it here too sometimes. Only in advanced for me, though.

Actually I think this quick-edit stalls when the problem occurs. No clue.

Yes it sometimes does stall, and sometimes it works ...

I love how many deleted test posts there are in this thread so far ;o

Okay. I think it's either random, or is determined by its usage. I've posted a script using [percent] in quick post and advanced, and neither times did it give a bad request.

Due to my past experiences though, I think it's determined by its usage. This can only really be tested by repeatedly posting something using a [percent] and seeing if it sometimes goes through of it it has to do with how it's being used.

Either way, it sucks. Fix please.

edit: okay, it stalled just from me using it then. So retarded.

%%%%%%%%%%%
10%, 20%, 30%, 40%, 50%

this.i = (this.i + 1) % 10;
%%%%%%%%%%%

lol, spam :x

hax

Please fix it :(

I'm just using quick edit to post them usually :d

Which doesn't seem to work anymore...

*post to quick edit to add a percent sign*
edit: % :)
edit2: dident work on any otherway ( quickreply,advanced ) for me xD
edit3: very random for the percent sign .. fix it :P

Looking through this thread, it seems almost as though a moderator has been here ;o

Why don't we just enable simple HTML like <b>, <i>, % (percent symbol), etc? It would simplify a lot of things..

Or just do away with whatever malicious code detection they put in. I don't think I've ever seen anyone abuse percent signs here before, and it certainly isn't enabled(or this horribly enabled) on other forums.

I didn't know percent signs could be horribly abused ...

it bothers me when i try to and i have to type it out
%


it works in quick reply

It doesn't work in quick reply. It's not a matter of how you post, it's a matter of what you post. I just tried posting a script I KNOW gave me problems from the code gallery in quick reply and it just stalls. Same with quick edit. If you attempt it in quick* it just won't do it. It'll sit there forever. If you do it from advanced, it'll send you to the bad request page.

Given it gave me problems back then, and still does now, I think it's safe to assume it only gives a bad request on given circumstances. We just don't know the circumstances :/

I can't quote that post.

:Ø Could this problem be fixed?
:Ø Could this problem be fixed?
:Ø Could this problem be fixed?
:Ø Could this problem be fixed?

It may already be fixed; you guys should check google for patches to VB.

We can't post links anyway, right?

Also, I think it's just with these forums; it doesn't happen on any vBulletin forums I've been on (same version).

Thankfully we can, however, send private messages. Technology is a wonderful thing, eh? :p
Check a bit before you come to conclusions - it's probably a common fairly problem.

I did; I did a quick Google search before posting that.

Wait, we can apply patches to VB? The VB installed here? o.o
(And Stephen, you found a link to something that might fix it?)

Bleh, it doesn't happen on the Symphonian Forums, which is VBulletin

Well, it's just PHP - it can be altered... which is probably what caused this to begin with. If I had to guess it was probably the swear filter... if it wasn't you could probably use a modified swear filter to read the ascii for the percent sign and convert it to regular percent sign - assuming there's some sort of difference between the input and output.

Just having the % replaced with "&#37;" before the post goes through any other processing should fix the problem.

(If you type &#37; in your post, it will be replaced with a %, by the way.)

There, Googi has found the process. Now we just need someone to modify the swear filter to convert all user entered percent signs into that code, so that it will display properly. We just have to hope that the swear filter is first in the line of code before it reaches whatever is messing it up.

It does?

%

It does :O

It appears that the swear filter is actually applied when you view posts, not when they're entered into the database.

The filter is applied as it post is processed for the database, so this should solve the problem?

It's possible to search posts using censored terms, which suggests that the post is stored in the database as-is, without the filter applied.

Edit: Actually, it seems the filter is applied both as a post is put into the database and when a post is viewed.

apparently my posts are nothelpful/spam

i dont get how any of these posts are helpful, but youknow.

It's not the swear filter.
Unixmad posted about what was causing it -- a filter of some sort that checks for malicious code that he recently(recent back then) put in.

We realize it's not the swear filter, it was simply the suggested method of correcting the problem for ease.

I guess it's a matter of priorities then. If the swear filter is done AFTER this malicious code filter(which I'm assuming it is), it won't matter because it'll give a bad request before the swear filter even gets a chance to process anything.

edit: I see Googi already covered this. Either way, this requires Unixmad's involvement... so we're **** out of luck.

Hay cow lips - that was ME.

Heh, I was referring to:
So either way, I don't think the swear filter is going to help any.