We didn’t want events showing in the RSS feed, this is the code I ended up with:

// Keep events out of RSS
add_filter('pre_get_posts', 'exclude_category_from_feed');
function exclude_category_from_feed($query) {
	if ($query->is_feed) {
		$query->set('cat','-'.get_cat_ID( 'Events' ));
	}
	return $query;
}

Adding that bit of code to the functions.php file for your theme will prevent posts in the “Events” category from appearing in your RSS feed. You can obviously change “Events” to whatever category you want to exclude.

It can be extended too, not just limited to keeping a category out of the RSS feed. For example, to keep a category off the home page or archive pages, you can change this:

if ($query->is_feed) {

To this:

if ($query->is_archive || $query->is_home) {

That’s it! Hope you find it useful.

The theme was designed by Jesper, all I did was turn it into a WordPress theme.

If you want to know more about HTML5Press, you can read the announcement post, check out the demo site, visit the HTML5Press page, or view the project on Github.

If you have any questions, feel free to ask in the comments on this post or in the comments on the HTML5Press page.

Please report any issues, bugs, or anything broken at the Github issues page for HTML5Press.

You can download HTML5Press here.

Hope you like it!

Not a whole lot has changed since 1.5.3, but the changes that were made are significant. Unwakeable 1.5.5 is compatible with WordPress 3.1.

The most notable change is the removal of title.gif file. That was the image file with “Unwakeable” written on it that sat in the top left corner. Instead of that image, text is now used. The name of the WordPress site is pulled and used in place of the image. You can see a demo over at the Unwakeable demo site.

I’ve also added support for custom menus that were introduced in WordPress 3.0. By default, the top menu is a list of pages. If you want to use a custom menu just set one up in your WordPress dashboard (Appearance –> Menus) and set that menu as the “primary navigation”.

My goal with this release of Unwakeable was to get it included in the WordPress theme directory. It’s still pending approval or rejection in the theme directory. If it’s rejected I’ll make the necessary changes, bump the version number, and submit it again.

If you’re interested in the exact changes that were made in Unwakeable 1.5.5, have a look at the following revisions in subversion:
r131
r132
r133
r134

The latest revision is r135 but that was just to tag the 1.5.5 release in subversion.

If you have problems or find something broken, please submit an issue on Github and I’ll look into it.

I like using the 1kb css grid system for laying pages out, so you can see what I use for css in the zip file. If you want to roll with that setup, you can just copy and paste the contents of css.css into the style.css file for your theme. And move sign.png into the images/ folder for your theme. You’ll also want to do something with the blog-directory.php file.

blog-directory.php is a custom page template for Twenty Ten. If you’re using the Twenty Ten theme, you can just drop blog-directory.php into the “twentyten” theme folder and be done. If you’re using another theme you’ll need to open blog-directory.php and copy everything between <!– start blog directory –> and <!– end blog directory –> and paste it into a custom template for your theme.

If you’re not familiar with custom page templates in WordPress, you can read about them here.

Download blog-directory.zip

Steve’s code is exactly what I was looking for. I made a few modifications to his code and wrapped it all into a custom PHP function, which you can see below.

Download The Code

The function returns an array that contains each category name, the CSS class that should be applied to the given category, and the category ID for linking to the page showing only questions in that category.

<?php
function tagCloud($maximum=0) {
	$cats = array(); // create empty array

	$query = mysql_query("SELECT categories.catDesc, categories.catId, COUNT( questions.id ) AS totalQuestions FROM questions, categories WHERE questions.categoryId = categories.catId GROUP BY categories.catId;");
	while ($row = mysql_fetch_array($query)) {
		$cat = $row['catDesc'];
		$counter = $row['totalQuestions'];
		$catid = $row['catID'];

		// update $maximum if this term is more popular than the previous terms
		if ($counter> $maximum) $maximum = $counter;

		$percent = floor(($counter / $maximum) * 100);
		if ($percent <20) {
			$class = 'smallest';
		}
		elseif ($percent>= 20 and $percent <40) {
			$class = 'small';
		}
		elseif ($percent>= 40 and $percent <60) {
			$class = 'medium';
		}
		elseif ($percent>= 60 and $percent <80) {
			$class = 'large';
		}
		else {
			$class = 'largest';
		}
		$cats[] = array('term' => $cat, 'class' => $class, 'catid' => $catid);

	}
	return $cats;
}
?>

You’ll also need some CSS to style your tag cloud. This CSS is pretty much identical to what Steve published, I only made some minor changes to font sizes.

#tagcloud {
    width: 300px;
    background:#FFFFCC;
    color:#0066FF;
    padding: 10px;
    border: 1px solid #FFE7B6;
    text-align:center;
}

#tagcloud a:link, #tagcloud a:visited {
    text-decoration:none;
}

#tagcloud a:hover, #tagcloud a:active {
    text-decoration: underline;
    color: #000;
}

#tagcloud span {
    padding: 4px;
}

.smallest {
    font-size: 10px;
}

.small {
    font-size: 12px;
}

.medium {
    font-size:14px;
}

.large {
    font-size:16px;
}

.largest {
    font-size:18px;
}

To use the function, do something like this:

<?php
$tagCloud = tagCloud();
foreach ($tagCloud as $t) {
	$cat = $t['term'];
	$class = $t['class'];
	$catid = $t['catid'];
	print "<span class=\\"$class\\"><a href=\\"category.php?id=$catid\\">$cat</a></span>";
}
?>

I am still testing this code, but so far it seems to do exactly what I need it to do. It’s best to use tagclouds in a virtual private server provider that supports PHP, MySQL and CSS. If you experience trouble with the code or if it doesn’t act as expected, please let me know in the comments. If you’ve got ideas on how to improve the function, I’d love to hear your thoughts as well!

K2 1.0 added more support for WordPress 2.9. For example, K2 1.0 supports new WordPress features such as post thumbnail images. One of the more noticeable changes to K2 since the 1.0 release is the absence of SideBar Manager (SBM). It sounds like it was simply too much work to maintain SBM, and was beyond the scope of what K2 is:

It’s worth mentioning that the last remnants of the old SideBar Manager, or SBM, have now been removed from the codebase. It started out as a fully-fledged replacement for WP’s lacking widgets system and ended up as a patch-of-sorts to the widget system, allowing for widgets to be placed only on specified pages. But in the end, while the native widget system is still very much in need of an update, it didn’t feel right for K2 to try and cover that particular area of the administration interface. And besides, other plugins for doing just that exist already.

So instead of spending our time patching that system for an ever-changing WordPress, our time is probably better spent on more theme-specific functionality, like the rolling archives or livesearch systems, as well as keeping up with new WordPress features, like for instance Post Thumbnails.

Rather than break down all of what’s changed in recent versions of K2, I’m going to make it easy on myself and direct you to the K2 1.0 release announcement. Just know that Unwakeable 1.5.3 sports all the features found in K2 1.0.3. You can comment on this post or on the Unwakeable page with questions or comments.

This release adds support for Threaded Comments and Child Themes. Styles have been improved. You can specify where Styles are stored at, activate multiple styles, and edit them in the WordPress Theme Editor. You can also now customize the Post Meta (the line that reads Published by John Doe…) without having to edit any code.

I plan on building the next version of Unwakeable in the next couple weeks and will likely base it off of K2 1.0-RC8.

Unwakeable 1.5.3 rc1 is up-to-date with K2 r776. K2 no longer includes the K2 Sidebar Manager. If you were using K2 Sidebar Modules and want to continue using it, you can download the plugin here.

There’s a new option on the Unwakeable Options page that allows you to customize top and bottom meta information for each post. The top meta information will be displayed directly under the title of a post. The bottom meta information will be displayed at the end of the posts content. You can use the following keywords to define what information you want to show: %author%, %categories%, %comments%, %date%, %tags% and %time%.

Have a look below to see what to enter in the top meta and bottom meta sections to display the same information that’s being displayed here.
Top Meta: Published by %author% on %date% at %time% %comments%
Bottom Meta: Categories: %categories% %tags%

You can download Unwakeable 1.5.3 rc1 from the Unwakeable page, or click here to download it directly.

The first thing you’ll notice about 2.7 is its new interface. From the top down, we’ve listened to your feedback and thought deeply about the design and the result is a WordPress that’s just plain faster. Nearly every task you do on your blog will take fewer clicks and be faster in 2.7 than it did in a previous version.

The latest stable version of Unwakeable, 1.5.1, seems to work just fine with WordPress 2.7, from what I’ve seen anyway. If you have any problems with Unwakeable 1.5.1 with WordPress 2.7, you may want to give Unwakeable 1.5.2 release candidate 1 a shot. As of this post, it’s current with K2 r739. Unwakeable 1.5.2 rc1 is currently running this site and appears to be very stable. I hope to have Unwakeable ready for inclusion in the WordPress theme directory by the time 1.5.2 is officially released.

If you have any problems with either of these versions of Unwakeable, please let me know by leaving at comment at the Unwakeable page.