How-to: Another Way to Exclude Posts From the Front Page
Posted on September 8, 2007
16 Comments
Over at WordPress support, it isn't all that unusual to see folks wondering how to exclude certain posts from their front page. I typically suggest they grab a "category excluder" plugin[1] and add the posts they don't want to see to a certain category.
The question came up again today, but the person was looking for something that wouldn't be category based. That got me thinking...
Well... I suppose you could look into a bit of theme hacking. Perhaps with a custom field (see Using_Custom_Fields) and then modify The_Loop to exlude posts with a custom field at a certain value?
Something to ponder at any rate.
So I pondered.
What I came up with is overly simple, but works so I figured I'd share.
First, edit the post that you don't want to show on the front page and add a custom field of "exclude" to it. The value of that field can be anything... we're not going to check the value, we just want to see if the custom field exists for the post.
Do this each time you want to set a post to not show in the main list.
You'll find the custom field section on your post editor page, just scroll down a bit past the image uploader. Click that picture to the right for an example.
Now, to actually use that custom field, we need to add two lines of code to your theme's index.php.
In most themes' index.php, you'll see a line like this:
-
<?php while (have_posts()) : the_post(); ?>
Right below that, add a new line of code. The result will look like this:
-
<?php while (have_posts()) : the_post(); ?>
-
<?php if ( get_post_meta($post->ID, 'exclude', true) == '') { ?>
That new line basically says, "look for the custom field named "exclude" associated with the post. If it is NOT there (that's the == '' bit) then proceed. As you might guess, if the custom field does exist, we pretty much drop it on the floor and move along.
A bit lower in the code, you'll see:
-
<?php endwhile; ?>
Right before that line, let's close that if statement we just added:
-
<?php } ?>
-
<?php endwhile; ?>
Done!
Caveats!
Some WordPress theme's use their index.php file for a variety of views and purposes. If your theme is one of those, this will probably wreak havoc and likely drop locusts from the sky. Let's try to avoid that.
First off, a glance at the Template Hierarchy documentation may help what follows make a bit more sense...
Remember, we don't want the post on the front page or main listing, but we do still want it to show up in the category archives (clicking that link may be helpful as well). If your theme doesn't have any category or archive specific template files, that post you just excluded will never show up anywhere! That's not desirable... but easily fixed.
So check: Does your theme have an archive.php? A category.php? A category-x.php? Then you're probably fine. If not, copy your index.php to archive.php (undo the changes we just made in the new archive.php) and you should be good to go.
Hope that makes sense and hope this might help someone out in the future.
[1] - Two that I frequently suggest are:
- The Category Visibility plugin.
- The Ultimate Category Excluder plugin
Tags: blog, category, support, tip, WordPress
Possibly Related Posts
Comments
16 Responses to “How-to: Another Way to Exclude Posts From the Front Page”
Leave a Reply
Why?
Would this be to keep things for feed-readers only?
That would be one reason, yep. I have a simple way of excluding posts from feeds (only) two that I should write up someday.
Some folks like to only include one or two categories on the main site (site news, club announcements, etc). Some folks use WP as a Content Management System and may have a lot of content as posts, but really only want it to show in category views. Etc. etc.
I cant keep wondering why you want to exclude posts from the front page. Blogging should be open as it states what is in your mind?
Just my 2 cents and way to go on your blog!
Mapblog, did you read my earlier comment right above your comment? Secondly, did you read the first paragraph of the article?
Hopefully, combining those two will help give some context to why I wrote the article. It’s not about being “non-open”. It’s about being flexible.
Also do note, this method doesn’t “stop” anything from going through the RSS feed. Can’t be much more open than that!
Good post! This is especially useful if you want to create articles as google food or posts that won’t appeal to your readers.
Hrm…
So I could I have index1.php that was all my post about fishing, but none of my posts about papier mache’ and have index2.php show all my papier mache’ posts but none of my fishing posts and index.php show all my posts together.
That way instead of having simplebooks.com, simplerich.com, etc…. I could have one blog with all that stuff only split the URL.
No, wouldn’t work. The feed would be terrifically confusing to all 3. I thought I’d found something wonderful for a minute there.
@Patrick - google food? Now there’s a term I hadn’t met yet!
@Rich - there may be easier ways to accomplish that through the joys of categories and category templates.
Thanks! I can actually use this bit of code for something that I have been wanting to do.
Andy, glad you found some aspect of it helpful.
… oh, and I’m very intrigued by your purple potato salad!
Gotta love the web. I was looking for this exact question and found my exact answer. Thanks Chris
CMS - so glad it was helpful. Thanks for stopping by.
As is got the discussion on wp-forums, i want to add this one for community over here too. another sollution would be to use a category-retriction tool. so only looged in users (who got an account) would see (for e.g) where the illegal techno party would be tonight … hehe. got the point?
I did everything Fine..but the Post isn’t appearing anywhere…. BUT i have a File called ARCHIVE.PHP
@Jad - archive.php isn’t the same as archiveS.php…
How is this “overly” simple? Something that is oversimplified is a thing pared so much it is no longer accurate or functional. This does appear to be “extremely” simple, however.
I’m sorry it doesn’t seem extremely simple to you.
I used the term “overly simple” to mean that the following examples are functional but a clever or more knowledgeable person would probably want to flesh things out a bit.
In other words, it’s a coarse approach that doesn’t pretend to code for edge cases.