Daily Twitter stopped working after 3 days

Mine is still working -- any chance your cron isn't being run? What happens if you run cron by hand, do you see any error output?

Hi,

No error after Cron :-(

I wonder what is the problem ?

Thanks for help.

Hrm. Sadly I don't have any ideas! =(

same problem here and cron is running fine as well.

JADESTORM,

am pretty sure this is a critical bug because the module fails to take into consideration a very important change in the Twitter API

http://apiwiki.twitter.com/Things-Every-Developer-Should-Know

and

http://apiwiki.twitter.com/Rate-limiting

is there a way to change this so that it calls Twitter once a day? take into consideration that if a person is using a twitter client like TweetDeck or TwitteGadget those are also calls to the API by the same account.

for those of us who have cron running every 5 or 10 minutes, twittering through TwitterGadget plus the cron calls of DailyTwitter would max out our allocations ---and Twitter will first block the site (which is pulling from them) instead of blogging the apps which is pushing into them content and creating traffic for them.

please revise this bug.

Uhm.. it doesn't check every time cron runs. It records the last time it contacted twitter and won't contact twitter again with the same account for a period of about 24 hours.

There is, however, some other issue going on. Either that code is no longer working properly as it did when I first wrote this, or something else is quite confused.

i was using TwittKit and it stopped working properly after Twitter changed the call rates to the API. TwitterGadget has always had a lag of 3 minutes by default so it doesnt affect it that badly, but am a power-twitterer (http://twitter.com/blogdiva), so my having an app open may just make it seem to your module that i've maxed out all calls.

I'll sniff around twitter more closely and see what I can come up :P

Just as a data point: http://daniel.vorpalcloud.org/
You'll see that mine is indeed posting daily like it's supposed to, however what it's posting is wrong =/

My plan is to rewrite this 'cause there's clearly some nasty bugs in the implementation. The call I make to twitter is supposed to be requesting "tweets within the last 24 hours" but ... it's giving me like the last 3 instead. Doesn't make a lot of sense.

am wondering if they've done some of their unannounced changes to the API. they seem to be doing those often.

Who, Twitter or Drupal? (I'm guessing Twitter)

twitter :) i seem to remember techcrunch reporting on developers' finding out about changes after apps started to break en masse yet w/o the company forewarning about the changes.

That's just annoying =) But yeah, I see the API call I was using before is completely gone. JOY! Working on that at the moment.