Support » Fixing WordPress » V1.5 Dashboard Dev Blog feed problem

  • Version 1.5-beta-1 2005-01-21

    This is low priority, I suppose, but I installed the nightly from 21 Jan and everything seems to work great except for the Dashboard. For some reason, the index page isn’t getting processed past the call to
    <code>$rss = @fetch_rss("");</code>
    (line 92 of wp-admin/index.php)
    Nothing after that gets processed as far as I can tell. I haven’t modified the page at all, and it works fine on a local install (so I wouldn’t call it a bug), just not on my remote host. I’ve checked to make sure the correct path is being used for the rss-functions.php include, and the file is complete as far as I can tell. Any ideas? Anyone else have this problem? It’s not that big a problem, really, since everything else seems to work, but I’d love to know when the dev blog is updated, and it’s so much work to actually paste in the URL…


Viewing 3 replies - 1 through 3 (of 3 total)
  • I’m pretty new to WordPress but I just installed it on my remote host and found the same problem.

    I tracked it down to wp-include/rss-functions.php and class-snoopy.php which was failing to fetch the feed.

    I checked out the documentation for it (i.e. Mapgie) and found this: which states:

    A connection error of type 1 means “permission denied”. This usually means that your ISP has configued PHP so that it can’t open outgoing sockets (usually for security reasons).

    The only solution to this is to ask your ISP for help.

    Sometimes you’ll also get the related connection failed (11) (e.g. on which also means PHP is configured in such a way that Magpie can’t work.

    So it looks like it’s mine and your hosts problem. It’s a small pity though that this error isn’t captured by WordPress itself.

    My error was this: Fatal error: Cannot redeclare class snoopy in /usr/www/users/grahame/blog/wp-includes/class-snoopy.php on line 40

    To solve this problem, I edited line 38 and changed ‘Snoopy’ to ‘snoopy’. get_declared_classes is returning a list of lowercased class names. So the comparison that was meant to catch just this error wasn’t matching, and therefore not catching the error.

    I’m really digging this dashboard feature.

    Thanks grahame, this solution worked for me.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘V1.5 Dashboard Dev Blog feed problem’ is closed to new replies.