• Resolved scip

    (@scip)


    Hi,

    I am using the ThechnoratiTags Plugin, which seems to work as expected. The tags I am adding to posts show up as links to technorati (http://www.daemon.de/blog/). However, my blog is not listed on technorati.

    The problem is, that the Technoratibot doesn’t fetch the feed but the blog url itself. I traced the communication between wordpress and ping.technorati.com using tcpdump and wp sends the correct feed URL:


    POST /rpc/ping HTTP/1.0
    Host: rpc.technorati.com
    Content-Type: text/xml
    User-Agent: The Incutio XML-RPC PHP Library -- WordPress/1.5.1
    Content-length: 326

    <?xml version="1.0"?>
    <methodCall>
    <methodName>weblogUpdates.extendedPing</methodName>
    <params>
    <param><value><string>ScipLog</string></value></param>
    <param><value><string>http://www.daemon.de/blog/</string></value></param&gt;
    <param><value><string>http://www.daemon.de/blog/feed/</string></value></param&gt;
    </params></methodCall>HTTP/1.1 200 OK

    However, the Bot request then looks like this:


    209.237.230.104 - - [26/Jun/2005:23:00:56 +0200] "GET /blog HTTP/1.0" 200 6908 "-" "Technoratibot/0.7"

    Does anyone have an idea, what’s wrong ?

    regards, scip

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter scip

    (@scip)

    Beside, I just found out, that my feed is completely empty, for whatever reason.

    I updated to version 1.5.2, but the feed is still empty.

    Please Help !

    – scip

    Thread Starter scip

    (@scip)

    Well, I applied this patch to wp-blog-header.php, now the feed works (1.5.2 didn’t fix this bug ?)

    However, I don’t think technorati works now.

    – scip

    Moderator James Huff

    (@macmanx)

    First, there is no v1.5.2.

    Second, yes, this bug was fixed in v1.5.1.2.

    Third, if the blog in question is http://www.daemon.de/blog/, then you’re still running WordPress v1.5.1. Here’s a quote from your source output:

    <meta name="generator" content="WordPress 1.5.1" />

    If you were running v1.5.1.2 (the latest), it would read:

    <meta name="generator" content="WordPress 1.5.1.2" />

    So, upgrade to WordPress v1.5.1.2 and your problems should be solved.

    I thought 1.5.1.2 only addressed a potential security issue if using the default theme.

    So did I, miklb, but I’ve since been “informed” that that’s not the case – no matter that it’s specifically stated to be the case on the dev board post….

    How odd. So 1.5.1.2 isn’t simply the

    1. Open the wp-includes/template-functions-category.php file in a text editor like Wordpad.
    2. Go to around line 103 where it says get_the_category_by_ID.
    3. Create a new line after that and paste in $cat_ID = (int) $cat_ID;

    ???
    Not that I did that, but I read it to me only if you are using the default template. Anyway, it’s not that big a deal to upgrade but, it’d be nice to know OTHER things were tweaked…

    I eventually just figured out which were the actual changed files and uploaded them to all 5 blogs. Seems to be fine *shrug* – as in nothing broke thereafter….

    Moderator James Huff

    (@macmanx)

    Come on, guys. Think.

    v1.5.1.2 was a simple security fix.

    v1.5.1.1 was a massive bug fix.

    You are running v1.5.1

    I haven’t mentioned v1.5.1.1, because it’s not available, and because upgrading to v1.5.1.2 will also take care of v1.5.1.1.

    Update announcement for v1.5.1 and v1.5.1.1: http://ww.wp.xz.cn/development/2005/05/one-five-one/

    Update announcement for v1.5.1.2: http://ww.wp.xz.cn/development/2005/05/security-update/

    I’m NOT running 1.5.1 or 1.5.11, macmanx.

    Moderator James Huff

    (@macmanx)

    You aren’t, but the Scip is. The point is that everyone around here tends to forget that v1.5.1.1 was a major bug fix, and whenever the question of upgrading from v1.5.1 to v1.5.1.2 is brought up, some one always say, “I though v1.5.1.2 was just a tiny security fix.”

    Thread Starter scip

    (@scip)

    Well, the file latest.tar.gz decompressed in a subdirectory wordpress/ which I didn’t notice. Very sorry ’bout this. So now I’ve got 1.5.1.2 running, and: feed works šŸ™‚

    – scip

    PS: a suggestion for future updates: the user has to execute wp-admin/upgrade.php after unpacking. You could tell the user from which version to which version the upgrade is going. In my case it would have read “upgrade from 1.5.1 to 1.5.1” or something šŸ™‚

    Thread Starter scip

    (@scip)

    However, Technorati still accesses the wrong url:


    209.237.230.104 - - [27/Jun/2005:21:17:39 +0200] "GET /blog HTTP/1.0" 200 6908 "-" "Technoratibot/0.7"

    Any ideas?

    – scip

    Moderator James Huff

    (@macmanx)

    Are your blog URLs set correctly in Options/General?

    Thread Starter scip

    (@scip)

    finally, I found a workaround, I added the following 2 lines to my apache config:


    RewriteCond %{HTTP_USER_AGENT} ^Technoratibot*
    RewriteRule ^/blog /blog/index.php?feed=feed

    this forces the technorati bot to receive the feed when it accesses the blog directly.

    – scip

    Thread Starter scip

    (@scip)

    > Are your blog URLs set correctly in Options/General?

    I think so. There are 2 urls:

    WordPress-Adresse (URL): http://www.daemon.de/blog
    Blog-Adresse (URL): http://www.daemon.de/blog

    This seems to be ok, because I am correctly listed on blogg.de (for example).

    – scip

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

The topic ‘Technoratibot doesn’t fetch feed’ is closed to new replies.