According to Richard Kraus: > Thanks for your comments. I apologize for latching on to you but my > programmer left and I'm afraid I don't understand any of this. > > By 'footer', I meant the bottom links (About | Multimedia | Galleries etc.) > This appears in the wrapper file and the results should appear above this. > Looking at my wrapper file, it does contain the $(HTSEARCH_RESULTS) variable > above these links. As you saw, the results appear below them. > What you would call the footer is contained in my footer.html file > ($(PAGEHEADER) $(PREVPAGE) $(PAGELIST) $(NEXTPAGE) ) > > In regards to your comment about the wrapper file. My Search folder > contains the following files: > footer.html > header.html > index.html > long.html > nomatch.html > pop_search.htm > short.html > syntax.html > wrapper.htnl. > > Are you saying that I don't need the header and footer? That the wrapper > would replace this? Perhaps having all these files is confusing the > situation.
Yes, I aggree that it gets confusing with all these files. What's more confusing is the fact that the wrapper file concept was added later, and the separate header and footer files were kept for backwards compatibility. By default, htsearch uses the separate header and footer files, and leaves search_results_wrapper undefined, so the wrapper.html file is unused. If you want to use a single wrapper file in place of the separate header and footer files, you must correctly define the search_results_wrapper attribute to point to a wrapper file with the $(HTSEARCH_RESULTS) string in it, and then this wrapper file will override the separate header and footer. If the wrapper file isn't set up just right, htsearch tends to fall back onto the separate header and footer files defined by the search_results_header and search_results_footer attributes. So, first of all you must make sure you do this, or else you must correctly set up the header and footer files. If you use a wrapper file, it should contain the ($(PAGEHEADER) $(PREVPAGE) $(PAGELIST) $(NEXTPAGE) ) part in the right spot, after the $(HTSEARCH_RESULTS) string. Based on the behaviour you're describing, though, it almost sounds to me like your so-called "wrapper" file is really being used as a header file by htsearch, i.e. that search_results_header is set to refer to the file that you believe is your wrapper file. Is it possible that this is your problem? > According to Richard Kraus: > >> I've got this search facility almost going: > >> http://www.peoplesvoice.gov.au/search/index.html. > >> > >> (Look up someplace like Sydney or Melbourne). > >> > >> However, the results are appearing under the footer and not in the middle as > >> it should. Any suggestions would be appreciated. > > > > Well, the page button do appear at the bottom, so I'm not too certain what > > it is you consider the footer. However, the header does seem to contain > > </BODY> and </HTML> tags before the search results come out, so there's > > obviously a bit of a problem in how the HTML is put together. > > > > Essentially, by default the search results are composed of: > > > > header.html > > several iterations of builtin-long or builtin-short templates > > footer.html > > > > So, if you edit header.html or footer.html with an HTML editor, you have > > to be careful that it doesn't put in tags that would invalidate the full > > HTML produced by the concatenation of all templates. This is actually > > the reason the search_results_wrapper attribute as added as a way of > > overriding the header and footer with a single wrapper file. > > > > See http://www.htdig.org/attrs.html#search_results_wrapper -- 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 _______________________________________________ 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
