Re: [mv] All in one question.

[Dan Busarow <dan@dpcsys.com>]

On Tue, 4 Jan 2000, Marty Vance wrote:
> Thanks for the info Dan.  However, your example won't work for me because x is set by the form
> on the client side as mv_searchspec.  Any other ideas?

Here's an old post from the list covering this.

Dan
-- 
 Dan Busarow                                                  949 443 4172
 Dana Point Communications, Inc.                            dan@dpcsys.com
 Dana Point, California  83 09 EF 59 E0 11 89 B4   8D 09 DB FD E1 DD 0C 82


Date: Sat, 30 Jan 1999 16:55:57 +0100
To: "Gideon van Gelder" <gideon@swingmaster.nl>
From: Frank Miedreich <miedreich@acm.org>
Subject: Remembering mv_searchspec (Was: Re: Thanks a lot!)
Cc: minivend-users@minivend.com

******    message to minivend-users from Frank Miedreich <miedreich@acm.org>     ******

Hi Gideon,

I am sending question and answer to the list, as other people might find
this useful.

>Dear Frank,
>
>Thanks a lot for helping me out with the small, but annoying problem with
>the [more-list].
>You seem to be quite an expert, so I was wondering if you could help me out
>one last time.
>As a header, for my search-result page I use this:
>
>[if value mv_search_match_count > 0]
> Search results for [value mv_searchspec][/if]
> [no-match]
> No Match Found
> [/no-match]
>
>This works fine, as long as there is only one page with results. As soon as
>you go to a next-page, the header says: "Search results for". Minivend
>leaves out the search-specification value.
>
>Is there any way to solve this ?
>
>Thanks again,
>
>-Gideon

Sure.

Put the following stuff on your searchpage:

[set search values]
[value name="searchterm" set="[value mv_searchspec]"]
[/set]

and include:

<INPUT TYPE="hidden" NAME="mv_check" VALUE="search values">

in your search definition.

this will allow you to display [value searchterm] on all subsequent result
pages.

As an added extra you get the option to let users edit their searchterm on
subsequent searches by setting mv_searchspec with:

<INPUT TYPE="Text" NAME="mv_searchspec" VALUE="[value searchterm]">

This way they can conveniently correct a search when they dicover a simple
typo.


A second solution is setting a scratch var or value on the result page, if
mv_searchspec is not empty. Display that variable. Same effect.


Greetings, Frank


--
Dual rounds of ROT-13 encryption discontinued. Somebody was able to crack this.
Frank Miedreich
Max-Planck-Institut fuer psychologische Forschung