Today, when I open the site's frontpage (which contains a Twitter block) I couldn't see any tweet on the block. When I look at the logs:

Could not retrieve data from Twitter. The error message received was: .

I don't understand the problem from this message.

But the real problem is, the latest tweet didn't change for 5 days. The module erases the tweet before pulling. I think it shouldn't erase it until the newest one comes successfuly.

Also the front page takes long time to load. I think it tries to fetch the tweet. If I disable the block, it opens very fast.

Comments

boftx’s picture

boftx CreditAttribution: boftx commented

I just noticed the same problem. The full error message is as follows:

Could not retrieve data from Twitter. The error message received was: Rate limit exceeded. Clients may not make more than 150 requests per hour..This site may be subject to rate limiting. For more information, see:http://apiwiki.twitter.com/Rate-limiting

This happened on a dev site that has essentially no traffic. This would imply that caching is not working correctly.

JSCSJSCS’s picture

JSCSJSCS CreditAttribution: JSCSJSCS commented

I too saw the log message and cannot see the content on a dev site with no traffic.

undersound3’s picture

undersound3 CreditAttribution: undersound3 commented

I just updated to latest drupal version 7.8 locally on LAMP, everything works locally, after a drush rsync / sqlsync twitter feeds are not showing up. I too get this message:

Could not retrieve data from Twitter. Bad Request This site may be subject to rate limiting

PixelClever’s picture

PixelClever CreditAttribution: PixelClever commented
Priority: Normal » Critical

I'm seeing this problem too, and I don't think I am getting over a 150 request per hour. I do believe there is a caching problem. Setting this to critical since no tweets are returned under these conditions.

totaldrupal’s picture

totaldrupal CreditAttribution: totaldrupal commented

Same issue here on a new site with almost no traffic. "Could not retrieve data from Twitter. Bad Request This site may be subject to rate limiting. For more information, see: http://apiwiki.twitter.com/Rate-limiting". Sometimes it works fine, most of the time though no tweets are displayed.

undersound3’s picture

undersound3 CreditAttribution: undersound3 commented

I migrated my site to a vps (linode) with less traffic on it and didn't received that message ever since. For me it was definitely the shared server problem and too many request from one ip (http://drupal.org/node/1073116#comment-4201602)

totaldrupal’s picture

totaldrupal CreditAttribution: totaldrupal commented

I notice that the rate limiting error in the log refers to a page that has no twitter pulls on it. Could this module be trying to pull on every page that loads and that's why the rate limit is exceeded?

totaldrupal’s picture

totaldrupal CreditAttribution: totaldrupal commented

If this rate limiting error is not a bug then perhaps it should have support for OAuth authentication? http://drupal.org/node/893394

radekdostal’s picture

radekdostal CreditAttribution: radekdostal commented

I had experienced similar problem, so I created a patch which helps a lot on shared webhosting:

http://drupal.org/node/1820002

Any comments will be greatly appreciated.

kenorb’s picture

kenorb CreditAttribution: kenorb commented
Issue summary: View changes
Status: Active » Closed (works as designed)

The issue is too old, Twitter API has been changed several times already. This needs to be fixed in 7.x if it's still the case.

For:

Could not retrieve data from Twitter. Forbidden

check: #2562681: Twitter 5.9 module incompatible with Twitter Pull.