Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Gene Ellis
I believe I am using the PHP Twitter libraries because I see Oauth.php and TwitterOauth.php being included in the script. I recently took this project over from the other developer and I am new to twitter programming, which is why I am unsure on how to grab that access level for the users in my

Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Abraham Williams
I can't test to confirm at the moment but I think I set up TwitterOAuth to include headers in the TwitterOAuth object. If you create a TwitterOAuth object like this: $connection = new TwitterOAuth($x, $y, $z, $a); Then you should be able to get the headers from the most recent request like

Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Gene Ellis
Hmmmgetting closer but I don't see the http headers in there. I even did a var dump, but didn't see anything related to http_info. Know where else I could look? On Tue, Jun 21, 2011 at 1:35 PM, Abraham Williams 4bra...@gmail.com wrote: I can't test to confirm at the moment but I think I

Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Scott Wilcox
var_dump the $connection object and find it in there. On 21 Jun 2011, at 19:55, Gene Ellis wrote: Hmmmgetting closer but I don't see the http headers in there. I even did a var dump, but didn't see anything related to http_info. Know where else I could look? On Tue, Jun 21, 2011

Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Gene Ellis
yep...that is what I did. This is what I received back: object(TwitterOAuth)#1 (5) { [http_status:private]= NULL [last_api_call:private]= NULL [sha1_method]= object(OAuthSignatureMethod_HMAC_SHA1)#2 (0) { } [consumer]= object(OAuthConsumer)#3 (3) { [key]= string(22) Oa8K2pY7L19CLwerewVzJ5eES1A

Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Gene Ellis
And this is the code I used to dump this: $connection = new TwitterOAuth(OAUTH_CONSUMER_KEY, OAUTH_CONSUMER_SECRET, $account['access_token_key'], $account['access_token_secret']); var_dump($connection); On Tue, Jun 21, 2011 at 2:00 PM, Gene Ellis gene.el...@gmail.com wrote: yep...that is

Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Matt Harris
Hi Gene, I've added support for this into my library which I hope helps show you how to read this information. My library is on Github: https://github.com/themattharris/tmhOAuth and the example with the X-Access-Level is the verify credentials one here:

Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Abraham Williams
You have to make an API request first. There is no header info if a request has not been made. Also you need to reset your consumer key/secret. Abraham - Abraham Williams | InboxQ http://inboxq.com/ | abrah.am @abraham https://twitter.com/intent/follow?screen_name=abraham |

Re: [twitter-dev] A few updates about the permission model change

2011-06-21 Thread Gene Ellis
boom! That was it. Thanks so much guys! On Tue, Jun 21, 2011 at 2:27 PM, Abraham Williams 4bra...@gmail.com wrote: You have to make an API request first. There is no header info if a request has not been made. Also you need to reset your consumer key/secret. Abraham -

[twitter-dev] A few updates about the permission model change

2011-06-13 Thread Matt Harris
Hey everyone, A number of updates were made to the Direct Message methods and OAuth screens at the end of last week. Here's what went out: * force_login is now supported on https://api.twitter.com/oauth/authorize * the OAuth screens now support a feature phone tier of handsets and render them in