Using Templates with YARPP 3
I am no longer maintaining the information here. It is out of date. Please see the Developing with YARPP section of the YARPP readme. If you have a YARPP support question not directly related to the templating feature, please use the YARPP support forums.
Version 3 of Yet Another Related Posts Plugin is a major rewrite which adds two new powerful features: caching and templating. Today I’m going to show you how you can use templates to customize the look of your related posts output.
Previously with YARPP you were relatively limited in the ways you could present related posts. You were able to set some HTML tags to wrap your posts in and choose how much of an excerpt (if any) to display. This limited interface worked great for many users—indeed, these options still exists in YARPP 3.0. However, there’s also a new option for those of you who want to put your PHP skills to work and have complete control over your related posts display. The option will let you choose any files in the templates
subdirectory of YARPP.
The structure of a YARPP template
Let’s take a look inside the example template, included with YARPP 3 (yarpp-template-example.php
):
There are two basic parts to this (and most all) YARPP template: (a) what you display when there are related posts and (b) what you display when there aren’t. We make this switch with the conditional on line 6. If there are related posts, we introduce an ordered list and use the while
loop to loop over all the related posts. For each post, we use the snippet the_post();
to load the appropriate post data, then print the line item.1
You’ll notice that we’re using familiar template tags here such as the_permalink()
and the_title()
. If you’ve ever had to tweak or build a WordPress theme before, you’ll immediately feel at home. I’ll touch on this again later.
The power of PHP
One big advantage of this new templating system is that you can control exactly how the posts are listed, breaking out of all of the previous structural limitations. For example, in the template-list.php
template, we put the information for each related post in an array and then concatenate the strings with implode
. This way, we produce a comma-separated list for our readers without any stray commas before or after the list, which was impossible until now.
You can also run any arbitrary PHP in the template file—even roll another WP_Query, as in the case of template-random.php
, where a random post is returned when there are no related posts.
Familiar template tags
As mentioned before, the tags we use in these YARPP templates are the same as the template tags used in any WordPress template. In fact, any WordPress template tag will work in the YARPP Loop. You can use these template tags to display the excerpt, the post date, the comment count, or even some custom metadata. I’ve also written two special template tags which only work within a YARPP Loop: the_score()
and get_the_score()
. As you may expect, this will print or return the match score of that particular related post.
In addition, template tags from other plugins will also work. For an example, take a look at the yarpp-template-photoblog.php
file:
In this template’s YARPP Loop, we use some template tags introduced by the Yet Another Photoblog plugin. If you have the Yet Another Photoblog plugin installed, you can use this template to display thumbnails of related posts in lieu of the titles. Notice that here we’re checking first whether each related post is indeed a photo post or not using yapb_is_photoblog_post()
and then using the Yet Another Photoblog yapb_get_thumbnail()
template tag to get the location of the thumbnail.
Templating in YARPP 3.0 enables the blog admin to uber-customize their related posts display using the lingua franca of PHP and template tags. Feel free to comment here with ideas, comments, and of course links to your YARPP-powered blogs. I look forward to seeing what the WordPress community does with this new feature!
-
For those of you interested in the WP and SQL voodoo used to make this happen, I’ve posted a more technical article. ↩