As I’ve been using WordPress more and more for blogging, I’ve started to get increasingly impressed, especially with the recent 2.7 and 2.8 versions. At work, I’m currently looking for a multi-user platform that can do more than just common-or-garden blogs, and WordPress (or sibling WordPress MU) is a good candidate.
Anyway, there are so many plugins for WordPress that it’s often hard to know which will serve your needs the best.
One that I’ve just implemented is really helpful: Custom Post Limits, written by Scott Reilly.
In the basic WordPress configuration, your blog consists of detail pages, which display a single blog post + comments, and archive pages, which display a series of posts.
Those archive pages can list posts belonging to the same category, marked with the same tag, posted in the same month, etc., but for each archive page, the number of posts included has to be the same.
With many WordPress template themes, that’s not a problem. However, since I switched to using Vigilance, that hit a snag.
On the front page of the blog (which also, for the sake of a whole lot of hair-splitting, should also be considered an archive) I want to list the most recent posts in full. For reasons of practicality, this limits the number of posts to display to about 10.
However, Vigilance’s archive and search pages only include the post title, not any element of the body. This means that the 10-post limit creates a page that is substantially shorter, and the list of relevant articles can split over multiple pages.
The Custom Post Limits plugin gets round that limitation by allowing you to specify how many articles to include on each type of archive page. Defaults trickle down the system: you can set a default for archives in general, and then override that default for, say, category archives.
What’s more, if you need really fine control, you can drill down to individual category level. Most blogs won’t need that, but if your setup demands such things, this plugin will be invaluable.