> > They can be, but you need to change your result template to make use > > of the new template variables that allow_in_form will define for you. > > You can pass these on as input text fields or hidden input fields if you > > want, in the followup search forms. However, if you want htsearch to > > build new select lists that use the current value as default, it gets a > > bit more hairy. See http://www.htdig.org/attrs.html#build_select_lists > > and http://www.htdig.org/hts_selectors.html > > > I've added the lines > > build_select_lists: SEARCHALGORITHM_LIST,multiple search_algorithm stringtyp e > 2 > 1 2 > > stringtype: "exact:1 synonyms:0.5 endings:0.1" words "substring:0.5" strings > > > to a conf form. Is that a correct format for defining a new select list to > permit the user to choose whether to match whole words or strings on each > successive search operation? > > If it is, how do I actually call the select list from htsearch? Should there > be a reference in header.html? If so, should the same reference take the pla ce > of the lines I have in the cited message above in the search form for the > initial search? > > I have found that header.html and footer.html are read for each search but > wrapper.html which is intended to subsume the function of header and footer > isn't read. Why not? Is that not the default?
Now I have Whole words or strings: <SELECT NAME="search_algorithm"> <OPTION VALUE="exact:1 synonyms:0.5 endings:0.1" SELECTED>words <OPTION VALUE="substring:0.5">strings </SELECT> in the search form and header.html and build_select_lists: SEARCHALGORITHM_LIST,multiple search_algorithm stringtype 2 1 2 "" "" stringtype: "exact:1 synonyms:0.5 endings:0.1" words "substring:0.5" strings in the conf form. That gives a choice of whole-word or string search on the initial search and searches which are part of a series of successful searches going back to the initial search. If the search is not successful, then this doesn't work because the nomatch.html and syntax.html files don't have those lines from the search form and header.html. Of course I could add them but isn't there some way of applying them to all search operations? Also, even when htsearch brings up the choice of whole-word or string search, the default is "words" even if the previous search was for "strings". I tried adding the line <input type="hidden" name="search_algorithm" value="$&(search_algorithm)"> to header.html before the option selection lines but the effect of that wasn't to change the default from "words" to whatever the previous selection was but rather to prevent string searches from working at all and to prevent searches for whole words from working unless "strings" had been selected, i.e. "strings" permitted whole-word searching and "words" permitted no searching. Any ideas? TIA. Douglas ======== Douglas Kline [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
