Marcus, Your problem is that you are only setting an access token. You should also set your application's consumerKey, consumerSecret and callbackUrl values so they can be passed into the access token object to create a valid signature (the key names for the options are identical to those in Zend_Oauth_Consumer).
I just performed a quick smoketest myself to double-check there's nothing else causing a problem and it works fine ;). Just bear in mind that the access tokens only carry the token data - the rest must be configured in addition and is passed to the HTTP Client generated by the access token for signature generation. Best regards, Paddy P.S. Will update the documentation in the next day or two showing the workflow more clearly. Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Justin Hart <[email protected]> To: Marcus Stöhr <[email protected]> Cc: [email protected] Sent: Thu, June 24, 2010 5:47:47 PM Subject: Re: [fw-general] Zend_Service_Twitter: Cannot update status using Zend_Oauth_Token_Access if you print_r the whole twitter object, do you see your Oauth_Token_Access in the structure? On Thu, Jun 24, 2010 at 3:58 AM, Marcus Stöhr <[email protected]> wrote: Hi there. > >>I'm using Zend_Oauth_Consumer to retrieve an access token from Twitter which >>is working fine. I instatiate Zend_Service_Twitter using the access token >>like this: > >>$options = array( >> 'accessToken' => unserialize($userConnection->getAccessToken()), >> 'username' => $userConnection->getId() >>); > >>$twitter = new Zend_Service_Twitter($options); > >>No exceptions are being thrown or such and when I try to update the status, I >>get the following response: > >>object(Zend_Rest_Client_Result)[131 >>] >>protected '_sxml' => >>object(SimpleXMLElement)[136 >>] >>public 'request' => string '/1/statuses/update.xml' (length=22) >>public 'error' => string 'Incorrect signature' (length=19) >>protected '_errstr' => null > >>The isAuthorised()-method gives me true, so I assume everything worked fine. > >>Any suggestions were the problems lies? > >>- Marcus
