Bubuku Post View Count

1.3.0

• New “at a glance” summary cards above the Stats tab: total views, last 30 days (with the change vs. the previous 30), AI referrals and AI bot crawling.
• New “Post views summary” widget on the WordPress dashboard (enable it from Screen Options if it’s hidden), with the same four figures plus a 7-day trend sparkline. Fully server-rendered from a background-refreshed snapshot, so it adds no extra queries or JavaScript to wp-admin.

1.2.3

• AI crawler tracking now recognizes 63 AI crawlers (up from 9), grouped into 4 categories — AI assistant, data scraper, AI search and AI training — each shown with its own color. Settings → Post View Count has a new collapsible “AI crawlers monitored” panel listing all of them with their vendor and category, and the “AI bot crawling” table in Stats shows a color dot next to each bot with a legend below it.
• New privacy setting: “Respect Do Not Track / Global Privacy Control”. When a visitor’s browser sends the DNT or Sec-GPC signal, the view is still counted (it was already anonymous, with no IP or user agent stored) but the optional device/referrer breakdown is skipped for that visit.
• Optional write buffer for high-traffic sites with a persistent object cache (Redis/Memcached): coalesces views for the same post into a single database write per minute instead of one per view. Off by default and has no effect without a persistent object cache.

1.2.2

• Evolution chart, period comparison, rising/falling content lists, device/referrer breakdown and the shortcode/block for showing view counts on the front end.
• Session dimensions: traffic broken down by device screen size and by where visitors came from (direct, search, social, AI assistants, etc.), never storing the raw referrer host or exact screen width.
• AI traffic reporting: a new “AI crawler tracking” setting (off by default) counts hits from known AI crawlers (GPTBot, ClaudeBot, PerplexityBot, CCBot, Google-Extended, Bytespider, Amazonbot, Applebot-Extended) in their own table, kept separate from the human view count; a new “AI traffic” section in Settings → Post View Count shows both AI referrals and crawler hits.

1.2.1

• Read-only query layer (Core\Query) powering most-viewed content, stale content, per-post stats, trends and summary — used by the new admin columns, WP-CLI commands.
• Sortable “Views” and “Last view” columns in the admin list table for every enabled content type.
• WP-CLI commands wp bbk-views top, wp bbk-views stale and wp bbk-views post <id> (only registered when WP-CLI is present).
• New: GET /bbk_postview/v1/trends REST endpoint (capability edit_posts, cacheable) for period-over-period view trends.

1.2.0

• The view counter now has its own database tables ({prefix}bbk_post_views, {prefix}bbk_post_views_daily), tracking the date and time of the first and last view per post in addition to the total — the first step towards analytics features (most-viewed content, stale content) planned for upcoming versions.
• New: a settings page under Settings → Post View Count. Choose which content types count views (defaults to Posts, same as before), exclude specific user roles (defaults to roles that can already edit content), optionally exclude known bots and crawlers (Googlebot, Bingbot, GPTBot, ClaudeBot, etc.), and set how long the daily view history is kept.
• New: a “delete all data now” button on the settings page to reset all recorded views without uninstalling the plugin.
• Improvement: the counter increment is now a single atomic upsert per table (no read-then-write), removing the last possible race condition under concurrent traffic.
• Improvement: existing views post meta is migrated automatically and incrementally (500 rows per batch via WP-Cron) into the new tables on upgrade — no data is lost, and the migration is safe to run more than once.
• Kept: the views post meta is still written on every view as a compatibility mirror for themes and queries that already read it (e.g. orderby=meta_value_num); a new views_last post meta exposes the last-view date the same way.
• Improvement: uninstall.php now removes the plugin’s own tables, options and deduplication transients (in addition to post meta), including on multisite. Whether to delete this data on uninstall is now configurable from the settings page (enabled by default, per WordPress.org guidelines).
• Note: this is a database schema change. Rolling back to 1.1.x after upgrading is safe — the views post meta is never removed, so the counter keeps working from where it was.

1.1.1

• Security: the view-count endpoint now also checks the request’s Origin/Referer against the site’s own URL, rejecting cross-origin browser requests in addition to the existing post_id validation and per-visitor deduplication.
• Improvement: internal refactor to a PSR-4 class structure (src/Core, src/Api, src/Frontend) — no functional change for site visitors.