Requires WordPress 6.8 and PHP 8.2.<\/p>\n\n
Settings migrate on activation, or on the first admin page load after updating.<\/strong> The settings screen is at If you copied Nothing a theme calls has been renamed.<\/strong> Custom PHP reaching into the plugin's classes needs editing.<\/strong> Every class is prefixed The bundled SCB framework is gone.<\/strong> It defined global functions and Want to replace the old ← Older posts | Newer posts →<\/em> links with some page links?<\/p>\n\n This plugin provides the Much of the 2.x line was the work of scribu<\/a>, whose write-ups on using it with secondary queries are still the ones the FAQ below points at. The plugin icon is by SimpleIcon<\/a> from Flaticon<\/a>.<\/p>\n\n I spent most of my free time creating, updating, maintaining and supporting these plugins, if you really love my plugins and could spare me a couple of bucks, I will really appreciate it. If not feel free to use it without any obligations.<\/p>\n\n In your theme, you need to find calls to next_posts_link() and previous_posts_link() and replace them.<\/p>\n\n In the Twentyten theme, it looks like this:<\/p>\n\n You would replace those two lines with this:<\/p>\n\n For multipart pages, you would look for code like this:<\/p>\n\n and replace it with this:<\/p>\n\n Go to WP-Admin -> Settings -> PageNavi<\/em> for configuration.<\/p>\n\n If you need to configure the CSS style of WP-PageNavi, you can copy the The stylesheet sets no font and no text colour, so it inherits both from your theme, and its two border colours are CSS custom properties. A small change needs no copy of the file at all:<\/p>\n\n Alternatively, you can set \"Use wp-pagenavi.css\" to No on the settings page and add the styles to your theme's style.css file directly.<\/p>\n\n There are filters<\/a> that can be used to change the default class names that are assigned to page navigation elements.<\/p>\n\n You're using pagenavi_options<\/code> becomes wp_pagenavi_options<\/code>, and the old row is deleted once copied.<\/p>\n\noptions-general.php?page=wp-pagenavi<\/code><\/strong>, still under Settings -> PageNavi<\/em>.<\/p>\n\npagenavi-css.css<\/code> into your theme, rename your copy to wp-pagenavi.css<\/code>.<\/strong> The plugin's stylesheet is now css\/wp-pagenavi.css<\/code> and the theme override is looked up under the new name; until you rename it your copy is ignored. Nothing inside it needs to change.<\/p>\n\nwp_pagenavi()<\/code>, wp_pagenavi_dropdown()<\/code>, the wp_pagenavi<\/code> filter and all ten wp_pagenavi_class_*<\/code> filters behave as before.<\/p>\n\nWP_<\/code>: PageNavi_Options<\/code> is WP_PageNavi_Options<\/code>, PageNavi_Call<\/code> is WP_PageNavi_Call<\/code>, PageNavi_Core<\/code> is WP_PageNavi_Core<\/code>. The settings screen was renamed as well as prefixed: PageNavi_Admin<\/code> is now WP_PageNavi_Settings<\/code>. PageNavi_Options_Page<\/code> and PageNavi_Core::$options<\/code> are gone \u2014 use WP_PageNavi_Options::get()<\/code> and WP_PageNavi_Options::get_defaults()<\/code>.<\/p>\n\nscb*<\/code> classes that any plugin bundling it loaded for everything else to use. Code calling html()<\/code>, html_link()<\/code>, set_post_field()<\/code>, scb_init()<\/code> or any scb_*<\/code> helper and relying on WP-PageNavi to provide them must now provide them itself. Another installed plugin may still be supplying them, in which case nothing breaks until that one stops.<\/p>"},"ratings":{"1":9,"2":0,"3":2,"4":11,"5":127},"assets_icons":{"icon.svg":{"filename":"icon.svg","revision":977997,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3639530,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3639530,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.00","2.00","2.01","2.02","2.03","2.10","2.11","2.20","2.30","2.31","2.40","2.50","2.61","2.72","2.73","2.74","2.80","2.81","2.82","2.83","2.85","2.86","2.87","2.88","2.89","2.89.1","2.90","2.91","2.92","2.93","2.93.1","2.93.2","2.93.3","2.93.4","2.94.0","2.94.1","2.94.2","2.94.3","2.94.4","2.94.5","2.94.6","3.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3639937,"resolution":"1","location":"assets","locale":"","width":1100,"height":1675},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3639937,"resolution":"2","location":"assets","locale":"","width":1280,"height":214}},"screenshots":{"1":"Settings -> WP-PageNavi, where every piece of the navigation text is set","2":"The page links under the loop, on a front page forty-two pages long"}},"plugin_section":[],"plugin_tags":[1753,3724,243,900,5826],"plugin_category":[43],"plugin_contributors":[77620],"plugin_business_model":[],"class_list":["post-174","plugin","type-plugin","status-publish","hentry","plugin_tags-navigation","plugin_tags-page-links","plugin_tags-pages","plugin_tags-pagination","plugin_tags-paging","plugin_category-customization","plugin_contributors-gamerz","plugin_committers-gamerz","plugin_committers-scribu"],"banners":{"banner":"https:\/\/ps.w.org\/wp-pagenavi\/assets\/banner-772x250.png?rev=3639530","banner_2x":"https:\/\/ps.w.org\/wp-pagenavi\/assets\/banner-1544x500.png?rev=3639530","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/wp-pagenavi\/assets\/icon.svg?rev=977997","icon":"https:\/\/ps.w.org\/wp-pagenavi\/assets\/icon.svg?rev=977997","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/wp-pagenavi\/assets\/screenshot-1.png?rev=3639937","caption":"Settings -> WP-PageNavi, where every piece of the navigation text is set"},{"src":"https:\/\/ps.w.org\/wp-pagenavi\/assets\/screenshot-2.png?rev=3639937","caption":"The page links under the loop, on a front page forty-two pages long"}],"raw_content":"\nwp_pagenavi()<\/code> template tag which generates fancy pagination links.<\/p>\n\nDonations<\/h3>\n\n
Usage<\/h3>\n\n
<div class=\"nav-previous\"><?php next_posts_link( __( '<span class=\"meta-nav\">←<\/span> Older posts', 'twentyten' ) ); ?><\/div>\n<div class=\"nav-next\"><?php previous_posts_link( __( 'Newer posts <span class=\"meta-nav\">→<\/span>', 'twentyten' ) ); ?><\/div>\n<\/code><\/pre>\n\n<?php wp_pagenavi(); ?>\n<\/code><\/pre>\n\n<?php wp_link_pages( ... ); ?>\n<\/code><\/pre>\n\n<?php wp_pagenavi( array( 'type' => 'multipart' ) ); ?>\n<\/code><\/pre>\n\nChanging the CSS<\/h3>\n\n
css\/wp-pagenavi.css<\/code> file from the plugin directory into your theme's directory as wp-pagenavi.css<\/code> and make your modifications there. This way, you won't lose your changes when you update the plugin.<\/p>\n\n.wp-pagenavi {\n --wp-pagenavi-border-color: #d0d0d0;\n --wp-pagenavi-border-color-current: rebeccapurple;\n}\n<\/code><\/pre>\n\nChanging Class Names<\/h3>\n\n
Filters<\/h4>\n\n
\n
wp_pagenavi_class_pages<\/code><\/li>\nwp_pagenavi_class_first<\/code><\/li>\nwp_pagenavi_class_previouspostslink<\/code><\/li>\nwp_pagenavi_class_extend<\/code><\/li>\nwp_pagenavi_class_smaller<\/code><\/li>\nwp_pagenavi_class_page<\/code><\/li>\nwp_pagenavi_class_current<\/code><\/li>\nwp_pagenavi_class_larger<\/code><\/li>\nwp_pagenavi_class_nextpostslink<\/code><\/li>\nwp_pagenavi_class_last<\/code><\/li>\n<\/ul>\n\nFilter Usage<\/h4>\n\n
\/\/ Simple Usage - 1 callback per filter\nadd_filter('wp_pagenavi_class_previouspostslink', 'theme_pagination_previouspostslink_class');\nadd_filter('wp_pagenavi_class_nextpostslink', 'theme_pagination_nextpostslink_class');\nadd_filter('wp_pagenavi_class_page', 'theme_pagination_page_class');\n\nfunction theme_pagination_previouspostslink_class($class_name) {\n return 'pagination__control-link pagination__control-link--previous';\n}\n\nfunction theme_pagination_nextpostslink_class($class_name) {\n return 'pagination__control-link pagination__control-link--next';\n}\n\nfunction theme_pagination_page_class($class_name) {\n return 'pagination__current-page';\n}\n\n\n\/\/ More Concise Usage - 1 callback for all filters\nadd_filter('wp_pagenavi_class_previouspostslink', 'theme_pagination_class');\nadd_filter('wp_pagenavi_class_nextpostslink', 'theme_pagination_class');\nadd_filter('wp_pagenavi_class_page', 'theme_pagination_class');\n\nfunction theme_pagination_class($class_name) {\n switch($class_name) {\n case 'previouspostslink':\n $class_name = 'pagination__control-link pagination__control-link--previous';\n break;\n case 'nextpostslink':\n $class_name = 'pagination__control-link pagination__control-link--next';\n break;\n case 'page':\n $class_name = 'pagination__current'\n break;\n }\n return $class_name;\n}\n<\/code><\/pre>\n\n\n\n
next_posts_link()<\/code> and previous_posts_link()<\/code> with wp_pagenavi()<\/code>. Usage below shows what that looks like in a stock theme.<\/li>\nWP-Admin -> Settings -> PageNavi<\/code> to change the wording and the number of page links.<\/li>\n<\/ol>\n\n\n\n
When I go to page 2, I see the same posts as on page 1!<\/h3><\/dt>\n
query_posts()<\/code> wrong. See The Right Way To use query_posts()<\/a><\/p><\/dd>\n