Blacklists keep on rolling :p
After the release of WPBlacklist 2.6, I got a couple of reports about a problem with the path in the installer utility. I had put the path in for my server where the WP installation is in the root server and had not tested things out thoroughly enough to catch the fact that this code would fail if somebody had WP installed in a sub-folder. I’d created a fix and was about to release a bug-fix release when a few other problems caught my eye. So I fixed all of them but then got caught up in some other stuff and didn’t have the time to test any of the changes till today. I guess comment spam is on the rise again because I’ve been getting a lot of reports from people who’ve tried the WPBlacklist plugin and found the error. So, to stem the tide of complaints, I decided to quickly test my changes and release WPBlacklist 2.6.1 :p Enjoy!
Update: Since everybody seems to link to this entry for WPBlacklist, I thought I’d add an update to point to the WPBlacklist page which actually has the latest version, which at the time of this update had a release of WPBlacklist which was 3 sub-versions ahead :p
[…] rases and automatically moderate them or delete them. You can get Farooks Blacklister from sm.farook.org/index.php?p=149 Note: Nothing is […]
[…] Hace poco que han empezado a meterme spam en los comentarios de blog, así que he instado WPBlacklist para filtrar en contenido de los comentarios. Incorpora una utilidad que busca y examina en todo […]
[…] This is why I dont’ like IP address blacklists, and why I don’t use one of the many WordPress plugins that use that technique, although I greatly respect the authors’ works. What I […]
hummm, I just checked my blacklist but didn’t find any “/” entry, they are all preceded with “”, I’m still getting that php error!
First, thanks for the plugin. It’s working wonderfully. I was running WP 1.2 but recently upgraded to 1.5 beta 1. I installed WPBlacklist but got errors on the installer (I had to chmod the installed files to 775) and then on the configuration. The three files in the wp-admin folder: wpblacklist.php, wpblmoderate.php and wpblsearch.php all declare the function add_magic_quotes. Apparently in WP 1.5 beta 1, this is already declared. In those 3 files, starting on line 7, you need to delete from line 7 to line 16 (or just comment them out). Once that is done, WPBlacklist works great.
2.6.1 not worky very well with wordpress 1.5. At least the management php files. Get stuff like:
PHP Fatal error: Call to a member function on a non-object in /foo/wpblacklist.php on line 89
line 89:
$results = $wpdb->get_results($sql);
*sigh*, still there after the upgrade to 2.8
Nope, WPBlacklist will not work with WP 1.5 yet since I just learnt of the release – been too busy to keep track of WP releases and so didn’t know that they’d come out of Alpha … not to mention even done a full release :p I’ll try to work on the code this weekend and come up with a new release that works with WP 1.5 … if you are really impatient, you can probably read some of the instructions given about in previous comments to get WPBlacklist working with WP 1.5 Alpha by somebody else … not sure if that works with the final release though ..
alright, thanks for the info. 🙂
[…] ²’è£ã€‚ä¸éŽå¾žç›¸é—œçš„介紹裡，先記下幾個未來å¯èƒ½åŽ»å˜—試的 plugins： WPBlacklist comment spam management based on blacklist Spam Karma Uses an extensive array of […]
[…] ent spam Filed under: Uncategorized — Chris @ 8:59 am I just installed this WPBlacklist plugin to kill comment spam in wordpress using jay allen’s blacklist.txt. It wasn’t quite update […]
[…] Online Poker/ Texas Hold Em your day of spamming is over!! The WP Plugin can be found here
3 Responses
[…]
[…] Some of the ones I will be reviewing for possible use will be: AuthImage Spammer Tarpit WP Blacklist Spam Karma WP-Hashcash dns-anti-spam TrencaSpammers
[…]
I get the following error when I try to run Blacklist Configuration w/v. 2.6.1
Fatal error: Call to a member function on a non-object in /home/.illustrator/dial_tone/dubbayoo.net/wp-admin/wpblacklist.php on line 89
How do I fix this?