Warning: Invalid argument

  • (7 posts from 5 members)
  • Started 3 months ago by Jeramiah
  • Latest reply from alleyjack
  • This topic is not resolved
  1. Jeramiah

    BNC Member (1 post)
    3 months ago #

    In the widget I am getting this error.

    Warning: Invalid argument supplied for foreach() in /home/content/s/t/c/stcloudscoots/html/jeramiahpearce/wp-content/plugins/wordtwit/html/twitter.php on line 4

    For the life of me I am sure it is something simple but I can not get it to go away.

  2. innerzinc

    BNC Member (1 post)
    2 months ago #

    I'm getting the same error. Did you figure it out? I've been trying, but I find nothing wrong with the code.

    It was showing BraveNewCode's feed just fine, then when I logged in with my account via the settings menu, I got the error.

    Hoping for some help here.

  3. pirogoeth

    BNC Member (1 post)
    2 months ago #

    I have the exact same problem, except I'm runnning three blogs on my server. WordTwit is only giving the error on one of them. blog.paranoia-dev.org is throwing that error, whereas blog.paranoia-dev.org/pirogoeth is not. I have tried replacing the entire wordtwit plugin directory with the one from my personal blog, but still no go.

  4. I am seeing the same issue as the rest. For the record here's my error message:

    Warning: Invalid argument supplied for foreach() in /home/lascivio/strange-hungers.net/wp-content/plugins/wordtwit/html/twitter.php on line 4

    I'm using WP 3.0 and WordTwit 2.4.4

    The problem began recently. I had tested this feature with WP 3.0 when it rolled out and everything was fine then. I suspect something has changed in the Twitter feed.

  5. Additional notes:
    I deactivated the WordTwit widget, but the widget error code persisted. It remained visible on my pages. I cleared caches and tested in three different browsers. Same results.

    The error message disappeared from my sidebar once I deactivated the WordTwit plug-in.

    I'm leaving WordTwit deactivated until this is resolved. Better to be without a feature, than to present a broken feature.

  6. alleyjack

    BNC Member (2 posts)
    2 days ago #

    Receiving the same error. Deactivating the widget has removed the error, but it remains if the widget is replaced. May try removing and then reinstalling the plugin if the error persists.

    As stated in the above link, a quick look into the Twitter accounts of the blogs affected has revealed that the error likely occurred immediately after a tweet starting with "@", in both instances.

  7. alleyjack

    BNC Member (2 posts)
    1 day ago #

    Error gone. In both cases, it disappeared exactly two "normal" tweets after the one starting with the @.


Reply

You must log in to post.