Re: [mv] 2 results pages... (mv 3.14) - solved

[". c . o . r . y . t . r . e . s . e" <digital@frognet.net>]

******    message to minivend-users from ". c . o . r . y .  t . r . e . s . e" <digital@frognet.net>     ******


> Also I discovered strange thing:
> this code
> [if value mv_searchspec > 0]
>   [value name="search_string" set="[value mv_searchspec]"]
> [/if]
> 
> prints mv_searchspec to HTML code when the condition is true. But why?

that is caused by the  
[value name="search_string" set="[value mv_searchspec]"]
tag, and is, believe me, desired behavior.  The set positional argument is used
to extend the [value] tag to allow you to both set and display the variable. 
This can be very useful in one-time tag uses (ie, writting to a database;
setting the write time in an [import] construct AND saving the value for
logging or evaluation purposes (or perhaps a set of second database writes,
etc.)


I offer two "solutions" / simple tricks here:


<!-- [if value mv_searchspec > 0]
[value name="search_string" set="[value mv_searchspec]"]
[/if] -->

This simply places the results in a html comment.  I do this with [export]
tags, which sometimes write out data (like a "1" ;)

--Or--


[if value mv_searchspec > 0]
  [set name="search_string"][value mv_searchspec][/set]
[/if]

<A HREF=[area href=scan
arg="
sp=brief
sf=category
ml=50
tf=code
st=sql
se=[scratch search_string]
" ]>
Brief </A>


which eliminates the use of a value tag and sets a scratch variable instead,
producing no output, but requiring a change to the first [area form="...
construct.

Thanks,

cory trese
digital@{specialty-books.com, frognet.net};
W: 800 466 1365 ext223]
H: 740 592 4493
-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list