swinton

This plugin is primarily aimed at theme developers, and intends to ease the 
creation of semantic, usable pagination controls for WordPress listings pages, such as 
arhive, author, category, search, tag listings etc.
Inspired by <a href="https://codex.wordpress.org/The_Loop" rel="nofollow ugc">The Loop</a> and <a href="https://codex.wordpress.org/Function_Reference/WP_Query" rel="nofollow ugc">WP_Query</a>, this plugin stays out of the theme 
developer’s way, allowing her to create the markup needed by providing the 
following template tags:
<ul>
<li><code>pp_has_pagination</code> – determines whether the current ‘view’ has any pagination to display, i.e. whether the content being browsed spans more than 1 page</li>
<li><code>pp_the_pagination</code> – initiates the pagination context, should be called at the beginning of each loop iteration</li>
<li><code>pp_rewind_pagination</code> – resets the pagination context, so that the pagination loop can be iterated over multiple times</li>
<li><code>pp_is_current_page</code> – for use in the pagination loop, returns a boolean indicating whether the current loop iteration is for the current page</li>
<li><code>pp_has_previous_page</code> – for use in the pagination loop, returns a boolean indicating whether there is a previous page, e.g. when at page 1, there is no previous page</li>
<li><code>pp_has_next_page</code> – for use in the pagination loop, returns a boolean indicating whether there is a next page, e.g. when at page N of N, there is no next page</li>
<li><code>pp_the_page_permalink</code> – for use in the pagination loop, echos the permalink for the current page</li>
<li><code>pp_the_previous_page_permalink</code> – for use in the pagination loop, echos the permalink for the previous page</li>
<li><code>pp_the_next_page_permalink</code> – for use in the pagination loop, echos the permalink for the next page</li>
<li><code>pp_the_first_page_permalink</code> – for use in the pagination loop, echos the permalink for the first page</li>
<li><code>pp_the_last_page_permalink</code> – for use in the pagination loop, echos the permalink for the last page</li>
<li><code>pp_the_page_num</code> – for use in the pagination loop, echos the page number of the current page being iterated over</li>
</ul>
For example, the following arrangement of template tags would provide a rudimentary pagination control:
<pre><code><?php if (pp_has_pagination()) : ?>
 <div class="pagination">

 
 <?php pp_the_pagination(); if (pp_has_previous_page()) : ?>
 <a href="<?php pp_the_previous_page_permalink(); ?>" class="prev">newer stories</a>
 <?php else : ?>
 newer stories
 <?php endif; pp_rewind_pagination(); ?>

 
 <?php while(pp_has_pagination()) : pp_the_pagination(); ?>
 <?php if (pp_is_current_page()) : ?>
 <?php pp_the_page_num(); ?>
 <?php else : ?>
 <a href="<?php pp_the_page_permalink(); ?>"><?php pp_the_page_num(); ?></a>
 <?php endif; ?>
 <?php endwhile; pp_rewind_pagination(); ?>

 
 <?php pp_the_pagination(); if (pp_has_next_page()) : ?>
 <a href="<?php pp_the_next_page_permalink(); ?>" class="next">older stories</a>
 <?php else : ?>
 older stories
 <?php endif; pp_rewind_pagination(); ?>

 </div>
<?php endif; ?>
</code></pre>
The template tags on offer by this plugin provide the theme developer with an 
unlimited array of possibilities for marking up the pagination control in a 
semantic manner.
For more information, see the original <a href="http://www.nixonmcinnes.co.uk/2009/07/27/making-wordpress-navigation-more-usable-through-pagination-patterns/" rel="nofollow ugc">blog post</a>.

Proper Pagination

A flexible framework for creating semantic pagination controls for a listings page based on established usability patterns.

Andrea Landonio

Picker is a simple and flexible plugin which allow users to choose a specific post inside admin widgets page and display it in their site frontend.
If you need to display a specific post, not a generic list of last posts, top ranked posts, category posts, etc.. but only the one that you configure in the backend. Picker plugin makes it possible in a very quick and easy way. It adds a widget on the admin widgets page that you can use to select and show a post on your site’s frontend. You can work with standard types (like posts) and custom types simply by changing the settings page of the plugin.
Picker plugin is extensible in many of its features, such as, applying filters and action, managing layout template, etc.. moreover, plugin is based on the WordPress Transient API for caching issue. 
As mentioned before, the plugin provides a way to override the default layout template. With a few lines of code, you can create your layout template (copying the default one) and completely override the plugin look&feel thanks to a complete access to all widget item data throw Picker classes.
<h4>Widget usage</h4>
You can use Picker plugin like all the other WordPress plugins, dragging the widget to a sidebar you can enable a Picker widget. Initially, the widget is not published on the frontend. In this way you can safely configure widget’s data and then publish/display the widget. 
Picker widget is composed by the following fields:
<ul>
<li>Publish checkbox: flag it to publish the widget</li>
<li>Widget title: a widget title, for backend and users only, not shown on frontend</li>
<li>Post list: a lists of the last posts by date</li>
<li>Post search: a search field to provide a post ID or search it if post is not in the above post list</li>
<li>Time to publish: a datetime to set when the widget could be shown on frontend</li>
<li>Time to expire: a datetime to set when the widget should be removed from frontend</li>
<li>Alternative URL: an alternative URL instead the default posts permalink</li>
<li>Alternative title: an alternative title instead the default post_title field</li>
<li>Alternative excerpt: an alternative excerpt instead the default post_excerpt field</li>
</ul>
For some field there is a jQuery validation to check right formats. Picker plugin checks all numbers, url and datetime fields showing you an alert if data are wrong.
<h4>Customizing layout template</h4>
Picker plugin provide a default widget template that show a linked title (using post title), the featured image of the post and the post excerpt. Alternatively, you can manage widget template overriding default template. Picker plugin has a tool to detect the template path used for widget layout inclusion. 
This is the load order of the template files:
<ul>
<li>theme / template_path / template_name (default: theme template folder)</li>
<li>theme / template_name (default: theme root folder)</li>
<li>default_path / template_name (default: plugin templates folder)</li>
</ul>
<h4>Plugin filters</h4>
Picker plugin provides many filters to extend default behavior of the plugin core functions. This is a list of the most important available filters:
<ul>
<li>picker_item_title: allow to modify picker item title</li>
<li>picker_item_excerpt: allow to modify picker item excerpt</li>
<li>picker_item_content: allow to modify picker item content</li>
<li>picker_template_path: allow to modify layout template path</li>
</ul>
To better understand how you can interact with plugin filters, here are some examples. 
If you want, you can modify the default (usually “picker/” folder), with a folder in your theme root. In the following example, adding the function to your “functions.php” theme file, we are telling to Picker plugin to search template files inside a “templates/” folder in your theme root.
<pre><code>function modify_picker_template_path() {
 return 'templates';
}
add_filter( 'picker_template_path', 'modify_picker_template_path' ); 
</code></pre>
Also, you can modify the default post title (usually “post_title” field), adding for example a prefix/suffix. In the following example, adding the function to your “functions.php” theme file, we are telling to Picker plugin to call your function before return to template the item post title value.
<pre><code>function modify_picker_post_title( $value ) {
 return 'my_prefix ' . $value;
}
add_filter( 'picker_item_title', 'modify_picker_post_title' ); 
</code></pre>
<h4>Template utility class and functions</h4>
As described in the previous paragraph, you can customize widget template according to you site specs. Inside the template file you can use a <code>$picker_item</code> global variable to access the picker class methods:
<ul>
<li>get_post_data(): get WP_Post object</li>
<li>get_permalink(): get post permalink</li>
<li>get_title(): get post title</li>
<li>get_excerpt($max_words = ”, $use_content_if_empty = false): get post excerpt</li>
<li>get_content($max_words = ”): get post content</li>
<li>get_categories($sep = ‘, ‘, $before = ”, $after = ”): get post categories as a list of category links</li>
<li>get_tags($sep = ‘, ‘, $before = ”, $after = ”): get post tags as a list of tag links</li>
<li>get_formats($sep = ‘, ‘, $before = ”, $after = ”): get post formats as a list of format links</li>
<li>has_image(): tell if post has image</li>
<li>get_image($size = ‘thumbnail’, $attr = array()): get post featured image (use <code>thumbnail</code>, <code>medium</code>, <code>large</code>, <code>full</code> default sizes or your registered new image size)</li>
<li>get_image_id(): get post featured image ID</li>
<li>using <code>__get</code> magic method you can read a custom field (eg: $picker_item->my_custom_field)</li>
</ul>
In addition to <code>$picker_item</code> global variable, you can use custom variables values, such as:
<ul>
<li>get_custom_url(): the provided alternative post URL</li>
<li>get_custom_title(): the provided alternative post title</li>
<li>get_custom_excerpt(): the provided alternative post excerpt</li>
<li>get_widget_sidebar(): which sidebar contains the the widget</li>
<li>get_widget_order(): the widget order (position)</li>
</ul>
In the template file are available special variables, for now:
<ul>
<li>$use_cache: boolean</li>
</ul>
Very important is the <code>widget_sidebar</code> variable. With this value you can display a different widget layout according to which sidebar contains the widget.
<h4>Caching management</h4>
To increase performance and reduce database queries Picker plugin use a persistent caching management. To get a persistent cache without using external plugins Picker plugin uses <a href="https://codex.wordpress.org/Transients_API" rel="nofollow ugc">WordPress Transient API</a>. 
Anytime WordPress display Picker plugin on a site frontend page a calls Picker plugin widget management. First of all, Picker plugin look for a cached object into Transient cache, if found it, gets data, prepares HTML and provides it to frontend. 
If data isn’t in Transient cache, Picker plugin go on with widget date and status validation, then, after looked up post into database, create Picker item object that contains all the widget post data, and in the end like a cached object prepares HTML and provides it to frontend. 
Before concluding by Picker plugin widget management, the Picker item is saved to Transient cache. Only the Picker item is saved to cache, no HTML neither frontend logic are saved to cache. The goal to Picker caching management is only to reduce database usage. 
Picker plugin cache has many expiration rules, the most important are:
<ul>
<li>widgets are cached 5 minutes if you specify a time to publish or a time to expire</li>
<li>widgets are cached 1 day if you don’t specify a time to publish and a time to expire</li>
<li>widgets cache expire if you update the widget</li>
<li>widgets cache expire when one of the following action is triggered:
<ul>
<li>save_post</li>
<li>deleted_post</li>
<li>publish_future_post</li>
<li>switch_theme</li>
</ul>
</li>
</ul>
<h4>Usage</h4>
<ol>
<li>Go to WP-Admin -> Appearance -> Widgets.</li>
<li>Drag Picker widget to a sidebar.</li>
<li>Customize Picker widget.</li>
</ol>
Links: <a href="http://www.andrealandonio.it" rel="nofollow ugc">Author’s Site</a>

Picker

Picker is a simple and flexible plugin which allow users to choose a specific post inside admin widgets page and display it in their site frontend.

Proper Pagination vs Picker