|
#1
|
||||
|
||||
|
"No intrusion! ?? :(" error
i'm trying to post comments on my own site to respond to what people have said but i get this error....
any ideas? the exact message i get when i post is a white screen with 'No intrusion! ?? ' on it.....and yes i have the latest update... thanks, Ash |
|
#2
|
||||
|
||||
|
horray! another bug!
I saw this bug on 1.4.3 and I was not able to recreate it to test it! what's your url? I want to test it
__________________
Photoblog: http://pblog.raminia.com Powered by Pixelpost 1.7 |
|
#3
|
|||
|
|||
|
I'm getting the same thing.
Only on my analog blog: http://www.lifekapptured.com/analog/ Not on my other one? http://www.lifekapptured.com/digital/ Both were upgraded to 1.4.3... Any help would be great ![]() Dave
__________________
http://analog.lifekapptured.com - film blog http://www.lifekapptured.com - gallery |
|
#4
|
|||
|
|||
|
I'm reverting back to 1.4.2 since that seems to solve the problem. If any pixelpost developer wants to use my test blog to play around and re-create the error, send me a PM or email for the info.
Dave
__________________
http://analog.lifekapptured.com - film blog http://www.lifekapptured.com - gallery |
|
#5
|
|||
|
|||
|
I think I'm making some progress on this 1.4.3 "No Intrusion" bug.
I can easily re-create the error. To create the error, type in your comment and hit "enter" instead of the "add" button. This creates an empty line in the comment box. To have a successful post w/o the error, there can not be any blank lines in the comment box. Is this making sense? I was able to do this with Safari, Firefox & Camino on Mac 10.4.3. and PixelPost 1.4.3. This doesn't happen in 1.4.2. Dave
__________________
http://analog.lifekapptured.com - film blog http://www.lifekapptured.com - gallery |
|
#6
|
||||
|
||||
|
sup David...
It's me Ash...I guess this is the place where I orignally found your blog.... I will try that...I was actually trying to reply to your post when this error occured... |
|
#7
|
|||
|
|||
|
Hey Ash.
It looks like the extra return at the end was causing some problems. I got your reply, and was able to post on your latest image tonight. Dave
__________________
http://analog.lifekapptured.com - film blog http://www.lifekapptured.com - gallery |
|
#8
|
|||
|
|||
|
the reason is that the returns at the line-end are not allowed, that is in the security - update and we must change that, because in message text carriage returns are no security risk
we were too overprotective ;=) |
|
#9
|
||||
|
||||
|
I'm greatful of our users! Thank you so much!
__________________
Photoblog: http://pblog.raminia.com Powered by Pixelpost 1.7 |
|
#10
|
|||
|
|||
|
Wow, fantastic!
Thank you for looking into this issue. I too am experiencing the same hickup at www.genestho.ca I just received an email from a frequent poster who's let me know about the issue. I too did some testing and as indicated above, I've figured out it is the line breaking in the comment box. I look forward to a small fix coming out as this one surpasses my knowledge of PHP. Great team! Thanks you so much. Dan |
| Post Reply |
| Thread Tools | |
|
|