Flawed feeds

It has been pointed out to me that my feeds are not showing complete posts; this is not intentional on my part, but apparently is intentional on the part of the WordPress development people.

I have unearthed a hack that should put things back to the (very satisfactory) way they were before, but I’ll have to wait until I get home to actually sort it out. In the meantime, thanks for your patience; regular service will be resumed as soon as is practicably possible.

6 thoughts on “Flawed feeds”

  1. Actually, reading your feed again, it might just be that your posts were spread across the excerpt and main text boxes (or whatever the continued on the post page bits are called in WordPress). If you look at your link dumps on the site you’ll see what I mean. So this post comes out fine, but anything after a “read more” is not included.

  2. Yeah; that amounts to incomplete syndication; the posts on the site have remained the same as before, but they’ve buggered with the rules of how feeds are parsed by the RSS engine. The WordPress people decided that that would be their standard from now on, despite it having riled quite a few users – but it’s their software, I guess; if they’re going to put the effort into coding it, I guess they can call the shots.

    The good thing about WP being FOSS is that some enterprising chap has already created a plugin to fix the problem – which I have now applied, so we should be back to normal forthwith.

  3. I did indeed upgrade, Sterling old chap. If you’ve only just checked the feed, you should indeed be getting the good version, as I’ve put the plug-in in place and repinged Feedburner, so they should have re-indexed and taken the full post versions.

    However, I noticed also that my redirection plug-in was out of kilter this morning; did you have a few days with nothing coming through, and then a big backlog arrive today?

  4. Yes, it all arrived today, starting with the post about upgrading to 2.1 which I just now read (going in feed/reverse order).

    Hmm, that’s a very odd decision on WordPress’ part. I’ll definitely be installing locally to play around with 2.1 before i upgrade the live sites. Thanks for the heads up!

Leave a Reply