SearchProfile
List files containing order and form profile definitions.
Synopsis
|
SearchProfile filename [filenames...]
|
The parameter is expected to be a list of filenames.
The default is blank.
Scope
This directive is only available for use in the local
(catalog.cfg) configuration file.
It will not affect any other website in any way.
This directive will not work in the global
(interchange.cfg) configuration file.
Description
This directive allows an unlimited number of search profiles
to be set up,
specifying complex searches based on a single click.
checkout process.
Files must be relative to the website's home directory, as specified
with the global Catalog directive.
As an added measure of control, the specification is evaluated with
the Interchange tag syntax to provide conditional setting of search
parameters.
The search profile is named by placing a name after a __NAME__ token,
in one of the listed profile files.
Multiple profiles can reside in the same file, if separated by __END__
tokens.
Example
Specifying a dictionary-based search in a "dict_product" table
__NAME__ dict_search
mv_search_file=dict_product
mv_return_fields=1
[if value fast_search]
mv_dict_limit=-1
mv_last=1
[/if]
__END__
|
The above search profile may be called,
from a HTML <form>, as follows:
|
<input type="hidden" NAME="mv_profile" VALUE="dict_search">
|
It may also be called, using a link, as follows:
|
<a href="[area scan se=Renaissance/mp=dict_search]">Renaissance Art</a>
|
See also
