Custom Captcha Field for Fluent Forms
Adds a “Custom Captcha” field to the Fluent Forms editor with three challenge types: Image captcha — a 6-character code rendered as an image, with customizable text color and a transparent background by default so it blends with any form design Math captcha — a simple arithmetic question rendered as an image Question and answer — you define the question (field label) and the expected answer Challenges are single-use and expire after 15 minutes. Answers are stored server-side via WordPress transients — nothing is exposed to the browser except the image itself. Visitors get a refresh button to request a new challenge, and the captcha automatically renews after each AJAX submission, so it also works on cached pages. On top of the captcha you get two extra spam defenses: Time-trap (optional, off by default) — submissions completed faster than a human possibly could are rejected via an HMAC-signed timestamp; enable it and set the minimum submit time per field Disposable email blocking (optional, on by default) — rejects submissions where an email field uses a temporary/disposable email domain like mailinator.com or yopmail.com; extend the list with the ffc_captcha_blocked_email_domains filter Everything runs on your own server: no external captcha service, no API keys, no cookies, no visitor data sent anywhere. Requirements Fluent Forms is required. The PHP GD extension is recommended for image rendering (with a plain-text fallback when unavailable). How To Use Activate the plugin Edit a form in Fluent Forms — a new “Custom Captcha” field appears in the editor Drop it into your form and pick the captcha type in the field settings Optionally set the text color, background color (RGB values like “68, 68, 68”, or “transparent”) and error message
Kama SpamBlock
Kama Spamblock blocks simple automated comment spam. It is invisible to normal visitors and does not use captchas. The plugin protects the standard WordPress comment endpoint, wp-comments-post.php. It adds a small check to the comment form. Direct requests that skip the form are blocked. This is a basic check, not proof that a person wrote the comment. Bots that load the page and run JavaScript can pass it. Kama Spamblock does not replace a full anti-spam service. It also checks pings and trackbacks for a link back to your site. Even if you are using an external comment system like Disqus, Kama Spamblock can add lightweight protection. Automated requests can be posted directly to the ‘wp-comments-post.php’ file, where the plugin can block basic bots. Simple and effective protection Kama Spamblock combines several small checks that are inexpensive for the site and invisible during normal commenting: The protective field name and its unique code rotate together every four hours. Ten recent pairs remain valid for pages served from full-page cache. Each marker is tied to the specific WordPress post, so a marker copied from another comment form is rejected. The form must remain open for at least three seconds before it can be accepted. Protective fields are added only after interaction with the comment submit button. If a valid comment is blocked, a JavaScript-only retry form preserves the entered data. The retry challenge changes its HTML structure to make basic scraping less reliable. Pingbacks and trackbacks must return a successful HTTP response, non-binary content, and a real backlink. These checks deliberately remain lightweight. A capable bot that loads the page, runs JavaScript, and reproduces normal browser behaviour can still pass them. Using Kama Spamblock with other anti-spam plugins Kama Spamblock can work with a full anti-spam plugin or service. It blocks simple direct spam requests first. The other tool can then check the comments that remain. For example, it can analyse comment text, reputation, or behaviour. The plugins complement each other. For this combination to work as intended: The other plugin should use the standard WordPress comment flow, or check comments after Kama Spamblock allows them. The site must show the standard comment form and allow the plugin’s JavaScript to run. Set the correct ID for the form’s submit button in the plugin settings. Test the setup if another plugin replaces the comment form, uses AJAX, or sends comments to its own endpoint. Kama Spamblock may need extra integration, or it may not check those comments.