RSS ERROR (sidebar widget) (6 posts)

  1. phattrance
    Posted 6 years ago #

    im getting this error message a few times / day on my sidebar rss widget when adding the forum rss post to the sidebar (standard in wordpress 2.6)

    Warning: Attempt to assign property of non-object in /home/phat/public_html/wp-includes/rss.php on line 440

    what does it mean?? and how can i fix it.

    Blog url: http://dailymobile.se

  2. Austin Matzko
    Posted 6 years ago #

    What it means is that the cached data object for your RSS feed occasionally doesn't exist.

    But that's not the real issue. The real issue is that for security purposes a live site should not be displaying any error messages whatsoever, much less warning messages, which is all this is. Contact your host and ask it to disable PHP messages for your site.

  3. phattrance
    Posted 6 years ago #

    im using the hyper cache plugin, will it help if i delete the current cache?

  4. scottintheoc
    Posted 6 years ago #

    Did deleting the current cache work? I, too, am getting this error.

  5. saraar
    Posted 6 years ago #

    I am getting this same problem. I am getting the RSS feed from a website hosted in the same server so it should have been even easier and faster (no remote host involved). I tried to find if there is a way to completely disable widget caching to no avail.

    I think this issue is something that should be addressed.

  6. wes50
    Posted 6 years ago #

    I've been having this problem too, and I've seen postings by others in other places indicating they are too.

    The only solution I've come up with is to disable the rss feed (remove widget) entirely, which I don't find a satisfactory fix for at least 2 reasons:

    1) it messes up the look of my sidebar
    2) the feed itself provides useful information when working properly

    Turning off the PHP error messages looks like a good step (like I just needed one more thing to do!) but has anyone got a REAL fix for this?

    Unfortunately, I'm not a PHP whiz, so I'm stuck. Also, I'm wondering if this problem didn't begin when I upgraded--2.71 currently.


Topic Closed

This topic has been closed to new replies.

About this Topic