Better Twitter Integration

I both love and hate the Twitter-Tools plugin for WordPress.

On one hand; I really like how it can integrate Twitter into my blog via both sidebar widget and weekly Twitter digest posts… But, on the other hand, I was really starting to feel like these digest posts were cluttering up both my blog and my archives. Several times recently I have found myself scrolling back through way too many Twitter digest posts in order to get at my ACTUAL blog posts and content that I had written. Basically, I came to the conclusion that “I didn’t like this” and I had to modify how Twitter integrated with my Blog.

Today I’ve taken the steps necessary to achieve what I believe is the best of both worlds. I now have weekly Twitter digest post created as usual; but they do not display in my main blog page or in my archives page — AND you have to specifically navigate to a “Twitter” page in order to see them at all.

This was actually a little more challenging for me than I’d like to admit – but I’ll go through the steps below:

First: Exclude the Category
To block out my Twitter category from displaying on my blog and archives, I added the following function to the functions.php file within my theme directory. The “-28” below refers to the corresponding category ID for the Twitter category. This code made it so all posts within the “Twitter” category are ignored in both my blog page and my archives.

function exclude_category($query){
if ($query->is_home) {
$query->set('cat', '-28');
}
return $query;
}
add_filter('pre_get_posts', 'exclude_category');

Second: Make the Category “Navigateable” from the Main Page
The more challenging part for me was figuring out an “easy” way to navigate to these Twitter digest posts. It sounded like a fairly easy thing to do; but I had a surprisingly difficult time with it.

I experimented with some .htacces redirection, and also some plugins that claimed to do exactly what I wanted (but, sucked). In the end; I chose to just modify my theme’s main loop logic and save it as a new page template. I copied the the text from my theme’s index.php file, and and pasted it into my a file called “twitter.php” which I saved as a new page template. I then replaced the following code:

if (have_posts()) :
while (have_posts()) : the_post();

With this code:
$recent = new WP_Query();
$recent->query('cat=28');
if ($recent->have_posts()) :
while($recent->have_posts()) : $recent->the_post();

This actually worked fairly well, and in retrospect is very easy – it just took me quite awhile to arrive at this solution! The final step here was then to add a page called “Twitter” via the administration panel; and simply change the page to use this Twitter.php template instead of the default page template.

Voila, a Twitter page that you can navigate to which displays all the weekly digest Twitter posts created automatically by the Twitter Tools plugin.

**** UPDATE ****
Vanlandw had a great recommendation about excluding these Twitter digest posts from my RSS feeds as well. That was very simple to do… My exclude function in the functions.php file in my theme directory now reads as such:
function exclude_category($query){
if ($query->is_home || $query->is_feed) {
$query->set('cat', '-28');
}
return $query;
}

And, now the Twitter digest posts are excluded from my RSS feed as well! 🙂 WordPress and PHP are both awesome.

6 thoughts on “Better Twitter Integration

  1. Vanberge Post author

    Vanlandwissimo,
    I don’t think so – I believe they will still be in my RSS feed. That’s good call though; I will investimujate.

  2. Jeffrey

    This was a fantastic idea, I’m glad you implemented it. However, I believe there are numerous plugins that could have achieved the functionality with much less hassle. i.e. Advanced Category Excluder.

  3. Vanberge Post author

    Fulljeff I’m pretty sure I tried that plugin and it I couldn’t easily find a way to create a page of just the one single excluded category.

    But you’re probably right – I often do things the hardest way possible.
    At least this time I have avoided changing wordpress core files that get over-written every upgrade.

  4. Pingback: PHP Site Tweaks | Eric VB.com

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.