According to Jim Cole: > Aviram Carmi's bits of Tue, 15 Oct 2002 translated to: > >I am new to HtDig. HtDig was installed with Red Hat 7.3 and seems to > >execute just fine. > > > >I just created a new config file and I am currently testing it. > > > >the search form is at http://www.knx1070.com/search.html > > > >the config file is at http://www.knx1070.com/htdigknx.config.txt > > > >I have several problems with finding the "appropriate" pages. > > > >For example, searching for "drama hour" does not bring up the > >"drama.html" page, even though the phrase "knx drama hour" is all > >over the page (title/H1/alt/keywords/description/links to the page > >from other pages) > > I am not familiar with how Red Hat sets things up, but something > seems to be wrong with your current setup. The result page doesn't > include either the header or footer. If the footer was present, you > would most likely have links to additional result pages that would > include the page you are looking for. Try doing a search on the > ht://Dig site and notice the information/search boxes at the top of > the page and the result page links at the bottom. There are the > header and footer sections that I am referring to. > > Did you at some point try to customize your result templates?
Or even if you didn't customize them, are you soure you installed them where you told ht://Dig they'd be when you configured prior to compiling? Are they readeable by everyone? Are the directories leading up to them executable by everyone? This is a classic symptom of htsearch (as run by the user ID under which the web server runs) being unable to read the header and footer files from your "common" directory. > >similarly, searching for "zabba" brings up pages with WSB, Sub, > >seebee, sabe, before bringing up the page with "zabba"...??? > > I would work on fixing the header/footer issue first. A default > header will give you additional information about what terms are > actually being searched on. That might provide a clue as to the > other problems you are encountering. It might be that htdig is > not even using the config file that you customized. Are you > passing the name of your custom config file to rundig (or htdig) > using the -c options? This behaviour doesn't jive with the config file you posted a day or two ago. In there, you had "exact" as the only algorithm defined in search_algorithm. But the behaviour above suggests you've got the soundex or metaphone fuzzy matching enabled. How are you specifying the config file in your search form? Which config file is htsearch actually using, and what is search_algorithm set to in there? See http://www.htdig.org/FAQ.html#q4.2 and http://www.htdig.org/FAQ.html#q5.30 -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
