Pixelpost

matttail · #1 08-08-2007, 11:29 PM

I saw a thread from over a year ago on this topic, but I've just installed the latest version of PP and if there's a ? without a space after it in a comment I get a "service temporarily unavailable" error.

BEFORE you tell me it's a problem with my ISP, let me tell you that the blame isn't totally on them. From the year old results it would seem this is an issue with mod_security. I'm not turning off mod_security to get around a parsing error with pixel post. Yeah, it's a problem with Pixel post because this issue doesn't go, "you can never use php to print a question mark!" It's Pixel post can't handle Question marks with out spaces after then posted by commenters.

Any tips on how to fix this?

**GeoS**+ · #2 08-09-2007, 12:17 AM

But that is still issue at server side what escalates to your ISP. As the mod_security is a layer between webserver and PHP (Pixelposts script) in user, browser, webserver, PHP script (Pixelpost) model then we cant do anything. We even dont get any data which we could handle in other way.

Please let me know is someone see this issue from other point of view or know any solution related to Pixelpost code.

matttail · #3 08-09-2007, 01:52 AM

First, mod_security is a Apache thing, and if website software can't handle being served by a standard installation of apace...

As far as how to fix it, how about programing in an automatic space at the end of every comment? I'm sure there's a much much better way, but that at least is one example of how to change pixel post coding to make it work.

**Dennis**+ · #4 08-09-2007, 06:33 AM

Ok, how about this. I write some code, tell you were to put it and you test it for me.

If it works, I'll put it into the next release.

**Dennis**+ · #5 08-09-2007, 07:26 AM

Additional info:
http://urbangiraffe.com/2005/08/20/m...ous-406-error/

matttail · #6 08-09-2007, 03:13 PM

I'm more than happy to test. I don't have an overly popular blog, but I will do as much as I possibly can.

**GeoS**+ · #7 08-09-2007, 03:58 PM

Ok, there is other solution. Handle content of comment by JS and then post it back to Pixelpost. All is at user side and server side gets valid data.

IMHO its the best solution because this lib can be attached by owner of site having such a problems. Much better then hacking each time Pixelposts core files.

**Dennis**+ · #8 08-09-2007, 08:51 PM

Problem is mod_security kicks in at the $_POST variables. I can not touch the comment with PHP prior to the $_POST.

Javascript is the only solution.

And the comment you made about it being Pixelpost's problem is not right either: the rules for the mod_security are to tight.

So after all, you can go with javascript or loosen up those rules. (and that would be a serverside issue).

Basically we can't fix it, because we can't control it.

Pixelpost

Authentic Photoblog Flavour