Raymond

<p>Tea Page Content is a powerful plugin that allows create widget or shortcode with content of any page, post, etc, and customize look of blocks via template system. You can select one or more entries, choose template (or create your own) and display it by widget or shortcode. Templates presents very flexible system for appearance control.</p>
<h4>Key features</h4>
<ul>
<li>Very flexible template system</li>
<li>Native support of all post types</li>
<li>Possibility to create your own templates</li>
<li>Developer and user friendly</li>
<li>Easy to use and beautiful UI</li>
</ul>
<p>If you found a bug or have a suggestion, please create topic on forum or send me email (raymondcostner at gmail.com).</p>
<h4>Documentation</h4>
<p>You can find primary description at <a href="https://wordpress.org/plugins/tea-page-content/other_notes/" rel="ugc">Other Notes</a> tab, and details at <a href="http://tsjuder.github.io/tea-page-content/" rel="nofollow ugc">Github Page</a>.</p>
<h3>Documentation</h3>
<h4>Shortcodes</h4>
<p>There is just one shortcode <code>tea_page_content</code>. Below there is an example with basic parameters.<br />
    [tea_page_content template=”default” order=”asc” posts=”12,45,23″]<br />
You also can used template variables (see Templates section at documentation) and options.</p>
<h4>Parameters</h4>
<p>There is some built-in options. Let’s take a closer look:</p>
<ul>
<li><strong>order</strong> allows you set entries order. All posts and pages will be sorted by date, and you can choose a direction – by ascending or by descending. Sorting by descending is a default behaviour.</li>
<li><strong>template</strong> allows you choose layout which will look as you want. In shortcode just type full name of your template without extension, for example <code>default</code> or <code>your-template-name</code>.</li>
<li><strong>show_page_thumbnail</strong> allows you enable or disable displaying thumbnail of entry. If you don’t want see page thumbnail, type <code>show_page_thumbnail="false"</code>. Default – <em>true</em>.</li>
<li><strong>show_page_content</strong> allows you enable or disable displaying content of entry. Default – <em>true</em>.</li>
<li><strong>show_page_title</strong> allows you enable or disable displaying title of entry. Default – <em>true</em>.</li>
<li><strong>linked_page_title</strong> allows you enable or disable linking title of entry. In other words, title will be link to full article. Default – <em>false</em>.</li>
<li><strong>linked_page_thumbnail</strong> allows you enable or disable linking thumbnail of entry. In other words, thumbnail will be link to full article. Default – <em>false</em>.</li>
</ul>
<h4>Creating simplest custom template</h4>
<p>By default plugin will be search custom templates in a folder named <code>templates</code> in your theme. For create the one just add into this directory a new file with name like <code>tpc-{template-name}.php</code>. Every template <strong>should</strong> be named by that mask! Then put in created file your code. For example:</p>
<pre><code><?php foreach ($entries as $entry) : ?>
    <div class="entry">
        <h3>
            <?php echo $entry['title'] ?>
        </h3>

        <div class="post-content">
            <?php echo $entry['content'] ?>
        </div>
    </div>
<?php endforeach; ?>
</code></pre>
<p>For using your templates in shortcode, you need just choose it in widget or pass full filename (but without extension) in shortcode. For example:<br />
    template=”tpc-my-template”</p>
<h4>Parameters in template</h4>
<p>Above you can see very simple example of custom template with <code>title</code> and <code>content</code> parameters. But this is not all – there is a full list of allowed parameters which you can use.</p>
<ul>
<li><strong>$count</strong> – Count of all passed entries</li>
<li><strong>$instance</strong> – Array with user defined and default parameters. There is all list of options from self-titled section above.</li>
<li><strong>$template_variables</strong> – Array with template-level variables.</li>
<li><strong>$caller</strong> – Special flag that determine a module that called template: from widget or from shortcode. Can be <code>widget</code> or <code>shortcode</code>.</li>
<li><strong>$entries</strong> – List of posts, pages, etc.
<ul>
<li><strong>title</strong> – Title of current entry</li>
<li><strong>content</strong> – Content of current entry. When page have more tag, will be used <code>the_content</code> function, in other cases will be used <code>the_excerpt</code></li>
<li><strong>thumbnail</strong> – Thumbnail of entry (if exists)</li>
<li><strong>link</strong> – Link of entry</li>
<li><strong>id</strong> – Entry ID</li>
</ul>
</li>
</ul>
<h4>Details & Filters</h4>
<p>Because full manual is too long, you can see it at <a href="http://tsjuder.github.io/tea-page-content/" rel="nofollow ugc">Github Page</a>. Get details and updating information about new features includes filters, template-level variables and more.</p>


Tea Page Content

Plugin that allows create widget or shortcode with content of any post, and customize look of blocks via templates.

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.

Tea Page Content vs Post-to-Post Links