Conditional CAPTCHA
| 开发者 | solarissmoke |
|---|---|
| 更新时间 | 2018年10月20日 11:16 |
| 捐献地址: | 去捐款 |
| PHP版本: | 4.0 及以上 |
| WordPress版本: | 5.0 |
详情介绍:
- If they fail, then the comment will be automatically discarded or trashed (and won't clutter up your spam queue).
- If they pass, it will be allowed into the spam queue (or approved, if you so choose). This means that any false positives from Akismet will be easily identified without you having to trawl through all the spam comments manually.
安装:
- Upload the wp-conditional-captcha folder to the
/wp-content/plugins/directory (or use the Wordpress auto-install feature) - Activate the plugin through the 'Plugins' menu in WordPress
- The settings for the plugin can be accessed from the Plugins administration menu.
常见问题:
I've installed it, now how do I check that it works?
You can try posting a spammy comment on your blog (make sure you're logged out) to check that it works, and to see what it looks like. Posting a comment with viagra-test-123 in the author/name field will always get it flagged by Akismet. If you are using basic mode, make sure you use a name and email that have not got a previously approved comment.
Does this plugin work with other comment form modification plugins, or with themes that use Javascript to handle comment submission?
Conditional CAPTCHA relies on WordPress' native form handling procedures. This means it will not work with plugins or themes that generate and process their own comment forms. Such plugins include WP AJAX Edit Comments, tdo-miniforms, Backtype and Contact Form 7. If comment submissions on your site are processed using AJAX, then the plugin will not work.
How long does the commenter have to complete the CAPTCHA?
There is a time limit of 10 minutes for the CAPTCHA to be submitted, otherwise it will be ignored even if it is correct.
What does the option to disable Akismet's comment history do?
Akismet stores a history for all comments on your site. It records whether or not it flagged the comment as spam, and any changes that you or other administrators make to the comment's status afterwards. This history is never deleted, and (in my view) just bloats your WordPress database without being at all useful. Selecting this option will prevent Akismet from storing comment histories. Note that this is feature is somewhat experimental, and not endorsed by the folks who wrote Akismet.
Didn't you say before that the plugin works with TypePad Antispam?
Yes, but not any more. The TypePad Antispam plugin hasn't been updated in over 4 years, and is not compatible with the latest version of WordPress.
更新日志:
- Drop support for reCAPTCHA v1 API which has been shut down.
- Fix handling of array inputs that other plugins might inject into the comment form.
- Add support for the new No CAPTCHA ReCAPTCHA
- Fix PHP warnings on CAPTCHA page when other plugins have injected arrayed content into the contact form.
- Allow line breaks in custom prompt message.
- Add a "Try Again" button for failed CAPTCHAs, instead of telling users to go back in their browser.
- Add CSRF protection to settings page.
- Revert all the changes made in version 3.5. It breaks way too many things.
- Changed logic to give priority to WordPress' built-in discussion options (especially moderation keywords/blacklist).
- Added HTTPS compatibility for ReCAPTCHA.
- Bugfix: make sure that WordPress can set commenter cookies when a CAPTCHA is completed correctly.
- Added a basic mode. The plugin no longer needs Akismet in order to work!
- Added some options to tweaks Akismet's behaviour: prevent history and prevent checking comments from logged-in users
- Fix to ensure that XML-RPC requests are not intercepted
- Introduced some compatibility checking
- Don't intercept comments submitted via AJAX.
- Add workaround for a bug in the latest version of Akismet, where comments from administrators can be flagged as spam.
- Added the option to customise the CAPTCHA prompt text.
- Minor tweaks to the settings page.
- Performance improvement to reduce size of plugin options
- Tweaked settings page to be more user friendly
- Minor changes to the behaviour of the plugin, as a result of changes in the latest version of Akismet.
- Bugfix: settings page Javascript caused errors when using jQuery < 1.6
- Added the option to leave comments for unsuccessful CAPTCHAs in the spam queue (provided the pass action something different)
- Bugfix: Options from previous versions of the plugin were not being properly upgraded
- Bugfix: Admin page Javascript was not compatible with jQuery >1.5.2
- Bugfix: Use blog character set instead of defaulting to UTF-8
- Better preview of CAPTCHA page
- Added basic validation of reCAPTCHA API keys
- Minor usability improvements
- Bugfix: don't mangle Unicode characters when submitting a CAPTCHA. Thanks to Mantas for pointing this out.
- Updated to fix issue with Akismet version 2.5.0 and Wordpress 3.0.3 when set to trash failed comments
- Added the ability to customise the appearance and language of reCAPTCHA
- Ensure that passed CAPTCHAs are reported as false positives to Akismet/TypePad Antispam. Thanks to Kevin for the suggestion.
- Added the option to place passed comments in the moderation queue
- Added support for non-js reCAPTCHA
- Updated reCAPTCHA API interface
- Modified upgrade routine because of changes to plugin update handling in Wordpress 3.1
- Added the ability to preview the CAPTCHA page from within the administration interface
- Minor performance optimisations
- Raised minimum Wordpress version to 2.8
- Bugfix: don't intercept spammy pingbacks and trackbacks. Thanks to Kevin for reporting this.