Since you are using the open twitter json format there is a limit of 150 calls from a client, not really a problem BUT while developing and refreshing the site several time you easily get up to 150.
The module needs some kind of system that if it dosen't get any tweets returns a "tweet" that says "limit reached" or something. In it's current state the site takes forever to load (if it loads at all) and the twitter block seems to have crashed
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | twitter_block_issue1096134.patch | 1.61 KB | benjamin.wallberg |
Comments
Comment #1
ZenDoodles commentedYou're absolutely right, but I don't expect to have time to work on this for a couple of weeks.
I'd probably accept a patch though!
Comment #2
benjamin.wallberg commentedPatch incoming! :) Patch caches the json reply. This is mainly good for development since if you activate cache block it will cache the block if you are a logged in user or anonymous. But not as admin! This is were this patch is great, since mostly you will reach the limit during development.
Comment #3
oranges13I selected 2 as the limit and it still shows about 10 tweets.
Comment #4
ZenDoodles commented@benjamin.wallberg I just looked at this. Very nice. Will test and hopefully commit this weekend. Thanks so much!
@oranges13 This issue talks about the twitter api limit. Twitter limits the number of times we can query the api anonymously, and this addresses that. The number of tweets returned in the block is not the same thing, however it is resolved in the dev version. If it is not, please open a new ticket, or reopen #1052570: Tweets not limited/filtered as expected.
Thanks!
Comment #5
ZenDoodles commentedComment #6
oranges13Hey thanks. But I've found another bug, will post about it.
Comment #7
ZenDoodles commentedPatch included in 7.x-1.0-beta1 release. http://drupal.org/node/1135176
Thanks @benjamin.wallberg!