4 thoughts on “Backend Changes

  1. I’m currently using the most recent version of WP on my site (see my name’s link).

    I just finished converting the entire site over to WordPress and decided to go with the most recent stable release.

    I turned off the RTE because I feel more comfortable writing without it.

    And just recently started burning my feeds – it’s more of an experiment.

    The only comment I can make so far is that the Feed Burner interface takes a little getting used to.

    The first day I was with them, the site was a little buggy and I had a few errors accessing my account. They seem to be cleared up now, but I’ll be keeping a close eye on things to see how it goes.

    Good luck with the upgrade!


  2. I’m using 2.01 and have been on FB for a while. The plugin never did work properly for me though, so I had someone write an .htaccess file for me and it works like a champ.

  3. I’m still using WP 1.5.2, as I’m loathe to attempt an upgrade. When initially installing 2.0.1 on a new blog, one theme and a handful of plugins did not work properly (the theme flat out b0rked the entire site, admin and all. Removing the theme via FTP fixed it). For a production environment, I believe 2.0.1 is a lot more sound than 2.0, but I’m still hearing of problems with it.

    As for feedburner, I’ve been using it since I first published an RSS feed (I started with my own home built blog, before switching to wordpress), and wouldn’t use anything else. FB gives me a lot of control over my feed’s display (including various delicious, technorati, etc… links), tracks click-throughs, and tells me how many people are reading my feed (24 hour aggregate in the chiclet, and live stats at the website). That’s just the free service.

    Teli’s experience with page bugs was likely when Feedburner was experiencing some issues. As with any web-based company, that’s a possibility (Google’s experienced a few, lately, with adwords/adsense, for example), but true to quality, the issues were fixed rapidly (within a day).

    If you do use feedburner, my suggestion is to get the FB plugin. This will create a “secret” filename for your feed, which you then give to feedburner as your feed’s location. Then, it re-writes your .htaccess to redirect all of your WP feed links to the FB feed, seamlessly. An example that difference can make? Darren Rowse at problogger used to run both FB feed, and WP feed. His FB feed reported around 1200 readers. He installed the plugin and redirected all of his WP feed readers to the FB feed, and his FB readers report jumped to over 3500, overnight.

    Allright, so I’m a little vocal about things, my apologies as a new commentor probably should not be so vocal, but… well, there you have it.

  4. Thanks for the comments everyone, I’ll keep everyone updated with the progress.

    Feedburner and bloglines seem to be having some problems – sometimes the feed updates and other times bloglines says the feed is broken.

Comments are closed.