While working on the new theme for the site, I quickly realized that I didn’t want to show pages in any of the searches on the site. I only wanted posts.

It was easy enough to find articles that illustrated ways to exclude certain categories or posts by ID, so I decided to apply those methods to pages as well. Simply paste the following into your theme’s functions.php file.

1
2
3
4
5
6
7
8
9

function gdmExcludePagesInSearch($query) {
	if ($query->is_search) {
		$query->query_vars['post__not_in'] = get_all_page_ids();
	}
 
	return $query;
}
 
add_filter('pre_get_posts', 'gdmExcludePagesInSearch');

This will remove all pages from the loop, and only on the search page.

Something unclear, or have something to add? Please leave a comment.

The project was really meant to extend an existing widget, and it seemed confusing to have both the default and extended version there side by side (plus it would be really nice to call them the same thing for transparency). I needed to get rid of it. You can’t just overwrite an existing widget by registering a new one by the same name – WordPress ignores it. And if I did manage to find a way to remove a default widget, when do you have to do it?

Luckily, some digging around found a solution.

1
2
3
4
5
6
7
8
9
10

function gdm_widget_meta_register() {
	// unregister the widget and its control
	wp_unregister_sidebar_widget('meta');
 
	// register the new and improved widget and control
	wp_register_sidebar_widget('meta', __('Meta'), 'gdm_widget_meta');
	wp_register_widget_control('meta', __('Meta'), 'gdm_widget_meta_control');
}
 
add_action('widgets_init', 'gdm_widget_meta_register', 1);

The really important pieces are the wp_unregister_sidebar_widget function and the widgets_init action hook. widgets_init actions are run right after all the default widgets are registered, giving us the perfect opportunity to call wp_unregister_sidebar_widget with the ID of the widget you’re getting rid of. Now you can register your own widget and control, effectively replacing a default WordPress widget.

And so we have the Home Page Link plugin.

The Plugin

The plugin does just what you think – adds a Home link to your site navigation (wp_list_pages). And it’s very easy to use.

1. Download and unzip the plugin archive.
2. Place the plugin file under wp-content/plugins directory on your WordPress Installation
3. Log in to your admin interface and activate Home Page Link under the ‘Plugins’ tab

That’s it! You should now be able to view your site with its shiny new Home link.

Like my other plugins, I hope to keep this going as a work in progress, and work along with the WordPress community to make it more useful and efficient. If you have something you’d like to see in an upcoming version, please don’t hesitate to add a comment or contact me.

Requirements

The current release requires a server running at least PHP4. The plugin has been tested on WordPress 2.x. If anyone has gotten it working on older versions of WordPress, please let me know.

Resources

If you’re interested in writing plugins, the WordPress Plugin article is an excellent resource.

Download the Plugin

All source code is provided under the Creative Commons Attribution-Sharealike License. If you agree to these terms, please download the plugin now.

I’ll still be hosting and supporting the plugin here for any of you that like to go straight to the source, but I’m hoping it will be easier to find and discover by other WordPress users over on the plugin site.

Here’s how I write my most of my CSS now.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

#menu ul {
	list-style: none;
	margin: 0;
	padding: 0;
}
 
#menu ul li {
	height: 1.2em;
	line-height: 1.2em;
}
 
#menu ul li a {
	color: #006699;
}
 
#menu ul li a.here {
	color: #999999;
}

Now that’s not very hard to read, but amongst hundreds, if not thousands, of other lines of CSS, it’s quite easy to lose track of those 18 lines. And I, being the unorganized designer I am, tend to throw lines of CSS in the middle rules that should otherwise be grouped together. And those relationships are quite important when we need to debug a design issue caused by a child inheriting styles from a parent. The CSS syntax really lends nothing to natural organization.

One way I’ve tried to become a more efficient with the current CSS model is through rule and style separation by files. For instance, I may create files like design.css, typography.css, etc. But then I run into scenarios where I can’t decide which files to keep certain rules in, since they may apply to both, and eventually that system collapses upon itself.

I’ve thought long and hard about how CSS can improve (and hopefully make us more productive). One idea is illustrated below.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

#menu {
	ul {
		list-style: none;
		margin: 0;
		padding: 0;
		li {
			height: 1.2em;
			line-height: 1.2em;
		}
	}
	a {
		color: #06699;
		.here {
			height: #999999;
		}
	}	
}

As you can see, I’ve nested my styles within parents to show relationships more efficiently. Nothing can come between any of the rules for the #menu element.

Another way this solution could help is by making it much easier to collaborate. My colleagues rarely organize their CSS files exactly like mine, and when we’re trading these files back and forth, there’s a lot of time spent familiarizing ourselves with each other’s personal style. I’m not saying that a syntax like this would completely cut out a “familiarization period”, but it would definitely reduce it by creating a rule-grouping standard.

I’m curious to know how you think CSS could be made more efficient and cleaner. It’s definitely a subject I want to discuss more.

If you’re going to be in Austin and would like to meet up, please don’t hesitate to contact me.

In case you’re wondering, this has nothing to do with Textdrive, my current host. I can say nothing but good things about the company and the community. I’m just very excited about the Grid Server technology and wanted to give it a try.

The motivation behind this plugin is the fact that excluding categories is somewhat of a barrier to those of us who are not programmers. It used to be that we would have to dig through PHP templates and add exclude=2,7 to the wp_list_cats tag. To clients or anyone not familiar with the WordPress system, that may seem like an impossible task. And, for those who are comfortable with the WordPress system, it can be just plain annoying. The Category Link Manager attempts to make things just a little bit easier.

One last note: I’d like to thank Valerie for sharing this idea with me.

The Plugin

The Category Link Manager Plugin is a WordPress plugin that adds an administration panel that allows users to pick which category links are included in the site navigation. It also provides a function that uses these settings to replace wp_list_cats. Adding it to your WordPress installation is as easy as ever.

1. Download and unzip the plugin archive.
2. Place the plugin file under wp-content/plugins directory on your WordPress Installation.
3. Log in to your admin interface and activate Category Link Manager under the ‘Plugins’ tab.
4. Go to the new panel under the ‘Manage’ tab called ‘Category Links’.
5. Select and update the categories you want included in your site navigation.
6. Open the source of the template file where you call the wp_list_cats function (the default file is sidebar.php, however it may be different if you’re using certain plugins) and replace it with gdm_list_selected_cats.

If you’re wondering, gdm_list_selected_cats is what does all the work for us. It takes the categories we chose to include in the navigation and works out what categories it should exclude. Besides that, it acts exactly like wp_list_cats — it even takes the same parameters.

Here’s a few examples of what we can do:

[php]
// sort the categories by name
gdm_list_selected_cats(‘sort_column=name’);

// sort the list by name and show empty categories
gdm_list_selected_cats(‘sort_column=name&hide_empty=0′);

// sort the list by name and manually exclude
// additional categories
gdm_list_selected_cats(‘sort_column=name&exclude=2,7′);
[/php]

Like my other WordPress plugins, I hope to keep this plugin going as a work in progress as it helps make content management just a little bit easier. If you have any problems, questions or suggestions, please let me know.

Requirements

The current release requires a server running at least PHP4. The plugin has been tested on WordPress 2.x. If anyone has gotten it working on older versions of WordPress, please let me know.

Download the Plugin

All source code is provided under the Creative Commons Attribution-Sharealike License. If you agree to these terms, please download the plugin now.

I’m a guy who thinks that WordPress wouldn’t be the success it is without the community involvement around it. So, I’m currently looking for some volunteers to help translate some of the output the plugin produces. It’s pretty much just small, but important, things like page headings and form labels and instructions. I’d like to get as many translations as possible for this next release, and I’m open to taking any localizations people are willing to provide.

If you’re interested in helping out, please download the translation file and email it to gmurphey@gmurphey.com once you’re done.

Just for the record — I took four years of Latin in high school, so unfortunately I can’t really contribute any translations for the plugin — unless someone really, really wants a Latin version.

The Functions

Since this is a new feature with this release (v0.2), there are only a few, but powerful, developer functions available.

bool gdm_is_excluded_page($id)
$id (Required). The page ID in question.
Returns TRUE if Page Link Manager has the page registered as excluded.

array gdm_get_excluded_pages()
Returns an array of all the pages Page Link Manager has registered as excluded.

string gdm_page_links_rebuild_query($query)
$query (Optional). A wp_list_pages style query string.
Rebuilds and returns a query string with dynamically generated exclude values.

If there’s anything you’d like to see added in the next version, please let me know.

Download Now

All source code is provided under the Creative Commons Attribution-Sharealike License. If you agree to these terms, please download the plugin and developer functions now.