 
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
|
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
In Reply to: is there a server problem? posted by Mart on March 24, 2004 at 15:34:27:
Yeah, something is going on with db connections which affects posts. It just started the last couple days, so I need to look at the logs and figure out what's going on. After the connections timeout, things are fine. I don't know what's up, yet.
Follow Ups:
♪ moderate Mart £ ♫ ☺ Planar Asylum
But when people use < nt > in the subject line on a long comment that exceeds the limit, then you get a hanging open bracket that makes the entire message look like a link. Rather than do a confoluted parsing to check to non-matching brakets, it stuck me that just changing them to parenthesis in the subject would do the job and it a lot easier.Did you see something where that's a problem?
For me I chose the < nt > brackets to conviently vanish in some references where the warning seemed irrelevent. So, when you went out of your way to change it, it seemed to beg the question. As always YMMV...
♪ moderate Mart £ ♫ ☺ Planar Asylum
Not really an effort, it's just a one line change. I just noticed this message today were got me to find the line.
the special characters < and > Then nobody should notice the difference.I assume you don't allow users to post HTML code in certain places. Titles, certainly. A substitution like this will negate any attempts at HTML and will keep things looking as the user entered them. If I'm not mistaken, they'll also display correctly within an field.
and I can't imagine why. It can only cause problems. If someone explicitly enters the special character codes "& l t ;" and "& g t ;" (minuse the spaces, of course), why substitue angle brackets? Unless that's an unintended consequence of using some library or other in your code.Substituting the special character codes, on the other hand, is a good way to keep HTML from being entered where you don't want it. And like I tried to say in the last post, it still displays correctly in input and textarea form elements.
Actually, the code used to alway substitute the & l t ; and so forth. The problem was when the subject line got truncated due to a limit. I probably could have done a complicated fix and checked for a hung open bracket, but what happens is that is looks like an href because it picks up the next Posted link or something and the whole message is a weird link. I think I posted an example to Mart. The easy way out was to just change the bracket to a ( in the subject.Yes, other html get's purged out too in various input field like script tages and whatnot.
This post is made possible by the generous support of people like you and our sponsors:
Top of Page ]
[ Contact Us ]
[ Support/Wish List ]
[ Copyright © 2025, Audio Asylum, all rights reserved ]
