Scribefire. . .more like. . .Poopfire

Posted on 07.30.2008 by Dan

Scribefire, a very excellent blogging tool I’ve been using for some time seems to have borked when it comes to interacting with WordPress.  Spent most of the afternoon, as well as the past few hours searching for a solution.  Keep getting the error:

“The server returned a malformed response.  Please check that your blog and API URLs are correct.”

So yes.  That’s annoying, as one of the nicer feature of Scribefire was the ability to post entries to multiple sites simultaneously.  Looks like I’ll have to bug Phil to give me a hand with this one.  I’ll likely be buying a few books on beginners web dev, so if you have any suggestions, they’d be appreciated.

This entry was posted in Rants and tagged , , , . Bookmark the permalink.
  • http://pennybutler.com/wordpress Penny Butler

    I’m getting the same error tonight for some reason, I have a bunch of blogs.. it is coming up just for a couple of my blogs (which were all working before I upgraded ScribeFire to the latest version last week).

    I have several that are working fine, they are all the same version of WordPress, mostly have the same plugins as each other, and some are working on the same server.. I can’t see what could be causing it, the API URL looks the same as the ones that are working..

    I’ll be watching your post for an update.. cos I LOVE scribefire and am lost without it .. :(

    I’m also getting the same API error when I go to “Edit” the blog settings in ScribeFire, which I wasn’t getting a few moments ago which is strange..

    Penny

  • admin

    Hey there, and thanks for the comment!

    I managed to dig up a solution this morning, or at least one that worked for me, give it a try:

    1. When entering a WordPress.org blog, instead of clicking the “Next >” you may be clicking “Configure Manually”. Then, from the list, the most common choice is “WordPress.com”. Since you are actually using your own install of wordpress (.org), you actually aren’t on wordpress.com and so get invalid login/password. For this case, simply adding the blog and clicking “Next” without clicking “Configure Manually,” fixes the problem.

    2. It seems, for whatever reason, a blog may not have the XML-RPC publishing option checked and this may disturb the process. In order to turn on XML-RPC publishing, go to your WordPress account. On the top, far right, click on the “Settings” option, followed by “Writing,” (from among top left options). Scroll down to find “XML-RPC Publishing,” and check the box that says “Enable the WordPress, Movable Type, MetaWeblog and Blogger XML-RPC publishing protocols.”

    Let me know how it goes!