I was recently contacted by a reader who was disappointed because they had chosen the same webhost as I did for their blog, assuming that I chose my host because they’re great for blogging and finding themselves bummed when they didn’t get the same performance as my blog has. I chose my webhost (Prohosters) years ago for reasons unrelated to blogging (and now am wishing they had cPanel and Fantastico…) and have a dedicated server which costs me $300 a month (I am self-employed, after all). But this reader chose one of their $25 a month shared solutions and found himself disappointed by the speed (or lack thereof) in which his WordPress powered site loaded. So he asked me, and now I’m passing the question on to you, my faithful readers:

What is the best webhosting company for WordPress bloggers?

I would personally love to hear all of your experiences, positive and negative, so please comment away!!

Well, it’s official! I’ve finally gone ahead and done what I’ve been wanting to do for ages now — I ported “How to Blog” from TypePad to WordPress and it now resides happily at http://www.emilyrobbins.com/how-to-blog/

Please update all of your bookmarks and feed subscriptions to reflect the new location!

I’m very excited to have the site powered by WordPress for a number of reasons:

• I can reopen trackbacks on all my old posts (which I’m still in the process of doing) and allow pings on all new posts because WordPress’s anti-spam plugins will delete all the crap (meaning I’m not stuck wading through hundreds of spam a day trying to find legitimate trackback pings) and you will soon be able to trackback to any and all of my posts, restoring full blogging functionality to How to Blog (since you all know I think trackbacks are essential to the blogging experience!) It may be a day or two before all of the posts have been updated to allow pings — in the port from typepad, WP used typepad’s settings and had pings turned off for all posts and unfortunately I haven’t been able to find a plugin that will allow a mass change to all posts to allow pings (developers - there’s an idea for ya!) so I’m sitting here manually going through each post and checking the ‘allow pings’ box, so bear with me
• I can have subcategories!!!!!!!!!!!!!!!!!
• I can finally have pagination controls (previous page, next page), making navigating the blog much easier (and something that TypePad was sorely missing).
• I can have an Archives page which displays Archives by month, by category, as well as an entire archive of every posting on How to Blog, essentially creating a sitemap so that you can more easily find what you’re looking for
• Speaking of sitemaps, I can use the Google Sitemap plugin to automatically generate a Google Sitemaps compliant sitemap of How to Blogand automatically ping Google everytime a create or update a post
• I can save time by using plugins like Jerome’s Keywords to automatically create my technorati tags for me based on the keywords I’ve entered
• I can save time by using the autolink plugin to automatically setup the hyperlinks for me on phrases that I often use, like WordPress
• I can allow people to subscribe to my blog by email using the Subscribe2 plugin, where you can choose how often you want to be notified by email when I create new posts, and you can even specify which categories of posts you want to be notified about
• I can get MUCH better stats, since I’m running wordpress on my dedicated server on my webhost (Prohosters.com) and I get really detailed stats through the use of Sawmill
• I have a seemingly endless number of wordpress themes to choose from (I haven’t had time to figure out what I want to go with for the long haul — I really like the look of Semiologic, but it’s very hard to customize because it requires serious PHP knowledge and whatever theme I choose will likely be heavily customized when I’m done with it — OR, I might just take the plunge and create my OWN theme )
• I can allow people to subscribe to comments on any particular post, and they will then receive subsequent replies to that post through email
• I’m sure there are a million other things I’m forgetting, and I’ll write about them in due time. The one thing I am gonna miss from TypePad is their excellent WYSIWYG editor — WordPress’s is rather disasterous and I recommend that all users disable it. If you still want a wysiwyg interface for blogging, there are several excellent tools available including the Performancing extension for Firefox, the windows client BlogJet, etc

For now, I’ve got to get back to the ultra mundane task of updating all of my old typepad posts one at a time to show the new URL of where the post can now be found and turn of commenting on those posts. Then I get to go through all of my posts in WordPress one at a time and check the box to allow pings. Then I get to email all the people who have linked to my old site and ask them to update their bookmarks. And I get to pray that I don’t lose all of my traffic and the great search engine rankings that I had on my typepad version of the blog.

By the way, I do realize that blogging.typepad.com is certainly an easier URL to memorize than www.emilyrobbins.com/how-to-blog/ - however, I wanted to have it on my emilyrobbins.com domain - but not in the root of the domain as How to Blog is only one part of who I am. And, when I experimented with porting the typepad blog over to wordpress, google immediately started indexing the URLs (something I hadn’t anticipated to happen so quickly - especially since I hadn’t made a final decision as to what I wanted the URL to be - should I use a subdomain or a subdirectory, or should I give it it’s own domain) and rather than having to set up 301 permanent redirects I decided that this must be what fate wanted as the new How to Blog location - so here we are, and I look forward to being able to get back to posting (and I have many posts which need some updating including my theme list) when the drudgery involved with making the move is completed!

I am feeling really frustrated right now – like I’m stuck in limbo with a conundrum on my hands. Why? Because I’ve grown to love WordPress so much so that I really prefer it over TypePad, for an increasing number of reasons. (Please note that in this review, when I refer to WordPress, I’m talking about the full version of it – the one that must be installed on your own web server. In the few instances where I refer to wordpress.com, the hosted and dumbed-down version of WP, I specify it’s wordpress.com I’m talking about.)

The main issue is how spam is handled. On TypePad, spam is a nightmare to deal with, whereas on WordPress spam is almost a non-issue (provided you are using the proper plug-ins like Spam Karma 2 for those running v1.5.x – or for those on WP 2.0, the included and revolutionary Akismet).

Then there are all the other easily customizable things. Like the look and feel of your site. Ok, so TypePad’s is easier to control without having to know any code — but really limited in comparison to WP. As my comprehensive wordpress theme list shows, there are now 615 free wordpress themes out there, and growing! OVER SIX HUNDRED. That’s a staggering amount of templates to choose from to give your blog it’s own unique flair. And they are all customizable as well (if you know some css) – and with WordPress 2.0, themes can be made customizable within the admin area by their authors such that bloggers can customize areas of the theme at will without ever touching any code!

Then there’s the issue of pagination. It’s quite simple – WordPress has it and TypePad doesn’t. By pagination, I mean those little links folks have grown accustomed to seeing on blogs that say “Next Page” and “Previous Page”. Don’t see them on this blog? That’s b/c TypePad doesn’t have that feature. TypePad bloggers get to choose the number of posts that will appear on their homepage, and after that – well, good luck navigating the blog b/c the only options are to do so through clicking on the categories or the monthly archives. TypePad doesn’t even have built-in search. And of course, WordPress does. (TypePad users should check out my article on how to make your typepad blog searchable).

And then there are the plugins. No small matter. WordPress has plugins that enhance it’s functionality for almost any thing you could want to do with it:

• Tagging plugins (such as Jerome’s Keywords or the Ultimate Tag Warrior) that provide an easy way to automatically tag posts with keywords for social bookmarking systems such as Technorati, del.icio.us, and Flickr. This means more traffic for your blog. Tags also provide a whole new way for readers to interact with a blog. For example, Jerome’s Keywords makes it so “readers can click on a post’s keyword/tag link to see other posts with the same tag. It’s a simple but effective way of letting users find content that interests them.”. You can even create a local tag cosmos.
• Post related plugins, such as the ability to display the top 10 most popular posts in your sidebar, or the ability to show a list of related posts when viewing an individual post
• Comment related plugins, such as giving users the ability to display gravatars in their comments and allowing blog readers to subscribe to a particular post’s comments
• There are just WAY too many ways in which plugins expand the functionality of WordPress way beyond the capabilities of TypePad to even discuss here. And from what I’ve been hearing about WP 2.0, which provides added hooks making it even easier for programmers to create even more fantastic plugins in the future, the possibilities seem limitless.

Customization of where you ping to notify the world that you’ve updated your blog — WordPress has it, and (you guessed it) TypePad doesn’t. The workaround with TypePad if you want to use a service like pingoat, is to paste the URL for pingoat’s RPC server into the Trackback area for each and every post, each and every time you update it.

And while this isn’t an issue for me in choosing a blogging platform, the issue of cost still needs to be brought up in any review. Again, it’s simple – WordPress is free, and TypePad isn’t. Of course, the full version of WP with all of it’s glory and customizable options (including access to all free themes and plugins) requires you to have a web hosting server with mysql support (which most do). Which means it really isn’t entirely free b/c now you’re paying for web-hosting. But if you do want entirely free, Wordpress.com offers that — and while it’s a really dumbed down version of WP, it still offers some things that TypePad doesn’t, like sub-categories (however, it doesn’t allow you to run adsense ads on your site – you get what you pay for with wordpress.com).

Then there’s ease of use when posting. When it comes to blogging editors, WordPress 2.0 finally has a built in WYSIWYG editor (something TypePad has had all along, and which I think every blogging tool should offer). The only problem is that WordPress’s wysiwyg editor is kinda buggy. See this problem that I encountered on my WordPress 2.0 test blog. However, I generally use an external windows client (BlogJet) to post to my blogs, which has it’s own WYSIWYG editor that’s better than both of them. But you also need to take speed into account when you talk about ease of posting. WordPress is very speedy when creating or updating posts. TypePad is very sluggish, especially if you are sending trackbacks to a large number of sites.

Want stats for your blog? Well TypePad only shows you referrers from the past 24 hours. That’s it. And not only that, but it is slow as molasses

Now there are a few areas in which TypePad sort of shines in comparison to WordPress, with the main one being maintenance and upgrading. I say sort-of, because sometimes TypePad has outages and when that happens there ain’t a thing you can do about it. On the other hand, every time WordPress comes out with an upgrade, it can sometimes be a major pain in the rear to install it, wreaking all sorts of havoc over your blog (although sometimes the upgrade process is totally smooth). All of that customizability that WP offers through themes, plugins, etc, makes for more things that can get broken every time there’s an upgrade. And sometimes it seems like those upgrades come every few days (like after the release of WordPress 1.5 when there were numerous minor point releases that were required updates because they pertained to security flaws which seemed to come out every few days!) And when there’s an upgrade, you’re the one that has to install it (unless you’re using a free wordpress host like blogsome, but then you’re at the mercy of them deciding which themes and plugins are available to you, and when and if they’re going to do an upgrade – right now they’re still using WP 1.5). When TypePad does an upgrade, it’s behind the scenes and you find out about it in the TypePad news (unless the upgrade wreaks havoc on their servers, in which case you get the joy of TypePad outages, the inability to post to your blog for sometimes days on end, etc – but ultimately they fix it, and it’s up to them, not you, to fix it).

All of this makes me want to move this blog and all of it’s posts (and future posts to come) over to wordpress on my own server at emilyrobbins.com. Which brings me to my conundrum (and the possible state of limbo). Is it worth moving an existing site that gets over 1000 visitors a day and is ranked well in the search engines over to another server, URL, and blogging system entirely, possibly losing all of my backlinks and high pagerank that I spent so much time in generating? And if so, should I wait until WordPress 2.0 has ironed out some more of the kinks (there are currently problems with trackbacks, which I think is a rather major issue, among other things) before proceeding?

WordPress 1.5.2 works great and is a very stable release. But I know I’ll eventually want to move to Wordpress 2.0.x — it’s new features are just too enticing. And I also know that I do not want to have to deal with doing the kind of major upgrade that going from 1.5 to 2.0 entails on a website that is this important to me (I just don’t have the time deal with it in case something goes wrong with the upgrade, and there have been far too many reports of people having trouble with the upgrade for me to risk it). But I’m getting so damn sick of TypePad’s limitations, and even more so of managing all the spam (I have to have all of my trackbacks and comments moderated because of the vulgar spam that people try to put through a zillion times a day – an issue that I wouldn’t have to deal with if I were using WordPress instead).

So what should I do? Should I hold off on doing any more posting until WordPress 2.0 comes out with a more stable version and then move the whole site over to WP 2? Should I just take the plunge now, and hope that the trackback issues don’t affect me too much until they are resolved? But what if I lose all of my traffic as a result?Should I just leave things as they are right now and stick with TypePad for ‘How to Blog’??

What to do? What to do??????

Update: I’ve taken the plunge now that WordPress 2.0.1 has come out and moved How to Blog over to http://www.emilyrobbins.com/how-to-blog/ so please update your bookmarks and RSS feeds!

Under the category of more absolutely ridiculous things that current blogging platforms are missing the boat on, I just found out that not only does TypePad not have pagination built in, but there is NO WAY of implementing it even through advanced templates.

By pagination, I mean the and
buttons that many bloggers and blog readers are accustomed to seeing at the bottom of a blog page (a feature that is built into WordPress, for example). TypePad gives you the option of customizing how many posts appear on a page, but no way to easily navigate to posts beyond those appearing on the front page. For example, the oldHow To Blog site is set to display 10 posts on the front page. But when users visit the site and read through those posts, and want to see the rest of what I’ve written, they have only 2 options, neither of which is optimal:

1. View each category one at a time
2. Go through the monthly archives

I had put it on my personal ‘to do’ list to figure out how to add Next and Previous links to the buttom of my TypePad pages, and when I finally decided to tackle the project and couldn’t figure it out on my own, I submitted a support ticket to Six Apart asking for help with it. I wrote:

WordPress has built in previous / next page links at the bottom of every page. This makes their blogs much more easy to navigate, especially for beginners. As each page only contains a certain number of posts, without having next and previous buttons it’s hard for people to easily navigate the blog.

In addition to making this a feature request, I’d also like to know what code I should use in my advanced templates in order to implement this on my blog on How to Blog.

Your prompt attention to this matter is greatly appreciated.

Thank you!
Emily Robbins

The response I got back from TypePad Customer Support was astounding (bold added by me):

Hi Emily,

Currently TypePad doesn’t offer pagination (Next Page and Previous Page links), so there isn’t any code that I can offer you to do this.

Thanks for the suggestion, though. We are always looking for ways to enhance TypePad for our users, so we will keep this in mind as a possible future feature for the system.

Please let us know if there is anything else we can do for you.

Thanks,
Kymberlie

Excuse me for the double-take, but NO CODE AVAILABLE TO DO THIS? How can this be when SixApart themselves acknowledged the importance of pagination features in their own article on Six Apart Pronet entitled “Building on Movable Type Part 3: Creating Pagination Controls”, wherein they say (again, bolding is from me):

Pagination controls are sufficiently ubiquitous that our own developers saw the value in creating a reusable mechanism for creating the links developers should all be too familiar with: “next page,” “previous page,” “last page,” “first page” and “you are viewing results X to Y out of Z.” This reusable framework is not only accessible within Movable Type, but by plugins as well.

So apparently Six Apart thinks that pagination controls are so ‘ubiquitous’ that we’d be ‘all to familiar’ with them, and they are not only built into the functionality of Movable Type but also accessible by MT plugins. GREAT. For Movable Type users.

So how come when SixApart created (and updated and updated) TypePad, this “ubiquitous” functionality was somehow forgotten?

Update: for those of you who click the link to my old blog at typepad to see the lack in pagination functionality, the template for the site has been changed to make it easier for folks to see the full URL for my new posts at the new site, making for a pretty ugly site. It didn’t use to look like that, but it’s okay that it’s ugly - none of you are supposed to be using that site anymore b/c I moved over here, remember

I know that I promised to test out the process of upgrading an existing WordPress installation from 1.5.x to 2.0, but until 2.0 has resolved some of the existing bugs (and the resulting slew of additional minor point release upgrades have been completed, forcing users to upgrade to 2.0.1, and then 2.0.2 possibly days later, etc - (remember what happened after 1.5?)) I’m holding off.

As mentioned before, I’ve done a clean install of WordPress 2.0, and while I’ve been told that much has been done in the underlying code base to provide for the possibility of future themes and plugins that are more spectacular than ever, those themes and plugins don’t exist yet, WP 2.0 itself is still way too buggy, and from an end-user perspective I just don’t see that much that’s new and exciting to compell anyone to want to upgrade.

Yeah, the new user interface is prettier. And it’s nice to have a built-in WYSIWYG plugin, but that too is quirky and WYSIWYG plugin options already existed for 1.5.x users who wanted them. The built-in spam plugin of Akismet is pretty darn cool, BUT it requires you to register at WordPress.com in order to get an API key to use it, and apparently if you use it too much you’ll be required to get a commercial license for it (and there’s some talk about the ethics of packaging a somewhat commercial product like Akismet with an opensource free product like WordPress). Not to mention the fact that there were already some pretty amazing spam fighting plugins available for WordPress 1.5.x that now don’t work properly in WordPress 2.0 (like SpamKarma2, for example). The purported benefit of Akismet over plugins such as SpamKarma2 is that it is always 100% up-to-date and never requires any upgrades.

I’ve no doubt that, eventually (and hopefully sooner rather than later), the bugginess of WordPress 2.0 will be resolved, and some amazing 2.0 specific themes and plugins will start to appear that will tantalize us to make the switch. But until then, I’m staying put.

Update: I’ve ported How to Blog to WordPress 2.0.1 and am thrilled to have done so! (Although the process of changing blog platforms and URLs is a nightmare of tedious endless little annoying tasks) Please update your bookmarks and RSS feeds to reflect the new, permanent location at http://www.emilyrobbins.com/how-to-blog/