FeedBurner has, for the moment, been classified as “that which I am powerless to change” in the Serenity Prayer system of nomenclature. I thought I’d set everything up correctly (I created a brand-new account on FeedBurner.com, then downloaded, installed, activated, and configured the FeedBurner plugin for WordPress…but nope, nothin’.
On the plus side, FeedBurner is gamely maintaining a remarkably-accurate simulation of a working thing. There’s a feed there and it works. But every time I try to subscribe to my own feed, I get the WordPress feed and not FeedBurner’s.
All of the official and user-generated documentation on this thing says that the plugin contains 100% of the necessary mojo. No need for me to edit the site’s .htcaccess file or to chalk anything onto the carpet that my former parish priest wouldn’t approve of. And yet…it ain’t working.
In a way, the most frustrating diagnostic problems are the ones dealing with tools that are just plain supposed to work without any addition configuration. If this plugin were more complicated, then fixing it would probably be a piece of cake. As it is, you wind up double-checking that the plugin is active and that you typed in the name of your feed correctly.
And then it’s all down to blinking and sighing until Bongo, The God Of Such Things decides that you’ve blinked and sighed enough and he grants you your boon.
Okay, well, I’ve turned FeedBurner off for now. To be honest, I had two concerns about it. Even if it worked like a charm, I still had to figure out how to best configure separate feeds for all the various kinds of content I’ll be slinging here. WordPress’ build-in RSS generator doesn’t have all the oomph of FeedBurner, but at least it works transparently.