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.