Tag Archives: blogging

This is the last time, I swear

There’s no reason I should still be posting about wordpress.com. I guess I’m just annoyed that I ever thought it was a good place to blog/journal/post. The exclusion of anyone who’s not a child or a christian has reached a fever pitch. They’ve just released the following guidelines ((taken to their logical extreme, with commentary)):

  • No inappropriate titles. Do we suppose this means that if you’re posting about the really hot sex you had last night, you should make sure the title is “fluffy kittens for everyone”?
  • No profanity or nudity. This means that my cuss-like-a-sailor-because-it-makes-people-respond-not-just-think-about-it tactic is definitely outlawed. I hate to think what it means for ICHC.
  • No extraneous categories. I’m sure my 2.0 category was causing serious consternation. let alone “cult-of-matt”. In fact, only the officially sanctioned categories are allowed. Anything else and you’ll be relegated to the dustbin, because then you won’t drive traffic to our ad-laden tag pages.
  • And really, you should only post to one category at a time. nevermind that wordpress.com categories can’t be used as categories, since the links lead out of your blog. if you use categories as tags (meta information), you’re definately going to be banned

Basically, if you’re not an aspiring member of the web 2.0 a-list-aspiring echo chamber, you’re not welcome on wordpress.com. fantastic. glad i left. now I’m off to find the 11 most relevant tags for this post.



wordpress 2.2 is out. Easy upgrading is still a ways off. unless you’re me, and you’ve moved to SVN. then it’s just svn switch http://svn.automattic.com/wordpress/branches/2.2/ 😀

the latest undocumented features include atom API support. all that coding in app.php does little good if you don’t reference it. going off of what my wordpress.com blog looks like, you should add this to the head of your blog:

<link rel="introspection" type="application/atomserv+xml" title="Atom API" href="<?php bloginfo('url') ?>/app.php" />

you can implement that as a plugin, or in your theme. i’d love to see XML support moved to the core, but that might just be me.

Importing a wordpress.com blog into an existing blog

I’ve merged my geek blog back into my main blog, so watch your step. wordpress.com readers may want to bookmark my feedburner feed, as i don’t think i’ll be triple-cross-posting for long.

Sometime last year i started maintaining a separate geek blog, where i was posting all the geeky sort of stuff about wordpress. What started as a list of hacks turned into something resembling a real blog, mainly because people were paying attention to the geeky stuff. When i started, i wanted to focus on writing more architecture/design related posts here. As it turned out, it was easier to bang out 5 minute posts on a new hack, or a new gripe with wordpress. Since i’ve barely had time to even post in one blog, this blog’s been a bit of a graveyard. To the point that i even started posting semi-design related things in the geek blog. So i’m giving up on the split.

However, i don’t want to lose all the lovely traffic that wordpress.com has brought me in the last year. Naturally, it’s not trivial to merge two blogs without breaking any links. but it’s the steps aren’t too bad one at a time:

  1. buy domain mapping on wordpress.com. once it’s been running for about a week, you can safely start the rest of the steps. the wp.com servers will start redirecting people from username.wordpress.com to username.yourdomain.com.
  2. export your entries. make sure to delete spam before you do. this shrank the size of my *.WXR file to a fifth of what it was.
  3. set up a subdomain with your host. most hosts do this fairly easily. bluehost definately made it a breeze. the process is going to be different for every host, though.
  4. install wordpress in said subdomain, immediately. until you’ve got wordpress set up, people are going to see an empty directory listing for every entry.
  5. import all your old entries into the subdomain blog.
  6. change your permalink structure to “date and name based” to match wp.com permalinks.
  7. install the Permalink Redirect plugin.
  8. in the “Old Permalink Structure” field, paste in /%year%/%monthnum%/%day%/%postname%/, and check the “redirect hostname” box.
  9. somewhere around here you should double check that any links to your wp.com blog are landing on your new subdomain blog.
  10. import the same entries into the destination blog.
  11. change the permalink structure of the subdomain blog to match the destination blog.
  12. check that all the entries have similar url’s. if you have posts in multiple categories, wordpress my change up the order on you. since my geek blog was pretty focused, i trimmed everything down to one category (with a whole lot of tags).
  13. Last step: double check everything before you do this (expecially the checkbox on step 8): on the subdomain blog, in general options, change your Blog Address (URL) to the address of your destination blog.

That will make the permalink redirect plugin start sending everyone to your destination blog’s URL, with the matching permalink structure. The plugin only works for posts that exist, though. it can’t just make up category names (or whatever else is in your permalink structure). As long as you don’t change the WordPress Adress option, you should still be able to access the backend of your subdomain blog (should you want to make placeholder posts).

Anyway, i don’t know how much use this is to anyone else, since most people have the good sense to not try to write two blogs at once, but there it is.

What not to post

best blogging rubric evar: “i don’t blog about who i date, what i ate, my weight, or who i hate“.
via violet blue.

obviously not something i adhere to. but if you wanted to write something important, it would be a good rule.

Defective Themes: Duplicate Content

Talking to Rob about his nifty architecture blog search engine, I realized just how important things like the Duplicate Content Cure Plugin are. Not just for fear of being kicked out of google, but because it makes your search results real. By default, your monthly, category, tag, and author pages (if they exist) show up, and force your relevant blog posts ‘below the fold’. Worse still, old articles won’t show up on category pages, despite being the reason a person landed on your blog. That’s exactly what happens with a search engine that searches only blogs, without using google’s blogsearch: pages and pages of archives, before you get to actual posts.

So, the plugin is nice, but you can also do it in themes, just add:

 <?php if ( is_category() || is_archive() || is_search() || is_author() ) { ?>

    <meta name="robots" content="noindex,follow"><?php

} ?>

<?php if (function_exists('is_tag')) { if ( is_tag() ) { ?>

    <meta name="robots" content="noindex,follow">

<?php } } ?>

to header.php. The UTW stuff (is_tag()) is a little annoying, but other than that, it’s boilerplate.

another wish that won’t come true

if we had a status blog, i would know what time i could finish posting a reply on my blog. the message “per the previous announcement, your dashboard will be available in 45 minutes”, doesn’t help when i missed the announcement. and i don’t want access to my dashboard. i just want to post a comment. i’d like some indication, somewhere of 45 minutes from when?

UPDATE: i may have spoken too soon. via ryan


lorelle’s latest challenge precludes you from using your own name, but not the names of your posts. that would be too easy, though, so i dug in my stats a bit, and suddenly wondered why one of my custom CSS templates was so much more popular than the others: oh, that’s because people are googling for a wordpress fork. if ever there was a metric for dissatisfaction with the hierarchy of your project, surely this is it.