in your browser.
[Bug (fixed)] backslashes in posts
Return to board index
I know I posted about this before, but I can't find my post, so I think I must've just added it into another post somewhere instead of making one.
Any backslashes in posts are removed when they're sent to the server. I imagine it's just escaping needing to be escaped, but it prevents me from using my colon backslash smiley (disasterous, I know). It also prevents listing windows-style paths.
The backslash, when it's removed, will also remove the character after it. Obviously.
Will be looked into this evening.
edit: This bug \\is now \fixed.
This bug \\is now \fixed.
Sko is my hero, yo. Ho, ho, ho.
I have to go...
So ... old bump, I know. But it's related. Now that I have this habit of bolding my smileys, the double-escaping of backslashes is interacting badly with the OTHER escaping of BBCODE tags. What I'd like to do is this...
But what I get is this ...
Now ... as for solutions...double escape the slash if it's preceded by a colon and escape the BBCODE if it isn't? kek...
What about ...
... so, if I double escape the smiley slash myself, it prints the slash now, but then still escapes the \ tag.
Triple escape? ...
... nah, it's still associating the two.
Can you think of any way to make that work? I don't think we can use stuff like ... oh wait, we can. Let's try ...
... Oh, you just allow some of them like ... and ... er, actually only
apparently. Any reason why you aren't allowing other HTML escapes? Or is that a security thing related to SQL injection in a way that I'm not imagining right now?
Any ideas? ilu
You have the WEIRDEST feature requests.
I hope it's endearing
. (<- see the bolded smiley?)
Certainly. But being endearing isn't enough to get a feature pushed through. :P
Well, what about an answer to the question of why only & nbsp; is allowed for escapes? If I could escape backslash, I could use that instead.
In it's broadest form, the answer to most of your questions is that the Wowhead forums were coded by one guy in a 3 day coding binge, then handed off between several other programmers of varying specialties. Wowhead has reached the point where it's like any big project—we can dig into our own code, even code that was written by the same person a few weeks back, and say "...why on earth did we do it that way?"
It just happens this way sometimes, and we do our best to accomodate. You use the forums at a higher level of complexity than most, so you tend to run up against the little quirks more often than most. :P
Well, if there's code to specifically allows and-en-bee-ess-pea-semicolon, and to specifically disallow the rest, is it possible to change that, easily? I mean, not now but, in the fullness of time and at the bottom of your whiteboard in the box for "__ed Up Stuff Pelf Has Asked For".
I think we can add it to the "in the fullness of time and at the bottom of your whiteboard in the box for "__ed Up Stuff Pelf Has Asked For"" list. In fact, I may start saying that instead of "soon". :)
Your double-nested quotes just broke your BBCODE parser. Way to go, Mal.
I love our BBCode since it lets me make snowmen.
You are not logged in. Please
to post a reply or
if you don't already have an account.
Connect with Wowhead
Other Fanbyte Sites
Hearthstone Top Decks
Final Fantasy XI
© 2021 Fanbyte