Renamed to Onsite Spam Guard, plus a capability check on the spam-log bulk delete. Settings and logs carry over unchanged.<\/p>","1.1.1":"
Fixes legitimate Jetpack contact form submissions being wrongly flagged as spam. Recommended for anyone protecting Jetpack forms.<\/p>","1.1.0":"
Tabbed settings, an option to keep your data on uninstall, and multisite-wide cleanup.<\/p>","1.0.1":"
Adds explicit-field support to the integration API for REST\/JSON forms and prevents false rejections for content-only integrations.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3644063,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3644063,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3644063,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3644063,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3644063,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250},"banner.svg":{"filename":"banner.svg","revision":3644063,"resolution":false,"location":"assets","locale":false}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.2"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3644063,"resolution":"1","location":"assets","locale":"","width":2520,"height":2376},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3644063,"resolution":"2","location":"assets","locale":"","width":2520,"height":1140},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3644063,"resolution":"3","location":"assets","locale":"","width":2520,"height":972},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3644063,"resolution":"4","location":"assets","locale":"","width":2520,"height":1814}},"screenshots":{"1":"The tabbed settings page \u2014 the Guards tab, with individual guard toggles and per-guard thresholds.","2":"The Allowlist tab \u2014 allowed IPs, CIDR ranges, and emails, plus the trusted-proxy option.","3":"The Logging tab \u2014 log retention and the option to keep or delete data when the plugin is removed.","4":"The Spam Logs viewer \u2014 filter by guard and context, a user-agent column, and per-row and bulk delete actions."}},"plugin_section":[],"plugin_tags":[109,107,598,599,286],"plugin_category":[44,45,54],"plugin_contributors":[275434],"plugin_business_model":[],"class_list":["post-348743","plugin","type-plugin","status-publish","hentry","plugin_tags-antispam","plugin_tags-comments","plugin_tags-honeypot","plugin_tags-spam","plugin_tags-woocommerce","plugin_category-discussion-and-community","plugin_category-ecommerce","plugin_category-security-and-spam-protection","plugin_contributors-jeromewincek","plugin_committers-jeromewincek"],"banners":{"banner":"https:\/\/ps.w.org\/onsite-spam-guard\/assets\/banner-772x250.png?rev=3644063","banner_2x":"https:\/\/ps.w.org\/onsite-spam-guard\/assets\/banner-1544x500.png?rev=3644063","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/onsite-spam-guard\/assets\/icon.svg?rev=3644063","icon":"https:\/\/ps.w.org\/onsite-spam-guard\/assets\/icon.svg?rev=3644063","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/onsite-spam-guard\/assets\/screenshot-1.png?rev=3644063","caption":"The tabbed settings page \u2014 the Guards tab, with individual guard toggles and per-guard thresholds."},{"src":"https:\/\/ps.w.org\/onsite-spam-guard\/assets\/screenshot-2.png?rev=3644063","caption":"The Allowlist tab \u2014 allowed IPs, CIDR ranges, and emails, plus the trusted-proxy option."},{"src":"https:\/\/ps.w.org\/onsite-spam-guard\/assets\/screenshot-3.png?rev=3644063","caption":"The Logging tab \u2014 log retention and the option to keep or delete data when the plugin is removed."},{"src":"https:\/\/ps.w.org\/onsite-spam-guard\/assets\/screenshot-4.png?rev=3644063","caption":"The Spam Logs viewer \u2014 filter by guard and context, a user-agent column, and per-row and bulk delete actions."}],"raw_content":"\n
Onsite Spam Guard blocks spam on the forms your visitors actually use \u2014 WordPress comments, WooCommerce product reviews, and Jetpack contact form blocks \u2014 without sending anything to a third-party service, requiring an API key, or putting a CAPTCHA in front of your users.<\/p>\n\n
Protection is built from a pipeline of independent guards<\/strong>. Each guard is a small, focused check (a hidden honeypot field, a submit-speed gate, a keyword filter, and so on). Guards run in priority order, and the first one to fail blocks the submission. Every guard can be toggled and tuned from a single settings page, and every block can be logged for review.<\/p>\n\n No further configuration is required \u2014 sensible defaults are applied on activation.<\/p>\n\n\n No. Every check runs on your own server. Nothing about a submission is sent anywhere outside your site.<\/p><\/dd>\n No. All protection is invisible. The honeypot field is hidden, and the timing and behavioral checks happen in the background.<\/p><\/dd>\n When a submission is blocked (and logging is enabled), the plugin records the guard that blocked it, the form context, the reason, a short excerpt of the content, the visitor IP address, and the browser user-agent. Entries older than the retention window (default 30 days, configurable; set to 0 to keep them indefinitely) are pruned automatically. The plugin also registers suggested privacy-policy text you can add to your site's policy.<\/p><\/dd>\n By default the plugin uses the direct connection IP, because forwarded headers can be spoofed to bypass the allowlist. If your site sits behind a trusted reverse proxy, enable Trust proxy headers for IP detection<\/strong> under Spam Guard \u2192 Settings \u2192 Allowlist<\/strong>.<\/p><\/dd>\n By default a blocked comment or review is placed in the spam queue<\/strong> (Comments \u2192 Spam) rather than being rejected outright, so you can restore a false positive with one click \u2014 nothing is lost. Open Spam Guard \u2192 Spam Logs<\/strong> to see which guard blocked it and why, then loosen that guard on the settings page \u2014 for example, raise the link limit, lower the behavioral threshold, or add the sender to the allowlist. If you would rather reject blocked comments with an error message, enable that option under Spam Guard \u2192 Settings \u2192 General<\/strong>.<\/p><\/dd>\n No \u2014 it complements it. Onsite Spam Guard's guards run before<\/em> WordPress's own comment checks, and those built-ins still run underneath: the duplicate-comment check, the comment flood throttle, the Disallowed Comment Keys<\/strong> blocklist, and the \"hold a comment with this many links\" setting (all under Settings \u2192 Discussion<\/strong>). Its Keyword, Link limit, and Duplicate guards overlap those, so you can rely on either or both. What it adds on top is the honeypot, timing, signature, and behavioral checks core has no equivalent for, one settings screen with logging, and protection for WooCommerce reviews and Jetpack contact forms \u2014 not just comments.<\/p><\/dd>\n Yes. The timing and authenticity checks use a token whose signature does not expire (unlike a WordPress nonce, which would go stale on a cached page and block legitimate visitors), so full-page caching does not produce false positives.<\/p><\/dd>\n By default, yes \u2014 deleting the plugin (not just deactivating it) drops its database table, removes all of its options, clears its scheduled task, and purges its transients, on every site of a multisite network. If you would rather keep your settings and logs (for example, before reinstalling), turn off Delete all plugin data when this plugin is deleted<\/strong> under Spam Guard \u2192 Settings \u2192 Logging<\/strong> first.<\/p><\/dd>\n\n<\/dl>\n\n\nSpam guards<\/h4>\n\n
\n
Why you might choose it<\/h4>\n\n
\n
Works with<\/h4>\n\n
\n
\n
onsite-spam-guard<\/code> folder to \/wp-content\/plugins\/<\/code>, or install it through Plugins \u2192 Add New<\/strong>.<\/li>\n\n
Does this send my data to any external service?<\/h3><\/dt>\n
Will legitimate visitors see a CAPTCHA or extra step?<\/h3><\/dt>\n
What does it store, and for how long?<\/h3><\/dt>\n
I'm behind Cloudflare or a load balancer and the wrong IP is logged.<\/h3><\/dt>\n
A legitimate submission was blocked. What do I do?<\/h3><\/dt>\n
Does it replace WordPress's built-in comment moderation?<\/h3><\/dt>\n
Does it work with caching plugins?<\/h3><\/dt>\n
Does removing the plugin clean up after itself?<\/h3><\/dt>\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n