author image
WordTwit 2.4 Released
May 31 2010 • Written By Duane Storey • 50 Comments

We just pushed out a new version of WordTwit. Twitter has announced that they will be discontinuing their old API in June and will only support their new OAuth version going forward. So, we ripped out the old authentication system in WordTwit and upgraded to the OAuth version.

So if you upgrade to WordTwit 2.4, make sure you go to the administrational panel and reauthorize your account. Also, the signature method required for the new Twitter API (hmac-sha1) is only available in PHP5. So unfortunately at this time we’ll only be support PHP5 for WordTwit.

If you have any problems with WordTwit 2.4, please drop a comment in the support forums.

Update – version 2.4.4 is now in the repository, please make sure you are using the latest version

50 Comments

  1. Hello. Im having thin error with 2.4:
    Fatal error: Cannot use object of type WP_Error as array in /home/ps2forum/public_html/wp-content/plugins/WordTwit/include/oauth.php on line 86

    Any ideas why?

    Thanks

  2. Duane Storey

    BNC Development Guru

    June 1st, 2010

    Hmm, no. But we’ll look into it a bit later today. We’ll probably push out an update this afternoon or this evening, so keep your eye out for that. Thanks.

    • Yeah, it’s odd. I installed 2.4 last night and it was working last night but today, it’s completely broken and I can’t even get into the dashboard at this point due to the error.

  3. Duane Storey

    BNC Development Guru

    June 1st, 2010

    Rename the WordTwit folder on disk, and that should disable it so you can get back into the dashboard.

  4. Adrian

    http://www.0-100.ro

    June 2nd, 2010

    Yes, i’m having the same problem with the WordTwit plugin.

    Fatal error: Cannot use object of type WP_Error as array in …/wp-content/plugins/WordTwit/include/oauth.php on line 86

    The problem is that i had to disable the plugin by force (renaming or deleting the folder) because i couldn’t access my website nor my dashboard because of this error. Another problem is that now that the plugin is disabled all my short links that have been posted in the past on twitter don’t work for the moment.

  5. Duane Storey

    BNC Development Guru

    June 2nd, 2010

    The WP_Error problem should have been fixed in 2.4.1. If it’s still there I’d be surprised.

    Can one of you possibly let me debug on your server?

    • vich11

      June 3rd, 2010

      Duane, email me vic at screenrant.com.

      I’ll set up an account for you on WP.

      Thanks,

  6. I had that error, it was quickly remedied once I allowed the OAuth.

    • vich11

      June 3rd, 2010

      David,

      I’m all set up correctly. It seems to now take about 20 minutes for a post to be tweeted, which is an unacceptable delay.

    • vich11

      June 3rd, 2010

      Duane,

      2.4.4 fixed the delay problem – thanks!!

      Vic

  7. I find WordTwit is too fast…sometimes I’ve forgotten to put in a schedule date on a post and it fires off as soon as its published…

    • vich11

      June 3rd, 2010

      Well I could live with a maybe 1-3 minute delay, but 15-20 is too much.

  8. Duane Storey

    BNC Development Guru

    June 3rd, 2010

    Are you guys using the latest version? Are you using the the experimental tweet queueing?

    • vich11

      June 3rd, 2010

      I’m using 2.4.1 and I don’t see any option for Tweet queuing.

  9. Duane Storey

    BNC Development Guru

    June 3rd, 2010

    Please update your version. 2.4.4 should be in the repository now.

    • vich11

      June 3rd, 2010

      Done, thanks. Hopefully that fixes it.

      Should I enable Tweet queuing for missed tweets (which has happened from time to time)?

      Also, FYI the Link Statistics don’t work for me – I get the AJAX spinning wheel but stats never appear. :)

      Thanks,

      Vic

  10. Duane Storey

    BNC Development Guru

    June 3rd, 2010

    I wouldn’t enable it for now. It works fine for me, but people seem to be having problems with it. We’re planning on rewriting WordTwit once WPtouch Pro is out, so this release was just meant to be a stop-gap measure that supports OAuth. I’ll check out the link statistics next time I do an update, thanks.