Today, the team at Twitter is shutting down their basic authentication service. For all you active tweeters, this is a good thing. Third party services will stop asking for your login information. You will finally be able to change your password in a single place. And you can put a definitive, one click, end to enthusiastic spamming on your behalf. I for one, welcome that change.

We’ve updated the Twitter Timeline plugin so it works seamlessly with Twitter’s new requirements and meets the needs for the majority of the Community. For example, if you are displaying a user or public timeline, and the feed you are using is not private, all the updated plugin needs is a screen name and you’re good to go.

Please note that if you are using the Twitter Timeline plugin, the update is required. The old version will silently stop working.

Happy Tweeting!

Its awesome that Oauth is now being used, but I have to say, finding this out by having all EE sites using Twitter Timeline just stop showing tweets was crappy.

Thanks for getting the updated plugin out even before any of my clients called to let me know about their broken feeds. I think I just updated that last one of our client’s sites and both the 1.6.x and the 2.1.x versions of the plugin worked as advertised! Thanks for the speedy solution.

Agreed, thanks so much for getting this fixed. Would have been nice a day earlier before I was freaking out, but still And it’s rock solid. Very nice, thanks guys.

Anyone have the code bit for {status_relative_date} so that it doesn’t show the long posted date? Meaning instead of “5 days, 1 hour, 55 minutes” ... something like “An hour ago” or “A month ago”.

FWIW, here’s the basis for what the Twit-ee module was doing to get the nice relative date format: http://stackoverflow.com/questions/11/how-do-i-calculate-relative-time/501415#501415

I don’t have the chops to make that happen for this plugin, but if someone else does…that’d be delightful.

A devot-ee search for relative date also reveals a handful of potential candidates. You could try passing {created_at} to one of those plugins.

@Pascal - That’s a great idea!

The Social Date plugin looks like it’d be perfect, but it is 1.x compatible only. I’m not sure how to convert 1.x plugins to 2.x, but I might take a stab at it later.

Is it possible to combine feeds from 2 or more twitter account with this plugin
like screen_name=“screen_name1|screen_name2|screen_name3”  ?

Would it be possible to ignore mentions/replies (@‘s) ? I don’t need people to follow my conversations on my website.

the new update works at first, then errors out on line 394. I cannot keep it working for more than 5 minutes… Any thoughts?

Warning: Invalid argument supplied for foreach() in /www/server/public_html/ee/system/plugins/pi.twitter_timeline.php on line 394

using EE1.6.x

We had this throw an error yesterday because we hit the rate limit so it was trying to loop through elements that didn’t exist.

It would be great if getting rate limited just made the plugin perform the same as if twitter were offline.

daniel090 - 02 September 2010 01:32 AM

Warning: Invalid argument supplied for foreach() in /www/server/public_html/ee/system/plugins/pi.twitter_timeline.php on line 394

I’m getting this exact same error. I’m using EE 1.6.9.

ver 1.2 allowed the parameter type=“friends”. Is this no longer available in 1.3?

cheers

Great job guys!

The 1.x download still says its version 1.3 should it work anyway?  It seems like its not updated on my end.

Yes, 1.3 is the incremented version for EE 1.x, and 1.4 is the version number for EE 2.x; the EE 2.x version of the plugin already had a 1.3 update for its conversion to EE 2.x.

The plugin doesn’t work when you’re on a shared server. I’m getting the following error (echo $rawxml in pi.twitter_timeline.php):

From def.twitter.com:

- Anonymous calls are based on the IP of the host and are permitted 150 requests per hour.
- OAuth calls are permitted 350 requests per hour.

Is there have a solution for this problem?

Looks like authentication was just removed from the Twitter Timeline all together.  Is there an interest in EllisLab to make the Twitter Timeline plugin authenticate via OAuth?  If not, I may take a stab at it myself since we have a client that needs authentication to work again (for their friends timeline).

Thoughts?