WordPress RSS Woes

For those of you who are new to the world of Blogging, it is a form of personal web publishing, allowing people to easily post information and comment about whatever they please. This blog is powered by a web application called WordPress, a fantastic system (although not for someone who is not familiar with the dark arts of website hosting) for running a small website.

Recently, an upgrade was issued to WordPress, bringing the version up to 1.5.1, promising lots of bug fixes and performance enhancements. I took the plunge, and a day later, I realised my RSS feed had ceased to be, throwing up an HTTP 304 error. Damn. A quick visit to the helpful folks on the WordPress support forums showed a number of people had the same problem and a fix had been issued. Basically, you need to download the patch, which is a file named “wp-blog-header.php”, and replace your old copy with it (after having backed it up or renamed it, of course!). I duly did this, and hey presto! A working RSS feed again.

Or is it? A quick check of this feed on Feed Validator, shows the error

  • line 69, column 3: content:encoded should not contain onclick tag (2 occurrences) [help]

    ]]>

  • line 69, column 3: content:encoded should not contain relative URL references (4 occurrences) [help]

    ]]>

  • Stumped! I’ll get on to the support forums and see if anyone can help out. In the meantime, apologies if you’re having a spot of bother with the feeds. SharpReader on Windows, and NetNewsWire on OSX don’t seem to have a problem with it, but some RSS parsers do (e.g. Carp and Magpie). If I do find a fix, I’ll post it here.

    3 Responses to WordPress RSS Woes

    1. Tom 24 May, 2005 at 1:40 pm #

      I’ve just updated WordPress to 1.5.1.1 and still no joy – time to hit the forums :-(

    2. Stuart 10 July, 2005 at 7:58 am #

      Hi Tom,

      I saw your post and have investigated it for you.

      Your first problem (onclick) is no longer present in the RSS feed, but the relative URL problem is still there.

      This can be easily fixed by changing your img tags to use the full URL of the image. This is currently only a problem in your post on “A quick review of RapidMetaBlog…”

      Note that the Feed Validator is not saying that the feed is invalid, just that it may cause problems for some users. It is a good idea to remove any javascript code (ie. onclick) or URLs that are not complete.

      Cheers,
      Stuart.

    3. Rowan 12 July, 2005 at 11:11 pm #

      I’ve noticed some bloggers using Feedburner; the website doesn’t say so explicitly, but it appears to be free. Since I’d like to create a syndicated account for your weblog on Livejournal, would you mind if I set up a feed for you?

    Leave a Reply