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">
<option value="Version6_0|Version7_0|Version7_1|Version7_2">Version 7.5
<option value="Version6_0|Version7_0|Version7_1|Version7_5">Version 7.2
<option value="Version6_0|Version7_0|Version7_2|Version7_5">Version 7.1
<option value="Version6_0|Version7_1|Version7_2|Version7_5">Version 7
<option value="Version7_0|Version7_1|Version7_2|Version7_5">Version 6
</select>
Book: <select name="restrict">
<option value="">All
<option value="DevGuide">Developers' Guide
<option value="APM_IDE">The APM Development Environment
<option value="ACE">Application Configuration
<option value="BPM">Business Process Design and Implementation
<option value="CRM">Business Process Design and Impl for CRM
<option value="CLIENT">Business Process Design and Impl for CRM Client
Procs
<option value="DATA">Data Management
<option value="DMT">Using the Data Mapping Tool
<option value="Proxy">Proxies
<option value="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
"" \
RESTRICT,select restrict book_names 2 1 2 restrict
"" \
version_names: "Version6_0|Version7_0|Version7_1|Version7_2" "Version
7.5" \
"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"
book_names: "" "All" \
"DevGuide" "Developers' Guide" \
"APM_IDE" "The APM Development Environment" \
"ACE" "Application Configuration" \
"BPM" "Business Process Design and Implementation" \
"CRM" "Business Process Design and Impl for CRM" \
"CLIENT" "Business Process Design and Impl for CRM Client
Procs" \
"DATA" "Data Management" \
"DMT" "Using the Data Mapping Tool" \
"Proxy" "Proxies" \
"API" "API Javadoc" \
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="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="CLIENT">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
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
ht://Dig general mailing list: <htdig-general@lists.sourceforge.net>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general
