hits_list_daily<\/code> database tables (table prefix may vary).<\/p>\n\nIt does not send tracking data to a third-party analytics service.<\/p>\n\n
Daily tracking buckets are retained for 180 days by default and older rows are removed automatically.<\/p>\n\n
You are responsible for describing your use of visitor analytics on your own site as needed.<\/p>\n\n
Source Code and Build Tools<\/h3>\n\n
The compiled block assets in blocks\/popular-posts\/build\/<\/code> are generated from the human-readable source files included in blocks\/popular-posts\/src\/<\/code>.<\/p>\n\nTo rebuild the block assets:<\/p>\n\n
\n- Go to
blocks\/popular-posts\/<\/code>.<\/li>\n- Run
npm install<\/code>.<\/li>\n- Run
npm run build<\/code>.<\/li>\n<\/ol>\n\nThe block build uses @wordpress\/scripts<\/code>. Runtime PHP, vanilla JavaScript, and CSS assets outside the block build are maintained directly in the plugin source.<\/p>\n\n\n\n- Upload the
the-hits-list<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n- Activate The Hits List through the Plugins screen in WordPress.<\/li>\n
- Go to Settings > The Hits List to configure tracking and display options.<\/li>\n
- If Top 10 data is detected, use the import button on the settings screen to migrate existing counts.<\/li>\n<\/ol>\n\n\n
\nDoes this send data to a third-party service?<\/h3><\/dt>\nNo. The Hits List stores tracking data locally in your WordPress database and does not call a third-party analytics endpoint.<\/p><\/dd>\n
Can I migrate from Top 10?<\/h3><\/dt>\nYes. The plugin can import compatible overall and daily counts from Top 10 tables. Imports are SQL-backed, resumable, and rerun-safe, so repeating the import does not double-count unchanged source data. Very large imports can be monitored from the settings screen or run through WP-CLI. If Top 10 is deactivated, existing Top 10 Popular Posts widgets can continue rendering through The Hits List using their saved settings, and the settings screen can convert those placements into native The Hits List widgets.<\/p><\/dd>\n
How long is daily data kept?<\/h3><\/dt>\nDaily buckets are retained for 180 days by default. Older daily rows are pruned automatically by a scheduled cleanup task.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.3.01<\/h4>\n\n\n- Added public post type selection to the Popular Posts block and widget.<\/li>\n
- Added a legacy Top 10 widget compatibility bridge so existing
widget_tptn_pop<\/code> placements keep rendering after Top 10 is deactivated.<\/li>\n- Added a native Top 10 widget migrator that rewrites saved sidebar placements while preserving third-party widget metadata.<\/li>\n
- Reworked Top 10 imports to run in resumable batches with status, progress, cancel\/restart controls, diagnostics, and WP-CLI commands for large migrations.<\/li>\n
- Reworked Top 10 import tracking to store large rerun state in database tables instead of oversized options.<\/li>\n
- Improved Top 10 import error messages and asset cache busting in the admin UI.<\/li>\n
- Added the
get_thl_posts()<\/code> helper alias for older integration examples.<\/li>\n- Avoided empty
.thl-meta<\/code> wrappers when all post meta display options are disabled.<\/li>\n- Confirmed compatibility metadata for WordPress 7.0.<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- Added WordPress dashboard cards for daily top posts, all-time top posts, and views over time.<\/li>\n
- Added post list table columns for total, daily, and condensed view counts.<\/li>\n
- Hardened public REST tracking and counter endpoints.<\/li>\n
- Removed the legacy query-string tracking endpoint.<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- Normalized tracking to use server-derived blog IDs and validated post targets.<\/li>\n
- Reworked daily tracking into true site-local day buckets with upgrade migration support.<\/li>\n
- Added rerun-safe Top 10 import state handling.<\/li>\n<\/ul>","raw_excerpt":"Track post views locally, display popular posts, and migrate Top 10 data into a completely free, drop-in replacement.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/304105","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=304105"}],"author":[{"embeddable":true,"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/adamgreenwell"}],"wp:attachment":[{"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=304105"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=304105"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=304105"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=304105"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=304105"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/es-uy.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=304105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}