The MU forums have moved to WordPress.org

/trackback/ results in '200 OK' error (9 posts)

  1. insyncnet
    Member
    Posted 17 years ago #

    Permalinks have the extra /trackback/ appended to the end of the link, which results in an '200 OK' error page, that says OK - the page has moved here, with the correct link (basically the permalink without the /trackback/).

    How do I fix this behavior? Thanks

  2. drmike
    Member
    Posted 17 years ago #

    You're not trying to bring this up in your browser, are you?

    Is the trackback sucessfully going through to the other site?

  3. insyncnet
    Member
    Posted 17 years ago #

    It goes to a page which gives the correct link: See it here.

    http://besthomesupdate.com/2006/05/28/flickr/trackback/

  4. drmike
    Member
    Posted 17 years ago #

    That's what it's suppose to do. The trackback is not for your browser like the XML feed isn't either. (Seems like we have to explain that a lot over in WP.com land.) It's an internal system.

  5. insyncnet
    Member
    Posted 17 years ago #

    Thanks. Still trying to wrap my mind around this stuff....I did notice that it did work correctly, as far as the admin dashboard.

  6. mypatricks
    Member
    Posted 17 years ago #


  7. mypatricks
    Member
    Posted 17 years ago #

    Try this send pingback
    http://kalsey.com/tools/trackback/

  8. gogetternow
    Member
    Posted 17 years ago #

    Drmike, pardon my bluntness, but I strongly suggest Wordpress developers learn Web User Interface 101 that says "if it looks like a link, it is a link" and "if it is a link, it should be clickable". So, the result of this click (see below) looks ugly, is unprofessional and just doesn't cut it! So, I guess, we need less explaining and more (fixing) action.

    "OK

    The document has moved here."

  9. drmike
    Member
    Posted 17 years ago #

    Might help them help you if you told them how you generated that output. :)

    "if it looks like a link, then it's clickable" doesn't hold true. If it did, all those aim: and feed: and other stange links would be 100% supported by all browsers.

    I do see where you're coming from though.

About this Topic

  • Started 17 years ago by insyncnet
  • Latest reply from drmike