Re: [htdig] Help! New htdig user...

[Ted Stresen-R. <ted...@ma...>]

Just out of curiosity, what was the search engine Verio was supporting? 
I would like to know why they dropped whatever they had and picked up 
htdig.

Ted Stresen-Reuter

On Monday, May 12, 2003, at 08:14  PM, bob williams wrote:

> My hosting service, Verio, has just recommended using htdig (which 
> they now
> make available on their site) as a search program to replace another 
> one
> they are no longer supporting. I have installed it and have spent 
> several
> hours trying to modify it using the htdig.org documentation but am 
> baffled
> by a couple of things:
>
> 1. When I try to modify the .conf file, using standard ASCII text 
> editors
> (have tried several different ones), and then upload the file I get the
> error below (Note: I get this error even if I don't change a single
> character in the file, just load it and save in back in varioys text 
> formats
> - I did this trying to troubleshoot) so it is not a modification I am 
> making
> that causes the error):
>
> ----------------------
> ht://Dig error
> htsearch detected an error. Please report this to the webmaster of this
> site. The error message is:
> Unable to read word database file
> Did you run htmerge?
> ----------------------
>
> After trying MANY different formats to save the file in, the ONLY one 
> that
> seems to not give the above error is MicroSoft Word with "MS-DOS Text"
> format ("Text Only", "ASCII Text", etc. does not work and gives the 
> above
> error). The problem is NOT with the Web Software upload format, 
> because I
> can take the same file and save it in that "MS-DOS Text" format and it 
> will
> at least do the search in the default results form, but if I make 
> changes to
> the .conf file, they still don't work right.
>
> Question 1: Why won't a standard ASCII Text word processor work for
> modifying the .conf file?
>
> 2. No matter what I have tried, I can't get the short.html modified 
> form to
> work or be recognized...I CAN get my modified  long.html form to work 
> (and
> modified header and footer also do work)...but for some reason, 
> short.html
> just doesn't work...when short is selected, the long form displays. I
> suspect that for some reason multiple attribute/value specifications
> seperated by the \ symbol are not working. The code used is the 
> standard
> code provided in htdig .conf file. In troubleshooting, I  removed the
> comment # characters as documented, and the long.html form works, but 
> the
> short.html doesn't work, so other than removing the comment 
> characters, I
> haven't changed anything and it doesn't work. I have tried changing the
> ${common_dir} to the exact address, etc, but I figure it must be right 
> if
> the long.html form works...
>
> -------------------------
> # The following are the templates used in the builtin search results
> # The default is to use compiled versions of these files, which 
> produces
> # slightly faster results. However, uncommenting these lines makes it
> # very easy to change the format of search results.
> # See <http://www.htdig.org/hts_templates.html> for more details.
> #
>  template_map: Long long ${common_dir}/long.html \
>         Short short ${common_dir}/short.html
>  template_name: long
>
> #
> -------------------------
>
> Question 2: What am I doing wrong? I have also removed/added spaces, 
> tabs,
> etc. and tried numerous combinations concerning the template_map 
> attribute,
> but with no success...
>
> Thanks in advance...
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise 
> solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> htdig-general mailing list <htd...@li...>
> To unsubscribe, send a message to 
> <htd...@li...> with a subject of 
> unsubscribe
> FAQ: http://htdig.sourceforge.net/FAQ.html
>
>
"How wonderful the world would be without Saddam and without Bush!"