Scott Reilly

<p>Easily create a link to another post using a shortcode to reference the post by id or slug; the link text is the post’s title, unless overridden.</p>
<p>When writing your posts, you can refer to other posts either by ID, like so:</p>
<pre><code>[post2post id="20"]
</code></pre>
<p>or by the post slug/name, like so:</p>
<pre><code>[post2post id="hello-world"]
</code></pre>
<p>When viewed on your site, the post-to-post link tag is replaced with a permalink to the post you’ve referenced. By default, the text of the link will be the referenced post’s title, resulting in something like:</p>
<pre><code>"<a href="http://example.com/archives/2005/04/01/hello-world/" title="Hellow World!">Hello World!</a>"
</code></pre>
<p>You can optionally customize the link text by specifying a <code>text=""</code> attribute and value to the post-to-post link tag:</p>
<pre><code>Check out [post2post id="hello-world"]my first post[/post2post].
</code></pre>
<p>Which yields:</p>
<pre><code>Check out "<a href="http://example.com/archives/2011/07/01/hello-world/" title="Hello World!">my first post</a>".
</code></pre>
<p>The plugin provides its own admin options page via <code>Settings</code> -> <code>Post2Post</code> in the WordPress admin. Here you can define text that you want to appear before and/or after each post-to-post substitution, and if you want to enable legacy tag support. The plugin’s admin page also provides some documentation.</p>
<p>Links: <a href="http://coffee2code.com/wp-plugins/post-to-post-links/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/easy-post-to-post-links/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/post-to-post-links/" rel="nofollow ugc">GitHub</a> | <a href="http://coffee2code.com" rel="nofollow ugc">Author Homepage</a></p>
<h3>Examples</h3>
<p>These are all valid ways to reference another of your posts on the same blog.</p>
<ul>
<li><code>[post2post id="25"]</code></li>
<li><code>[post2post id="25"/]</code></li>
<li>`[post2post id=”the-best-post-ever”]</li>
<li>`[post2post id=”the-best-post-ever”/]</li>
</ul>
<p>Assuming all of the above were used to reference the same post, the replacement for the post-to-post shortcut would be:</p>
<pre><code>"<a href="http://example.com/2011/07/01/the-best-post-ever" title="The Best Post Ever!">The Best Post Ever!</a>"
</code></pre>
<p>For any of the above you can also optionally wrap the shortcode around text. If so defined, that text will be used as the link text as opposed to the referenced post’s title.</p>
<ul>
<li><code>[post2post id="25"]this post[/post2post]</code></li>
<li><code>[post2post id="blog-anniversary"]Congratulate me![/post2post]</code></li>
</ul>
<p>The first of which would produce:</p>
<pre><code>"<a href="http://example.com/2011/07/01/the-best-post-ever" title="The Best Post Ever!">this post</a>"
</code></pre>
<p>You can also optionally definte the text that appears before and after the generated links. By default these are quotes.</p>
<ul>
<li>`[post2post id=”25″ before=” ” after=”!”]</li>
</ul>
<p>Yields:</p>
<pre><code> <a href="http://example.com/2011/07/01/the-best-post-ever" title="The Best Post Ever!">this post</a>!<h3>Legacy</h3>
</code></pre>
<p>The legacy syntaxes — which are disabled by default and not recommended for use unless you’ve used version of the plugin earlier than v3.0 — allow you to refer to other posts by ID using a pseudo-shortcode syntax or an HTML comment syntax, like so:</p>
<pre><code>[post="20"] or ``
</code></pre>
<p>or by the post slug/name, like so:</p>
<pre><code>[post="hello-world"] or `.`
</code></pre>
<p>The HTML comment notation was the original syntax employed by earlier versions of this plugin (pre v2.0). While it is still supported, it is no longer the primary and recommended syntax. The pseudo-shortcode syntax was in use between v2.0 and v3.0 of the plugin.</p>
<p>NOTE: The HTML comment syntax notation does NOT play well with the visual (aka rich-text) editor in the WordPress admin.</p>
<p>Examples of old legacy syntax follow. Those that use the pseudo-shortcode syntax (i.e. <code>[post=25]</code>) only work if you’ve checked “Enable legacy pseudo-shortcode tag support?”. Those that use HTML comment notation (i.e. <code></code>) only work if you’ve checked “Enable legacy HTML comment-style tag support?”.</p>
<ul>
<li><code>[post=25]</code></li>
<li><code>[post="25"]</code></li>
<li><code>[post = "25"]</code></li>
<li><code>[post='25']</code></li>
<li><code>[post = '25']</code></li>
<li><code>[post="the-best-post-ever"]</code></li>
<li><code>[post = "the-best-post-ever"]</code></li>
<li><code>[post='the-best-post-ever']</code></li>
<li><code>[post = 'the-best-post-ever']</code></li>
<li><code></code></li>
<li><code></code></li>
<li><code></code></li>
<li><code></code></li>
<li><code></code></li>
<li><code></code></li>
</ul>
<p><strong>NOTE:</strong> Only activate the legacy mode(s) that apply to your use of older versions of the plugin. If you started using the plugin at v3.0 or later, you should not activate either legacy mode.</p>
<h3>Filters</h3>
<p>The plugin exposes one filter for hooking. Typically, customizations utilizing this hook would be put into your active theme’s functions.php file, or used by another plugin.</p>
<p><strong>c2c_post2post_shortcode (filter)</strong></p>
<p>The ‘c2c_post2post_shortcode’ hook allows you to define an alternative to the default shortcode tag. By default the shortcode tag name used is ‘post2post’. It is recommended you only utilize this filter before making use of the plugin’s shortcode in posts and pages. If you change the shortcode tag name, then any existing shortcodes using an older name will no longer work (unless you employ further coding efforts).</p>
<p>Arguments:</p>
<ul>
<li>$shortcode (string)</li>
</ul>
<p>Example:</p>
<pre><code>/**
 *  Use a shorter shortcode: i.e. [p2p id="32"]
 *
 * @param string  $shortcode The default shortcode name.
 * @return string The new shortcode name.
 */
function change_post2post_shortcde( $shortcode ) {
    return 'p2p';
}
add_filter( 'c2c_post2post_shortcode', 'change_post2post_shortcde' );
</code></pre>

Post-to-Post Links

Easily create a link to another post using a shortcode to reference the post by id or slug; the link text is the post's title, unless overridden.

scribu

Lester Chan

<p>Want to replace the old <em>← Older posts | Newer posts →</em> links with some page links?</p>
<p>This plugin provides the <code>wp_pagenavi()</code> template tag which generates fancy pagination links.</p>
<h3>Usage</h3>
<p>In your theme, you need to find calls to next_posts_link() and previous_posts_link() and replace them.</p>
<p>In the Twentyten theme, it looks like this:</p>
<pre><code><div class="nav-previous"><?php next_posts_link( __( '<span class="meta-nav">&larr;</span> Older posts', 'twentyten' ) ); ?></div>
<div class="nav-next"><?php previous_posts_link( __( 'Newer posts <span class="meta-nav">&rarr;</span>', 'twentyten' ) ); ?></div>
</code></pre>
<p>You would replace those two lines with this:</p>
<pre><code><?php wp_pagenavi(); ?>
</code></pre>
<p>For multipart pages, you would look for code like this:</p>
<pre><code><?php wp_link_pages( ... ); ?>
</code></pre>
<p>and replace it with this:</p>
<pre><code><?php wp_pagenavi( array( 'type' => 'multipart' ) ); ?>
</code></pre>
<p>Go to <em>WP-Admin -> Settings -> PageNavi</em> for configuration.</p>
<h3>Changing the CSS</h3>
<p>If you need to configure the CSS style of WP-PageNavi, you can copy the <code>pagenavi-css.css</code> file from the plugin directory to your theme’s directory and make your modifications there. This way, you won’t lose your changes when you update the plugin.</p>
<p>Alternatively, you can uncheck the “Use pagenavi.css?” option from the settings page and add the styles to your theme’s style.css file directly.</p>
<h3>Changing Class Names</h3>
<p>There are <a href="https://codex.wordpress.org/Glossary#Filter" rel="nofollow ugc">filters</a> that can be used to change the default class names that are assigned to page navigation elements.</p>
<h4>Filters</h4>
<ul>
<li><code>wp_pagenavi_class_pages</code></li>
<li><code>wp_pagenavi_class_first</code></li>
<li><code>wp_pagenavi_class_previouspostslink</code></li>
<li><code>wp_pagenavi_class_extend</code></li>
<li><code>wp_pagenavi_class_smaller</code></li>
<li><code>wp_pagenavi_class_page</code></li>
<li><code>wp_pagenavi_class_current</code></li>
<li><code>wp_pagenavi_class_larger</code></li>
<li><code>wp_pagenavi_class_nextpostslink</code></li>
<li><code>wp_pagenavi_class_last</code></li>
</ul>
<h4>Filter Usage</h4>
<pre><code>// Simple Usage - 1 callback per filter
add_filter('wp_pagenavi_class_previouspostslink', 'theme_pagination_previouspostslink_class');
add_filter('wp_pagenavi_class_nextpostslink', 'theme_pagination_nextpostslink_class');
add_filter('wp_pagenavi_class_page', 'theme_pagination_page_class');

function theme_pagination_previouspostslink_class($class_name) {
  return 'pagination__control-link pagination__control-link--previous';
}

function theme_pagination_nextpostslink_class($class_name) {
  return 'pagination__control-link pagination__control-link--next';
}

function theme_pagination_page_class($class_name) {
  return 'pagination__current-page';
}


// More Concise Usage - 1 callback for all filters
add_filter('wp_pagenavi_class_previouspostslink', 'theme_pagination_class');
add_filter('wp_pagenavi_class_nextpostslink', 'theme_pagination_class');
add_filter('wp_pagenavi_class_page', 'theme_pagination_class');

function theme_pagination_class($class_name) {
  switch($class_name) {
    case 'previouspostslink':
      $class_name = 'pagination__control-link pagination__control-link--previous';
      break;
    case 'nextpostslink':
      $class_name = 'pagination__control-link pagination__control-link--next';
      break;
    case 'page':
      $class_name = 'pagination__current'
      break;
  }
  return $class_name;
}
</code></pre>
<h3>Development</h3>
<ul>
<li><a href="https://github.com/lesterchan/wp-pagenavi" title="https://github.com/lesterchan/wp-pagenavi" rel="nofollow ugc">https://github.com/lesterchan/wp-pagenavi</a></li>
</ul>
<h3>Credits</h3>
<ul>
<li>Plugin icon by <a href="http://www.simpleicon.com" rel="nofollow ugc">SimpleIcon</a> from <a href="http://www.flaticon.com" rel="nofollow ugc">Flaticon</a></li>
</ul>
<h3>Donations</h3>
<p>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>


WP-PageNavi

Adds a more advanced paging navigation interface.

Post-to-Post Links vs WP-PageNavi