The DLL file is also in the bin folder. My document type has the "tweeted" property as well.
If I copy and paste the above login and username (obviously censored here) from this tweet.config to their web interface I am able to login successfully. However, after publishing the node my umbracoLog table logs the following:
FMDOCTWEET:: The remote server returned an error: (401) Unauthorized. FMDOCTWEET:: Cannot tweet
So it looks like something is wrong while authentication on the API. I am sure my login and password work when loggin in via web.
Thanks for your replies. The credentials were right, but the API wouldn't log me it at all. I see now that Darren is right, basic authentication via Twitter API has been deprecated on 16th August 2010. Looks like we've got to use OAuth from now on.
Problem loggin into Twitter API
Hi,
I am trying to use this package to automatically publish my blog posts into my Twitter account.
My tweet.config appears to be in the correct folder: /umbraco/plugins/DocumentPublishTweet/tweet.config with the right configuration, as follows:
The DLL file is also in the bin folder. My document type has the "tweeted" property as well.
If I copy and paste the above login and username (obviously censored here) from this tweet.config to their web interface I am able to login successfully. However, after publishing the node my umbracoLog table logs the following:
FMDOCTWEET:: The remote server returned an error: (401) Unauthorized.
FMDOCTWEET:: Cannot tweet
So it looks like something is wrong while authentication on the API. I am sure my login and password work when loggin in via web.
Any ideas or suggestions, please?
Thanks in advance,
Andre
Hi Andre
And you're absolutely positive you have not overseen a typo in your credentials?
/Jan
Hi - Twitter no longer supports user/pass authentication using their API so this package is redundant.
Thanks.
Hi Jan, Darren
Thanks for your replies. The credentials were right, but the API wouldn't log me it at all. I see now that Darren is right, basic authentication via Twitter API has been deprecated on 16th August 2010. Looks like we've got to use OAuth from now on.
Thanks,
Andre
is working on a reply...