Re: Question re: select fields

Andreas, thanks so much for your response; it seemed promising!
but I can't see the ^M when I view either my conf or my search.html
file. Though I do create both files on a Windows machine, I use
vi for the conf file, and I checked both files through vi on the Linux
box where I am running the search. Possibly the one you are seeing is
an artifact of the copy/paste I did for the e-mail?

Any additional suggestions on how to see that ^M or other fixes for
this problem?

Hi Kyle,

On Fri, Sep 14, 2007 at 03:32:17PM -0500, Kyle Dallaire wrote:
>
> version_names: "Version6_0|Version7_0|Version7_1|Version7_2"; "Version
> 7.5" ^M
^^
> "Version6_0|Version7_0|Version7_1|Version7_5"; "Version
> 7.2"
> "Version6_0|Version7_0|Version7_2|Version7_5"; "Version
> 7.1"
> "Version6_0|Version7_1|Version7_2|Version7_5"; "Version 7"
>
> "Version7_0|Version7_1|Version7_2|Version7_5"; "Version 6"

Try it without the ^M after the in the first line

Regards,
Andreas
--
! Andreas Jobs Network Operating Center !
! Ruhr-Universitaet Bochum !
! The only way to clean a compromised system is to flatten and rebuild. !

_____________________________________________
From:   Kyle Dallaire 
Sent: ;  Friday, September 14, 2007 4:32 PM
To:     htdig-generallists.sourceforge.net
Subject:      ;  Question re: select fields

I have a very stable htDig 3.1.6 setup I have been using for three or four
years that is suddenly giving me fits.

I use the search for a software documentation website which includes
documentation for multiple versions of the software; each version of
the software includes several different books.

My search.html form has two custom select fields: one which allows users
to select which version of the documents to search, and one which allows
them to choose to search among all documents of that version, or a
specific document.

Here are the definitions from my search.html file:

Version: <select name=";exclude&quot;>
<option value=&quot;Version6_0|Version7_0|Version7_1|Version7_2">Version 7.5
<option value=&quot;Version6_0|Version7_0|Version7_1|Version7_5">Version 7.2
<option value=&quot;Version6_0|Version7_0|Version7_2|Version7_5">Version 7.1
<option value=&quot;Version6_0|Version7_1|Version7_2|Version7_5">Version 7
<option value=&quot;Version7_0|Version7_1|Version7_2|Version7_5">Version 6
</select>

Book: <select name=";restrict&quot;>
<option value=&quot;">;All
<option value=&quot;DevGuide&quot;>Developers' Guide
<option value=&quot;APM_IDE&quot;>The APM Development Environment
<option value=&quot;ACE">Application Configuration
<option value=&quot;BPM">Business Process Design and Implementation
<option value=&quot;CRM">Business Process Design and Impl for CRM
<option value=&quot;CLIENT&quot;>Business Process Design and Impl for CRM Client Procs
<option value=&quot;DATA";>Data Management
<option value=&quot;DMT">Using the Data Mapping Tool
<option value=&quot;Proxy&quot;>Proxies
<option value=&quot;API">API Javadoc
</select>

I've also defined the 'exclude' and 'restrict' attributes in my conf file:

build_select_lists: EXCLUDE,select exclude version_names 2 1 2 exclude "&quot;
 &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp; RESTRICT,select restrict book_names 2 1 2 restrict "&quot;

version_names: "Version6_0|Version7_0|Version7_1|Version7_2"; "Version 7.5"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp;  "Version6_0|Version7_0|Version7_1|Version7_5"; "Version 7.2"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp;  "Version6_0|Version7_0|Version7_2|Version7_5"; "Version 7.1"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp;  "Version6_0|Version7_1|Version7_2|Version7_5"; "Version 7"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp;  "Version7_0|Version7_1|Version7_2|Version7_5"; "Version 6"

book_names: "&quot; "All&quot;
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "DevGuide" "Developers' Guide";
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "APM_IDE" "The APM Development Environment"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "ACE&quot; "Application Configuration"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "BPM&quot; "Business Process Design and Implementation"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "CRM&quot; "Business Process Design and Impl for CRM"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "CLIENT" "Business Process Design and Impl for CRM Client Procs";
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "DATA" "Data Management"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "DMT&quot; "Using the Data Mapping Tool"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "Proxy" "Proxies"
 &nbsp; &nbsp; &nbsp; &nbsp;   ; "API&quot; "API Javadoc&quot;

This has worked just fine until today, when tried to add another release
version to the site. This means an additional Version field option:

<option value=&quot;Version6_0|Version7_0|Version7_1|Version7_2">Version 7.5

an additional exclude value for each existing option (so each now has four
patterns to exclude instead of three),

and a new document:

<option value=&quot;CLIENT&quot;>Business Process Design and Impl for CRM Client Procs

Everything displays and appears to function just fine in the search.html file, but
the Version field does not display properly in the search results pages. Mostly,
instead of a select field, just the *definition* of the last-selected version is
displayed, as text:

Version: Version6_0|Version7_0|Version7_1|Version7_2

If I continue on from there, the definition disappears and the field name remains,
but no selection box.  The initial search seems to return the correct set of urls,
but searches from the mangled results pages seem to include all versions instead
of just one.

If I run a search on all documents, this happens every time. If a run a search on
a single document, sometimes the first results page displays a select field with
the appropriate (last-selected) value shown, but there's only one additional option,
and it consists of garbage characters.

My first thought -- since these restrict and exclude lists have been growing steadily
-- is that I have reached some kind of string length limitation, but I am not a
programmer so this is just a wild guess. BTW, the book selection field is just fine; it's
just the Version one that is messed up.

I know this list is pretty quiet these days, but if anyone can point me in the right
direction, I'd be very grateful!

Kyle Dallaire