Thread

I’m using the twit-ee module to display a client’s Twitter feed on their homepage.  It has worked fine, but at the moment isn’t displaying anything.

Is there a way to test if the problem is Twitter or the module?  I checked the Twitter Status Blog but didn’t see anything that could be related.

Twitter feed still not displaying.  I wonder if anyone else is experiencing problems, either with Twitter or Twit-ee?

When did the problem start? Twitter recently killed the old authentication scheme. I haven’t used twit-ee, but you might want to make sure you have the latest version.

Ah, I see now that Twitter has switched to OAuth.  I’ve submitted a ticket to the Twit-ee developer on GitHub to see if he plans to update it.  Until then it looks like I need to find a replacement…

For anyone else who comes looking for answers because Twit-ee has stopped working, George Ornbo, the developer of Twit-ee, is unable to update the module for OAuth at the moment but it’s open to anyone who wants to update it.  Thanks, George, for your prompt reply.

And I missed this blog post about Twitter Timeline being updated for OAuth — that appears to be the way to go now.  One note, as of this post they are troubleshooting why the “create_links” parameter is not working properly.  You can read about that in this thread.

Just an aside: Is it possible for you to use the Twitter account’s public RSS feed? We use this in a couple of cases to simplify the display of tweets - use Magpie or another RSS “reader” to display the feed (and/or re-format as necessary).

Just an aside: Is it possible for you to use the Twitter account’s public RSS feed? We use this in a couple of cases to simplify the display of tweets - use Magpie or another RSS “reader” to display the feed (and/or re-format as necessary).

You can, but there could be problems to watch out for. Twitter’s api rate limit will go into effect after 150 hits per hour. But, if you cache the results, and only hit the RSS/Atom feed once every 10 min, then you should be fine.

We’ve never run into issues with this approach since we’re not worried about a 5-10 minute lag between tweet updates. There are some free JS-based solutions that provide immediate gratification when displaying tweets. We’ve actually run into more issues with Twitter’s stability (i.e., fail whale) though their move to the new datacenter should be an improvement in their fairly poor uptime [we hope].