I get this message when creating new content that is supposed to also be published on Twitter:
An error occurred when posting to twitter: 401 Unauthorized
It happens whether I tick the option to post or untick it (on node/add/* page).
This is all without a trigger assigned to it, because when using triggers even unwanted posts are pushed to Twitter (unpublished, and unticking it when creating new content) so I disabled them.
Possibly related - Unpublished nodes are posted to Twitter
Comments
Comment #1
kostajh commentedSame problem. It was working fine, then a week ago I started getting this message. I checked my password for the default Twitter account to see if that might have been an issue, but it isn't.
Comment #2
tomcatuk commentedSame issue here - subscribing.
Comment #3
CobraMP commentedi had to remove my twitter accounts in my profile then I had to re-enter the user/pass in the setup
Comment #4
lokolo commentedhave the same problem...it was working fine, now suddenly a 401 error... removing the accounts didnt help
Comment #5
baxterjones commentedsame problem.. and removing accounts didn't help..
Anybody got some ideas i can try?
thx
Comment #6
lokolo commentedI solved it with deactivating the "Twitter Actions" module (dont need it) and removing and re-adding the twitter accounts. Now it works again.
Comment #7
tryitonce commented... one more subscribing - first my linkedin integration went now Twitter - ..... hope this solves it.
No, nothing here helped - twitter was working well and then suddenly without any apparent reason on my Drupal installation - 2 different sites -same host - stopped posting to twitter some 23 hours ago.
????????????
Comment #8
youkho commentedSeems to be a general problem with Twitter 2 of my sites different hosts and same error and got an email from twitter that they're going on for big changes maybe that's why
Comment #9
foxtrotcharlie commentedI suspect this could be due to twitter changing their API and no longer supporting basic authentication. See: http://drupal.org/node/404470 and http://blog.twitter.com/2010/08/twitter-applications-and-oauth.html
I love this quote "Fortunately, developers have known about our transition to OAuth since last December, so they’ve had time to update their apps"...
Comment #10
tryitonce commented.... yeeeesssssss and in true big boy fashion - I just received the email announcing the changes from Twitter - 2 days after the event ...
So, what is the answer then for those wh wasted time trying to install, re-install and reset things time and again.
Someone out there who can give us a brief note on what to do now?? Thanks .....
Comment #11
KingMoore commentedHey Guys,
We are all having problems today! Check out this issue:
http://drupal.org/node/404470
Hopefully we can get a quick fix up for 2x... it doesn't seem like we are that far away. I unfortunately don't understand the project enough to help with the coding.
Comment #12
Rhino commentedThat's good news Kingmoore
Comment #13
DjC4 commentedSubscribing to thread. Hoping for OAuth patch soon :(
Comment #14
Gerben Zaagsma commentedsubscribing
Comment #15
mandclu commentedSubscribe.
Comment #16
tryitonce commented.... go to http://drupal.org/node/404470 and follow the solutions there - don't hang around here and hope for a magic solution - well, up to you ....
Comment #17
bryanb229 commentedThanks!
Comment #18
rar9 commentedSubscribe
Comment #19
avpadernoThis report is a duplicate of #532368: 401 error when authorised user posts to twitter.