WP-PageNavi · Version history
WP-PageNavi changelog and version history
- Latest version
- 3.0.1
- Aug 28, 2026 (2 months ago)
- Releases
- 43
- since 2007
- In the last year
- 3
- about one every 17 days
- Tested up to
- WordPress 7.1.4
- PHP 8.2 or later
Releases each year
- 20078 releases
- 20082 releases
- 20092 releases
- 20103 releases
- 20113 releases
- 20121 release
- 20131 release
- 20142 releases
- 20154 releases
- 20161 release
- 20172 releases
- 20181 release
- 20191 release
- 20202 releases
- 20211 release
- 20232 releases
- 20244 releases
- 20263 releases
20263 releases
WP-PageNavi 3.0.1Latest
- CHANGED: The settings migration now runs early on every request instead of only when wp-admin is loaded, so a site whose dashboard is never opened still picks up its settings after an update
- FIXED: Network-activating the plugin upgraded only the site the click happened on. Every other site on the network kept serving its front end with the default settings — its real, pre-3.0.0 settings sat unread until somebody opened that site’s wp-admin, which also means nothing was lost and any sit…
WP-PageNavi 3.0.0
- BREAKING: WP-PageNavi now requires WordPress 6.8 and PHP 8.2. A site running anything older will not be offered the update
- BREAKING: The settings are stored in wp_pagenavi_options instead of pagenavi_options. The old row is copied over and removed automatically
- BREAKING: The settings screen has moved from options-general.php?page=pagenavi to options-general.php?page=wp-pagenavi
- BREAKING: pagenavi-css.css is now css/wp-pagenavi.css, and a copy in your theme directory must be renamed to wp-pagenavi.css to keep overriding it
- BREAKING: Every class is now prefixed. PageNavi_Options, PageNavi_Call and PageNavi_Core are WP_PageNavi_Options, WP_PageNavi_Call and WP_PageNavi_Core, and PageNavi_Admin is now WP_PageNavi_Settings
- BREAKING: PageNavi_Core::$options has been removed. Use WP_PageNavi_Options::defaults() and WP_PageNavi_Options::get() instead. See the FAQ
- BREAKING: PageNavi_Options_Page has been removed and replaced by WP_PageNavi_Settings
- BREAKING: Dropping the SCB Framework also removes the global functions and scb* classes it defined, since they were loaded into WordPress by whichever plugin bundled it. If your theme or another plugin called html(), html_link(), set_post_field(), scb_init(), scb_register_table(), scb_install_table…
- NEW: Removed the bundled WP SCB Framework. The plugin now runs entirely on WordPress core APIs and has no dependencies
- NEW: The settings page is built with the WordPress Settings API
- NEW: Restructured into includes/ following the Plugin Handbook layout
- NEW: A wp_pagenavi_capability filter over the capability the settings screen requires
- NEW: A wp_pagenavi_version row holding the plugin and schema version markers, so a future upgrade has something to compare against
- CHANGED: The stylesheet’s two colours are CSS custom properties with fallbacks rather than hardcoded hexes, and it now carries a dark colour scheme
- CHANGED: The stylesheet uses no physical CSS properties, so one file serves left-to-right and right-to-left sites alike
- FIXED: An inline SVG arrow no longer deletes the entire previous/next link. wp_kses_post() removes an SVG rather than cleaning it, which left the link text empty, and a link with empty text is dropped altogether. The navigation text is now filtered against wp_kses_post()‘s list plus the inline SVG…
- FIXED: Multisite uninstall no longer stops at the hundredth site, so a large network has its options removed everywhere. Reported by Cal at toolshed (#73)
- FIXED: The navigation aria-labels now match the strings WordPress core defines, so they are translated in every locale core supports. Reported by Cal at toolshed (#73)
- FIXED: An array submitted where a text setting belongs no longer raises a PHP 8 notice, and option keys the plugin does not define are no longer stored. Reported by Cal at toolshed (#73)
- FIXED: Page links are escaped with esc_url() instead of esc_attr()
- FIXED: Page numbers derived from a WP_User_Query are cast to integers, so the current page is marked correctly
- FIXED: The stylesheet version now tracks the plugin version instead of being pinned to 2.70
- FIXED: The label on each Yes/No setting pointed at an element that did not exist, so clicking it did nothing
- NOTE: No hook and no template tag is renamed. The ten wp_pagenavi_class_* filters, the wp_pagenavi filter, wp_pagenavi() and wp_pagenavi_dropdown() all keep the names they shipped with
WP-PageNavi 2.94.6
20244 releases
WP-PageNavi 2.94.5
WP-PageNavi 2.94.4
WP-PageNavi 2.94.3
WP-PageNavi 2.94.2
20232 releases
WP-PageNavi 2.94.1
WP-PageNavi 2.94.0
20211 release
WP-PageNavi 2.93.4
20202 releases
WP-PageNavi 2.93.3
WP-PageNavi 2.93.2
20191 release
WP-PageNavi 2.93.1
20181 release
WP-PageNavi 2.93
20172 releases
WP-PageNavi 2.92
WP-PageNavi 2.91
20161 release
WP-PageNavi 2.90
20154 releases
WP-PageNavi 2.89.1
WP-PageNavi 2.89
WP-PageNavi 2.88
WP-PageNavi 2.87
20142 releases
WP-PageNavi 2.86
WP-PageNavi 2.85
20131 release
WP-PageNavi 2.83
20121 release
WP-PageNavi 2.82
20113 releases
WP-PageNavi 2.81
WP-PageNavi 2.80
WP-PageNavi 2.74
20103 releases
WP-PageNavi 2.73
WP-PageNavi 2.72
WP-PageNavi 2.61
20092 releases
WP-PageNavi 2.50
WP-PageNavi 2.40
20082 releases
WP-PageNavi 2.31
WP-PageNavi 2.30
20078 releases
WP-PageNavi 2.20
WP-PageNavi 2.11
WP-PageNavi 2.10
WP-PageNavi 2.03
WP-PageNavi 2.02
WP-PageNavi 2.01
WP-PageNavi 2.00
WP-PageNavi 1.00
Questions about WP-PageNavi’s releases
What is the latest version of WP-PageNavi?
3.0.1, released on Aug 28, 2026 (2 months ago). It’s tested up to WordPress 7.1.4 and needs PHP 8.2 or later.
How often is WP-PageNavi updated?
3 releases in the last year, about one every 17 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 freeRelease dates come from the day each version’s folder was made in WP-PageNavi’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.