This is correct.

I personally had to delay upgrading the Twitter component on Twitgoo until
later because I still have clients logging in with username/password
credentials - so a oauth-only solution was not feasible. This will be forced
to change in a few weeks (http://dev.twitter.com/pages/oauth_faq says
Aug16).

You can find my interim twitter oauth extension here
http://bitbucket.org/onyxraven/zend-contrib/src/tip/zs-Twitter-Oauth/ - I'll
be moving that to git this week with an updated version, and will link back
there as well..

On Sun, Jun 27, 2010 at 8:26 PM, Shaun Farrell <[email protected]> wrote:

> Zend_Service_Twitter as of 1.10.6 requires oauth for logging in.
>
>
> Shaun J. Farrell
> Washington, DC
>
>
>
> On Sun, Jun 27, 2010 at 10:10 PM, Jack Houghton <[email protected]> wrote:
>
>>  Robert,
>>
>>
>>
>> Unfortunately, I may not be of that much help. I ran into the same issue
>> and switched to using cURL for my twitter feed (without OAuth). I posted
>> this to the list a month back and came away with the realization that
>> Zend_Service_Twitter was simply broken and based on cURL working with the
>> user/pass authorization I can confirm that OAuth is not yet required.
>>
>>
>>
>> Please let me know if you get anywhere with this.
>>
>>
>>
>> -Jack-
>>
>>
>>  ------------------------------
>>
>> *From:* robert mena [mailto:[email protected]]
>> *Sent:* Sunday, June 27, 2010 7:32 PM
>> *To:* Zend Framework
>> *Subject:* [fw-general] Zend_Service_Twitter not working
>>
>>
>>
>> Hi,
>>
>>
>>
>> I am trying to use Zend_Service_Twitter (ZF10.6.5 / PHP 5.3.2) but it
>> always complains about the credentials even tough I've tested the
>> username/password. I found a post somewhere that Twitter will/was no longer
>> accept this and I'll be 'forced' to use Oauth.
>>
>>
>>
>> Is this true?  In that case does anybody have a quickstart?  The manual of
>> Zend_Service_Twitter does not cover that and I am unsure of how to add the
>> capability for my app to post stuff automatically
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 9.0.830 / Virus Database: 271.1.1/2966 - Release Date: 06/27/10
>> 14:35:00
>>
>
>

Reply via email to