Scott Reilly

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.
When writing your posts, you can refer to other posts either by ID, like so:
<pre><code>[post2post id="20"]
</code></pre>
or by the post slug/name, like so:
<pre><code>[post2post id="hello-world"]
</code></pre>
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:
<pre><code>"<a href="http://example.com/archives/2005/04/01/hello-world/" title="Hellow World!">Hello World!</a>"
</code></pre>
You can optionally customize the link text by specifying a <code>text=""</code> attribute and value to the post-to-post link tag:
<pre><code>Check out [post2post id="hello-world"]my first post[/post2post].
</code></pre>
Which yields:
<pre><code>Check out "<a href="http://example.com/archives/2011/07/01/hello-world/" title="Hello World!">my first post</a>".
</code></pre>
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.
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>
<h3>Examples</h3>
These are all valid ways to reference another of your posts on the same blog.
<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>
Assuming all of the above were used to reference the same post, the replacement for the post-to-post shortcut would be:
<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>
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.
<ul>
<li><code>[post2post id="25"]this post[/post2post]</code></li>
<li><code>[post2post id="blog-anniversary"]Congratulate me![/post2post]</code></li>
</ul>
The first of which would produce:
<pre><code>"<a href="http://example.com/2011/07/01/the-best-post-ever" title="The Best Post Ever!">this post</a>"
</code></pre>
You can also optionally definte the text that appears before and after the generated links. By default these are quotes.
<ul>
<li>`[post2post id=”25″ before=” ” after=”!”]</li>
</ul>
Yields:
<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>
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:
<pre><code>[post="20"] or ``
</code></pre>
or by the post slug/name, like so:
<pre><code>[post="hello-world"] or `.`
</code></pre>
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.
NOTE: The HTML comment syntax notation does NOT play well with the visual (aka rich-text) editor in the WordPress admin.
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?”.
<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>
NOTE: 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.
<h3>Filters</h3>
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.
c2c_post2post_shortcode (filter)
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).
Arguments:
<ul>
<li>$shortcode (string)</li>
</ul>
Example:
<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.

Post-to-Post Links vs Nested Pages