Manuel Lemos - 2005-02-01 07:57:48 - In reply to message 1 from Mario Bittencourt
Basically you need to start telling class to create a new Ht:/Dig configuration file to index the site you want. Take a look at the htdig_setup_configuration.php script for an example of how to do that.
Then you need to tell the class to call htdig to index your site. This is something that you probably will do once a day if your site is updated every day. Take a look at the htdig_build_databases.php for an example of how to setup htdig to crawl your site.
Once your site is indexed, you can start using the class to provide an interface to search your site pages. Take a look at the htdig_search.php script for an example site search page.
Jens Potthast - 2005-02-04 18:29:09 - In reply to message 2 from Manuel Lemos
I might have been running into the same problem.
"Digging" seemes to be ok, but htdig_search.php allways returns a "Sorry no pages were found." message.
After searching for possible configuration errors near the database part - since I use de_DE locale - with no success, I inserted a "var_dump($output)" in line 86 of htdig_search.php.
It showed that my searches gave back many hits (though almost not to recognize being var_dumped), but still a "Sorry no pages were found." at the bottom of the page (of course).
$first and $last are both int(0).
Maybe in htdig-3.2.0b6 the way resulte are returned changed.
I'll be able to make some more tests soon.
Manuel Lemos - 2005-02-05 23:11:15 - In reply to message 3 from Jens Potthast
If you have generated the HT:/Dig configuration on the example htdig_setup_configuration.php script, make sure you have adjusted the options start_url, limit_urls, exclude_urls according to your own site URLs and patterns of the pages that you want to crawl.
Manuel Lemos - 2005-02-08 06:47:35 - In reply to message 5 from Mario Bittencourt
That is because the class requires that htsearch command returns the results formatted with a certain patterns, so it can parse the results and extract the relevant information. Therefore the htsearch program needs to use the supplied template files.
When you use a custom configuration file, it uses the default result pages template files, and so the class is not able to parse the result data that the htsearch program and it fails.
Anyway, you are right. This class needs better documentation. Therefore, I have just uploaded a README file. Thank you for the suggestion.
miggy - 2006-07-27 22:21:23 - In reply to message 9 from Manuel Lemos
But it is already in the correct path...
i have htsearch in /usr/local/htdig/bin/htsearch
so i putted the path in php file so: