Bubuku Post View Count
| 开发者 |
lruizcode
bubuku |
|---|---|
| 更新时间 | 2026年9月23日 03:27 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-3.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
安装:
- Unzip the plugin ZIP file on your computer.
- Copy or move the resulting folder to the "wp-content/plugins/" directory of your WordPress installation.
- Log in to the WordPress admin area and navigate to the "Plugins" screen.
- Locate "Bubuku Post View Count" in the plugins list and click "Activate" to enable the plugin.
- Ensure your installation meets the requirements listed in the plugin header (WordPress and PHP versions) before using it in production.
常见问题:
How do I see the view count for a post?
Since 1.2.0 the source of truth is the plugin's own database table, but the total is still mirrored to post meta for backwards compatibility. You can keep using get_post_meta( $post_id, 'views', true ); the date of the last view is available as get_post_meta( $post_id, 'views_last', true ).
Does the 1.2.0 update lose my existing view counts?
No. On activation the plugin copies every existing views post meta into its new table in the background, in batches. The date of the last view isn't available for posts that were only counted before 1.2.0 — the count itself carries over intact.
Does uninstalling the plugin delete my view data?
Yes, by default — deleting the plugin removes its tables, options and deduplication data, in line with WordPress.org's guidelines against leaving data behind. You can turn this off from Settings → Post View Count if you'd rather keep your data for a future reinstall.
Can I choose which content types count views, or exclude certain user roles and bots?
Yes, since 1.2.0. Go to Settings → Post View Count to choose which content types are counted (only Posts by default, same as before), exclude specific user roles (roles that can already edit content are excluded by default), and optionally exclude known bots and crawlers. Unchecking a content type stops counting new views for it but never deletes the views already recorded.
Can I reset the view counts without uninstalling the plugin?
Yes. Settings → Post View Count has a "Delete all data now" button that clears every recorded view, with a confirmation prompt before it runs.
Does this plugin affect page load speed?
The lightweight counter is deferred and sends its request only after the page has accumulated five visible seconds, so it stays outside the initial rendering path. As with any analytics request, its actual server cost depends on the site's traffic and database performance.
Is this plugin compatible with multisite installations?
Yes, the plugin now includes multisite support, including in the uninstall routine.
Can I show the view count inside a post or page?
Yes. Use the [bbk_post_views] shortcode, or add the "Bubuku · Vistas del post" block in the block editor. Both show the current post's view count; add show_last_viewed="1" to the shortcode (or toggle "Mostrar la fecha de la última visita" on the block) to also show the date of the last view. A content type that isn't counting views, per your settings, shows nothing.
Can I see how views have evolved over time?
Yes. Settings → Post View Count includes a chart of views over time (day/week/month) and a comparison of the current 30-day period against the previous one, both drawn from the same data used by the REST/MCP trend endpoints.
Does the plugin respect "Do Not Track" or Global Privacy Control?
Yes, by default. When a visitor's browser sends the DNT or Sec-GPC signal, the plugin still counts the view (it's already anonymous — no IP or User-Agent is ever stored) but skips recording the optional device-width and referrer breakdown for that visit. You can turn this off in Settings → Post View Count if you'd rather always record the full breakdown.
更新日志:
- 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.
- 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.
- 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.
- 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 staleandwp bbk-views post <id>(only registered when WP-CLI is present). - New:
GET /bbk_postview/v1/trendsREST endpoint (capabilityedit_posts, cacheable) for period-over-period view trends.
- 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
viewspost 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
viewspost 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 newviews_lastpost meta exposes the last-view date the same way. - Improvement:
uninstall.phpnow 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
viewspost meta is never removed, so the counter keeps working from where it was.
- Security: the view-count endpoint now also checks the request's
Origin/Refereragainst 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.
- Fix: production zip was missing the Composer autoloader, causing a fatal error on activation. The plugin now uses its own lightweight autoloader and no longer depends on
vendor/at runtime. - Security: the view-count endpoint no longer accepts arbitrary/invalid post IDs, and now deduplicates repeated views per visitor instead of relying on a broken nonce check.
- Fix: race condition that could undercount concurrent views; the counter is now incremented atomically.
- Fix: the tracking script was loaded in the page
<head>with jQuery as an unused dependency instead of deferred in the footer. - Removed: translation loading — WordPress.org already serves translations automatically for public plugins since 4.6, and the previous implementation never worked (wrong textdomain path).
- Improvement: added multisite support to the uninstall routine.
- Compatibility: WordPress 6.2 - WordPress 6.5.3
- Compatibility: WordPress 6.1 - WordPress 6.2
- Fix some PHP errors
- Updated for WordPress 6.1
- Fix: Internationalization Issues
- Fix: It counted in categories.
- Initial release.