WordPress.org

Ready to get started?Download WordPress

Forums

Trackback returns Error - 200 OK: Document has moved here. (14 posts)

  1. Xitanto
    Member
    Posted 8 years ago #

    The trackback links on my site aren't working:

    http://www.mediahug.com/

    The result of clicking on one (screenshot):

    http://www.mediahug.com/images/help/200ok.jpg

    Can I please have an explanation for this? Another user who posted this same problem didn't recieve any replies.

  2. Samuel B
    moderator
    Posted 8 years ago #

    At a guess - it's a permlink problem. Do you have a custom structure?

  3. Xitanto
    Member
    Posted 8 years ago #

    I have one of the defaults set.

    /%year%/%monthnum%/%day%/%postname%/

    Same as pretty much everyone else.

  4. Xitanto
    Member
    Posted 8 years ago #

    Yes, I'm bumping this because I can't get a good answer, and this hasn't been replied to for a day and a half.

  5. jdybka
    Member
    Posted 8 years ago #

    I'm having the same issue. WP 2.0.2.

  6. Xitanto
    Member
    Posted 8 years ago #

    Bump, no replies yet. jdybka also has the same problem and we can't get any answers!

  7. Xitanto
    Member
    Posted 7 years ago #

    Bump - still no explanation. Does this have anything to do with the "Breadcrumbs & 200 OK" bug?

  8. jwurster
    Member
    Posted 7 years ago #

    So, now I have this after upgrading to 2.0.3 from 1.5.2, but only on a couple of my Pages which are redirected to some archives scripts I use. Will regerating my permalinks help with this?

  9. allonline
    Member
    Posted 7 years ago #

    Hi I get this as well now after upgrading.
    Initially i spotted it after my host moved me to a new server which had php as cgi and i had to change the htaccess file to add ExecCGI to get php to run. Then i upgraded the Feedwordpress pugin and everything was ok then the server crashed and after a restore it was ok then it crashed again. found out it was due to the Server APi being CGi was Apache. When apache averything worked, but when CGI not everything did including Feedwordpress. found a fix for Feedwordpress giving the 200 ok problem. Posted it on my blog. soemthing to do with returning the correct header status.
    http://www.coolwebpagetools.com/blog/posts/200-ok-document-has-moved-here-page-problem-with-wordpress/

    However i noticed that while checking other links that the trackback link at the bottom of posts also gave same error and have tried to see if i could hack a wordpress file same as for Feedwordpress but cant really find what bit to change so in the end i just edited the template to remove the links at the bottom of posts. If anyone has an idea post a reply and i'll try it.

    Might have more time this weekend to play around. I have a test blog on the same server under another domain name which i can mess around with.

    Regards

    Rob

  10. gripmedia
    Member
    Posted 7 years ago #

    Bump:

    Having it also... several threads about this...

    does ANYONE have an aswer for this?

    the moved here link on our servers redirects to the URL MINUS the trackback

    IE: when you click a track back, the URL is:

    http://www.aboutralph.com/blog/archives/4/trackback/

    then you get the:

    OK

    The document has moved here.

    Apache/1.3.34 Server at http://www.aboutralph.com Port 80

    the link to here then becomes:

    http://www.aboutralph.com/blog/archives/4

    HELP!!!!

  11. Perhaps I'm missing something here, but what are you expecting to happen when you click a trackback url? Trackback urls are for blogs to talk to other blogs. You either copy the link to another site's posting form, or the software picks it up automatically.

    I wouldn't expect clicking the link to show anything very interesting at all...

  12. gripmedia
    Member
    Posted 7 years ago #

    LesBessant:

    It most certainly shouldn't show a server generated page error. I am not expecting dancing girls and a light show... I am expecting it to go to the correct article URL and display that page like it does on most standard WordPress installations. I want it to work like it is supposed to. An apache 200 page error is NOT how it's supposed to work.

    This is a technical issue not a functional or aesthetic issue.

    How come no one can come up with a sentient, cogent response to this question posed in a half dozen threads?

    Thanks for anyone's help.

  13. gripmedia
    Member
    Posted 7 years ago #

  14. gogetternow
    Member
    Posted 7 years ago #

    Like I already wrote in the thread above, I am surprised WordPress don't even bother commenting on this... :(

Topic Closed

This topic has been closed to new replies.

About this Topic