schultemn

Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)

  • Pings are indeed working in the current cvs as well as the 2005-01-07 daily… !

    Has anyone else noticed that the pingback text includes extraneous text that both precedes the original post, and (if the ping is short enough) closes with text that comes after the end of it? Has this always been the expected behavior?

    This is using kubrick theme.

    I think there’s a problem with xmlrpc.php on the 1.5 betas. Here’s what I’ve found out in a few minutes of digging around. I apologize if the formatting is not great on this message. I can post more detailed information if this is too vague.

    I have two hosts:

    production: running wp 1.5-beta-1 2005-01-03
    development: running wp 1.5-beta-1 2005-01-05

    I:

    1) made a test post on production which will be used to ping from development

    2) made a test post on development with a link embedded in the body pointing at the test post I made on production

    I sniffed the ethernet between the two machines and saw this (trimmed down)

    T development:1296 -> production:80 [AP]
    GET /archives/2005/01/04/pingback-test/ HTTP/1.1..Host: blog.schulte.org..User-Agent: WordPress/ PHP/4.3.10….

    [ development getting the link to check to see if anything is pingable ]

    T production:80 -> development:1296 [A]
    HTTP/1.1 200 OK..Date: Wed, 05 Jan 2005 05:43:07 GMT..Server: Apache/1.3.33 (Unix) mod_gzip/1.3.26.1a PHP/4.3.10..X-Powered-By: PHP/4.3.10..
    X-Pingback: https://blog.schulte.org/xmlrpc.php..Transfer-Encoding: chunked..Content-Type: text/html….bb9..<!DOCTYPE html PUBLIC “-//W3C//D

    [blah blah, this is production sending the page back to development , with all the embedded info that it should need to complete the ping]

    T development:2625 -> production:80 [AP]
    POST /xmlrpc.php HTTP/1.0..Host: blog.schulte.org..Content-Type: text/xml..User-Agent: The Incutio XML-RPC PHP Library — WordPress/1.5-beta
    -1 2005-01-05..Content-length: 335….<?xml version=”1.0″?>.<methodCall>.<methodName>pingback.ping</methodName>.<params>.<param><value><arra
    y><data>. <value><string>https://testblog.schulte.org/wordpress/?p=2</string></value&gt;. <value><string>https://blog.schulte.org/archives/2005
    /01/04/pingback-test/</string></value>.</data></value></param>.</params></methodCall>

    [this is development now POSTING the ping to production]

    T production:80 -> development:2277 [AP]
    HTTP/1.1 200 OK..Date: Wed, 05 Jan 2005 05:43:08 GMT..Server: Apache/1.3.33 (Unix) mod_gzip/1.3.26.1a PHP/4.3.10..X-Powered-By: PHP/4.3.10..
    Connection: close..Content-Type: text/html….<div id=’error’>….<p class=’wpdberror’>WordPress database error: [You have
    an error in your SQL syntax near ” at line 1]
    ….SELECT ping_status FROM wp_posts WHERE ID = ….</div>
    .<b>Fat
    al error</b>: Call to undefined function: trackback_response() in <b>/usr/home/schulte/WWW/htdocs/misc/virt/blog/xmlrpc.php</b> on line <b
    >1225</b>
    .

    [this is production’s reply, NOTE THE SQL ERRORS! It looks like production is barfing on some mysql problem in xmlrpc.php, and this is why the link is not being posted]

    Thread Starter schultemn

    (@schultemn)

    You’re right, the content is properly protected when I clear my cookies. Sorry about that. There still might be an issue, however.

    Check out https://blog.schulte.org/archives/2005/01/01/this-should-be-protected/ and use 123 as the password. Notice at the bottom that it’s not possible to add comments. Only “This post is password protected. Enter the password to view comments.” is shown.

    If I revert back to the default theme, that same page shows the comment block fine (when the password is entered), and I am able to post a response. Then when I switch back to Kubrick 1.3.0-rc2 the comments are gone and the same “This post is password protected. Enter the password to view comments.” message is shown even when I can see the actual content fine.

    A problem with the distributed Kubrik theme?

    Those two new files also didn’t fix things for me. I reverted back to the distribution files.
    This is a fresh 1.2.2 install here. Nothing fancy at all.
    Why would pingback work for one user, and not the other?
    Could a php.ini setting foobar something?
    I’ve got Server: Apache/1.3.33 (Unix) mod_gzip/1.3.26.1a PHP/4.3.10.
    With mod_gzip disabled for the particular virtual host the blog is running on.

    I’ve got the same problem with 1.2.2. I just installed it. I am able to use a remote blog tool and it does an auto pingback to my wordpress blog just fine.
    When I use wordpress to create a new entry linking back to an entry in that other blog, the pingback does not work, even though I have “PingBack the URIs in this post” checked.
    When I look at the web logs for the remote blog, I see that wordpress is indeed GETting the correct url of the blog entry that I linked to (so it’s parsing the message for the propper URIs to ping), but it does not POST back to the correct trackback url. Maybe the wordpress engine is not finding the correct trackback url? I look at the code of the other page and it has the correct entries needed for autodiscovery.
    Any ideas?

Viewing 5 replies - 1 through 5 (of 5 total)