Professional Freelance Web Developer
CodeIgniter Activist, Caffeine Junkie

Elliot Haughin

Twitter CodeIgniter Library gets oAuth Love!

1st May 2009

After asking for your opinions on which library I should release, there was a clear trend towards oAuth integration in the current ‘Twitter CodeIgniter Library

There’s some important changes with this release.

  1. Twitter_Connection.php is now contained within Twitter.php
  2. Code has been completely refactored
  3. Controller logic remains almost identical, despite large changes to the library
  4. Allows 3 types of authentication: none, basic, oauth
  5. oAuth is now fully operational

First of all, I must say a big thank you to everyone who helped me test and debug this library, I’ve had some real headaches with getting this operational.

Eventually, I had to use EpiTwitter by Jaisen Mathai. A big thank-you for his great work on Github. That code has been ported to this library, so credit to him for much of the oAuth work.

Eventually all the Epi functionality will be rewritten from scratch, but for now, the library seems to work pretty well.

Because Twitter’s oAuth uses a callback with a query param (that’s a ? in the url), Jamie Rumbelow’s MY_Input is bundled with the application to let use the Twitter library $_GET['oauth_token'].

It’s very important that you read the new documentation for the library if you want to use oAuth.

Twitter CodeIgniter Library with oAuth

Related posts:

  1. Twitter API Library For CodeIgniter Released
  2. CodeIgniter Twitter Library
  3. CodeIgniter Vimeo API Library Released
  4. New CodeIgniter Library: Facebook Connect

blog comments powered by Disqus

Boring Stuff

Design © copyright Elliot Haughin 2009

Content published here are copyright their respective owners.

You cannot copy content from this site, either in English or translated to another language.

Keep Subscribed

Theres lots of ways for you to keep up with me on the web.

Please Note

Information given out on this blog should only be used as a guideline. I hold no liability for any code I write.

Always consult a professional before acting on this guidance.