Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

WP-PostViews · Version history

WP-PostViews changelog and version history

Latest version
2.0.1
Aug 24, 2026 (2 months ago)
Releases
28
since 2007
In the last year
3
about one every 16 days
Tested up to
WordPress 7.1.4
PHP 8.2 or later

Releases each year

  • 20077 releases
  • 20082 releases
  • 20092 releases
  • 20144 releases
  • 20153 releases
  • 20162 releases
  • 20171 release
  • 20181 release
  • 20221 release
  • 20231 release
  • 20251 release
  • 20263 releases

20263 releases

  1. WP-PostViews 2.0.1Latest

    • NEW: A Settings link on the plugin’s row on the Plugins screen
    • FIXED: “Count Views From” was only honoured while the page rendered. On a cached site the counting happens through a separate AJAX or REST call instead, and that path never asked the setting — so with “Registered Users Only” a guest hitting a cached page was still counted, and the bot exclusion nev…

  2. WP-PostViews 2.0.0

    • FIXED: The two templates are echoed as markup on the strength of being wp_kses_post()‘d when saved — and that was true only of the settings screen. The 2.0.0 migration writes through a different door, and the row it folds in comes from a release that stored the field with no filtering at all, so a…
    • FIXED: The deferred counting endpoint checked only that an ID named something, and every row in wp_posts answers to that — revisions, autosaves, auto-drafts, attachments, trashed posts, drafts, menu items, reusable blocks. An unauthenticated caller could walk the ID space writing a view row against…
    • FIXED: A view count that is not a number — the meta key is unprefixed, so anyone who can edit a post can type one into Custom Fields — turned every listing containing that post into a fatal error on PHP 8, because both count tokens are built whether or not the template uses them
    • NEW: An editor block, Post Views, under Widgets. It renders on the server through the same code the shortcode uses, so a block and a shortcode showing the same post produce the same markup, and previewing it in the editor never counts a view. The [views] shortcode is unchanged and still supported —…
    • NEW: A wp postviews WP-CLI command — list and get. It reads and never writes.
    • NEW: A postviews/v1 REST API carrying one route, for counting a view from a cached page. Reading a count is already a views field on the core post resource. The admin-ajax.php wp_postviews action is unchanged and still supported.
    • BREAKING: Requires WordPress 6.8 and PHP 8.2.
    • BREAKING: The the_views filter is now wp_postviews_the_views. The template tag the_views() is unchanged.
    • BREAKING: The postviews_should_count filter is now wp_postviews_should_count.
    • BREAKING: The postviews_increment_views and postviews_increment_views_ajax actions are now wp_postviews_increment_views and wp_postviews_increment_views_ajax.
    • BREAKING: The settings are stored in wp_postviews_options instead of views_options, and the upgrade markers in wp_postviews_version instead of views_version. Both are migrated automatically.
    • BREAKING: The WP-Stats toggles move out of the shared stats_display and stats_mostlimit rows into this plugin’s own settings, and the shared rows are deleted. Update all seven WP-Stats plugins together.
    • BREAKING: The widget class WP_Widget_PostViews is now WP_PostViews_Widget. Configured widgets are unaffected.
    • BREAKING: The AJAX action a cached page posts to is now wp_postviews instead of postviews.
    • BREAKING: The six Display Options settings — home page, single posts, pages, archives, searches and other pages — are removed, and the stored keys are dropped on upgrade. Their replacement is the wp_postviews_should_display filter.
    • NEW: Restructured into includes/ classes. The template tags — the_views(), get_most_viewed(), get_least_viewed(), and the category and tag variants — are unchanged and keep working exactly as before.
    • NEW: The options screen is rebuilt on the WordPress Settings API and no longer loads jQuery.
    • NEW: The WP-Stats section, and how many entries its most viewed lists carry, are now settings on Settings -> WP-PostViews.
    • NEW: The wp_postviews_should_display filter decides whether a count is shown. It is read by the_views() only; the [views] shortcode and the admin Views column are explicit requests and ignore it.
    • CHANGED: The settings screen is two tabs, Settings and Templates, over one settings group and one option row.
    • CHANGED: The settings screen is titled “Post Views Settings”, matching the other settings screens in this family.
    • CHANGED: WP-Stats now receives one Views section rather than three separately toggled panels, so the most viewed pages list appears alongside the posts list.
    • FIXED: %VIEW_COUNT_ROUNDED% picked its unit before rounding, so 999,950 displayed as “1000K” instead of “1M” and 999,999,999 as “1000M” instead of “1B”.
    • FIXED: Titles were truncated on bytes rather than characters, because the multibyte branch was gated on MB_OVERLOAD_STRING, which PHP 8.0 removed. A CJK title cut mid-character disappeared from the most/least viewed lists entirely.
    • FIXED: The AJAX endpoint recorded views against post IDs that do not exist, letting anyone add rows to wp_postmeta indefinitely.
    • FIXED: ?v_orderby=ASC was compared against lowercase only, so an uppercase direction — which is what the FAQ tells you to use — silently fell back to descending, the opposite of what was asked for.
    • FIXED: The widget silently discarded changes made in the block widget editor and the customizer, because it required a hidden form field neither of them sends.
    • FIXED: The widget warned about undefined array keys when rendered from the block widget editor or the customizer.
    • FIXED: Uninstalling on a network of more than 100 sites left options and view counts behind on every site after the hundredth, and reported success. Network activation could fatal on the removed wp_get_sites().
    • NOTE: The settings screen moved from options-general.php?page=wp-postviews/postviews-options.php to options-general.php?page=wp-postviews. Update any bookmark; the Settings -> WP-PostViews menu item is where it always was.

  3. WP-PostViews 1.78.1

20251 release

  1. WP-PostViews 1.78

20231 release

  1. WP-PostViews 1.77

20221 release

  1. WP-PostViews 1.76.1

20181 release

  1. WP-PostViews 1.76

20171 release

  1. WP-PostViews 1.75

20162 releases

  1. WP-PostViews 1.74

  2. WP-PostViews 1.73

20153 releases

  1. WP-PostViews 1.72

  2. WP-PostViews 1.71

  3. WP-PostViews 1.70

20144 releases

  1. WP-PostViews 1.69

  2. WP-PostViews 1.68

  3. WP-PostViews 1.67

  4. WP-PostViews 1.66

20092 releases

  1. WP-PostViews 1.50

  2. WP-PostViews 1.40

20082 releases

  1. WP-PostViews 1.31

  2. WP-PostViews 1.30

20077 releases

  1. WP-PostViews 1.20

  2. WP-PostViews 1.11

  3. WP-PostViews 1.10

  4. WP-PostViews 1.02

  5. WP-PostViews 1.01

  6. WP-PostViews 1.00

  7. WP-PostViews 1.00beta

Questions about WP-PostViews’s releases

What is the latest version of WP-PostViews?

2.0.1, released on Aug 24, 2026 (2 months ago). It’s tested up to WordPress 7.1.4 and needs PHP 8.2 or later.

How often is WP-PostViews updated?

3 releases in the last year, about one every 16 days. Its first release on WordPress.org dates from March 2007.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in WP-PostViews’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.