Okay I figured out what the problem was. The example I was following
had a bad API call:
$to->OAuthRequest('https://twitter.com/status/update.xml', array
('status' => 'Test OAuth update. #testoauth',), 'POST');
should be:
$to->OAuthRequest('https://twitter.com/statuses/update.xml', array
('status' => 'Test OAuth update. #testoauth',), 'POST');
I guess the fact that the response was telling me it is forbidden,
coupled with the fact that my http://twitter.com/account/connections
page is showing an error was throwing me off. Doh!
On Mar 21, 8:19 pm, ldnStreetLife <[email protected]> wrote:
> In PHP I've setup some test scripts following the exact example found
> herehttps://docs.google.com/View?docID=dcf2dzzs_2339fzbfsf4
>
> Everything looks good and it works to the point where can come back
> into my application from Twitter after authorizing access. I can make
> the acount/verify_credentials.xml request and get a valid response
> with a full result set, but when I make the status/update.xml request
> I am returned "403 Forbidden: The server understood the request, but
> is refusing to fulfill it."
>
> I have setup my application to get read/write access.
>
> When I go tohttp://twitter.com/account/connectionsI get "Something
> is technically wrong. Thanks for noticing—we're going to fix it up and
> have things back to normal soon." so it might just be something I have
> to wait out till it's fixed on the server, but I'm new to all this so
> maybe I'm missing something.
>
> Thanks - Rich
