Ours is was broken. Now it’s better. Thanks, as usual, to Bryce for able assistance. If anyone continues to have problems with the RSS feed, please make a note in comments, or send an e-mail. Thanks.
(Note: The post previously read —
See? Does this look like a familiar and easy-to-fix problem, anyone who might know? Or is it likely to be more complicated? Glory, honor, and riches gratitude await anyone who might have an idea on this one.
Thanks in advance!)
This kind of error usually means that the sending of header information was inadvertently terminated at some point prior to the intended completion. A quick look at the wordpress support forums (you are on wordpress, right?) turned up this.
I’ve been meaning to look at this. I’ll give it a shot.
The link above indicates stray white space either in opening or closing of a tag (e.g,. ‘< ?php' tag or after a closing '?>) of the specified file or extra space at the very end of the file.
OK, I took out the trailing linefeeds, but now it’s complaining that there’s no stylesheet.
… Gotta go deliver some Christmas candy. I’ll look later.
DKL could easily be correct about trailing white space at the end of some code. More than once that was a problem I had that needed to be fixed (and it’s very very easy to fix that kind of a thing).
Hurry up and check that please. I want some of that glory and honor.
It looks like someone fixed it — thanks! (Bryce?)
It’s still not entirely fixed for me — there’s no stylesheet associated with the feed.
Firefox 1.0PR/Win2k
Can others report whether it works for them, and their browser/operating system?
Please ignore that last comment. I had my browser settings messed up.
Does anyone know why the trailing linefeeds are such a problem? I’ve run into the same issue using b2evolution — their documentation screams “do not add any extra lines” to their files.
There’s probably a market somewhere for a simple PHP script that strips trailing linefeeds.
I can write a simple Perl script that does the job.
RSS works. Good work, Bryce I.
DKL —
Your link helped. I was already working on finding those extra lines when I saw your post — it helped me feel good about what I was doing, and since there was more than one file to fix, it caused me not to give up when changing the first file didn’t do the job.
btw
sed -i -e :a -e ‘/^\n*$/{$d;N;ba’ -e ‘}’ <filename>
will strip the trailing newlines of from any file <filename> (much simpler than perl)
DKL, I had no idea you were a php and css coder. Good to know.
One more problem: “Your feed appears to be encoded as “utf-8”, but your server is reporting “US-ASCII” — see http://feedvalidator.org/check?url=http%3a%2f%2fwww.timesandseasons.org%2fwp%2fwp-rss2.php
BTW, I am using SharpReader, which won’t work with the RSS feed as-is (but at least it explains why).
BTW#2: what is the e-mail address for the blog administrator? I can’t find it anywhere.
Why not put the whole text in the post? I find abbreviated rss feed annoying.
Let me rephrase that in English this time. I suggest that you include the entire text of each posting in the RSS feed. It is annoying to read the first so-many words of an article in a newsreader and then have to jump to the website and re-read what you just read to find out where you left off. It is like dropping a book while in the middle of a sentence (or having your six-year-old mischievously slam it shut when you are entranced). If people don’t want the entire entry, let them control it with their newsreader.