100% indexed. Cron ok. No search
hip - May 23, 2006 - 12:50
I have a 100% indexed. Cron seems to work ok. But searchs for terms I DO HAVE in posts show a 'no-result' answer!
I'm on Drupal 4.6 and have locale.module activated (for spanish) and no clean URLs (because of a horrible host).
I'm pretty lost for I've already reinstalled the module, redone (copied and pasted) that bit of code in the theme, rerun the cron.php and double checked the search module info page in the admin. Where should I look for the error / solution?
Thanx in advance,
hip
Search String length/Access control
- In the settings for search, what is the minimum allowed search string length in characters? if it's too long, it will ignore your searches... the shorter ones... I would make it 3 characters
- Is the anonymous user or your current role allowed to search in Administer->access control?
- I would also change hosts to one that allows mod_rewrite for clean URLS...
Take a look at site5.com (I do not own it, I swear ;)
-----
iDonny - Web Content Management System Design, Development. & CRM
Fast replies: I have
Fast replies:
Thanx for the interest but I'm still LOST. Any other direction I should take to find a solution? (any relation to 'dirty-URLs' or spanish/locale version?)
Thanx in advance for your help,
hip
Take a look on tables
Take a look on tables search_index and search_total in your DB. I suppose you will see a lot of ????? in "word" fileld...
I think here is the
I think here is the clue.
Both tables search_index and search_total happen to have 0 items!!! though at
mydrupalroot/?q=admin/settings/search
it says '100% of the site indexed'
I'm definitely doing something WRONG. (I've even checked if I was pointing to some other database, but no, I'm pointing to the right one). It sounds as some configuration issue.
Any help now?
Thanx for the replies and your time,
hip
search does not work here too
On my site it also says '100% of the site has been indexed' but I can not find some words like 'Joomla',...
I pushed the 'Re-index site' and am waiting for the result.
After reindexing site, now
After reindexing site, now the search module works perfectly.
I've been re- reindexing it
I've been re- reindexing it but still can't get no items in the search tables in DB. :-(
Sometime it works, sometime it doesn't
Search.module doesn't work well. Even when cron is OK and "100% of the site has been indexed" as drupal said, 2 tables search_* are empty. But today I changed "Items to index per cron run" from to 200, "Minimum word length to index" to 3, check "Simple CIJ handling", then after running the cron, search.module works well again.
Can someone explain me what is happening?
Same Boat
I've been having the same issue with search. It tells me it's 100% indexed, and I've tried re-indexing, but the tables are empty:
mysql> select * from search_index;
Empty set (0.00 sec)
mysql> select * from search_total;
Empty set (0.00 sec)
search_dataset has plenty in it, though.
I've got a 4.7.0 install that was upgraded from 4.6.6, but I never tried to search in 4.6.6. I too would appreciate any insight someone could provide.
-Ding
Good to know
Good to know I'm not alone in this boat.
I'm pretty confused and being not only one single case may lead to move this post to the search.module issues list. I'll wait though for some more replies (or more time) in this thread.
Thanx again for your time and replies and have a good (working) day,
hip
Taxonomy Issue Related?
Whenever I add a new node, and cron runs to index it, I get this in my logs:
Invalid argument supplied for foreach() in /var/www/modules/taxonomy.module on line 1184.
That's this chunk of code, which seems like it might involve the broken search functions we're dealing with:
function taxonomy_node_update_index(&$node) {$output = array();
foreach ($node->taxonomy as $term) {
$output[] = $term->name;
}
if (count($output)) {
return '<strong>('. implode(', ', $output) .')</strong>';
}
}
Happens every time there's something new to add to the index. http://drupal.org/node/63392 seems like it might be related. You getting that too, hip?
-Ding
Yes, I'm getting this error
And all the other characteristics mentioned on this thread -- the modules are on, the permissions are right, etc.
And this error too.
I'm Fixed!
I just upgraded to 4.7.2 and my search works. I didn't have to rebuild the index or anything. Just... bam! There it was.
Strange, though. I run Drupal for a personal site on a different host, and the search there has worked all along.
Oh well. I'm happy. I'd like to hear if 4.7.2 fixes others' problems as well.
-Ding
Same problem with 4.7.2
Hi Ding,
I'm suffering this issue also. Drupal says that a 0% of the site is indexed. I wiped the search_* tables, upgraded to the 4.7.2 release, and force reindex (by clicking on the corresponding button) and cron (by visiting cron.php on the browser). But it is still at 0%, and the search don't work. In fact, the search tables are filled with some data, but not all the data. I checked it with some words, from the drupal interface and from the mysql client, and I can conclude that some words are not added to the database.
It seems that a lot of people has similar issues, so probably the search module is broken at least partially.
Any new idea?
I can't say what going wrong...
I can't say what going wrong in your case... But I make some changes in search.module (4.6) for multibyte string support...
in line 400
//$word = strtolower($word);$word = mb_strtolower($word,'utf8');
in line 500
//$arguments[] = strtolower($word);$arguments[] = mb_strtolower($word,'utf8');
Of course you must enable mb_string extension in your php configuration.
Possibly source of problem
Possibly source of problem is the same I had - You can look at my posts http://drupal.org/node/64857 and http://drupal.org/node/64333 . Post contains patch which helped in my case (for version 4.7.0)
Sincerely
Maris
Me too, I'm done!
Hi,
I've already solved my problem.
I believe it came from moving the Drupal installation from one server to another one. I can't get a closer view of it. I've then given it some time (as time helps to settle things down) and retaken my issue. What I did:
-I've installed poorman's cron (accessing directly through the URL drop a 'Server error', because I'm on a shitty host - see above)
-I changed indexing options from words with aminimum of 3 characters to 4
-I visited some page of mine (at my Drupal installation) in order for poorman's cron to start doing its job
-indexing started!!! (and appeared, as it should, in the index DB table)
-I changed it back to 3 characters (for is what I want)
-I visited again pages for poorman's cron to work again
-after a while (and some visits) 100% indexed for real now
Thanx for all your posts/ help. Have a good day!
hip
I have the problem that I
I have the problem that I get a 500 script error on the server when I run cron. But only when search is activated. The weird thing is that the cron runs until the index is on 18 -20 %, then I get this server script error, like you get it when a script takes too long to run. But this comes right when I press return.
Is there a change to debug run the cron and see what will cause this error.
I installed a backup of this site on my local wamp server and the search runs, I get at least 99%.
---
Join the virtual march to stop global warming.
http://www.stopglobalwarming.org/marchers/?142067
I'm having a somewhat
I'm having a somewhat similar problem. I've set up a drupal site with 4.6.9., cron.php seems to be working fine - the logs tell me that that cron job was successfully completed. I've taken a look at the search_index table on the database, and it's filled with indexes. However, everytime I try to do a search, I never get any results back. I was having a problem with cron before but after following this quick fix: http://drupal.org/node/12857#comment-68981 i had no problems. would this be related to the current problem i am having?
I've got php 4.3.2-26 and mysql 3.23.58-2.3. Anyone have any suggestions?