Track/pingback

  • I have put in the latest CVS version of post.php and the 5/12 version of wp-trackback.php, xmlrpc.php, class-xmlrpc.php and class-xmlrpcs.php
    As of this moment, the 760 error is gone and I can accept trackbacks. But I cannot send them and pingbacks aren’t working at all, coming or going.
    If anyone has any ideas, I’m all ears.

Viewing 15 replies - 1 through 15 (of 18 total)

  • I believe that Kitten has solved this issue, and it has been forwarded to the Devs for review and implementation.
    Please correct me if I’m wrong, someone! ??

    Thread Starter MickC

    (@mickc)

    That would be great.
    If it would help, I’d be happy to test!

    The problem for me with recieving TBs was that the Options > Permalink page was generating .htaccess code that was missing a few characters. Cleaning that up fixed the incoming TB problem. I wasn’t able to figure out a fix, so I forwarded along what I found to Matt. Hopfully he’ll be rolling that in soon. (I had been playing with a new permalink structure, and regenerated my .htaccess file, that’s when things broke for me.)
    As for sending TBs, it seems ok.
    And Pings seem to be dead in the water for now. ??

    One more thing about TBs, if you have ‘require name and email’ ticked for your comments, TBs will be held for modding because there’s no email addy in them.

    I’m sure the pingback issue will be resolved for the 1.2 release? Right?

    I’m sure the pingback issue will be resolved for the 1.2 release?

    Not on my installation. Just upgraded to the RC1 version. Tested pingback and trackback by trying to pb and tb the message about the RC1 release in the dev blog. Didn’t work.
    I recall someone mentionign that there may be some issues with the mod-rewrite rules of re-RC1. I checked teh rules that RC1 generates and they seem to be the same as I used in the pre-RC! CVS versions.
    If anyone wants to test ping- and trackback with a RC1 site, you can use this URI:
    https://blog.openartifact.org/archives/2004/05/14/test-ping-and-track/

    I just tried to trackback your uri with RC1. Doesn’t seem to work.
    It didn’t work with the Delta either. Nobody knows what’s causing this?

    These issues (pingback and trackback) really should be fixed before releasing a RC, IMO. I’m willing to help if I receive some guidance as to what I can do. Let me know.

    just confirming they don’t work for me either – rc1 epsilon 5/14 build

    Well, I can trackback between my RC1 sites just fine. mod_rewrite rules look good. My attempt to trackback the openartifact link timed out. Putting the trackback link directly into the browser properly redirects back to the post, however. I’ll look some more.

    Hey, it was fixed in CVS right before I updated. That’s why I don’t see a problem. The bug has been squashed by Laughing Lizard.

    I updated to the CVS version rboren mentioned; Trackback seems to be working. But I’m not sure (yet) about Pingback. My initial tests tell me “no.” Any others?

    Ping still not working.

    Thread Starter MickC

    (@mickc)

    So the solution to the trackback problem is to d/l RC1.
    Is there any documentation on how pingbacks work? I don’t know beans about that process but if I did then I might be able to help out with that.

    Thread Starter MickC

    (@mickc)

    I upgraded to RC2 today and outgoing track/pingback don’t appear to work. I had trackbacks apparently working at one point with RC1 and that appears to have gone away.
    Am I the only one still experiencing this problem?

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Track/pingback’ is closed to new replies.