Let’s try and narrow this rss feed problem in 1.5 to one solution set

  • There are 4 or 5 feed problem conversations going on. All have different instructions as to what you can do to fix your feed, but after me and a few others trying to fix so we can have our rss feed available, nothing seems to be working for me. Has someone come up with a single solution that will work for all, or is this something that will continue to get mired in various posts with information everywhere confusing many people who aren’t php experts, like myself. I’m trying as hard as I can to follow what everyone is saying and trying the fixes, but nothing seems to work.

    One solution for everyone would be great! If that is possible. And if someone could post the solution to their blog, even better so it’s clearly stated and everyone can try the fix.

    Are the developers aware of this problem?

    I’ve been told to go get the new wp-blog-hearder.php, but that doesn’t work for me either. If you look at my validation code, it says the problem is in my rss-2.php file, not the wp-blog-header.php file.

    So, can anyone help once and for all, it would be such a relief, this is preventing me from promoting my site because I don’t want to put it out there and then have people not be able to get it through rss-2.

    Any cohesive, final fix would be greatly appreciated! Thanks in advance.

Viewing 7 replies - 1 through 7 (of 7 total)

  • The two feed problems that I’ve encountered since upgrading to 1.5 both were caused by totally different things, so there’s no way that they could both have been solved by a single solution. I really don’t think that we could get a single solution that would solve all feed problems because the problems come from different places which may be totally unrelated so any fix for one might not effect the other at all.

    I think it would be a good idea, however, if we consolidated all the feed problems and their solutions into a single place, perhaps as a new page in the Codex? I’m not sure if this has been done yet, but it would be nice if it were. We can start by consolidating feed problems and solutions here so that they’re all in one place.

    So, the first feed problem that I’ve heard of is that when clicking on a feed link, the browser returns an error about an unregistered or unsupported protocol. This is because in the default theme, the feed links are prefixed with feed:, which is a new protocol that has yet to be picked up widely. The solution is to edit the feed links, usually just in footer.php on the default, and remove the feed: prefixes.

    The second problem that I’ve seen, and that I myself went though, was an XML parsing error. The error was that the XML processing instruction did not appear on the first line of the document. This was caused because in several of my plugin files there were extra empty lines before the first <?php and after the final ?>. This was solved by going through all of my plugin files and checking for extra lines, and can be avoided in the future by checking plugins that you download before uploading and installing them on your blog.

    Your feed currently has a PHP parse error, so I can’t check it. Most 1.5 feed problems are caused by bug 903. The symptoms are 404 file not found errors. The fix for that is the updated wp-blog-header.php.

    Beyond that, there are a couple of feed validations issues that you might be running in to 929 or 963. If you’re using a language besides English you will encounter this bug.

    If any of those problems look like yours and the bug is still open, add your comments. You can also look through the bug tracker and search on “feed” to see if you find anything pertinent. If nothing looks like your problem, report a new bug and include a link to your feed, a description of the problem, what validator you are using, and what web server you are using.

    feed: URI scheme.

    Why can not wp just use the method that most use for feeds?

    The open an external application is to me the root of the problem

    If some one has an rss feed why not use the method that this particular forum uses also as shown in this link below
    https://www.ads-software.com/support/rss.php?topic=27048

    feed: is easily changed via the templates. If we want to gripe about the use of feed:, let’s do it in another thread and focus this thread on problems with the actual feed. I posted the link only as an explanation of what “feed:” is.

    Thread Starter Tony Zeoli

    (@tonyzeoli)

    Hi all,

    Thanks Avenir for the summary. I made all the changes listed here by you and by. I made sure I have the new wp-blog-header.php, with the “index.php” changed to just “.php”.

    Then, I made sure I took out the “feed:” prefixes from footer.php in my default folder.

    Finally, I made the parse change in bug 929

    echo utf8_encode(html_entity_decode($title));

    instead of echo $title;

    My NetNewsWireLite is now returning Domain: HTTP error Type: parse failure

    Feedvalidator.org seems to be up sometimes and down at others, so I can’t check what the validation problem is at this very moment, but I will post again when their site is back up. Maybe there is too much web traffic and I’m just not getting through, I do not know. Does anyone else have this problem with feedvalidator.org?

    Ryan, thanks as well for your comments. I will do a search as you suggested and see what I can come up with.

    My apologies to all as it’s been very frustrating, wading through all the answers and trying to figure out which one is going to work. I am not a PHP or RSS expert by any means, so your assistance is all I can go by to try to get these things fixed. I really appreciate each of your attention to my problem. It’s amazing that this WordPress world exists and that all of you care so much about making sure it works for everyone. Thanks!

    I’m sure we’ll get this fixed one way or another, lol. ??

    My wp-rss2.php and wp-atom.php validated, but wp-rss.php did not. I received the XML error described above. My (simplistic?) solution was to change line 31 of wp-rss.php (based partly on https://mosquito.www.ads-software.com/view.php?id=1132 ) from

    <description><?php the_content_rss('', 0, '', get_settings('rss_excerpt_length')) ?></description>

    to

    <description><![CDATA[<?php the_content_rss('', 0, '', get_settings('rss_excerpt_length')) ?>]]></description>

    Maybe I’m naive, but it just looks like this was missed in the orig. Hope this helps and if I’m totally wrong, let me know.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Let’s try and narrow this rss feed problem in 1.5 to one solution set’ is closed to new replies.