Careful Upgrading to WordPress 2.0.6

For those upgrading your WordPress blog to the new 2.0.6 version, take care if you use Feedburner. After upgrading, your Feedburner feed will (at times) give you an invalid xml error. Thankfully, over on NeoSmart they’ve posted an explanation of the error as well as a couple workarounds.

Explanation

FeedBurner uses something called “Conditional Get requests” to ask your server whether or not the page has changed since the last it viewed it, in order to save you some bandwidth. Depending on how popular your site is, FeedBurner may hit up your feed up to hundreds of times a day, so this is a really good idea! Unfortunately, in WordPress 2.0.6, your site doesn’t respond in a way that FeedBurner recognizes. The 304 headers it sends back to let it know that the content hasn’t changed are malformed and corrupt - and FeedBurner has no idea what they mean.

This entry was posted on Monday, January 8th, 2007.
You can leave a comment, or trackback from your own site.

2 Comments

  1. Eric Olson, January 8, 2007:

    Eric from FeedBurner here. Thanks for sending everyone over to the workarounds on NeoSmart. If you and anyone else has questions on this please feel free to shoot me a note. Take care!

    Cheers,
    Eric

    —-
    Eric Olson
    Publisher Services - FeedBurner
    E-mail: erico@feedburner.com
    Office: 312.756.0022 x2034
    Mobile: 508.335.9221
    Skype/AIM: EricJohnOlson

  2. Vernon, January 8, 2007:

    Hey Eric -

    I must say it’s an honor to have you comment here! Thanks a lot for stopping by!

    Best,
    Vernon

Leave a comment