#92 Problem with "result" page links

cannot reproduce
closed-works-for-me
htsearch (60)
5
2002-01-03
2001-12-10
norman porter
No

I'm using version 3.1.5 that I downloaded from my ISP
Mindspring.

The engine works great, but when I try to go from page
1 of the results to page 2 0r 3, I get the URL:

http://www.restaurantsolutionsinc.com/cgi-bin/htsearch?
restrict=;exclude=;config=htdig;method=or;format=builti
n-long;sort=score;words=sinks%20stoves%
20continental;page=2

and no error message.

When I try to go back in the result pages, from 3 to 1
or 3 to 2, I get the URL:

http://www.restaurantsolutionsinc.com/cgi-bin/htsearch?
restrict=;exclude=;config=uXXX%2FwfpXXXXX%2Fhtdig%
2Fconf%2Fhtdig;method=or;format=builtin-
long;sort=score;words=sinks%20stoves%
20continental;page=1
(I changed the entries to the X"s)

And I get the error message:

Unable to read configuration
file '/web/uXXX/wfpXXXXX/htdig/conf/uXXX/wfpXXXXX/htdig
/conf/htdig.conf'

Its there!

Please help. Ive tried all I can to get it to work.
Please leave my e-mail address visible. Its
webmaster@restaurantsolutionsinc.com

Thank you.............Norman

Discussion

1 2 > >> (Page 1 of 2)
  • Logged In: YES
    user_id=149687

    I can't think of anything in the standard htsearch code that
    would explain the corruption of the config input parameter
    as you report. Is it possible that your /cgi-bin/htsearch is
    really a wrapper script that processes the input parameters
    before passing them to the real htsearch? If so, you should
    take a look at that wrapper script for the source of the
    problem.

    I tried a few searches on your site, but nothing seems to
    produce page buttons at this time.

     
    • summary: Problem with "result" page links --> Problem with "result" page links
    • milestone: --> cannot reproduce
    • status: open --> pending-works-for-me
     
  • norman porter
    norman porter
    2001-12-11

    • summary: Problem with "result" page links --> Problem with "result" page links
    • status: pending-works-for-me --> open-works-for-me
     
  • norman porter
    norman porter
    2001-12-11

    Logged In: YES
    user_id=398370

    thanks for responding. You won't see buttons because my
    footer page has them edited out and I set the number of
    matchs to 300 in the htdig.conf

    I've added no wrapper script. I wouldn't know how.

    When I have the regular footer.html, the buttons work fine
    going up from page to page, but not comig down from page to
    page.

    Any ideas?

     
    • assigned_to: nobody --> grdetil
    • summary: Problem with "result" page links --> Problem with "result" page links
     
  • Logged In: YES
    user_id=149687

    You may not have set up a wrapper script, but what about
    Mindspring? The standard 3.1.5 version of htsearch doesn't
    distinguish between page buttons that go up to a higher page
    and those that go down to a lower page. It generates the
    same URL for all page buttons, with only the page number
    that changes from button to button. The config input
    parameter is always passed along unchanged in all of these
    page button links. The behaviour you describe can't occur
    with the standard 3.1.5 code, so Mindspring must have either
    altered the code or used a wrapper script to somehow modify
    the behaviour.

     
  • norman porter
    norman porter
    2001-12-11

    • summary: Problem with "result" page links --> Problem with "result" page links
     
  • norman porter
    norman porter
    2001-12-11

    Logged In: YES
    user_id=398370

    I put the buttons back in if you have time to go back and
    look. When you put the cursor above page2 its correct and
    will give you page two. When you put the cursor above page
    1 to go back, you'll get the full url to htdig.conf that
    causes the error message instead of displaying the page.

     
    • summary: Problem with "result" page links --> Problem with "result" page links
     
  • Logged In: YES
    user_id=149687

    OK, I tried a few things out on your site. It doesn't really
    matter whether you select a higher page or a lower page,
    though. What seems to matter is the level of nesting. If you
    go from the first page to page 2, and from there to page 3,
    you still get the error. The problem is that whenever
    there's a "page=" in the query string, the "config=" value
    gets messed up. I've tried a number of other query string
    variations to confirm this. I've also noticed that if you
    omit the "config=htdig" in your query string, it gets added
    in to the query string for the page buttons. The standard
    3.1.5 code doesn't do either of these things, so it must be
    a modification or wrapper that Mindspring developed. Please
    contact their tech support about this, as there's nothing we
    can do about it.

     
1 2 > >> (Page 1 of 2)