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.

brendaegeland

A common web design pattern is to have a primary navigation with the top level pages, and then a separate 
navigation element on each page that shows only those pages related to a common top-most page. This widget helps 
to build those secondary navigation elements.
If your page structure was like this:
<ul>
<li>Home</li>
<li>About</li>
<li>— Our History</li>
<li>— Our Staff</li>
<li>— — Employment Opportunities</li>
<li>Services</li>
<li>— Widget Development</li>
<li>— Gadget Deployment</li>
<li>Contact Us</li>
</ul>
and you added the widget with its default settings to a sidebar, it would create a list like this:
<ul>
<li>About</li>
<li>Our History</li>
<li>Our Staff</li>
<li>— Employment Opportunities</li>
</ul>
on any of the pages in the About subtree. Notice that the top-most ancestor, About, is included as the first element of the list.
<h4>Options</h4>
<ol>
<li>Title. The widget title. If left blank, it defaults to the title of the top ancestor page.</li>
<li>Show Title. Maybe you don’t want a title. Just turn it off here.</li>
<li>Top Page. You can select one of your pages to be the top page, or you can choose Default, which determines the top-most ancestor of the page being displayed.</li>
<li>Menu Class. Gets applied to the outermost <ul> element.</li>
<li>Before Links. HTML to be inserted before links in the list.</li>
<li>After Links. HTML to be inserted after links in the list.</li>
</ol>

Subpages in Context

Lists pages and subpages for a given page, or the top ancestor of the current page and all of the ancestor's descendants

Admin Posts Navigation vs Subpages in Context