Twitter Signin module incompatible with OAuth 6.x-3.x branch

The dependancy in twitter_signin.info is wrong, change:
dependencies[] = oauth
to
dependencies[] = oauth_common

this solved the problem

After i take a look at oauth module, there is a big different between version 6.x-2.x and 6.x-3.x

twitter module seems to use oauth 6.x-2.x version

This should be made explicit on the modules page. Patch attached.

Use hook_requirements() instead? http://api.drupal.org/api/function/hook_requirements/6

@voxpelli Good point!

Here's a new patch for hook_requirements().

Here's a patch against DRUPAL-6--3

@claudiu.cristea: Please read #4 - OAuth 2.x are not compatible with OAuth 3.x and OAuth Common is now OAuth 3.x. The patch in #8 is the correct approach for now.

There is an initiative on upgrading this module to use version 3.x of OAuth.

This would probably be a good distinction between twitter-6.x-3.0 and twitter-6.x-3.1+. I think 3.0 should forever be incompatible with OAuth 3.0 so that a severe change like this isn't made mid-stream.

http://wi-ca.org/Twitter_Signin_OAuth

Eagerly waiting for this nice work and accept the error messages in my admin pages & not to use this module until the definitive fix / new release.

Won't use OAuth 2.x, as I have my site seen crashing more than once before on updating (interrelated) modules...

Maybe I should thoroughly remove Twitter 3.x too, as former poster remarks that a working version should be in >3.1 and the present 3.x version is completely different.

Hi,

Apologies if this is the wrong queue to post this question in, yet I'm trying to find a solution for the fact that (with re-directs enabled) my site crashes due to a bug in the linked-in module. Unless I set it to use non secure plain text encryption. I'm using the 3.0-beta3 version of Twitter and because it's not compatible with the Oauth 3.x branche I can't upgrade Oauth to solve the problem.

(http://drupal.org/node/1046490)

I don't use the Twitter signin sub module, my interest lies in the other features of the Twitter module. Would the patch from #10 allow me to upgrade to oauth 3.x and still use the Twitter module?

Thanks in advance!

What is the status of porting functionality to OAuth 3.x? I'd like to help if i can.

+1 same issue here. I am using Services 3.x which requires OAuth 3.x so I would also like to know the status. thanks

See: #1255510: Upgrade to oauth 3.x (oauth_common)