sbbn

Ah, got it. Thanks for the code, it worked great!

Terrific, that worked – thanks! I also tested by replying to a post, and it works fine.

What do you mean about CSS changes? I’m not sure what to look for.

Thank you both! I used both your replies to tweak the widths on my blog and it worked great.

Deleting that part of code worked, thanks.

Thanks Jeremy, I have asked on the Bulletproof forum.

Note that the comments worked just fine with Bulletproof until the WP 3.5 update and the update to the more recent Bulletproof. Something obviously changed, but I’m not seeing a whole bunch of complaints about it, only a handful here and there. I wonder if this is theme dependent?

@gabrielesque – I use Akismet with Jetpack comments and love it. That’s one reason why I’d really like to get Jetpack comments back on while also having Bulletproof security. Right now, because Jetpack comments are off, I get 10-15 spam comments a day that I have to manually delete.

Okay, that worked.

I disabled Bulletproof, went out on the Dashboard and updated the permalinks to get a new .htaccess file, reinstated the Jetpack comments and did a test comment. It went through fine this time.

What precisely does this mean? I’ve seen others on the help forums indicate there is a Bulletproof Security problem (that I think involves javascript, if I’m understanding it correctly), so is Bulletproof the issue here? Does it cause problems with Jetpack?

I’ve re-enabled Bulletproof as of now, btw.

Well, Bulletproof comes with a custom .htaccess file, and I did modify it with a few IP addresses of Russian hackers (using “allow,deny” commands). I did that a couple of weeks ago though, and it worked fine with the modifications then. That said, I DID update Bulletproof the same day I updated to WP 3.5, though when I disabled Bulletproof I assumed that custom .htaccess file was also disabled.

I couldn’t tell you about iFrames, but the only two security plug-ins I use are WordPress Firewall 2 and Bulletproof, as I listed above. The only code modifications I’ve made in the last few months were adding those IPs on .htaccess.

Hi! Sorry I haven’t responded sooner.

I updated Jetpack tonight, but no improvement on the comments.

I do have Bulletproof Security and WordPress Firewall 2 — I disabled both and tried Jetpack comments, but they still didn’t work.

I changed to Twenty Eleven, and the same thing happened.

What I notice happens is when I try to reply, I get the Page Not Found error, but my blog loads into the small comment box where my reply should be. So I see the top toolbar and my blog header where my reply had been, and below that, “The page you requested could not be found”. It’s very odd.

I’ve posted over there too, thanks.

Thanks Ethical, I have Namecheap too so this helps me as well.

Damian: My husband downloads copies of plug-ins used on our website to our hard drive after installing them on the blog. I thought it was unnecessary, but it turned out to be REALLY handy to have a 0.47.4 that we could grab and re-install when .5 didn’t work out.

I’m going to mark my thread as resolved — that second Jetpack update seemed to fix the problem.

“that may be something like having to create different htaccess files based on Hosts”

Which is very similar to what I was asking about in the first place, you know. Hack Repair Guy said it on the first page, too — just say goodbye to that code you claim is “misinterpreted.” It’s obvious they’re getting respect and actual information from you, which is good for those sticking with BPS. But it’s unfortunate you couldn’t extend that courtesy to everyone here.

Given the nature of this thread, honey, I don’t think it’s ME who’s having a bad day. And you seriously owe a HUGE apology to Spock. Dang.

Here’s the thing: You have framed this as “Namecheap has a new scanner on their Servers that is incorrectly quarantining both BPS plugin files and BPS .htaccess files.” But that doesn’t seem right, unless you’re saying Namecheap just by coincidence had a new scanner installed the day of the BPS update.

Their scanner didn’t think the prior version of BPS contained malware. So I think it’s perfectly logical to ask why you say this is Namecheap’s new “malfunctioning scanner” when it seems more like new code in BPS has caused a conflict with Namecheap’s existing malware scanner.

All I was trying to do is ask if, as a workaround, we could remove or comment out that conflicting code so we could still update BPS, because security is a huge issue on my websites, plus I know out-of-date plug-ins are a security problem.

It feels very much like you think I’m attacking you by asking these questions, and you have spent a lot of time on this thread complaining about Namecheap, and about people posting “different problems under the same thread” and “panicking” and “yelling FIRE” and “just venting” so therefore don’t deserve a reply.

It makes the entire thread feel hostile. Therefore, I’m bowing out of this thread.

Given that the prior version of BPS works, I’m a bit iffy on the logic of this being all the fault of Namecheap’s malware detection. See, I reinstalled the prior version and created an .htaccess file without problem, so Namecheap doesn’t think THAT is malware. Only the .htaccess created by the updated BPS is seen as malware by Namecheap.

Seems like something new was added to the .htaccess file generated by BPS which causes this issue. Is this true? Is this new thing added to the .htaccess file necessary or can it be removed, just as a workaround for right now?

As for your other comments, I don’t think I was merely a troublemaker “yelling FIRE” and “panicking” at all. I understand your frustration, but honestly, plug-ins are breaking constantly. They screw things up or get hacked or don’t play well with the new WordPress version. We had a trojan in one plug-in download, for pete’s sake. On top of all that, we are constantly being hit with hackers.

So while I appreciate you’re trying to protect your plug-in’s reputation, I’m just trying to protect my websites. After all the problems we’ve had, and as important as security is for our sites, I don’t think I was overreacting or panicking in the least.

Okay, thanks for the clarification. So anyone using WordPress installations at Namecheap who installs BPS will have this problem until Namecheap fixes the issue of their malware detection thinking .htaccess is malicious code.

This thread is ridiculously overwhelming, so it’s no wonder that different problems are being “lumped into” one problem. Perhaps separating out the problems into new threads would have been helpful.