Description
Effectively prevent automatic spam when a spam comment is posted with Kama Spamblock, a plugin that operates discreetly and remains completely invisible to users—no captcha codes required. The plugin not only blocks spam comments but also conducts thorough checks on pings and trackbacks to ensure the authenticity of backlinks.
Even if you are using an external comment system like Disqus, installing Kama Spamblock remains valuable. This is because autospam can be posted directly to the ‘wp-comments-post.php’ file, and the plugin serves as a robust defense against such comments.
Screenshots
Plugin settings on standart WordPress
Settings > Discussionpage.
Spam alert, when spam comment detected or if user have javascript disabled in his browser. This alert allows send comment once again, when it was blocked in any nonstandard cases.
FAQ
-
When posting a comment on the site, I received a message, ‘Antispam blocked your comment!’. Is this a normal function of the plugin?
-
No! The plugin is invisible to users. You should navigate to the ‘Discussion’ settings page in WordPress. At the bottom, you’ll find ‘Kama Spamblock settings.’ Set the correct ID attribute for the comment form submit button there. You can obtain this attribute from the ‘source code’ of your site’s page where the comment form is located. Look for:
type="submit" id="??????".
Reviews
Contributors and Developers
“Kama SpamBlock” is open source software. The following people have contributed to this plugin.
Contributors
“Kama SpamBlock” has been translated into 2 locales. Thank you to the translators for their contributions.
Translate “Kama SpamBlock” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Change Log
1.8.2
- Minor refactoring.
1.8.1
- Code refactoring.
kama_spamblock__process_comment_typeshook added.
1.8
- FIX: WordPress 5.5 support.
1.7.5
- FIX: bug with uniq code comparation
- minor code fixes
1.7.4
- CHG: change sanitize-options-on-save function – sanitize_key() to sanitize_html_class() – it’s not so hard but hard enough…
- CHG: ‘sanitize_setting’ function call. Seems it hasn’t have back-compat for wordpress versions less then 4.7
1.7.3
- FIX: options fix of 1.7.2
1.7.2
- CHG: move translation to translation.wordpress.org
- ADD: new ‘unique code’ option.
- IMP: some code improvements.
1.7.0
- BUG: Last UP bug fix…
1.6.0
- CHG: check logic is little change in order to correctly work with page cache plugins
1.5.2
- ADD: delete is_singular check for themes where this check work wrong. Now plugin JS showen in all pages
1.5.1
- ADD: js include from numbers of hooks. If there is no “wp_footer” hook in theme
1.5.0
- ADD: Russian localization