|
||||||
|
|
|
|
|
|
||
|
For the longest time, I couldn't figure out why the Spamlookup keyword plugin wasn't working for me. It would catch the built-in keywords, but it overlooked the keywords that I added. I think I may have figured it out:
Those are the plugin files that are bundled with the MT 3.3 installation. A bunch of them seem to be missing -- according to this page, here's what's supposed to be there: * Directory: mt/plugins/spamlookup/ There doesn't seem to be anyplace online to download those missing files. Argh. THRILLING UPDATE! As usual, I was wrong. Brad's comment below reveals the true reason it wasn't working. (In my defense, Spamlookup's interface is not totally idiot-proof, so it was left highly vulnerable to me.)
May 12, 2007 5:35 PM |
Permalink
| Comments (1)
Leave a comment |
Things and stuff. Subscribe to this blog's feed. 
|
||
|
|
|
|
Comments (1)
May 21, 2007 10:56
Hi... just ran across this.
Those installation instructions are from my site and are rather old. The front door to the Trac install for SpamLookup says that, but if you found this page through a Google search you may have missed it. I've updated the page to repeat the 'out of date' notice there.
Basically, those files are part of the standalone SpamLookup plugin that was outdated with the release of Movable Type 3.2. Unless you've removed files from your MT installation, you should still have everything you need to run the plugin.
As for your problem, I can suggest a couple of things to check:
1. SpamLookup can be configured on a system-wide AND blog-level basis. If you have keywords configured for BOTH, SpamLookup will use the blog-level keyword list instead of the system-wide list. So be wary of that. If you have blog-level settings and didn't mean to, you can click the 'Reset' button at the blog-level to clear those settings.
2. Check your system-wide activity log for any errors.
3. It has come to our attention that one of the IP blacklist services has closed it's doors. 'opm.blitzed.org' is no longer functional, so if you use IP blacklist lookups, make sure that server is no longer specified (otherwise, you'll experience some lengthy delays for posting comments).
Hope that helps.