tadhg.com » WordPress

sabbatical.close()

Tadhg — Mon, 17 May 2010 06:36:56 +0000

After a highly enjoyable, productive, and extended period, it’s time for me to return to the world of paid work.

I’m quite happy with the things I’ve done during my time off. Many of them are important only to me, but then, it’s been my time off.

Here are some of the things I’ve done since leaving Metaweb that I consider significant:

CrossFit. I’m approaching the one year mark, and it’s hard to overstate the importance of that for me. This is the first time in my life I’ve managed to keep an exercise routine of any kind going for that long. Not coincidentally, I’m also in the best shape of my life. I now feel that some kind of regular, intense, exercise has a similar place in my life to my morning pages—that is, something I I regard as mandatory and more or less permanent.
Diet. Not just switching back to eating meat, but also radically cutting down on sugar and processed foods. This also has a lot to do with my being in good shape.
Document format. Until this year, I hadn’t found a text-based document format I liked, but I have now finally settled on reStructuredText. One of the effects of this is that I shifted to doing all of my writing in a text editor rather than doing some of it in word processors. Another effect is that all of my writing is now much more amenable to programmatic manipulation.
Programming my own environment. Following from the previous item, I spent quite a bit of time working on solutions to various small niggles in my workflows, so that far less of my time is consumed by setup for writing. Some examples of this include scripts to insert the template for blog posts into my editor, scripts to publish to my blog directly from my editor, scripts to do word counting precisely as I wish it to be done, and many other small utilities that remove minor annoyances that I previously encountered almost every day. In many respects this kind of thing is precisely what programming and computers are for: to make it easier to create, and to lessen the gap between a thought and expression of that thought.
Digital organization. This includes recovering my subversion repository, restoring my blog to proper working order, and various other steps that have made my digital domain much more manageable. This is bound up with the previous item too.
Switching to Vim. This was probably a long time coming, but nevertheless required a fair amount of work, not least in porting all my scripts for jEdit over to it. I’ve been extremely happy with Vim. I think that to most people this might sound trivial; how many people would regard switching word processors as an “achievement”? But a text editor is different from a word processor, and switching to Vim isn’t like switching between non-modal text editors. This, combined with moving all my writing to text editors and thus to Vim, is a profound change for me, and one that I’m very happy I took the time to get through.
WordPress plugins. I wrote some of these to improve my blog after I got it working again.
PyWordCount. My word counting script/Vim plugin is done, but I have to finish the documentation for it and make it public. It’s significant to me because it’ll be my first self-contained public Python project, and also because it’s an outgrowth of the document format switch, the Vim switch, and the focus on programming my own environment to a much greater degree.
Q’Rith. I ran my first roleplaying sessions in 15 years, and am currently running my first roleplaying campaign in 15 years, in a world that I’ve created and am quite happy with so far.
Tennis. I started playing it again, and don’t know why I ever stopped.

Those are the main highlights. Many of them are internal, or are things that only I notice, but I think the effect they’ve had on me is actually quite major, and in positive ways.

As for what’s next, I’ll write about that tomorrow.

Tags: coding, CrossFit, diet, document formats, exercise, food, games, goals, personal, python, reStructuredText, roleplaying, software, sports, T, tech, tennis, text editing, version-control, Vim, WordPress, writing

WordPress 2.9 Upgrade

Tadhg — Sun, 10 Jan 2010 23:56:30 +0000

I upgraded this blog to WordPress 2.9 today, and it appeared to go entirely smoothly. Please let me know if you notice any breakage.

Tags: Blog, coding, PHP, tech, web-development, WordPress

404 Pages

Tadhg — Fri, 11 Sep 2009 07:36:15 +0000

wpbeginner has a list of their favorite WordPress 404 pages. There are some good ones in there, but none of them do what I think they should do—that is, as well as provide helpful links to popular pages, also provide a list of guesses about where the user was actually trying to go. Coincidentally, today I also read this excellent article about finding the longest common subsequence between two strings. So, at some point, I’ll improve my blog’s 404 page so that it calls, probably via asynchronous request, a Python script that checks the user’s requested URL against all valid URLs WordPress knows about, and then suggests to the user whatever the closest matches are. I’m somewhat surprised that this isn’t done more often, but it seems that far too many sites are really blasé about 404s.

Tags: PHP, python, web-development, WordPress

Better reST–WordPress Pipeline

Tadhg — Wed, 29 Jul 2009 07:15:47 +0000

Last week I posted about my setup for going from reStructuredText to WordPress. It involved a shell script, some Python scripts, and the pbpaste and pbcopy commands. It worked, but it was a little on the convoluted side.

Now I have a slightly better process, and one that I will have used to publish this post.

The previous version was launched via Quicksilver and operated on the contents of the clipboard; the new version is run from the command line—or, even better, from within jEdit—and operates on a file. It:

Runs the contents of the file through my reST–Wordpress script, which uses rst2wp and some customized other Python scripts.
Submits the transformed text to WordPress via python-blogger, a script for doing blog XMLRPC operations in Python.
Runs svn add on the file.
Opens the WordPress Edit Draft page for the submitted post.

So, the previous steps for me were:

Write post in reStructuredText in jEdit.
Select all.
Copy.
Invoke a shell script via Quicksilver.
Switch to WordPress new post tab in Firefox.
Paste.
Fiddle with the post settings slightly.
Post.

While the new ones are:

Write post in reStructuredText in jEdit.
Save.
Invoke a jEdit macro to run the Python script from within the editor.
Switch to WordPress new post tab in Firefox.
Fiddle with the post settings slightly.
Post.

(As a bonus, this version also adds the file to Subversion.)

The jEdit macro seems

These are the components necessary to make it work:

Docutils—of course, to handle the reStructuredText
rst2wp, which I’ve modified a little for my own purposes.
python-blogger, to talk to WordPress in Python.
WordPress with XMLRPC enabled so that software can talk to it.
A short script of my own that pulls the pieces together. (This uses os.subprocess, so Python 2.4 or better is required)
A jEdit macro to run the script from the last step within the editor.

I’m pretty happy with it, and I think it should be fairly cross-platform, which is important to me as I’d like to take this whole setup with me if I switch environments in future.

Tags: coding, personal, python, reStructuredText, software, tech, web-development, WordPress

Blog Workflow with reStructuredText

Tadhg — Wed, 15 Jul 2009 06:57:00 +0000

I wrote about moving my writing over to reStructuredText on Sunday, and since then I’ve moved both my morning pages and my blog writing to it. The latter proved more complicated, primarily because I wanted to make the process almost as easy as writing pseudo-HTML (which is more or less WordPress’ native format, and kind of mine, too, for the last several years). With some hacky wrangling, I’ve managed to set that up.

I don’t write my posts in the browser. That’s too prone to crashing, and I like my text editor, jEdit, too much for that. On top of that, I want to be able to use Subversion for my posts, as I do for more or less everything I wrote. So for the last couple of years, I would write the posts in jEdit and then copy and paste the finished product into the WordPress new post window.

Since I generally tinker with a few things once I see the post preview, it’s never been worth it to me to try to do automatic posting from the command line, which I know is theoretically possible with WordPress. I thought I might move in that direction given the reStructuredText move, but it didn’t work out that way.

One option was to use the rest-wordpress plugin, which would do the reStructuredText parsing on the blog side, so that my workflow would be to paste the reStructuredText source into the WordPress edit field as usual, and then have it turn it into HTML. While that seemed a reasonable option, I was eager to create some custom directives that would let me make reStructuredText even more useful. Sadly, custom directives aren’t that easy to add in, and I decided that if I planned to develop those, I should do it locally rather than on the server side.

The old workflow was:

Write post in pseudo-HTML in jEdit.
Select all.
Copy.
Switch to WordPress new post tab in Firefox.
Paste.
Fiddle with the post settings slightly.
Post.

The new workflow:

Write post in reStructuredText in jEdit.
Select all.
Copy.
Invoke a shell script via Quicksilver.
Switch to WordPress new post tab in Firefox.
Paste.
Fiddle with the post settings slightly.
Post.

Just one extra step, and that step consists of hitting Command-Space, typing blog, and hitting return. Given how easy that is, I’m quite happy with it. Particularly since some of my custom directives make certain kinds of content easier, and because reStructuredText is better to compose in than psuedo-HTML.

In fact, when I first wrote about reStructuredText, I complained about the hyperlink format, but having written a blog post or two with it, I find that I actually prefer it. It makes it easier to highlight the links and then go get the actual URLs later, if that’s what I want to do, and if not the short link syntax is actually fine.

Getting to that workflow turned out to be fairly tricky. I’m sure that I could have approached it in ways that would have made things easier. The critical components are:

A local install of Docutils
rst2wp, a WordPress writer for reStructuredText by Matthias Friedrich.
Some pre- and post-processing Python scripts.
The OS X Terminal pbcopy and pbpaste commands, which I wasn’t really aware of before.
A shell script to tie it all together.

This is what happens, thanks to a combination of those components, when I invoke the shell script with Quicksilver, after I’ve copied the text in jEdit:

The shell script pastes the contents of the clipboard to the pre-processor, which strips out some things, like metadata that I have in the file but don’t want in the post, and puts the newly-cleaned content into the clipboard
The shell script pastes the clipboard to rst2wp, which then puts its output to the clipboard.
The shell script pastes the clipboard to the post-processor, which does some minor rearranging to suit my particular workflow.

All of which saves what would be quite a lot of time if I had to do the cleanup by hand.

One of the major obstacles I encountered was, of course, character encoding. I’ll probably write that up later this week, because the solutions are poorly doumented, and it’s not a fun thing to bang your head against.

At some point I might try to clean the scripts up and to make the effort to post to WordPress directly. I think the best way for that to work would be to submit the post as a draft, get the id of the draft, and then open a browser window with that draft open for editing. That would save at least a moment or two… the tricky part, it appears, is getting the tags to submit properly.

I do have some issues with reStructuredText, but need to put a little more thought into how I think they should be fixed before posting about them. I’m primarily unhappy with how custom directives are handled.

All in all, very much a developer’s endeavor: lots of effort to make something seem almost exactly the same for benefits that most people wouldn’t notice or might think of as disadvantages.

Tags: coding, personal, python, reStructuredText, software, tech, web-development, WordPress

PyWebSF Site Update

Tadhg — Tue, 23 Jun 2009 23:46:01 +0000

I did some work on the PyWebSF site, so that it looks rather better than it did with the default WordPress theme. I altered a pretty good WordPress theme called Arras Theme, which I was fairly impressed with. As a reminder, the first meeting is tonight.

Tags: design, python, web-development, WordPress

WordPress 2.8 Upgrade

Tadhg — Mon, 15 Jun 2009 01:44:08 +0000

Today I upgraded this blog to WordPress 2.8, a relatively smooth process. I ran into completely unrelated problems (hitting the process limit for my shell account) that derailed things for a while, but the WordPress upgrade itself was smooth.

I use Subversion to upgrade, first using
svn export --force http://core.svn.wordpress.org/tags/2.8/ .
in my development environment, seeing if things look okay there, then checking in the 2.8 changes to my own repository (the only niggly part because I neglected to clean the dev environment of changes before the export, so I had to look through things to see what was part of the upgrade), backing up my live database, and then checking the changes out to the live environment. It all looks fine, and hopefully will continue to function normally.

Tags: Blog, coding, PHP, tech, web-development, WordPress

Fiction Organization

Tadhg — Sun, 24 May 2009 23:04:21 +0000

I made a WordPress page containing a list of all the fiction I’ve published on this blog. I had to do this by hand, because it appears difficult to get a reasonable list using various WordPress approaches (such as tags). The page I created is hardly a masterpiece of user interface design (I hope to improve it significantly over time), but it’s better than what was there previously.

I will end up making it more complicated from a code point of view, because I want to be able to display by each link the publication date and some of the tags of the piece—and I don’t want to have to edit those by hand. This mix of manual selection and arbitrary tagging isn’t handled very well by the current WordPress functionality, which isn’t that surprising. I did think it would be slightly easier to achieve than it looks like it will be, however.

The series plugin I hope to write at some point would address some of the issues, by making it easy to get a list of links to each piece in a series, but even that wouldn’t address the lists that aren’t series.

One of the problems is with tagging. Partly it’s a nomenclature/overloading issue: I use the “fiction” and “writing” tags to mean not just my fiction and writing, but also the works of others and commentary on fiction and writing. For some reason the notion of a “my fiction” tag is unappealing to me.

The notion of a “my favorites” tag even less appealing. I don’t mind putting together a list of the pieces that I’m most happy with, but somehow tagging each one of them as a favorite seems extremely cheesy. That might be nomenclature again, and I could perhaps get around it somehow by having a less cloying name for the tag. I need to think about that one further and see if I can figure out just what the problem is.

Until I do, though, having all of my fiction work handily linked from one page is a significant advance (the power of HTML!). Use it to find stories of mine to read or re-read—and, hopefully, enjoy.

Tags: Blog, fiction, WordPress, writing

Bad Behavior Plugin

Tadhg — Tue, 07 Apr 2009 18:55:14 +0000

The various blog moves and reworkings seemed to reduce the amount of comment spam I was getting, but now it’s gotten out of hand once more, so I’m resuming the use of the Bad Behavior WordPress plugin. Hopefully this isn’t something any legitimate readers or commenters will notice, but if for some reason you find it affecting you, please let me know via email.

Tags: Blog, WordPress

WP Plugins: Recent Commentary and Show Tags in RSS

Tadhg — Tue, 24 Mar 2009 03:38:25 +0000

I finally got around to writing up docs for, and then packaging, the two WordPress plugins I’ve finished recently:

Recent Commentary Widget, which contains the code used for the current comments sidebar on the main page and which I described here.
Show Tags in RSS, which adds a list of the tags for a post to the end of the post’s entry in the RSS feed.

I’m currently looking at support for series in WordPress, and am considering either writing my own plugin or using/forking the Organize Series plugin.

Tags: Blog, coding, PHP, SQL, tech, WordPress

Some RSS Changes

Tadhg — Fri, 20 Mar 2009 03:44:20 +0000

I’ve made some changes to my Related Posts by Tags plugin, so that it’s now possible to add the list of related posts to the RSS feed entries. As I was experimenting with this, I realized that I wanted the RSS entries to show the tags for a post as well, so I wrote a (very simple) plugin to do that, too.

As a result, those of you reading this via RSS will now see a list of tags at the end of posts, followed by links to related posts. Please let me know if this doesn’t work as intended, or if you have other comments on the change.

Tags: Blog, coding, PHP, tech, WordPress

New Blog Functionality: Recent Commentary

Tadhg — Tue, 24 Feb 2009 05:39:10 +0000

I’ve had a Recent Comments section on the front-page sidebar of the site for quite some time, and decided it was time for an upgrade. The old version was straightforward: it displayed a list of the most recent comments and who made them. What I decided I wanted was, rather, a list of the posts with the most recent comments on them, how many comments there were, and a list of the people who made the comments in timestamp order.

That’s what I have on the front page now. I wrote this functionality as a WordPress plugin, and will release it sometime soon—I’m not doing so yet because to work as expected it needs the user to write some CSS, so either I write docs on how to do that, or I add an option to insert some styling with the widget HTML.

I think it’s a better approach, because it displays more information in about the same area, and because it allows posts with discussions to remain present in the widget for longer, rather than being bumped off due to multiple comments about some single post. I think that’s likely to be more interesting.

At the heart of the plugin are two SQL queries that I couldn’t figure out how to turn into a single query, and which took me a little while to figure out.

The desired result is a list of the n posts with the most recent comments on them, and a list of the comments for each post, with the comment list linked to the post in some fashion. I initially thought that the first query would be easy, but I was making poor assumptions about SELECT DISTINCT that mean that I was actually getting a list of the posts with comments ordered by the time of the first comment, not the latest comment. Simplified somewhat, the right way to do that is this:

SELECT wp_posts.ID, MAX(wp_comments.comment_date) as datesort
FROM comments
LEFT JOIN wp_posts ON (wp_comments.comment_post_ID = wp_posts.ID)
WHERE wp_posts.post_status = 'publish'
    AND wp_posts.post_type = 'post'
    AND wp_comments.comment_approved = 1
GROUP BY wp_posts.ID
ORDER BY datesort DESC

If, as I did initially, you use SELECT DISTINCT, or you use GROUP BY without the MAX function and sort by comment_date instead of datesort, it’s sorted by the first comment, not the latest comment.

From those results we have the latest posts. After putting their IDs into a comma-separated list, we can then get the comments we want:

SELECT *
FROM wp_posts
LEFT JOIN wp_comments ON (wp_posts.ID = wp_comments.comment_post_ID)
WHERE wp_posts.ID IN ($comma_separated_list_of_post_ids)
    AND wp_comments.comment_approved = 1
ORDER BY field(wp_posts.ID, $comma_separated_list_of_post_ids), wp_comments.comment_date;

This basically means “go get the comments on the specified posts”. The only interesting part is the ordering: I wanted to get the rows back so that the comments about a given post would all be together, and it turns out that the field() function is the way to do this, as it lets you sort things by whatever arbitrary order you like: it takes the column to sort on as the first argument, and a comma-separated list of values as the arbitrary order.

(It turns out that I didn’t need the ordering from field(), because of the PHP that later handles this data, but I left it in the example because it’s an interesting feature.)

After I have the results from that query, I go through them in PHP to organize into objects that I can handle more easily, essentially placing the post data at the outermost level and the comment data corresponding to each post inside the post data ($post_ids is the array of IDs of the posts with recent comments, $recent_commentary_results is the result from the latter SQL query above):

$recent_commentary = array();

    foreach ($post_ids as $key=>$value) {
        //Go through each post, extract the data relevant to it from the
        //query results, and add it to the array we're going to return.
        $postdata = array(
            "id"=>$value,
            "comments"=>array()
        );
        foreach ($recent_commentary_results as &$row) {
            //If the row matches the current post, insert the title, the
            //comment count, and add the row itself to the list of comments
            //on that post.
            if ($value == $row->ID) {
                $postdata["title"] = $row->post_title;
                $postdata["comment_count"] = $row->comment_count;
                array_push($postdata["comments"], $row);
            }
        }
        array_push($recent_commentary, $postdata);
    }

    return $recent_commentary;

That returns the required information in a format that’s relatively easy to go through and turn into HTML; none of the rest of the plugin code is particularly interesting.

I hope to release the plugin later this week.

Tags: Blog, coding, PHP, SQL, tech, WordPress

My WordPress Development Setup

Tadhg — Sat, 14 Feb 2009 00:29:20 +0000

One of the first things I did with my resuscitated blog was to figure out how I could develop for it in a reasonable fashion.

I’m pretty happy with the development environment at this point, the key features of which are:

Version Control: Subversion

Version control of some kind is simply necessary. If you really have to, you can do without something like Subversion, but there’s no real reason to—even if your host doesn’t give you shell access (in which case you should probably switch hosts), you can still use Subversion on your local machine, with your repository also running locally. That’s not an ideal situation, but it’s a lot better than no version control.

I strongly advise using the WordPress Subversion installation procedure, but with one alteration. You’re going to be keeping track of your changes in Subversion, and it’s not worth it to try to deal with svn externals for this. So instead of using svn checkout, use svn export, e.g.

svn export http://svn.automattic.com/wordpress/tags/2.7.1 .

(This also means that you should use svn export instead of svn sw when you’re upgrading.)

Separate Production and Development Code Trees

For small projects like this, a full suite of development, staging, and production isn’t necessary. But having both a production environment and a development environment is. These could be on separate machines, but in my case they’re on the same machine, as separate virtual hosts. Both code trees are local checkouts of the same project in Subversion. One useful trick for me was enabling error reporting on the development server:

php_value display_errors "1"

That line can be placed in either a .htaccess file or the VirtualHost section for the host. Here’s the list of php.ini directives, which tell you where they can be set/overridden.

Separate Production and Development Databases

You need to screw around with the WordPress database in various ways during development, and you don’t want that to alter your production site. Three simple steps will take care of this:

Create a new database (named something like yourwpdatabasename_development).

Back up the production database:

mysqldump -u MySQLusername -p yourwpdatabasename > database_backup.sql

Alter the backup file to change the hostname from your production hostname to your development hostname. The easiest way to automate this is probably to create a file called dev_setup.sql with these lines:
```
UPDATE wp_options
SET option_value="http://development_wp_url"
WHERE option_value = "http://production_wp_url";
```
and then use cat to append this to the backup file:
```
cat database_backup.sql dev_setup.sql > development_load.sql
```

Load the altered backup file into the development database:

mysql -u MySQLusername -p yourwp_development_databasename < development_load.sql

Change the wp-config.php MySQL settings in the development tree:

/** The name of the database for WordPress */
define('DB_NAME', 'yourwp_development_databasename');

/** MySQL database username */
define('DB_USER', 'yourwp_development_username');

/** MySQL database password */
define('DB_PASSWORD', 'yourwp_development_password');

(The last two settings might not need to be changed.)

One note here is that you should make sure not to check the wp-config.php file in to or out of your development tree.

Focus on Theme and Plugin Files

It should be possible to make more or less all the changes you want without altering anything but plugin and theme files. If you do change the core WordPress files, you'll have to be more careful with tracking updates, so unless your changes are extremely minor or you're planning on forking WordPress, stick to the plugin and theme directories. Further, new functionality should really go in plugins if possible. It requires some more work to develop, but it's far easier to maintain, and will make dealing with future moves or upgrades significantly easier.

So far, I've moved a 2.0 WordPress install over to 2.7, written a finished plugin and and unfinished plugin, installed several plugins, altered my theme, and installed an update (2.7 -> 2.7.1) using this environment, and it's all been quite smooth.

Tags: coding, PHP, tech, web-development, WordPress

Twitter Experimentation

Tadhg — Fri, 13 Feb 2009 02:00:40 +0000

After refusing for quite some time, I’ve decided to give Twitter a try. This might prove short-lived, but we’ll see. I like the concept of easy status updates and of disconnecting them from a larger, clunkier framework, e.g. Facebook.

I’ll experiment with them for a while and see how I like it. So far, it’s interesting enough to try integrating them with my blog, which is why there’s now a grey line at the top that says “Status:” followed by my last twitter update. The placing and look are experimental, and we’ll see whether I change that, but for the moment I think that’s where it should go.

I’m using Alex King’s Twitter Tools, with some minor modifications (like giving the timestamp element a class of its own), to handle blog integration.

Apart form showing status on this blog, this will also post notifications about my blog posts to my Twitter status, which I’m not sure about. I guess it depends on how many people follow the blog but not my Twitter status, or vice versa—if there’s a lot of overlap between those two groups (as I suspect there will be) then I might disable that feature.

Tags: Blog, personal, tech, Twitter, WordPress

tag_id	post_id
A	1
A	2
B	1
C	1
B	5
C	5
C	7

New Blog Functionality: Related Posts

Tadhg — Mon, 02 Feb 2009 07:37:02 +0000

Having revived my proper blog and transferred my content over, I’ve now started adding improvements, some of which I’ve been wanting to add for quite some time. The first one is a list of related posts on the individual post pages.

I used to have a spot there for similar content, but it merely fetched posts that had some tag in common with the current one. The new version selects ten posts ordered by a) the number of tags shared with the current post and b) by date (newer first). That’s a significant improvement for browsing around, and with links to both related and random posts, I think that it makes the content on the site significantly more discoverable (which is increasingly important as I add more of it; WordPress counts 919 posts on the site, not including this one).

Those of your reading on RSS feeds won’t get much benefit from it, but I might try to add its functionality into my feeds sometime soon.

I found the process of writing it interesting, and learned a small SQL pattern that I think is interesting, but that’s something I’ll blog about another time, probably when I release the functionality as a plugin.

Tags: Blog, tech, WordPress

Blog Move Steps, Part Three: DNS Change

Tadhg — Wed, 28 Jan 2009 07:58:43 +0000

I’ve wrangled my old plugins and custom code so that it mostly works, except for one or two features (such as “related posts” based on tags) that I’ll revive later. Good enough for now, so I’m making the DNS changes and going ahead.

If you’re seeing this text, you’re on the new server, and all should be well. But if you don’t see another post after this one by about Friday, it suggests RSS problems, so please drop me a line.

Tags: coding, web-development, WordPress

tadhg.com » WordPress

sabbatical.close()

Related Posts

WordPress 2.9 Upgrade

Related Posts

404 Pages

Related Posts

Better reST–WordPress Pipeline

Related Posts

Blog Workflow with reStructuredText

Related Posts

PyWebSF Site Update

Related Posts

WordPress 2.8 Upgrade

Related Posts

Fiction Organization

Related Posts

Bad Behavior Plugin

Related Posts

WP Plugins: Recent Commentary and Show Tags in RSS

Related Posts

Some RSS Changes

Related Posts

New Blog Functionality: Recent Commentary

Related Posts

My WordPress Development Setup

Version Control: Subversion

Separate Production and Development Code Trees

Separate Production and Development Databases

Focus on Theme and Plugin Files

Related Posts

Twitter Experimentation

Related Posts

Related Posts Plugin and SQL Trickery

Related Posts

New Blog Functionality: Related Posts

Related Posts

Blog Move Steps, Part Three: DNS Change

Related Posts