Init View Count – Minimal, Accurate, Extensible -- WordPress 插件

开发者	brokensmile.2103
更新时间	2026年9月26日 11:41
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

2.0.2 – September 26, 2026

Security: the init_plugin_suite_view_count_shape_reset admin-post action (clears learned Traffic Shape data) had no capability check and no nonce, so any logged-in user (even a Subscriber), or a CSRF link, could wipe the learned data. It now requires manage_options and a valid nonce. A Reset traffic shape data button (with nonce) has been added to Settings → Init View Count. Custom links must now be built with wp_nonce_url( admin_url( 'admin-post.php?action=init_plugin_suite_view_count_shape_reset' ), 'init_plugin_suite_view_count_shape_reset' )
Security: GET /top now only accepts post types that exist and are publicly viewable (is_post_type_viewable()), so the public endpoint can no longer expose titles/excerpts of internal post types such as wp_block. The init_plugin_suite_view_count_top_post_types filter still runs afterwards, so developers can explicitly add other types. number is capped at 100 (filterable via the new init_plugin_suite_view_count_api_top_max_number filter). An array passed as terms no longer causes a PHP fatal error
Security: the [init_view_ranking] front-end script now builds items with DOM APIs (textContent) instead of injecting API strings into innerHTML, and only allows http(s) links/images
Bug fix: on sites with a negative UTC offset (the Americas, etc.) the daily reset computed the day of week/month from a timestamp that had the timezone offset applied twice, so at 00:01 it thought it was still the previous day — weekly counters were reset on Tuesday instead of Monday and monthly counters on the 2nd instead of the 1st. All date math now uses real Unix timestamps with wp_date(). The $now value passed to the existing hooks/filters is unchanged
Bug fix: the daily reset event now re-aligns itself to 00:01 site time after daylight-saving changes (WP-Cron's daily recurrence is a fixed 24h and used to drift to 23:01 or 01:01). Sites without DST are never touched
Bug fix (Trending): post age was computed as "local timestamp minus GMT timestamp", adding the site's UTC offset to every post's age (e.g. +7 hours on GMT+7 sites), which skewed freshness boost and time decay. Age is now computed from real Unix timestamps. Old trending_last_calculation values stored in local time are handled safely on upgrade
Bug fix (Trending): hot topics passed term_taxonomy_id values to get_term() as if they were term IDs. The two are not always equal (split/merged terms, migrated sites), so "hot" boosts could be attributed to the wrong category/tag. The query now returns term IDs and taxonomies directly
Bug fix (Trending): the EWMA momentum component was stored in the non-persistent object cache, so on sites without Redis/Memcached it never carried over between runs and effectively did nothing. It now works on every site
Bug fix: [init_view_count time="true"] showed "Posted 7 hours ago" for a just-published post on GMT+7 sites (GMT timestamp compared against a local timestamp)
Bug fix: a single POST /count request containing the same post ID several times (e.g. [5,5,5]) incremented that post several times. Duplicate IDs in one request are now ignored
Bug fix: [init_view_ranking] only initialised the first ranking block on a page; additional rankings stayed on the loading skeleton forever. Every ranking block is now initialised, and each keeps its own post_type
Bug fix: the ranking script fell back to /wp-json/ when the tracking script was not on the page (archive pages, the Dashboard widget), which broke on sites installed in a subdirectory or without pretty permalinks. The correct REST URL is now always provided
Bug fix: the view-count tracking script stopped completely when the browser blocked localStorage/sessionStorage (Safari private mode, strict privacy settings). Storage access is now guarded with an in-page fallback
Bug fix: block className values with multiple classes (e.g. foo bar) were merged into foobar; [init_view_count class="..."] now accepts multiple classes too
Bug fix: block attributes containing square brackets or quotes (e.g. a list title Top [2026]) broke the generated shortcode. Blocks now call the shortcode callback directly with an attribute array (core pre_do_shortcode_tag/do_shortcode_tag filters still apply)
Bug fix: auto-insert now only adds the view counter to the content of the post actually being viewed, not to other posts' content rendered on the same page, and not to excerpts generated from content (e.g. SEO meta descriptions)
Bug fix: the front-end tracker now uses the queried post ID instead of get_the_ID(), so a theme/plugin that runs a secondary query before wp_head without resetting it can no longer make views count toward the wrong post
Bug fix: the Shortcode Builder read the wrong localized object name, so "Copy", "Close" and "Shortcode Preview" were never translated. Copy now also works on non-HTTPS admin screens
Bug fix: init_plugin_suite_view_count_format_thousands() could output 1000.0 K (for 999,950) and 2.0 K; it now outputs 1 M and 2 K
Bug fix: turning on Disable Trending now also hides previously calculated trending data from GET /top, as the setting describes
Performance: POST /count now increments all counters of a post (total/day/week/month) with a single atomic UPDATE instead of one query per counter — 2 queries per view instead of 5 in the common case. First-view inserts and stale-cache situations are still handled atomically
Performance: the daily rollover now only writes rows that actually change. Posts with no views in the period whose "previous period" value is already 0 (the vast majority on large sites) are no longer deleted and re-inserted every day; existing rows are updated in place. In testing on 42 posts, a typical day went from 126 inserts + 129 deletes to 3 updates + 3 deletes. The end result in the database is identical to the previous version (verified against the old logic with randomized data)
Performance: the hourly Trending calculation primes post, term and meta caches up front, reads comment counts from the post object, stores EWMA/score-cap/streak state in a single non-autoloaded option instead of hundreds of per-post transients, and the MMR diversity re-rank is now O(limit × n) instead of O(limit² × n) with identical output. In testing, one run went from ~590 queries to ~30
Performance: GET /top primes featured-image caches in one query; its cache key ignores parameter order and cache-buster parameters (_, no_cache); [init_view_list] also primes featured images
Performance: front-end scripts are loaded with the defer strategy; fetch uses keepalive so a view is still sent if the visitor leaves right as it qualifies
Improvement: batch mode keeps queued IDs beyond the batch size for the next send instead of dropping them; the view number updates in every place the post's counter appears on the page
Improvement: the View Count block uses the block context postId (Query Loop, FSE templates) when Post ID is 0
Improvement: new filter init_plugin_suite_view_count_ip_headers to restrict which headers are trusted for Strict IP check (e.g. only REMOTE_ADDR on servers not behind a proxy/CDN)
Improvement: cron events are removed on plugin deactivation; uninstall now also removes the yesterday/last week/last month meta, all plugin options and transients (including cached /top results, which the previous uninstall could not find), and runs on every site of a multisite network
i18n: regenerated init-view-count.pot with WP-CLI; new strings translated in init-view-count-vi.po/.mo
Code quality: all PHP files now pass WordPress Coding Standards (WordPress-Extra) with zero errors and warnings

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_count directly 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 0 did 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 to 0. Root cause was a value || fallback pattern in the front-end script, which treats a valid 0 as falsy and always substitutes the default. Both options are now validated on save, enforced again at output time (so sites that already had 0 stored 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 scroll event handler, and no scroll event 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. 0 is 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 loop get_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 via init_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 in GET /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 of rest-api.php and shortcodes.php into a new includes/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

2.0.0 – August 4, 2026

Breaking change: Requires at least is 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-count category so AI agents and automation tools can discover and query view-count data through the standardized wp_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 as GET /top and 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 the render field in block.json) that builds the same shortcode tag and calls do_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) using ServerSideRender for a live preview directly in the editor
Tested up to: 7.1

1.22 – August 4, 2026

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 underlying WP_Query calls were missing ignore_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 with requestAnimationFrame instead of running its calculation on every single scroll event, 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 as passive to avoid blocking scroll rendering. Also fixed a theoretical division-by-zero edge case when a page's content is shorter than the viewport

1.21 – July 17, 2026

New optional setting: Require REST nonce verification? (Settings → Init View Count). Off by default. When enabled, POST /count requires a valid X-WP-Nonce header and rejects the request with 403 otherwise, 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 /top is 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 to languages/init-view-count.pot, with ready-made Vietnamese translations in languages/init-view-count-vi.po / .mo

1.20 – July 16, 2026

Performance & accuracy overhaul for the /count REST endpoint:
View counters (total, day, week, month) are now incremented with a direct, atomic SQL UPDATE ... SET meta_value = meta_value + 1 instead of a read-then-write get_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 on shutdown, 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:ignore justifications, no behavior change to existing filters/actions)

1.19 – October 2, 2025

Hotfix: Daily/Weekly/Monthly counters now enabled by default
init_plugin_suite_view_count_enable_day → default = 1
init_plugin_suite_view_count_enable_week → default = 1
init_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

1.18 – October 1, 2025

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):
range parameter extended with yesterday, 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_key for 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

1.17 – August 20, 2025

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_shape provides 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_enabled allows enabling/disabling collection
Reset & admin:
New admin-post action init_plugin_suite_view_count_shape_reset to 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_used and fallback flags for transparency

1.16 – August 16, 2025

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_row available 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

1.15 – August 8, 2025

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., only manga)
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

1.14 – July 24, 2025

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

1.13 – July 13, 2025

Added init_plugin_suite_view_count_top_post_types filter to allow overriding post_type in top view REST API route
Useful for restricting or customizing results (e.g., only manga, article, etc.)

1.12 – July 8, 2025

Shortcode [init_view_count] now supports id="..." 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 id is omitted, the current post will be used as before

1.11 – June 30, 2025

Shortcode [init_view_ranking] now supports post_type="..." to filter rankings by custom post type
JS file ranking.js updated to pass post_type to REST API and cache results per tab and type
Removed redundant function init_plugin_suite_view_count_human_time_diff() in favor of core human_time_diff()
Updated [init_view_count] shortcode to use native human_time_diff() for publishing time display
Updated all templates to use native human_time_diff() instead of removed custom function

1.10 – June 26, 2025

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_shortcode allows developers to override default auto-insert output
New filter init_plugin_suite_view_count_auto_insert_enabled gives control over whether auto-insert is active per context
Fully backward-compatible: all new features are optional and disabled by default

1.9 – June 24, 2025

Replaced all PHP 8+ match expressions 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_key and 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

1.8 – June 22, 2025

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)

1.7 – June 21, 2025

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

1.6 – June 19, 2025

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

1.5 – June 16, 2025

Added shortcode builder panel to settings screen for easier shortcode generation
Introduced new init-shortcode-builder.js with 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

1.4 – June 8, 2025

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=trending support added to /top REST 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

1.3 – June 7, 2025

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

1.2 – June 5, 2025

Enqueued style.css earlier 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_key consistently across REST API, shortcodes, and background tasks
Fixed issue where custom meta key override was ignored in some cases

1.1 – May 28, 2025

Added page parameter to /top REST endpoint for pagination
Added page attribute 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

1.0 – May 18, 2025

Initial release
REST-based view counter
4 templates included
Fully extensible with filters/hooks
Shortcodes with layout switching

Init View Count – AI-Powered, Trending, REST API

标签

下载

详情介绍:

安装:

屏幕截图:

常见问题:

更新日志: