When you send a form to Minivend, it reads the values and places them in the user session. The following form:
<FORM ACTION="[area index]" METHOD=POST> <INPUT TYPE=hidden NAME=mv_action VALUE=return> <INPUT TYPE=hidden NAME=foo VALUE=bar> <INPUT TYPE=submit NAME="Make foo=bar"> </FORM>
will make the [value foo]
tag equal to bar
on the next page then send you to the page index(.html). Same for this link:
<A HREF="[area href=index form=' foo=bar mv_action=return ']">Make foo=bar</A>
[value varname]
The [value ...]
MML tag expands into the current value of the
customer/form input field named by field. If the set
value is present, the form variable value will be set to it and the new value returned. Use this to ``uncheck'' a checkbox or set other form variable values to defaults. If
HIDE is set, the value will be set but not returned to the page.
The filter="filter1 filter1"
parameter applies any of the standard MiniVend filter types to the value.
See Filters.
When the value is returned, any MiniVend tags present in the value will be escaped. This prevents users from entering MiniVend tags in form values, which could be a serious security risk.