ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Problem with the updated Twitter Timeline plugin...

September 01, 2010 12:31am

Subscribe [57]
  • #16 / Sep 03, 2010 6:10pm

    Paul B

    241 posts

    Experiencing same issue despite deleting cache.

    EE 1.6.9 / PHP Version 5.1.6 (EngineHosting) / Twitter Timeline V 1.3

    Message:
    Warning: Invalid argument supplied for foreach() in (path)/ee/plugins/pi.twitter_timeline.php on line 394

  • #17 / Sep 03, 2010 6:20pm

    Sue Crocker

    26054 posts

    Paul, Pascal is aware of the problem, but doesn’t have a fix available yet.

  • #18 / Sep 05, 2010 9:03pm

    mooo

    168 posts

    I’m having the same problem-must be because I’m in dev and refreshing the page pretty often. Hopefully there will be a fix soon!

  • #19 / Sep 06, 2010 4:08am

    John Henry Donovan

    12339 posts

    Best advice here at the moment is to subscribe to this thread for updates

  • #20 / Sep 07, 2010 11:31am

    Liam Spencer

    37 posts

    Delighted to see this is getting worked on as I just found the error myself. Great work on the plugin guys, and look forward to seeing the fix.

  • #21 / Sep 07, 2010 12:06pm

    Sue Crocker

    26054 posts

    I’m certain Pascal will post here when he has a fix available.

  • #22 / Sep 07, 2010 4:36pm

    Clive Portman

    83 posts

    Is there a way to disable the warnings?

  • #23 / Sep 08, 2010 3:29am

    John Henry Donovan

    12339 posts

    monkey_don,

    Do you still see the warnings when logged out as SuperAdmin?

  • #24 / Sep 08, 2010 8:34pm

    Dabbledoo

    172 posts

    I have a client seeing the “Invalid argument supplied for foreach() in /#######/plugins/pi.twitter_timeline.php on line 394” error as well, ever since the upgrade to the new version.  I am wondering if this is due to Twitter limiting the number of requests from a certain IP.  My client is on EngineHosting, and I am betting a bunch of people are hitting Twitter via EngineHosting as well - likely the same IP address.  Could this be the reason this problem is popping up?

  • #25 / Sep 09, 2010 6:25am

    Nelga

    41 posts

    I’ve got a big site launching tomorrow…

    If there is no immediate fix, is there a workaround method i can deploy in the interim?

  • #26 / Sep 09, 2010 6:29am

    Liam Spencer

    37 posts

    I just remove the tag in question and I still manage to get the tweets, just without any hyperlinks being generated. It is the create_links=“user_mentions|hashtags|urls” paramater that has been causing problems with me. I just removed it and I now have my tweets appearing but with no links.

  • #27 / Sep 09, 2010 6:33am

    Nelga

    41 posts

    That’s what I initially suspected too, however i’ve had quite a few instances since removing where I still get php errors.

    From earlier discussion I think it’s to do with the number of requests the extension makes.

  • #28 / Sep 09, 2010 1:48pm

    Clive Portman

    83 posts

    Working fine for me in the UK now, but will test later when US comes online (Engine Hosting presumably not getting much UK traffic?).

  • #29 / Sep 09, 2010 7:49pm

    Brandon Jones

    5500 posts

    Thanks, all. We will update this post when we have more information.

  • #30 / Sep 10, 2010 12:10pm

    2ways

    16 posts

    Hi Folks,

    Thanks for all this good information.  Looking forward to some resolution as well.

    I wanted to add a comment from my experience with this plugin over the past few days.  I’m getting no php errors or any template errors, but I don’t ever see any tweets at all.

    The template debugging just says that it can’t get any data from twitter (and it takes 5 minutes to load the blank page along the way, I timed it!).

    Thanks.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases