Hi, I'm migrating an older htDig implementation (Solaris-based) to 3.2.0b6 on Linux.
I have multiple digs the run, creating multiple search dbs. On each page
of our site, there will be a search box which will search all collections
(by default). There will also be an "advanced" search which will allow
the user to search 1 or more of the collections.
The problem I'm experiencing has to do with searching with mulitple
configs. If use the default search page and only reference a single
config, the results URLs returned are correct. If, however, I have
multiple configs on the search form to search multiple collections, the
results returned by htsearch are mangled. The URLs actually are not
valid.
I've looked at the db.docs file after running htdig, and the URLs appear
fine there.
Here's my example search form referencing only 1 config:
<table cellpadding="0" cellspacing="0" border="0" width="900">
<tr>
<td width=100% align="left" valign="top" style="padding-top:15px;">
<form method="get" action="/cgi-bin/bin/htsearch.cgi">
<input type="text" size="30" name="words">
<input type="hidden" name="restrict" value="">
<input type="hidden" name="format" value="long">
<input type="hidden" name="sort" value="revtitle">
<input type="hidden" name="protected_icon" value="false">
<input type="hidden" name="pdf_icon" value="false">
<input type="hidden" name="narrowsearch" value="0">
<!--<input type="hidden" name="config"
value="htdig-documentation">-->
<input type="hidden" name="config" value="htdig-eco-90">
<!--<input type="hidden" name="config" value="htdig-eco-eB">
<input type="hidden" name="config" value="htdig-eco-eB2">
<input type="hidden" name="config" value="htdig-eco-eB21">
<input type="hidden" name="config" value="htdig-catchall">-->
<input type="submit" value="Search All Content">
</form>
</td>
</tr>
</table>
And, when I search using this form....the results returned are good:
QAD | ServiceLinQ | ECO | New ECO List
... M190 M192 M196 M197 M198 M199 M19B M19C M19D M19F M19G M19H M19J M19K
M19P M19Q M19V M19X M19Y M19Z M1B1 M1B2 M1B3 M1B5 ...
http://support-dev2.qad.com/software_update_information/eco/90SP5/eco/new.html
06/27/07, 38873 bytes
QAD | ServiceLinQ | ECO | M19J
... | Compile List | Menus ECOs Modified Files Previous ECO M19H
Next ECO M19K ECO Number: M19J ECO Date: 07/30/01 ECO Release ...
http://support-dev2.qad.com/software_update_information/eco/90SP4/eco/m19j.html
06/27/07, 24812 bytes
QAD | ServiceLinQ | ECO | M19J
... | Compile List | Menus ECOs Modified Files Previous ECO M19H
Next ECO M19K ECO Number: M19J ECO Date: 07/30/01 ECO Release ...
http://support-dev2.qad.com/software_update_information/eco/90SP7/eco/m19j.html
06/27/07, 36130 bytes
However, if I uncomment the 'htdig-eco-eB' config in the search form
(allowing search to search mulitple collections), I get the following:
QAD | ServiceLinQ | ECO | New ECO List
... M146 M14L M14M M15H M15N M164 M169 M181 M18W M199 M19B M19H M19J M19Y
M19Z M1B5 M1B7 M1B8 M1BW M1BZ M1C2 M1C3 M1C4 M1C6 ...
http://support-dev2.qad.com/software_update_information/eco/90SP6/eco/new
06/21/07, 45967 bytes
QAD | ServiceLinQ | ECO | New ECO List
... M190 M192 M196 M197 M198 M199 M19B M19C M19D M19F M19G M19H M19J M19K
M19P M19Q M19V M19X M19Y M19Z M1B1 M1B2 M1B3 M1B5 ...
http://support-dev2.qad.com/software_update_information/eco/90SP5/eco/new.html
06/27/07, 38873 bytes
QAD | ServiceLinQ | ECO | M19J
... | Compile List | Menus ECOs Modified Files Previous ECO M19H
Next ECO M19K ECO Number: M19J ECO Date: 07/30/01 ECO Release ...
http://support-dev2.qad.com/software_update_information/eco/90SP7/eco/m19j
06/21/07, 24283 bytes
QAD | ServiceLinQ | ECO | M19J
... | Compile List | Menus ECOs Modified Files Previous ECO M19H
Next ECO M19K ECO Number: M19J ECO Date: 07/30/01 ECO Release ...
http://support-dev2.qad.com.shtml/m19j 06/21/07, 46704 bytes
QAD | ServiceLinQ | ECO | M19J
... | Compile List | Menus ECOs Modified Files Previous ECO M19H
Next ECO M19K ECO Number: M19J ECO Date: 07/30/01 ECO Release ...
http://support-dev2.qad.com/m19j 06/21/07, 51726 bytes
Notice the weird characters and lack of reference to any HTML docs in the
URLs? I suspect it's something simple I'm overlooking (at least that's
my hope).
BTW, all the collections are built....the databases exist and are
correctly referenced in the config files....and I can successfully search
any individual collection without problem.
Appreciate any thoughts/suggestions the list might have.
Thanks,
Bruce<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
<<image/gif>>
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ 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

