Weblog


13
Dec 08

wordpress upgrade (2.7)

Posting about upgrading your incredibly common blogging software isn’t very interesting. But I’m going to take this opportunity to suggest that this time, if you are able, switch to using subversion for wordpress.

Installing wordpress is pretty easy. Upgrading it is also easy, but you still have to move your plugins, themes, and wp-config.php around, or delete stuff that gets in the way. Using subversion makes all of that that go away. Yay!

Update: Sadly, since I have been such a blog slacker, I was able to upgrade to wordpress 2.7.1 while this post was still the top post. Using svn did, in fact, make this the easiest wordpress upgrade I’ve done.

Update 2: Even more sadly, I just upgraded to 2.8.1.


20
Jan 06

Blog upgrade

If you actually visit this blog, you may have notice a sudden change in theme. Or maybe not. Anyway, what happened is that I finally got around to upgrading to Wordpress 2.0 — and this broke the theme that I was using. And, since I am lazy, instead of fixing the theme, I just replaced it. And instead of finding another off-the-beaten-path them, I went with my favorite of the most readily available WP2 themes. At least it is still blue.


12
Nov 05

Non-Zero

My blog is worth $4,516.32. How much is your blog worth?

No clue how this happened


7
Oct 04

More on WordPress + Markdown

Two developments.

  1. I’ve discovered that you can post to WordPress without publishing. You know, drafts, and private blog posts. Neat.
  2. While MarsEdit cannot preview using Markdown, ecto can!

Not that you really need an external posting tool with WordPress. The web form is perfectly fine, although I currently don’t have spellchecking working. I’m guessing that the php installation that comes with RedHat 9.0 doesn’t have pspell support compiled in. Or I maybe doing something else wrong.

So far, WordPress is looking pretty good.


5
Oct 04

wordpress — initial impressions.

Markdown

After getting this blog up and running, I immediately enabled the Markdown plugin.

It works! Except — it doesn’t work everywhere. For instance, not in the RSS feed or in trackbacks (apparently). Unlike how I expect blojsom does this (take your Markdown post, run it through the perl filter, and save the result as the entry), WordPress with the Markdown plugin actually saves the entry in Markdown format.

Which is a good thing, really.

It is lovely to be able to edit the post in Markdown format rather than html. But it really ought to be html everywhere else. Particularly in the RSS feed.

Update: Some fiddling and switching to a full content RSS feed has fixed the formatting issue for the RSS feed, at least. See http://wordpress.org/support/10/5493 for the gist of this.

MarsEdit

Even though you cannot get MarsEdit to autodetect anything, you can get it to work. You can get it to work well (although I haven’t tested this much) by patching WordPress’s xmlrpc.php file.

I don’t think that you can get MarsEdit to preview using Markdown, however, so it is sort of difficult to tell if you’ve done something wrong until you’ve actually posted.

Update: a little bit more experimentation has shown that WP’s solution of storing the comments in original Markdown format has a downside: if you are ever tempted to turn the Markdown plugin off, you will have to go back an reformat all of your previous posts.