I feel a bit like Dr. Gregory House. Now the indexing problem seems to be solved and I don’t know why, I need to find out what caused those symptoms, since they could come back in the near future.

Neither disabling WP-HashCash nor Kramer did work («Put 0.5 mg of Atropine» would said House). It wasn’t that, so what was it? I disabled most plugins in my system and about half an hour later I was indexed («The patient is reacting and everything has come back to normal»).

I’ll keep investigating on it. By now, the previous post was indexed while having the LiveCalendar plugin enabled, so this one is discarded. Today I’ve written after enabling WP-PostRatings. Now lets expect some reaction…

Update: «Of course! How didn’t I realize?» House said.

Examining the plugin WP-PostRatings (the voting stars you see below), I realized the file postratings.php had the following code:

<?php
  217         foreach ($bots_useragent as $bot) {
  218                 if (stristr($useragent, $bot) !== false) {
=>219                         exit();
  220                 }
  221         }

Line #219 terminates the script if an internet bot is reading the page. This function is hooked to the blog main page, thus preventing the bot to read remaining blog. Simply, changing replacing that line with return; fixes the problem:

<?php
  217         foreach ($bots_useragent as $bot) {
  218                 if (stristr($useragent, $bot) !== false) {
=>219                         return;
  220                 }
  221         }

The author has been told about this issue and it will be fixed in the next release.

Posted by Boriel as Wordpress at 10.44 am

Rate This Post:

(25 votes, average: 3.52 out of 5)