cartermason

Also, if you are paranoid about permissions like I am… you need to do another recursive chmod’ing back to 755 or whatever you’d like when you’re done. Kind of takes the fun out of an “automatic plugin upgrade” but it is easier than downloading, unpacking, and reuploading.

If you can ssh in to your server… A recursive chmod’ing of the plugins folder worked for me. I don’t know why it didn’t work when I chmod’d the plugins folder and the folder I was trying to upgrade, but I suspect it was because every single file in the folder needed the permissions changed in order for the upgrade to go through.

Now the automatic plugin upgrade feature works for me.

Try this, with the full path to your plugins directory at the end from the command line in an ssh session:

chmod -R 777 /the/path/to/your/plugins/directory

Yeah, this is not working for me, either. I’ve changed the permissions to 777 on the plug-ins directory, the individual directory for the plug-in I was trying to upgrade, and it did not work. Help!

I changed the permissions back to 755, since this did not resolve the issue.

A plugin that blocks spam should actually be attempting to target spam, not just targeting any client that has doesn’t do javascript. There’s been lots and lots of man-years put into spam recognition techniques, because the goal is to sort out what is spam and what is not. That’s what Akismet attempts to do.

With the exception of a very early release of wp-spamfree, I’ve had zero real comments blocked on my site as a result of wp-spamfree, but automated comment spam has virtually disappeared.

I agree with the original author of this thread, WP-SpamFree is AWESOME!!

Also, Akismet has blocked many legitimate comments in the past. I do use Akismet in conjunction with wp-spamfree, but I simply do not have the time to go through hundreds of spam comments in Akismet without wp-spamfree. If a legit comment from a human gets flagged by Akismet now, it’s pretty much the only comment there for me to read, since I do not get targeted by human comment spammers very often.

WP-SpamFree blocks entirely. It doesn’t take into account the fact that it might be wrong.

Isn’t there a way around that for a future release? Perhaps by modifying the blocked page with a way to prove you’re human. Just a thought… it seems like your criticism–especially since the core of it is that this might not work so well for a long time even though it works great right now–is a thing for the developer to keep in mind for future releases to make this absolutely amazing plug-in better rather than a reason to not use it on your blog.

I think even the ADA criticism could possibly be handled with this plug-in by tweaks rather than abandoning the concept.

And, by the way, I read your earlier comment about Bad Behavior. I had two blogs which were taken down because of that incident. A spam tool which can take down your entire blog is FAR more dangerous than anything you’ve listed here. Besides losing a modest amount of AdSense revenue, the downtime is freakin’ embarrassing!

And as someone engaged in the SEO industry, I was pissed to read what programmers wrote (correctly, I might add) in the posts WebGeek mentioned and elsewhere about Bad Behavior not properly validating search engine spiders properly. Blogs are a key tool for many SEO strategies. Using Bad Behavior would be irresponsible for anyone in charge of gaining traffic for a company through search engines.

wp-spamfree works, is being actively developed, and won’t take down your entire site even if it does block an extremely small number of users. Though I don’t have stats to back it up, my experience would lead me to believe Akismet would block more real users by sending real comments to its spam area which is too intense for most of us to give a regular thorough checking than wp-spamfree would deny real human comments.

Success!

Okay, this is a pain in the butt… but it works!

I have a modified .htaccess file, and I can’t allow WP to modify it, because it breaks my site every time it updates it. I’m guessing that you who are having the permalink static page problem also do not have WP automatically updating their .htaccess. So…

What fixed this problem of static pages not working with permalinks, I just had to resave my settings and then cut and paste the new .htaccess code from the permalinks page into my .htaccess file, upload, and then voila! The page works…

If I figure out how to make it so the automatic updating of .htaccess doesn’t break my site, I’ll report back to this thread and let y’ll know if that also fixes the static page permalink issue.

My post URL’s are working great. I just ported over a blog from b2evolution, and all’s well. I didn’t have a single URL change…

But I just tried to create a static page through WP’s admin, and the URL doesn’t work. All the other pages have the correct URL structure, but not the static pages. Has any one else encountered this?

Oh, and for those of you having the problem of WP rewriting your .htaccess and breaking it all over again… delete your .htaccess from the server and then reupload it. Or change the permissions manually and make it not writeable.