• I wanted to upgrade my WordPress installation (1.5) to the current version (1.5.1.2). While fiddling around with it and MarsEdit, I discovered that Trackback with XML-RPC doesn’t seem to work at all, at least not the way MarsEdit sends Trackback URIs. MarsEdit sends Trackbacks as an array of data (<value><array><data><value><string>http://www.myuri.com...[closing tags]). That’s not what the XML-RPC API of WordPress seems to expect or is able to handle. It seems to expect a comma-separated list of URIs. With that behaviour, Trackback URIs would only show up in the admin view as “Array”. I hacked a few of the involved scripts to work correctly in that manner, i.e. implode the Trackback URI list in case it’s an array.

    The second bug was a lost post id when editing an existing entry. In xml-rpc.php, in method mw_editPost, somewhere between fetching the post_ID (line 563) and sending the trackbacks (which I tested specifically) and the call to trackback_url_list() the post_ID is set to 1 as it seems. Since wp_update_post() returns the number of affected rows of its update, it might be obivous, where that 1 comes from.

    So I wonder, if I’m the only one experiencing those problems, and if it’s of any help, I’ll open an issue for that and attach my patches.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Try upgrading to v1.5.1.2 first. There were several changes made to the handling of pingbacks and trackbacks.

    Thread Starter pombsd

    (@pombsd)

    As I already wrote, I _did_ upgrade to 1.5.1.2 😉

    I read those bug reports you might refer to, but those do not correspond to the errors I had.

    Cheers, Mathias

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    As I already wrote, I _did_ upgrade to 1.5.1.2

    No, you wrote, “I wanted to upgrade my WordPress installation (1.5) to the current version (1.5.1.2).” Since you did not clarify whether or not the update was completed or even attempted, the phrase translates to, “I wanted to upgrade to v1.5.1.2, but the following problem prevented me from doing so.”

    Replace your xmlrpc file with a fresh one. Also, test the trackbacks with only the Default Theme and no plugins enabled. And, test the trackbacks using this interface: http://redalt.com/External/pingomation.php

    Thread Starter pombsd

    (@pombsd)

    Yes, you’re right, that’s what I was saying. Let’s just say I tested 1.5.1.2 and found two bugs that prevented me from upgrading my “production” blog (running 1.5) with it.

    I don’t know if you got it, or maybe I wasn’t clean enough about it but I tested it (on a naked WordPress installation), and I fixed the bugs I mentioned. So the question here is, if you want those patches or not. I tested sending out trackbacks with and without my patches. Without them, sending out trackbacks via MarsEdit & XML-RPC does not work for me. So I tracked down the errors and fixed them. And it at least works for me. So I won’t replace my xmlrpc.php file. The problem was not receiving pingbacks/trackbacks (since this works), it was about sending them out, when a message comes in/gets updated via XML-RPC.

    I hope, I’m being clear enough now about what I did.

    Cheers, Mathias

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Well, I’d like to see the patches implemented, but as I’m a volunteer here, there’s not a thing I could do with them. If you want the developers to see the patches, there is a procedure for that: http://codex.wordpress.org/Submitting_Bugs

    Make sure that you clearly detail what you did and what happened. And, please include your patch with the bug report.

    Thread Starter pombsd

    (@pombsd)

    Okay, now that’s just the simple answer I wanted 😉

    Cheers, Mathias

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Trackbacks with XML-RPC’ is closed to new replies.