Init View Count – AI-Powered, Trending, REST API
| 开发者 | brokensmile.2103 |
|---|---|
| 更新时间 | 2025年10月26日 23:37 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | 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
安装:
- 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. Just insert a Shortcode block and paste [init_view_count] or [init_view_list] as needed.
= 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.
更新日志:
1.19 – October 2, 2025
- 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