According to Frank Richter:
> in a search form for htsearch I'm using
> <INPUT TYPE="hidden" NAME="keywords" VALUE="word_has_to_be_in_result">
>
> In the "header" file for the search results page I use:
> <INPUT TYPE="hidden" NAME="keywords" VALUE="$(KEYWORDS)">
>
> Unfortunately $(KEYWORDS) isn't substituted like $(RESTRICT) or so.
> Could this be added?
You're right. This does appear to be an oversight. One of the things I
was hoping to do for the 3.1.2 release was to systematically go over all
input parameters in htsearch to make sure they're handled consistently,
unless there's a good reason for any of them to be handled differently.
Unfortunately, I ran out of time. I'll try to do this for 3.2.
In the meantime, I think you can kludge it up to support this sort of
propagation of the keywords by adding this attribute to your htdig.conf:
allow_in_form: keywords
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
