Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Andre 6 posts 26 karma points
    Apr 21, 2011 @ 11:31

    Problem loggin into Twitter API


    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:

            <account key="mainaccount">
            <document_type alias="BlogPost">
                    <tweet domain_filter="">
                        <message>New post on our Blog! - '#title#' #url#</message>

    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,



  • Jan Skovgaard 11245 posts 23441 karma points MVP 6x admin c-trib
    Apr 21, 2011 @ 17:50
    Jan Skovgaard

    Hi Andre

    And you're absolutely positive you have not overseen a typo in your credentials?


  • Darren Ferguson 1022 posts 3258 karma points MVP c-trib
    Apr 22, 2011 @ 12:51
    Darren Ferguson

    Hi - Twitter no longer supports user/pass authentication using their API so this package is redundant.


  • Andre 6 posts 26 karma points
    May 12, 2011 @ 13:20

    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.



Please Sign in or register to post replies

Write your reply to: