Init View Count – AI-Powered, Trending, REST API
| 开发者 | brokensmile.2103 |
|---|---|
| 更新时间 | 2026年8月29日 23:17 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Init View Count is a fast, clean plugin to track post views without clutter. It:
- Uses REST API and JS to count real views
- Prevents duplicate counts with session/local storage
- Stores counts in meta keys like
_init_view_count,_init_view_day_count, etc. - Provides
[init_view_count]and[init_view_list]shortcodes - Includes
[init_view_ranking]shortcode with tabbed ranking by time range - Supports template overrides (like WooCommerce)
- Lightweight. No tracking, no admin bloat.
- Includes REST API to query most viewed posts
- Supports pagination in
[init_view_list]via thepageattribute - Batch view tracking support to reduce REST requests on busy sites
- Optional strict IP-based filtering to block fake view requests posted directly to the REST endpoint
- Includes a Dashboard widget to monitor top viewed posts directly in wp-admin
- Learns site-wide traffic shape (hourly & weekday) via AI-powered smoothing
- Shapes cached and updated efficiently with minimal overhead
- Safe reset action to rebuild patterns automatically
- Fully integrated with Trending Engine v3 for uplift-based scoring
- Native Block Editor (Gutenberg) support with 3 dedicated blocks, no build step required
- Abilities API support (WordPress 6.9+) — read-only abilities for AI agents and automation tools
安装:
- Upload plugin to
/wp-content/plugins/init-view-count/ - Activate via Plugins menu
- Use
[init_view_count]or[init_view_list]in your content - Customize settings in Settings → Init View Count
屏幕截图:
![Shortcode builder for [init_view_list] – generate view-based post lists with custom templates.](https://cdn.jsdelivr.net/wp/init-view-count/assets/screenshot-2.png)
![Shortcode builder for [init_view_ranking] – generate tabbed rankings for different view ranges.](https://cdn.jsdelivr.net/wp/init-view-count/assets/screenshot-3.png)
![Shortcode builder for [init_view_count] – display view count for current post with format options.](https://cdn.jsdelivr.net/wp/init-view-count/assets/screenshot-4.png)
常见问题:
Can I reduce the number of view requests sent to the server?
= Can I customize the layout of the list? =\
Yes. Use the template attribute in [init_view_list] (e.g. template="grid"), and override the corresponding file in your theme like WooCommerce templates.
= Does it work with custom post types? =\
Yes. Just set post_type="your_custom_type" in the shortcode or REST query.
= How does it avoid duplicate views? =\
Init View Count uses both time delay and scroll detection via JavaScript, and stores viewed post IDs in either sessionStorage or localStorage (your choice).
= Is the view count updated immediately? =\
Yes. When the scroll+delay conditions are met, the count is updated via REST API and saved using update_post_meta().
= What meta key is used to store views? =\
By default:
_init_view_count(total)_init_view_day_count_init_view_week_count_init_view_month_count\ These keys can be changed via theinit_plugin_suite_view_count_meta_keyfilter. Trending scores are calculated separately and stored in a transient. = Can I display view counts in my template manually? =\ Yes. Useget_post_meta($post_id, '_init_view_count', true)or similar keys. Or use[init_view_count]shortcode in post content.
/top) are cached using transients.
= Can I use it in block editor / Gutenberg? =\
Yes — since version 1.23 there are 3 native blocks (search "View Count", "Popular Posts List", "View Ranking" in the block inserter, under the "Init View Count" category), each with its own settings panel and live preview. You can still use the classic Shortcode block with [init_view_count] / [init_view_list] / [init_view_ranking] if you prefer.
= What is Abilities API support and do I need it? =\
Since version 1.23, on WordPress 6.9+ the plugin registers two read-only Abilities (init-view-count/get-post-views and init-view-count/get-top-posts) via the core Abilities API, so AI agents and automation tools can discover and query view-count data in a standardized way. This is entirely optional and has no effect on sites without the Abilities API (WordPress below 6.9) or on how the plugin otherwise works — no view/increment/reset ability is exposed.
= Does it track bots? =\
No. Since counting only happens after scroll and delay via JavaScript, bots like Googlebot are naturally excluded.
= Can I sort posts by views in WP_Query? =\
Yes. Use 'meta_key' => '_init_view_count' and 'orderby' => 'meta_value_num' in your WP_Query args.
Yes. You can enable batch view tracking in the plugin settings. Instead of sending one request per view, views will be stored in the browser and sent in a group once the threshold is reached.
Should I enable "Require REST nonce verification"?
It's optional and off by default. Enabling it makes the /count endpoint reject requests that don't carry a valid WordPress REST nonce, which helps block fake POST requests sent directly to the endpoint. However, WordPress nonces expire after roughly 12-24 hours. If your site uses full-page caching with a long TTL, cached pages will keep serving an old nonce and view counting will quietly stop working on those pages until the cache refreshes. Leave it off on sites with long-lived page caching, or make sure the cache is purged/refreshed regularly. The /top endpoint is unaffected either way, since it's read-only and public by design.
更新日志:
2.0.1 – August 29, 2026
- Bug fix: on a site where the admin had never opened and saved Settings → Init View Count at least once, the day/week/month view counters would keep incrementing normally (that code path defaults to "enabled" when the option doesn't exist yet) but would never be reset by the daily cron (that code path had no default and treated the missing option as "disabled"). Reading
_init_view_day_countdirectly would show it growing forever instead of rolling over into_init_view_day_yesterday. All reads of the day/week/month enable options now consistently default to enabled, matching the REST counting logic and the settings page's default-checked checkboxes - Bug fix: setting "Delay before counting" to
0did not actually count views immediately — it silently fell back to the default (15000ms) or, depending on the browser, sometimes did not count at all. Same issue affected "Scroll percent required" set to0. Root cause was avalue || fallbackpattern in the front-end script, which treats a valid0as falsy and always substitutes the default. Both options are now validated on save, enforced again at output time (so sites that already had0stored take effect without needing to re-save), and parsed correctly in the front-end script - Bug fix: on pages shorter than the viewport (nothing to scroll), the scroll-percent check could never pass, because the scroll threshold was only ever evaluated inside the
scrollevent handler, and noscrollevent fires when there is nothing to scroll. The script now also evaluates the scroll condition once immediately after the page settles, in addition to on scroll - Change: "Delay before counting" is now clamped to a 100ms–600000ms (10 min) range, and "Scroll percent required" to a 1%–100% range.
0is intentionally disallowed for both: a 0ms delay risks counting views before the page has actually rendered, and a 0% scroll requirement would silently disable the scroll check entirely - Performance: the daily cron reset (
init_plugin_suite_view_count_reset_counts— rolls today's/this week's/this month's view counts into yesterday/last-week/last-month and clears the counters, across every publicly-registered post type, no configuration needed) used to loopget_post_meta()+update_post_meta()+delete_post_meta()per post per counter, which on sites with many posts could mean tens of thousands of individual DB queries in a single cron run. It now performs the same rollover in batched, direct SQL (500 posts per query by default, filterable viainit_plugin_suite_view_count_reset_batch_size), cutting query count from O(number of posts) to O(number of batches), then flushes the object cache for affected posts in one pass — using the object cache's batch-delete method when the active cache backend supports it (WordPress core does, since 6.0), and falling back to individual cache-delete calls otherwise for compatibility with third-party object cache drop-ins (Redis, Memcached, etc.) that may not implement it. Behavior is unchanged: every eligible post still ends up with a "previous period" value (0 if it had no views), preserving correct results inGET /top?range=yesterday|last_week|last_month; verified against the previous per-post logic across 1,000+ randomized scenarios before release - Internal: extracted shared helper functions (
init_plugin_suite_view_count_atomic_increment(),init_plugin_suite_view_count_flush_meta_cache(), IP-detection helpers, the K/M/B number formatter, and the new integer-clamping helper) out ofrest-api.phpandshortcodes.phpinto a newincludes/utils.php, loaded first. No behavior change, purely a code-organization cleanup - Internal: replaced
extract()in the internal template-rendering helper with an explicit variable assignment for WPCS compliance (WordPress.PHP.DontExtract); the helper is only ever called with a single fixed key, so behavior is unchanged
- Breaking change:
Requires at leastis now WordPress 6.9. This major version bump reflects two significant new features added in this release — Abilities API support and native Block Editor support (see below) - New: Abilities API support (WordPress 6.9+). Registers two read-only abilities under the
init-view-countcategory so AI agents and automation tools can discover and query view-count data through the standardizedwp_register_ability()registry, without needing to know the plugin's REST routes: init-view-count/get-post-views— returns the tracked view count for a single post (total/day/week/month)init-view-count/get-top-posts— returns a ranked list of the most viewed posts (wraps the exact same logic asGET /topand the[init_view_ranking]shortcode, so results always match)- No write/destructive abilities are registered, by design — nothing can increment or reset view counts through this API
- New: Block Editor (Gutenberg) support with 3 dynamic blocks matching the existing shortcodes 1:1 — View Count, Popular Posts List, and View Ranking (Tabbed). Each block is a thin PHP wrapper (
render.php, via therenderfield inblock.json) that builds the same shortcode tag and callsdo_shortcode(), so there is no duplicated display logic and output always matches the shortcode. The editor script is plain vanilla JavaScript (no build step, no JSX) usingServerSideRenderfor a live preview directly in the editor Tested up to: 7.1
- Bug fix: sticky posts were no longer being excluded from view-based rankings.
GET /top(and by extension the[init_view_ranking]shortcode, which consumes it) and the hourly Trending Engine calculation could show a sticky post at the top of the list regardless of its actual view count, since the underlyingWP_Querycalls were missingignore_sticky_posts. All ranking queries now explicitly ignore sticky posts, consistent with[init_view_list], which already did this correctly - Performance: the scroll-progress listener in the front-end tracking script (
script.js) is now throttled withrequestAnimationFrameinstead of running its calculation on every singlescrollevent, and is automatically removed once the scroll threshold is reached — reduces main-thread work on long pages and low-end mobile devices. The listener is also registered aspassiveto avoid blocking scroll rendering. Also fixed a theoretical division-by-zero edge case when a page's content is shorter than the viewport
- New optional setting: Require REST nonce verification? (Settings → Init View Count). Off by default. When enabled,
POST /countrequires a validX-WP-Nonceheader and rejects the request with403otherwise, helping block direct spam POSTs to the endpoint that skip loading the page first - The nonce is only added to the localized config, and the client only sends the header, when this setting is turned on — zero overhead otherwise
GET /topis intentionally excluded, since it's a read-only, public-by-design endpoint- Documented trade-off: WordPress nonces expire after ~12-24h, so sites using long-lived full-page caching may see view counting silently stop working on stale cached pages until the cache refreshes. See the Settings page description and the FAQ for details
- i18n: added missing English source strings (
Invalid post ID.,Not enabled for view counting.) plus all new strings from this release tolanguages/init-view-count.pot, with ready-made Vietnamese translations inlanguages/init-view-count-vi.po/.mo
- Performance & accuracy overhaul for the
/countREST endpoint: - View counters (
total,day,week,month) are now incremented with a direct, atomic SQLUPDATE ... SET meta_value = meta_value + 1instead of a read-then-writeget_post_meta()+update_post_meta()pair, removing a race condition that could drop views under concurrent traffic - The value returned to the client is derived locally (
cached value + 1) instead of re-querying the database after the write, saving a query per counted key - The object cache for a post's meta is now invalidated exactly once per post per request (after all of its keys are updated), instead of once per key
- Traffic Shape Learner: hourly bin tracking is now buffered per-request and flushed with a single
get_option()/update_option()call onshutdown, instead of once per counted post — meaningful reduction in option writes on sites using batch view tracking - General hardening pass across the REST API code path (WPCS-compliant direct queries with documented
phpcs:ignorejustifications, no behavior change to existing filters/actions)
- Hotfix: Daily/Weekly/Monthly counters now enabled by default
init_plugin_suite_view_count_enable_day→ default = 1init_plugin_suite_view_count_enable_week→ default = 1init_plugin_suite_view_count_enable_month→ default = 1- Fixes issue where counters stayed disabled unless user manually saved settings
- No migration required – existing installs automatically respect new defaults
- Backward compatibility: behavior unchanged if options already set explicitly
- Reset & history tracking:
- Daily, weekly, and monthly reset now archive values into
_init_view_day_yesterday,_init_view_week_last,_init_view_month_last - Enables direct retrieval of “Yesterday”, “Last Week”, and “Last Month” stats
- Fully backward-compatible – existing keys remain unchanged
- Shortcode
[init_view_ranking]: - New ranges supported:
yesterday,last_week,last_month - Default tabs unchanged (
total,day,week,month) for compatibility - Added i18n labels for new ranges (“Yesterday”, “Last Week”, “Last Month”)
- REST API (
init_plugin_suite_view_count_top): rangeparameter extended withyesterday,last_week,last_month- Auto-maps to new meta keys, preserves existing defaults
- Minimal/full field responses and caching remain consistent
- Settings & control:
- New option “Disable Trending” in settings page
- When enabled: trending engine, shape learner, and all related calculations return no-op
- When disabled (default): trending runs as normal, no behavior change for existing sites
- Performance & stability:
- Only 3 additional meta writes per reset cycle
- All new keys pass through
init_plugin_suite_view_count_meta_keyfor extensibility - Trending, shape learner, and caching unaffected unless explicitly disabled
- Backward compatibility:
- Existing shortcodes, API calls, and filters continue to work unchanged
- No migration required – new keys auto-populate from next reset cycle
- Traffic Shape Learner – AI-powered hourly & weekday distribution model:
- Collects raw hourly bins per day and rolls them up into site-wide traffic shape
- Hour-of-day pattern: updated via EMA with Bayesian prior smoothing (kappa control)
- Day-of-week pattern: updated via EMA with stabilized daily totals
- Both distributions normalized to mean = 1 for consistent multiplicative scaling
- Performance & caching:
- Learned shapes cached in transient for 2h with filterable TTL
- Rollup action protected by object-cache lock to avoid race conditions
- Minimal overhead: only 1 write per view increment + 1 rollup per day
- Filters & extensibility:
init_plugin_suite_view_count_site_traffic_shapeprovides current hour/day shape arrays- Tunable alpha/kappa values via filters for both hour-of-day and weekday models
init_plugin_suite_view_count_shape_collect_enabledallows enabling/disabling collection- Reset & admin:
- New admin-post action
init_plugin_suite_view_count_shape_resetto clear all learned shape data - Fully safe to run anytime – plugin will rebuild patterns automatically
- Backward compatibility:
- All existing trending and view count filters remain intact
- Trending Engine v3 (1.16) automatically integrates with learned shapes for uplift calculation
- Trending Engine improvements:
- Multi-key fallback (day → week → month → total) ensures enough posts even at start of day
- Day-views fallback estimation from week/month averages prevents empty scores at early hours
- Optimized CRON queries: skip week/month/total lookups if daily data already sufficient
- Debug payload now includes
views_day_usedand fallback flags for transparency
- Trending Engine v3 – AI-powered uplift & momentum detection:
- Seasonality-aware uplift: compares actual views against expected traffic shape (hour-of-day, day-of-week) for true anomalies
- EWMA momentum with acceleration: smoother trend detection, keeps natural growth without noise
- Anti-gaming protection: robust ratio checks (day vs month/total) and capped score growth per run
- Exposure fatigue: reduces dominance of posts that stay at the top too long, keeps feed fresh
- MMR re-ranking: maximized marginal relevance for better diversity across categories and tags
- Explore/exploit logic: occasional boost for promising new posts with strong uplift signals
- Performance & caching:
- Cached EWMA velocity per post with 12h TTL, minimal overhead
- Site traffic shape cached for 2h with filterable override hook
- Added transient-based streak tracking for fatigue multiplier
- Debug & transparency:
- Extended debug payload includes uplift_raw, expected_views, ewma_val, acc, fatigue_streak
- New action
init_plugin_suite_view_count_trending_debug_rowavailable for developers to log detailed trending rows - Fully backward-compatible:
- Existing filters remain intact (
init_plugin_suite_view_count_trending_component_weights,init_plugin_suite_view_count_meta_key) - Default weights added for uplift, ewma, fatigue, explore, and mmr with safe multipliers
- Trending Engine v2 – optimized for performance and stability:
- Added cache lock (object cache) to prevent race conditions when cron overlaps
- Soft-cap scoring using an exponential formula for smooth limits (avoids hard caps)
- Optimized O(n) diversity filter with auto fill-back to always return enough items
- Improved hot topics SQL for ONLY_FULL_GROUP_BY compatibility and timezone safety with post_date_gmt
- Reduced N+1 queries by caching author_id, categories, and tags per post
- New filters for Trending:
init_plugin_suite_view_count_trending_post_types– limit/override post types (e.g., onlymanga)init_plugin_suite_view_count_trending_component_weights– adjust weights for velocity, engagement, freshness, momentum- Sanitize & fallback: normalized post types from settings, auto-remove
attachment, safe fallback when empty - Engagement smoothing: improved stability when daily views are low
- Introduced a powerful hybrid trending algorithm with hourly updates
- Trending score is calculated based on five dynamic components:
- View velocity (per hour, adjusted by recent growth patterns)
- Time decay (natural dropoff over time, with extended half-life)
- Engagement quality (comments, likes, shares per view)
- Content freshness boost (heavier weight for new posts)
- Category/tag momentum (boost for trending topics in the last 24 hours)
- Trending list is automatically cached and refreshed every hour
- Added diversity filter to ensure balanced results across authors and categories:
- Max 2 posts per author and 3 per category if diversity allows
- Automatically lifts limits if not enough authors/categories to fill the top list
- Fully filterable and compatible with all public post types, taxonomies, and view tracking logic
- Added
init_plugin_suite_view_count_top_post_typesfilter to allow overridingpost_typein top view REST API route - Useful for restricting or customizing results (e.g., only
manga,article, etc.)
- Shortcode
[init_view_count]now supportsid="..."attribute to display the view count of any post (not just the current one) - Allows showing view counts for related posts, custom queries, or manually selected IDs
- Fully backward-compatible: if
idis omitted, the current post will be used as before
- Shortcode
[init_view_ranking]now supportspost_type="..."to filter rankings by custom post type - JS file
ranking.jsupdated to passpost_typeto REST API and cache results per tab and type - Removed redundant function
init_plugin_suite_view_count_human_time_diff()in favor of corehuman_time_diff() - Updated
[init_view_count]shortcode to use nativehuman_time_diff()for publishing time display - Updated all templates to use native
human_time_diff()instead of removed custom function
- Added new
icon="true"attribute to[init_view_count]shortcode to display inline SVG before the view count - New setting: "Auto-insert shortcode into post content?" with options to insert before or after post content
- Auto-insert only applies to post types where view tracking is enabled (manual shortcode use still supported)
- Added
schema="true"attribute to[init_view_count]to output Schema.org microdata (InteractionCounter) - Added
class="custom-class"attribute to allow injecting custom CSS classes into the shortcode wrapper - New filter
init_plugin_suite_view_count_default_shortcodeallows developers to override default auto-insert output - New filter
init_plugin_suite_view_count_auto_insert_enabledgives control over whether auto-insert is active per context - Fully backward-compatible: all new features are optional and disabled by default
- Replaced all PHP 8+
matchexpressions with backwards-compatible logic using array maps and switches - Now fully compatible with PHP 7.4 and above – no syntax errors on legacy environments
- All changes preserve existing filters like
init_plugin_suite_view_count_meta_keyand template behavior - Maintained consistent behavior across REST API endpoints,
[init_view_list], and[init_view_count]shortcodes - Improved code clarity and maintainability without altering plugin output or logic
- Added new "Strict IP check" option to block repeated views from the same IP in a short timeframe
- Uses hashed IPs and transient-based FIFO cache (default: 75 recent IPs per post)
- Designed to prevent fake views posted directly to the REST endpoint (e.g., bots, cURL scripts)
- Fully privacy-safe: does not store raw IPs and automatically expires over time
- New setting: "Enable strict IP check?" (disabled by default)
- Added Dashboard widget with [init_view_ranking] display
- Introduced admin-style.css optimized for clean, one-line layout
- REST API /count now respects the batch limit setting to avoid overload
- Added batch view tracking option to reduce server requests on high-traffic sites
- Views can be temporarily stored in localStorage and sent in groups
- New setting: "Batch view tracking" (default = 1 for real-time)
- Updated JS to support batch logic with scroll + delay detection
- REST API now accepts multiple post IDs and returns array responses
- View count updates instantly after tracking, no reload needed
- Added shortcode builder panel to settings screen for easier shortcode generation
- Introduced new
init-shortcode-builder.jswith full shortcode configuration UI - Supports
[init_view_list],[init_view_ranking], and[init_view_count]shortcodes - i18n-ready: all UI strings are fully translatable via
InitViewCountShortcodeBuilder.i18n - Improved JS architecture to separate builder panel from core builder logic
- Introduced "Trending" scoring system based on daily views and post age (views per hour)
- Trending posts are calculated hourly via cron, optimized for high-traffic and large sites
- New
range=trendingsupport added to/topREST endpoint with built-in sorting and pagination - Shortcode
[init_view_list range="trending"]now fetches trending posts - Internal meta key filtering is fully respected in all ranking and trending logic
- Improved post meta cleanup for day/week/month reset with filterable keys
- Prepared shortcode UI and REST responses for enhanced performance and data accuracy
- Added new
[init_view_ranking]shortcode to display tabbed ranking UI by day/week/month/all-time - Shortcode uses lazy-loading via REST API and includes built-in skeleton loaders for smoother UX
- Fully compatible with headless or SPA environments – optimized to load only when visible
- All assets are conditionally enqueued: JS loads only when shortcode is used, styles are shared via
style.css
- Enqueued
style.cssearlier to avoid being printed in the footer - Added toggle option to disable plugin’s default CSS in the settings page
- Applied
init_plugin_suite_view_count_meta_keyconsistently across REST API, shortcodes, and background tasks - Fixed issue where custom meta key override was ignored in some cases
- Added
pageparameter to/topREST endpoint for pagination - Added
pageattribute to[init_view_list]shortcode for paginated lists - Removed infinite scroll trigger for simplicity and better template control
- Fully compatible with existing templates and theme overrides
- Initial release
- REST-based view counter
- 4 templates included
- Fully extensible with filters/hooks
- Shortcodes with layout switching