Twitter Actions/Post/Signin Requiring oauth_common [#1437628]

I have been using Twitter Post all along with no issues and all the sudden I noticed that is no longer showing on our "create node" pages. When I looked at the module section, I noticed that the sub-modules are unchecked and greyed out now and showing "Depends on: Oauth_common (missing)".

I have the new "oauth" module installed, as it has been all along. Why would the latest version of Twitter be showing that an obsolete module is dependent?

Comment	File	Size	Author
	twitter-issue.png	47.5 KB	marty.true

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Anonymous (not verified) CreditAttribution: Anonymous commented 4 April 2012 at 11:53

Same problem here. What I don't get this:
When using the old oauth-6.x-2.02 it works to add an account, but e.g. Twitter Post can't be enabled.
When I download the latest oauth (6.x-3.0-beta9, recommended here http://drupal.org/node/1226204) I can enable Twitter Post etc. but adding a user doesn't work anymore, as the oauth token is empty.

The newer oauth also doesn't allow me to set an encryption either, just "Enable the oauth provider, This option controls whether this site should act as a OAuth provider or not" and "Request token lifetime (in seconds)". The old oauth module allows me to set an encryption.

Not sure if this post is more a twitter module or an oauth module problem.

* Edit *
For some reason it worked when deploying it on the server. This time it doesn't ask for oauth_common either anymore.

Comment #2

juampynr CreditAttribution: juampynr commented 5 April 2012 at 23:56

xstatic, do you have the latest version of http://drupal.org/project/oauth?

Deraynger: I would appreciate further feedback so I can find out what is happening. If the latest version of OAuth has fewer settings, then create an issue for that project and relate to this one. OAuth's issue queue has been dead for months but I am looking for some time lately to help on it, so your issue will get attention.

Comment #3

marty.true CreditAttribution: marty.true commented 9 April 2012 at 14:04

I was not. I was using 6.x-2.02...
I have updated to latest version and that seemed to fix the issue. Thanks for your comment and solution juampy!

Comment #4

marty.true CreditAttribution: marty.true commented 9 April 2012 at 14:25

Ok, that fixed the ability to have "Post to Twitter" but once I updated and attempted to use it in that way, I get the following error:
Fatal error: Cannot redeclare class OAuthException in /mysite/modules/oauth/oauth.lib.php on line 17

Comment #5

juampynr CreditAttribution: juampynr commented 9 April 2012 at 16:19

xtatic, remove Oauth 2.02 and use Oauth 3 instead. Are you sure you have this version and have removed the old oauth?

http://drupal.org/node/1118300

Comment #6

Anonymous (not verified) CreditAttribution: Anonymous commented 18 April 2012 at 13:51

Using OAuth 6.x-3.0-beta4 and Twitter 6.x-3.0-beta9 on a local test server and on the staging server (where it worked).

I think the main problem was that it didn't work to add an account on the local test server, but on the staging it worked to add the account. Locally it still doesn't work.

Comment #7

dsudheesh CreditAttribution: dsudheesh commented 24 April 2012 at 13:22

I am also using the OAuth 6.x-3.0-beta4 and Twitter 6.x-3.0-beta9 on a development server. But when i click on the Sign in with twitter link on the login page I am redirected to the http://api.twitter.com/oauth/authenticate?oauth_token=
and get a message

" Whoa there!

There is no request token for this page. That's the special key we need from applications asking to use your Twitter account. Please go back to the site or application that sent you here and try again; it was probably just a mistake."

I am not able to figure out why this issue is happening. I have configured the Oauth consumer key and Oauth Consumer secret properly at admin/settings/twitter.

Comment #8

juampynr CreditAttribution: juampynr commented 2 May 2012 at 20:08

dsudheesh, are you still having that issue? I do not know why a token is not generated.

Been a development server, I would suggest to reinstall both modules (oauth_common, twitter and twitter_sign).

You can also try to reset your API keys at the Twitter settings page.

Comment #9

juampynr CreditAttribution: juampynr commented 2 May 2012 at 20:09

Status:

Active

» Postponed (maintainer needs more info)

Changed status.

Comment #10

Anonymous (not verified) CreditAttribution: Anonymous commented 3 May 2012 at 11:09

Ok, got it to work locally too, just so I can help you guys out:

drush pm-disable oauth_common (y)
drush pm-uninstall oauth_common (y)
drush dl oauth (overwrite = y)
Go to modules and enable oauth and twitter post
Go to oauth settings and save as is (not sure if necessary)
Go to dev.twitter.com and add the app.

Make sure it has read and write permission*
For the "Callback URL" the Drupal twitter module suggested: http://dev.my-site.com/de/twitter/oauth, but as it automatically picks a language, I gave in http://dev.my-site.com/twitter/oauth

Add the OAuth consumer key & secret on the twitter module settings page

Save

Flush all caches
Go to your user, twitter accounts, add account, and "Allow Application" from twitter page.
Test with some content type

*If it wasn't read & write, and a user had been added already, easiest way for twitter post to work for me was by removing the twitter user in Drupal and re-adding him

Hopefully it works for you now :)

Comment #11

nnmlss CreditAttribution: nnmlss commented 12 May 2012 at 19:32

Deraynger, can you describe where the "Allow Application" option/checkbox is? Is it possible to be skipped/unnecessary in Drupal7?

i start develop drupal to twitter first on drupal6 with no success and found same oauth_common issues and with few modules uninstall/ user twitter accounts remove, fix'em out but no connection achieved.. Then I have to replace the drupal6 installation with drupal 7 and start from scratch again following http://drupal.org/node/1346824 as a guide a few times, from start to end, even delete and register apps again but all I achieve is I can receive my tweets in Drupal, but no any chance for drupal to twitter connection.........

Once I have installed in sites/all/libraries/twitter/twitter.lib.php and add twitter account in drupal, I received the twitter status in drupal, but when I try to post to twitter by submitting a new drupal page, I receive a status msg in drupal

Successfully posted to Twitter

Basic page title_of_the_page has been updated/created.

but no tweet in my twitter account?

When I try to login with a twitter account, once I click on the login-with-twitter button I receive the next message

Whoa there!
There is no request token for this page. That's the special key we need from applications asking to use your Twitter account. Please go back to the site or application that sent you here and try again; it was probably just a mistake.

I try all of this in Drupal7 site, the 'green'(latest) Twitter and Oauth Drupal7 versions of the modules from drupal.org/project with a twitter.lib.php from the https://github.com/juampy72/twitter-rest-php/downloads library, read and write enabled titter application with both OAuth key and secret added in drupal..

Any help is appreciated..

Comment #12

Anonymous (not verified) CreditAttribution: Anonymous commented 15 May 2012 at 09:24

Hi nnmlss,

"When I try to login with a twitter account, once I click on the login-with-twitter button I receive the next message"...

I'm using Drupal 6, but my description solved exactly that problem for me. I'm not sure if Drupal 7 is another story. Did you follow my description (including the first 3 steps)? If you don't use drush, you could try to go to modules (in D6, (site)/admin/build/modules) and deactivate the oauth modules, then uninstall them (in D6, (site)/admin/build/modules/uninstall).

Regarding the "Allow Application", I just meant, log in to twitter with your account (after adding the account to your Drupal-site), then it'll ask if you want to allow the application to use your twitter account. For this to work, the "Whoa there..."-problem has to be resolved first, else you can't add your account to your Drupal-site and can't post to Twitter.

Comment #13

juampynr CreditAttribution: juampynr commented 19 May 2012 at 00:06

Status:

Postponed (maintainer needs more info)

» Closed (won't fix)

Please check http://drupal.org/node/1346824 to verify that you got Twitter and OAuth configured correctly.

Regarding not being able to post to Twitter, please have a look at #335459: Does not post to Twitter, despite "Successfully posted to Twitter" message.

This issue's title is related to Actions/Post/Signin Requiring oauth_common, which is in fact a dependency as the Twitter API requires OAuth for these actions.

Closing then.

Comment #14

nnmlss CreditAttribution: nnmlss commented 25 May 2012 at 20:56

EDIT:
Hooray! I successfully posted to twitter from my localhost Drupal installation. The key I was missing was exactly "Allow the application". I never seen this screen before because I never click the 'add account' button once I add the twitter account in my Drupal site because I thought this button belongs there to be used if you want to add another account, but not to authorize the current one. I think it will be more meaningful if the text is replaced with 'Authorize account' instead of 'add account'.

10x for your help, guys.