Support » Plugin: WP to Twitter » [Plugin: WP to Twitter] XMLRPC, long message, and Bug

  • Resolved n8vision


    I found posting using XMLRPC (in my case the WordPress iOS client) there is apparent bug. I am also using shortener.

    The bug manifests when the title of the post is over-sized. An error appears showing “403 Forbidden: The request is understood, but it has been refused. This code is used when requests are understood, but are denied by Twitter. Reasons can include: Too many Tweets created in a short time or the same Tweet was submitted twice in a row, among others. This is not an error by WP to Twitter.”

    But I think this is a problem with the WP to Twitter plugin. After a lot of playing about, I have fixed it by patching my local install:

    I changed line 437:

    $diff = $url_strlen – 19;


    $diff = $url_strlen – 20;

    Hope this helps someone, can can be tackled in the next release of WP to Twitter.

    Love the plugin, great work!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Joe Dolson


    I don’t think this has anything to do with; but the string length issue is a chronic bear. For most installations, what you’re doing will result in a character limit of 139 characters, which is certainly safer. Maybe I should institute an option to reduce the character limit for people who are having this issue.

    Plugin Author Joe Dolson


    So, in researching this, I found a really pretty random number in the truncation routine, which was causing truncation to frequently end up 2 characters too long. So, I released an update today to fix that, along with a couple other minor changes.

    Sounds perfect, thanks for all your hard work Joe!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: WP to Twitter] XMLRPC, long message, and Bug’ is closed to new replies.