Re: collective.twitter.accounts auth problem

OK. Weird...

I'm trying to grep the code for "SignatureMethod_HMAC_SHA1()" and it seems that the oauth2 egg is not in the current buildout cache for some reason.

I find it in my backup instance but not in the current one.

That would be a likely problem!

But why wouldn't rerunning buildout in the new instance fix this!?

The oauth2-1.5.211-py2.7.egg is not coming in? 

Solution: add oauth2 to the buildout!

Fer cryin' out loud ;-)

Not real sure why this was necessary now, but was not before.

P


On 17 Jan 2015, at 2:41 PM, Peter Fraterdeus wrote:

>> 
>> Check line 94 of "collective.twitter.accounts.browser.token"
>> to find out which module lacks "SignatureMethod_HMAC_SHA1".
>> If this is a general module (one that comes with Python rather
>> than "collective.twitter"), you may see a local problem
>> (missing header files, two old system library, ...).
> 
> 
> Thanks Dieter, 
> 
> Well, indeed... line 94 has a notation in the code!
> 
>        # XXX: this seems not to be used
>        signature_method_hmac_sha1 = oauth.SignatureMethod_HMAC_SHA1()
> 
> So why is it still there?!
> 
> I've commented it out (in the build-out cache, though...)
> I assume I should actually move the egg to ./dev/ and update my buildout.
> But seems strange that this should be an issue at all.
> 
> Unfortunately, that didn't solve my problem.
> Now, it's complaining that
> 
> Traceback (innermost last):
>  Module ZPublisher.Publish, line 138, in publish
>  Module ZPublisher.mapply, line 77, in mapply
>  Module ZPublisher.Publish, line 48, in call_object
>  Module collective.twitter.accounts.browser.token, line 95, in __call__
> AttributeError: 'module' object has no attribute 'Consumer'
> 
> The line in the code is:
> 
>        oauth_consumer = oauth.Consumer(key=consumer_key,
>                                        secret=consumer_secret)
> 
> Now I'm wondering if there is indeed a problem with the oauth module.
> It's all been installed with buildout, and seems to be working fine on my other instances.
> 
> How to test it??
> 
> Thanks for your thoughts.
> 
> P
> 
> 
> On 8 Jan 2015, at 1:56 AM, dieter wrote:
> 
>> Peter Fraterdeus <[email protected]> writes:
>> 
>>> I'm unable to get twitter accounts to authenticate.
>>> 
>>> It has been working fine on my other sites (different server), but testing it today had the same problem.
>>> 
>>> I get errors when requesting the token, using the PloneTweet "app" on the control panel (builtin).
>>> I also tried setting up my own custom "app" at dev.twitter.com, got all the various secret info, tokens and so forth, but still no joy.
>>> 
>>> Plone 4.3.2 UI
>>> 
>>> Traceback (innermost last):
>>> Module ZPublisher.Publish, line 138, in publish
>>> Module ZPublisher.mapply, line 77, in mapply
>>> Module ZPublisher.Publish, line 48, in call_object
>>> Module collective.twitter.accounts.browser.token, line 94, in __call__
>>> AttributeError: 'module' object has no attribute 'SignatureMethod_HMAC_SHA1'
>>> 
>>> Is anyone else using this package? 
>> 


------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet