WordPress.org

Ready to get started?Download WordPress

Forums

RSS empty feed - 2.5 upgrade issue (15 posts)

  1. timbearcub
    Member
    Posted 6 years ago #

    OK this is a weird one - upgraded to 2.5 from 2.23 (I think) and all seemed fine - until users pointed out my feed was empty.

    Because of legacy going back to when I started the podcast, I have the blog in a seperate directory and the RSS2 feed (rssfeed.php) points to that directory, so as to not have to change the URL.

    Weird thing is: http://www.mutantpop.net/radioclash/rssfeed.php is empty
    Pasting in the new wp-rss2.php and pointing the wp-config at the blog works, but they are exactly the same code. Even copying and renaming the same file - same result.

    http://www.mutantpop.net/radioclash/wp-rss2.php

    They are exactly the same code. Why is one working and the other not? And no I requireonce or include of the wp-rss2.php file doesn't work either - looks like it has to come from wp-rss2.php.

    If I leave the spaces in I get an error like this:

    Warning: main(/home/.desiree/fireslug/htdocs/blog/wp-includes./feed-rss2.php) [function.main]: failed to open stream: No such file or directory in /home/.desiree/fireslug/htdocs/radioclash/testfeed.php on line 8

    Warning: main(/home/.desiree/fireslug/htdocs/blog/wp-includes./feed-rss2.php) [function.main]: failed to open stream: No such file or directory in /home/.desiree/fireslug/htdocs/radioclash/testfeed.php on line 8

    Fatal error: main() [function.require]: Failed opening required '/home/.desiree/fireslug/htdocs/blog/wp-includes./feed-rss2.php' (include_path='.:/usr/local/lib/php') in /home/.desiree/fireslug/htdocs/radioclash/testfeed.php on line 8

    Help!

  2. timbearcub
    Member
    Posted 6 years ago #

    I've reverted back to 2.3; I've tested it again - you don't lose RSS posts until you update the database.

    Also quite scarily I got locked out and had to use emergency.php when I downgraded...first time that's ever happened. I got database errors also.

    Oh and my categories no longer work. Sigh.

  3. cosmictap
    Member
    Posted 6 years ago #

    My feed has gone empty, too - at first I blamed Feedsmith plugin, but it's continuing even with the plugin deactivated. Ideas?

  4. solarcrash
    Member
    Posted 6 years ago #

    i've got the exact same issue, thought it was feedburner, but it was since i upgraded to 2.5.1 i believe from 2.5

  5. solarcrash
    Member
    Posted 6 years ago #

    i just discovered that /feed works but not /wp-rss2.php

    anyone know why? i might need to reset my feedburner link then...

  6. Mark
    Member
    Posted 6 years ago #

    Hey, I have the same problem and feed works for me too. Dunno why.

  7. omnash
    Member
    Posted 6 years ago #

    The moderators are super, crazy, ridiculously slow to address this huge issue. There's no bug fix for this issue that I can find. If I switch to feed from wp-rss2, that means I have to jettison my feedburner subscriber base. Not cool.

  8. omnash
    Member
    Posted 6 years ago #

    spoke too soon. reinstalled from scratch, applied the fix at http://trac.wordpress.org/ticket/6460, works like magic

  9. brianwong73
    Member
    Posted 6 years ago #

    I got the same problem! Is there a fix?

  10. stonegauge
    Member
    Posted 6 years ago #

    Same issue here. Mind you, I had issues with my upgrade of my blog in question the first time around but with it running fine...

    wp-rss.php doesn't work (or any of the other files) while /feed does.

  11. troutdream
    Member
    Posted 6 years ago #

    Help! I've looked at http://trac.wordpress.org/ticket/6460 and read it like four times, but I'm not a programmer. Just a blogger. I have no idea what to DO with this information or how to implement it.

    For now, I've updated my Feedburner feed to /feed (thanks for that!) but I'm concerned some people may have subscribed to the old address.

    I upgraded not by installing it myself but by clicking the "upgrade to 2.5.1" button provided by my host.

    I'm willing to dig into the files if I have to, but I don't know how.

    My blog is at http://evamoon.net/blog

    Thanks for your help.

  12. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    The fix for this will be in 2.5.2.

    And you should never have been using wp-rss2.php in the first place. The correct feed URL, for all WordPress blogs, is either ?feed=rss2 or /feed. It has been that way for all versions since 2.0. The wp-rss stuff is a left over from the old 1.5 days, over three years ago. We really should remove it, IMO.

    BTW, if you are using non-default permalinks, then you can simply DELETE the wp-rss.php and wp-rss2.php file, and all your feed users will get redirected to the correct URL of /feed the next time they hit the site. Those got integrated into the permalinks, there's no need to keep those files around anymore. This will fix it right now, no waiting around.

  13. nalts
    Member
    Posted 6 years ago #

    For those that may still be having problems with the feed issue, here's what I did to fix the problem.

    The RSS link in my client's Meta section read:
    url/feed/
    This is what works.

    In his footer.php file he had a old feed url that read:
    url/wp-rss.php

    Deleting this second, older feed as described above did not fix the issue.

    In his template>footer.php file I changed this:
    url/wp-rss.php

    to this:
    url/feed/

    and it now works properly.

    I'm not certain if other templates are set up the same, but it may be worth a shot.

    Good Luck!

  14. thebabar
    Member
    Posted 6 years ago #

    I had been using url/wp-rss.php till recently and after upgrade to 2.5.1 my feeds stopped working and today I changed the feed address in feedburner to url/feed.

    My question is: is there anything I can do right away(without waiting for 2.5.2) to have the existing subscribers automatically redirect to new feed address?

  15. BloggerSavvy
    Member
    Posted 5 years ago #

    Rebooting the server fixed this for me. It seemed that some server services were behaving badly and causing this. (Using WP 2.7).

Topic Closed

This topic has been closed to new replies.

About this Topic