From 2c9bc9f5fe9383a6e99fd49ce699e855701dc663 Mon Sep 17 00:00:00 2001 From: Chris Portscheller Date: Fri, 13 Nov 2026 19:34:06 -0600 Subject: [PATCH] Release 2.12.0 with separate request outcome analytics --- cdn-files/plugin-info.json | 6 +++--- changelog.txt | 6 ++++++ readme.txt | 17 ++++++++++++++++- webdecoy.php | 4 ++-- 4 files changed, 27 insertions(+), 6 deletions(-) diff --git a/cdn-files/plugin-info.json b/cdn-files/plugin-info.json index 47783b0..0556125 100644 --- a/cdn-files/plugin-info.json +++ b/cdn-files/plugin-info.json @@ -1,17 +1,17 @@ { "name": "WebDecoy Bot Detection", "slug": "webdecoy", - "version": "2.11.4", + "version": "2.12.0", "author": "WebDecoy", "author_profile": "https://webdecoy.com", "requires": "6.1", "tested": "7.1", "requires_php": "7.4", - "download_url": "https://cdn.webdecoy.com/wordpress/webdecoy-2.11.4.zip", + "download_url": "https://cdn.webdecoy.com/wordpress/webdecoy-2.12.0.zip", "sections": { "description": "

WebDecoy provides enterprise-grade bot detection and fraud protection for WordPress websites. Unlike simple CAPTCHA solutions, WebDecoy uses a layered defense approach that analyzes visitors from multiple angles — including deterministic tripwires that catch scanners with zero false positives.

Key Features

", "installation": "
  1. Upload the plugin files to /wp-content/plugins/webdecoy
  2. Activate the plugin through the Plugins menu
  3. Tripwires and local protection are active out of the box — no API key required
  4. Optionally go to WebDecoy > Settings > WebDecoy Cloud to connect for centralized monitoring and enforcement
", - "changelog": "

2.11.4

2.11.3

2.11.2

2.11.1

2.11.0

2.10.6

2.10.5

2.10.4

2.10.3

2.10.2

2.10.1

2.10.0

2.9.1

2.9.0

2.3.1

2.3.0

2.1.0

2.0.0

1.3.0

", + "changelog": "

2.12.0

2.11.4

2.11.3

2.11.2

2.11.1

2.11.0

2.10.6

2.10.5

2.10.4

2.10.3

2.10.2

2.10.1

2.10.0

2.9.1

2.9.0

2.3.1

2.3.0

2.1.0

2.0.0

1.3.0

", "faq": "

Does WebDecoy slow down my site?

No. WebDecoy adds negligible latency; tripwire checks are a fast path lookup and clearance minting is idle-deferred.

Will it block search engines?

No. WebDecoy automatically allows 60+ known good bots including all major search engines, and tripwires only fire on hidden paths no legitimate crawler follows.

" }, "icons": { diff --git a/changelog.txt b/changelog.txt index 4056f04..16b80ba 100644 --- a/changelog.txt +++ b/changelog.txt @@ -1,5 +1,11 @@ *** WebDecoy Bot Detection Changelog *** += 2.12.0 - 2026-11-13 = +* Added: separate request counters on Dashboard and Statistics for WebDecoy blocks (HTTP 403), throttles (429), challenges and decisions withheld by monitor mode or safety checks. Repeated blocks count even when no new detection row is saved. +* Added: Today, 7-day and 30-day UTC calendar comparisons, with the tracking start time shown. Counts start after upgrade; historical requests are not reconstructed. +* Privacy: request counters keep only an hourly bucket, outcome and count for 30 UTC calendar days. Requests stopped by another firewall or served before WordPress are outside these counters. +* Fixed: counter storage failures do not alter the protection response or display database errors. + = 2.11.4 - 2026-11-11 = * Added: after a week on your site, WebDecoy asks once for a review on WordPress.org, naming how many bot visits it counted. Only administrators see it, only on the dashboard and WebDecoy pages, and only when bots were counted. Choose Leave a review, Maybe later or Don't ask again. diff --git a/readme.txt b/readme.txt index 2f00906..cabfaca 100644 --- a/readme.txt +++ b/readme.txt @@ -4,7 +4,7 @@ Donate link: https://webdecoy.com Tags: ai crawlers, bot analytics, bot detection, woocommerce, card testing Requires at least: 6.1 Tested up to: 7.1 -Stable tag: 2.11.4 +Stable tag: 2.12.0 Requires PHP: 7.4 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html @@ -39,6 +39,12 @@ Most site owners have no idea how much of their traffic is GPTBot, ClaudeBot, By Only a count per bot per hour is kept: no IP addresses, no pages, and nothing about human visitors. Pages served from a page cache never reach WordPress, so the counts are minimums. += See detections and actual blocked requests separately = + +A saved detection is a finding, not a count of every blocked request. Dashboard and Statistics now separate detection rows from WebDecoy HTTP blocks, throttles, challenges and decisions withheld by monitor mode or safety checks. Repeated requests from a blocked address increase the request counter without creating duplicate findings. + +Compare Today, 7 days and 30 days in UTC calendar windows. Tracking starts after upgrading to 2.12.0, with no historical backfill. Only requests reaching WordPress PHP and handled by WebDecoy count; another firewall's blocks and cached responses are outside this view. Local counters need no account. + = Stop WooCommerce card testing and fake orders = Card-testing bots run stolen card numbers through your checkout. You pay a gateway fee for every attempt, your decline rate climbs until the processor takes notice, and real orders drown in the noise. WebDecoy watches checkout the way a fraud analyst would: @@ -315,6 +321,12 @@ The bundled good-bot list (sdk/src/GoodBotList.php) stores a documentation URL f == Changelog == += 2.12.0 = +* Added: separate request counters on Dashboard and Statistics for WebDecoy blocks (HTTP 403), throttles (429), challenges and decisions withheld by monitor mode or safety checks. Repeated blocks count even when no new detection row is saved. +* Added: Today, 7-day and 30-day UTC calendar comparisons, with the tracking start time shown. Counts start after upgrade; historical requests are not reconstructed. +* Privacy: request counters keep only an hourly bucket, outcome and count for 30 UTC calendar days. Requests stopped by another firewall or served before WordPress are outside these counters. +* Fixed: counter storage failures do not alter the protection response or display database errors. + = 2.11.4 = * Added: after a week on your site, WebDecoy asks once for a review on WordPress.org, naming how many bot visits it counted. Only administrators see it, only on the dashboard and WebDecoy pages, and only when bots were counted. Choose Leave a review, Maybe later or Don't ask again. @@ -524,6 +536,9 @@ Safety release. Please update. This version deliberately makes the plugin do les == Upgrade Notice == += 2.12.0 = +Separate blocked-request counters from saved detections. New counters start after upgrade; no historical backfill. Local analytics need no account. + = 2.10.6 = Restores classic WooCommerce checkout protection when WebDecoy loads before WooCommerce. Recommended for WooCommerce stores. diff --git a/webdecoy.php b/webdecoy.php index dea7e5e..5f4798e 100644 --- a/webdecoy.php +++ b/webdecoy.php @@ -3,7 +3,7 @@ * Plugin Name: WebDecoy - AI Traffic Analytics & Bot Protection * Plugin URI: https://webdecoy.com/wordpress * Description: Understand AI crawler visits and bot identity evidence in WordPress, with local analytics and protection against spam, login abuse, and WooCommerce card testing. - * Version: 2.11.4 + * Version: 2.12.0 * Requires at least: 6.1 * Requires PHP: 7.4 * Author: WebDecoy @@ -41,7 +41,7 @@ function str_starts_with(string $haystack, string $needle): bool } // Plugin constants -define('WEBDECOY_VERSION', '2.11.4'); +define('WEBDECOY_VERSION', '2.12.0'); define('WEBDECOY_PLUGIN_FILE', __FILE__); define('WEBDECOY_PLUGIN_DIR', plugin_dir_path(__FILE__)); define('WEBDECOY_PLUGIN_URL', plugin_dir_url(__FILE__));