Version 3.0.0 released! | Peter's Custom Anti-Spam for WordPress | Forum
Back to the custom anti-spam plugin page
This is a pretty major release with a change in the audio file generation and added protection for registration forms.
- The generated audio files are now wav files. This makes them bigger than before, but is important as I couldn't easily vary the size of the audio files with mp3s. Now the wav files are "stretched" upon generation to a variable length by the sox filter, which is built in to most severs. Thanks to Jose for pointing out this problem.
- Following some testing on the beta release with registration form protection, this has been incorporated into the main code. See the bottom part of the settings section in the file to customize the registration form protection.
Download the release on the plugin page, as always:
http://www.theblog.ca/anti-spam
If you have a question not related to this specific release, please start a new topic.
11:55 am
It would be ideal to be able to disable the exec('sox') option at the top of the custom_anti_spam.php script. If you do not have sox installed on your server, the root user will see an error such as 'sh: sox: command not found' randomly in the shell.
You may also wish to append '> /dev/null 2>&1' to the end of the command. This will prevent the output from sox such as 'sox: STRETCH clipped X values...' to appear in the shell.
Great plugin!
If you mean to not include the audio files at all so that people can make their own, I would rather keep the release simple and just have people replace the files themselves, since the download size of the plugin isn't massive.
If you mean to disable the feature, you can simply change the value of this setting to "false":
// Set this to TRUE to enable wav files of the anti-spam words so that visually enabled users can comment
$cas_wav = true;
7:15 pm
Awesome plugin! I've found it very useful, and I love how you can add your own words to flavor it to your journal.
I'm having a bit of a problem with this plugin in conjunction with OpenID, though -- I have it so that users can post using an OpenID login on the comment page. However, when they are directed back to my site from the OpenID provider (I tested with LiveJournal), they're informed that they didn't enter the anti-spam verification -- even though, at that point, they should be logged in and it shouldn't be necessary. Any clue as to how I might fix this?
Admin edit: I've moved the discussion on this topic here, since it relevant to the plugin as a whole, not just to the 3.0.0 release.