mbrinson

Admin Posts Navigation solves a common WordPress admin workflow problem: having to go back to the post list every time you want to edit the next or previous post.
Key Features:
<ul>
<li>Seamless Navigation: Navigate directly between posts without returning to the post list</li>
<li>Customizable Sorting: Choose between Date Published, Alphabetical, or Post ID sorting</li>
<li>User Preferences: Each user’s sort preferences are saved per post type</li>
<li>Universal Support: Works with posts, pages, and all custom post types automatically</li>
<li>Dual Editor Support: Full compatibility with both Classic Editor and Gutenberg Block Editor</li>
<li>Smart Ordering: Uses appropriate default ordering (date for posts, alphabetical for pages)</li>
<li>Position Tracking: Shows your current position (e.g., “Position: 3 of 15 posts”)</li>
<li>Security First: Rate limiting, nonce verification, and capability checks</li>
<li>Performance Optimized: Intelligent caching and optimized database queries</li>
<li>Developer Friendly: Multiple filter hooks for customization</li>
</ul>
How It Works:
In the Classic Editor, navigation buttons appear below the post title with a sorting dropdown that lets you choose between Date Published, Alphabetical, or Post ID ordering.
In Gutenberg, a “Post Navigation” panel appears in the Document Settings sidebar with Previous/Next buttons and a sorting dropdown for customizing the navigation order.
Sorting Options:
<ul>
<li>Date Published: Navigate by publication date (newest first for posts, oldest first for pages)</li>
<li>Alphabetical: Navigate by post title in alphabetical order (A-Z)</li>
<li>Post ID: Navigate by WordPress post ID in ascending order</li>
</ul>
Each user’s sorting preference is remembered per post type, so you can have different sorting for posts vs. pages vs. custom post types.
Perfect For:
<ul>
<li>Content managers editing multiple posts in sequence</li>
<li>Bloggers reviewing and updating existing content</li>
<li>Developers working with custom post types</li>
<li>Anyone who finds the default WordPress admin workflow tedious</li>
</ul>
The plugin automatically detects all your custom post types and provides navigation for any content type you can edit.
<h3>Developer Hooks</h3>
Filters:
<ul>
<li><code>twf_admin_posts_navigation_excluded_types</code> – Exclude specific post types from navigation</li>
<li><code>twf_admin_posts_navigation_orderby</code> – Customize ordering for specific post types </li>
<li><code>twf_admin_posts_navigation_order</code> – Customize sort direction for specific post types</li>
<li><code>twf_admin_posts_navigation_query_args</code> – Modify the query arguments for finding posts</li>
</ul>
Example Usage:
<pre><code>`php
</code></pre>
// Exclude a custom post type 
add_filter(‘twf_admin_posts_navigation_excluded_types’, function($excluded) { 
 $excluded[] = ‘my_private_post_type’; 
 return $excluded; 
});
// Custom ordering for events 
add_filter(‘twf_admin_posts_navigation_orderby’, function($orderby, $post_type) { 
 if ($post_type === ‘event’) { 
 return ‘meta_value’; 
 } 
 return $orderby; 
}, 10, 2);
// Navigate only through featured posts 
add_filter(‘twf_admin_posts_navigation_query_args’, function($args, $current_post) { 
 if ($current_post->post_type === ‘post’) { 
 $args[‘meta_query’] = array( 
 array( 
 ‘key’ => ‘featured_post’, 
 ‘value’ => ‘1’, 
 ‘compare’ => ‘=’ 
 ) 
 ); 
 } 
 return $args; 
}, 10, 2); 
 `

Admin Posts Navigation

Navigate between posts and pages without returning to the post list. Works with Classic Editor, Gutenberg, and all Custom Post Types.

strix-bubol5

This plugin’s page-list has an input box that allows you to directly specify the page number you wish to display.
This plugin has a setting to display page-list in reverse order
You can specify style-sheet and some options at each page.
This plugin has several sample stylesheets by default.
By passing an array of options to the function as arguments on each page, it is possible to change the appearance of multiple linked listings within the same page, except for the style.
It is common to have two linked lists, one at the top of the page and one at the bottom. In such cases, when the function is called a second time, the list created the first time is reused from memory to avoid having the same process performed twice.
This plugin has a custom block for Gutenberg Block Editor.
Even if you don’t know much html or php, this plugin has the ability to insert linked list at the beginning and end of an html element using Javascript by specifying the ID of the html element where you want to display it. 
Furthermore, if you have no idea about the ID of html elements, etc., go into the plugin’s options settings page and try typing “search” in the “Page-lists outputted by javascript” field. When the page is displayed, the plugin uses javascript to find the html elements of the main content, and if it is lucky enough to find it, it will use Javascript to insert a page-lists at the beginning and end of that HTML element. Perhaps it might work.
<h3>Arbitrary section 1</h3>
Explanation of errors detected by the plugin “Plugin Check (PCP)” 
*file： \simplistic-page-navi\simplistic_pagenavi.php
1:881行 ERROR WordPress.Security.EscapeOutput.OutputNotEscaped All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found ‘$ret’.
＞This variable $ret contains the assembled pagination and is pointed out as not being escaped in the final output. The option values ​​set by the user are sanitized when saved and are also sanitized individually when actually used. The tags that are incorporated into the pagination are only pre-defined ones, and I understand that there is no need to escape the final assembly..
2:410行 WARNING WordPress.Security.NonceVerification.Recommended Processing form data without nonce verification.
＞This is a function that gets the parameters (query) of the accessed URL. Because it only gets values ​​that exist in public_query_vars set by WordPress, I think that nonce verification is not necessary.
3:860行 ERROR WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: “$simplistic_page_navi_start”.
4:888行 ERROR WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedFunctionFound Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: “direct_splcpn_style”.
＞The plugin is encapsulated in a class, but these variables and functions are outside of that class. I could add a prefix as instructed, but I’ve left it as it is because it might already be in use.。
5:The plugin is encapsulated by a class, and for most of the variables in the files included by the methods in that class, an error occurs saying “Because it is a global variable, you must add a prefix.”。
＞However, since these variables are used within methods inside a class, they cannot possibly be global. I believe this is a false positive that undermines reliability. It’s annoying, so I’m handling it with “// phpcs:ignoreFile”.。

Simplistic page navi

This plugin displays a linked list by page number. It is simple but has several features.

Admin Posts Navigation vs Simplistic page navi