Thread

Ok so this thing never works for me. Others have had issues… I am on EE 1.7.1 and have the latest version…

Instead of deleting the cache I read what was in it:

1309477034
<?xml version=“1.0” encoding=“UTF-8”?>
<hash>
  <error>Rate limit exceeded. Clients may not make more than 150 requests per hour.</error>
  <request>/1/statuses/user_timeline.xml?include_entities=true&screen_name=danielphillip</request>
</hash>

I have the following code:

{exp:twitter_timeline screen_name="danielphillip" create_links="user_mentions|hashtags|urls" cache="yes" refresh="60" limit="10" use_stale_cache="yes"}



{text}
<a href="http://twitter.com/danielphillip" target="blank" rel="noopener">{created_at format="%g:%i %a  %M %d"}</a>


{/exp:twitter_timeline}

I believe this should only update every hour.. so why is the plug-in making so many requests? Maybe this helps fix it… maybe not. Here’s hoping

Hi Daniel,

Looks like one of your parameters might be wrong, so the plugin is making an API call every time its loaded. Instead of refresh, try using the parameter twitter_refresh instead.

Did that take care of it?

updated my code and 2 hours later… same PHP error on line 452… same cache message.  :(

Warning: Invalid argument supplied for foreach() in /plugins/pi.twitter_timeline.php on line 452

Thanks tho!

OKAY. I even took out the ‘refresh’ variable entirely. Still the same errors persist. *so confused*

Warning: Invalid argument supplied for foreach() in /plugins/pi.twitter_timeline.php on line 452

We’ve discovered this error can appear when Twitter throttles back your ability to make API calls to their servers, something that typically happens when your site tries to retrieve its timeline too often within an hour or so. You will need caching on for this plugin or you’ll continue to receive these errors. Make sure you have the most recent version of the plugin since a caching bug was fixed in version 1.3.2. Make sure you’re using the twitter_refresh parameter.

Now check to make sure your ./system/cache folder is set to have 777 permissions, and delete any folders already in the cache folder.

Does the plugin operate correctly now?

No. Sadly the same error pops up.

Hey daniel090,

Sorry this is causing so much frustration. Be on the lookout for an email from me. We’ll see if we can’t get to the bottom of this.

Hey Daniel,

So it looks like Twitter now sends an error message that isn’t formatted correctly according to its own documentation. Now that we know that, I’ve tweaked the plugin’s code to compensate. You’ll still often receive a rate limiting error response from Twitter (which was the case here), but the plugin’s handling of that error will now do what it was designed to do: display no errors on screen, and just print the error message into the template debugger.

Regarding the rate limiting, that’s happening because Twitter rate limits unauthenticated requests by the IP requesting it, and if you’re on a shared server with other sites that are pinging the Twitter API, you’re all bundled together as one group and rate limited together.

The updated plugin is already loaded in your installation, and I’ll make sure the plugin gets updated and posted to our website very soon. Does that take care of it for you?

THANK YOU SO MUCH!! 😊

Woot! Kevin, you rock!

Glad this fixes everything for you Daniel, please post again if you have any more issues.

Thanks!