WP to Twitter Updated to OAuth

August 16, 2010

Topics: WordPress.

Well, it’s a day for updates. Today was (at one point) the deadline for Twitter to permanently disable Basic authentication. The date has now been extended to August 31st, but the difference isn’t really significant.

The one benefit which it will provide is a little extra time to debug the new OAuth version of WP to Twitter before it becomes the only working version.

There are a lot of complications surrounding the OAuth update — most of them unfortunate. For the first time since I began work on this plugin, I had to remove features. As far as I can tell, there’s no way to operate two separate user accounts with an OAuth authenticated application, for example. As a result, I’ve had to remove the ability to assign separate author accounts for Twitter posting. As development progresses, a way forward may show up — but for now, I just don’t really have another option.

My biggest request at this time: if you can, please decide you’re willing to use this version now, to provide me with feedback so it will work as well as it possibly can when all past versions cease to be functional.

There will be problems; I’m sure of it. I just hope to find them all soon enough.

105 Comments to “WP to Twitter Updated to OAuth”

  1. Obviously, answering every question individually is beyond what I can keep up with at the moment. Here are some general notes:

    1) Error: Call to undefined function curl_init()

    Yes, you need cURL support for this plugin to work at this time. This will not be altered soon.

    2) Fatal error: Class ‘OAuthSignatureMethod_HMAC_SHA1’

    This comes from installations which are using a different OAuth class from that required by the plugin. Inform your host that you need to be using an OAuth class which supports that option; either by disabling their default OAuth library or by updating it to a different version.

    3) Parse error: syntax error, unexpected T_STRING, exp. T_OLD_FUNCTION or T_FUNCTIONor T_VAR or ‘}’

    This error comes from PHP 4 not recognizing the public or private directives in the Twitter OAuth class. You need to upgrade to PHP 5.

    4) Twitter is blocking your application

    I’m sorry about that, but there’s absolutely nothing I can do about it. This is one of the powers which Twitter wanted to gain from this change: they can shut down any individual application. If they decided they didn’t like yours, that’s something I am unable to help with.

    5) If in doubt about what URL, Application Name, or Description you should be using, be aware that in general you should be referring to your own web site as the operating application. What you are essentially doing is registering your web site as a Twitter application.

    6) If you need to change your hosting server to PHP 5 you need to contact your host. I can’t help you with that.

    7) Blank page – I believe that this is the same as the other undefined function or various fatal errors, but on installations with error reporting disabled. If somebody can tell me otherwise, that would be great.

    8) Failure to post.

    First steps: check your settings and verify everything is set up as expected. If using individual author options, disable it. Second: verify that Twitter has not disabled your application. Third: try various options, including posting an edit, posting a new post, and the test cycle before contact me. Give me as much detail as you can before reporting an error. I will no longer respond to uninformative requests for help – I don’t have the time to ask everybody for the details of their issues.

    Thank you – I’m closing comments on all WP to Twitter related posts except for the Support thread.

  2. I’ve done my own Twitter App and enter all required Keys. When i click on “Connect to Twitter” following Error Message appears:

    Parse error: syntax error, unexpected T_STRING, exp. T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in twitterOAuth.php on line 18

  3. How do I switch my blog settings to php5?

  4. @Michelle B and for anyone else having trouble filling in the form – Here’s a quick screenshot of a sample application: http://bit.ly/b6kT0T

    @Omar Here’s what my application page looked like after filling out the form (with secret stuff blocked out): http://bit.ly/9tl6Id