WP to Twitter
[resolved] XMLRPC, long message, and Bit.ly Bug (4 posts)

  1. n8vision
    Posted 3 years ago #

    I found posting using XMLRPC (in my case the WordPress iOS client) there is apparent bug. I am also using bit.ly 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!


  2. Joe Dolson
    Plugin Author

    Posted 3 years ago #

    I don't think this has anything to do with Bit.ly; 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.

  3. Joe Dolson
    Plugin Author

    Posted 3 years ago #

    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.

  4. n8vision
    Posted 3 years ago #

    Sounds perfect, thanks for all your hard work Joe!

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • WP to Twitter
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic


No tags yet.