There are numerous issues in the queue where people have followed the instructions but are unable to post.
Many of these are caused by people setting their twitter app to read-only. This is inadvertent since the twitter settings page will not save the read/write settings if you are adding the application from this page:
If instead you add and edit your app from this page:
https://dev.twitter.com/apps/new
your settings will stick.
This confusion is made worse because the admin/settings/twitter/default page links to https://twitter.com/apps/new , not https://dev.twitter.com/apps/new.
It's a simple change, and I am attaching a patch against 3.x-dev for it.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | link_change-1164568-1.patch | 782 bytes | meecect |
Comments
Comment #1
meecect commentedhere is the patch
Comment #2
michaek commentedOh, boy. This does seem to resolve some problems!
Notably, I was looking at #335459: Does not post to Twitter, despite "Successfully posted to Twitter" message, and not getting anywhere. In order to get this to work, I had to delete and re-add my authorized twitter account in Drupal, after updating my application at dev.twitter.com.
Thanks for working out this issue, and thanks for the patch. I will be pushing hard to get this into the module.
Comment #3
michaek commentedThis is committed to dev, working toward a stable release.
Comment #4
khan2ims commentedI have set the Access level to Read, write, and direct messages. Yet its not posting to Twitter.
Please help.
Comment #5
michaek commentedDid you create your app at the correct location, on dev.twitter.com? That's what this issue communicates - read/write is secondary.
Comment #6
pixel8r commentedI am having the same issue, created the app at the new dev.twitter.com this morning. I get the "successfully posted" message, but nothing on the account... Any suggestions?
** UPDATE** - Fixed. Had to delete both Twitter and oAuth and reinstall, reset all keys, delete and re-activate twitter account. Still not sure what the issue was.
Comment #7
Anonymous (not verified) commentedBig ups on #6 - thanks for the tip pixel8r! Uninstalling Twitter & Oauth modules, resetting all keys and then re-configuring somehow make it work.