Super Search 3.x

Legacy documentation for Super Search 3.x.

Super_Search:Form template tag

The Super_Search:Form tag allows you to build a search form. It also handles the parsing and formatting of previously performed search values in the search form fields. By default, the Super_Search:Form tag will always remember the users most recent search, and display that query (if the variables have been placed into the value attribute of the form field(s)).

When used in conjunction with the Super_Search:Save_Search_Form and Super_Search:History tags, your users can save search queries and then view them at a later date. What happens is that the Super_Search:Save_Search_Form tag allows the user to save a search query, which remembers each search term, and then gives the search query a unique ID. The Super_Search:History tag displays those search queries, and lets you link back to the Super_Search:Form form with that unique ID. That unique ID gets passed to the search_id parameter and tells Super Search which search query data the variables should parse out.

Super Search also respects the EE member group search settings (Members -> Member Groups -> Member Group Name). The Access search utility preference needs to be set to Yes for member groups / guests to use Super Search.

{exp:super_search:form return="supersearch/results"}
    content
{/exp:super_search:form}

Parameters

The following parameters are available for use:

form:attribute=

form:class="your_class"

This parameter allows you to control any form attribute for the form in your template. Simply replace attribute with an attribute name such as id, name, class, etc, and specify a value for that attribute. You can specify this parameter multiple times to control as many attributes as necessary. This would normally be done to control your form with Javascript or style it with CSS.

method=

method="get"

If you wish to use GET method for searches, specify this parameter with a value of get. Otherwise, ignore this parameter as the default is POST.

return=

return="template_group/template_name"

This parameter determines where to send users once they have submitted the form. Specify the path to your Super_Searchs/Results page.

search_id=

search_id="{segment_3}"

This parameter is meant for use with the Super_Search:History tag. From that tag, you would link back to the Super_Search:Form page with the unique search query ID. With that ID in the URI and fed to this parameter, this tag will remember the saved search query, and load all of the previous search term values into each search field. If this parameter is empty or omitted, the last search performed by the user is used.

secure_action=

secure_action="yes" 

This parameter allows you to set the action on the form to have https://. Used for securely processing forms with SSL.

secure_return=

secure_return="yes" 

This parameter allows you to set the return on the form to have https://. Used for securely processing forms with SSL.

Variables

All form field names further below on the page can be parsed as variables within the Super_Search:Form tag. All variables are called using the {super_search_ prefix.

Conditionals

Conditionals are available on all variables. Additionally, the following conditional is available for use:

super_search_field_name_VALUE

{if super_search_body_pants} {/if}

Since people can submit search multiple arguments using checkboxes or multi-select fields, we need a way to parse them. When a block of checkboxes are all named as a POST array like this: bedrooms[], you can fetch the submitted values using this special conditional. This syntax applies to custom fields, channels, categories, and statuses.

Parsing this conditional on a custom field that contains multiple values might look something like this:

<input
    type="checkbox"
    name="bedrooms[]"
    value="1"
    {if super_search_bedrooms_1}checked="checked"{/if}/> 1

<input
    type="checkbox"
    name="bedrooms[]"
    value="2"
    {if super_search_bedrooms_2}checked="checked"{/if}/> 2

<input
    type="checkbox"
    name="bedrooms[]"
    value="3"
    {if super_search_bedrooms_3}checked="checked"{/if}/> 3

Or:

<input
    type="checkbox"
    name="food[]"
    value="apple"
    {if super_search_food_apple}checked="checked"{/if} /> Apple
<input
    type="checkbox"
    name="food[]"
    value="strawberry"
    {if super_search_food_strawberry}checked="checked"{/if} /> Strawberry
<input
    type="checkbox"
    name="food[]"
    value="rhubarb"
    {if super_search_food_rhubarb}checked="checked"{/if} /> Rhubarb

For channel searches, it might look something like this:

<select name="channel[]" multiple="multiple">
    <option
        value="articles"
        {if super_search_channel_articles}selected="selected"{/if}>
        Articles
    </option>
    <option
        value="products"
        {if super_search_channel_products}selected="selected"{/if}>
        Products
    </option>
    <option
        value="blog"
        {if super_search_channel_blog}selected="selected"{/if}>
        Blog
    </option>
</select>

For category searches, it might look something like this:

<select name="category[]" multiple="multiple">
    <option
        value="shirts"
        {if super_search_category_shirts}selected="selected"{/if}>
        Shirts
    </option>
    <option
        value="pants"
        {if super_search_category_pants}selected="selected"{/if}>
        Pants
    </option>
    <option
        value="jackets"
        {if super_search_category_jackets}selected="selected"{/if}>
        Jackets
    </option>
</select>

For status searches, it might look something like this:

<select name="status[]" multiple="multiple">
    <option
        value="open"
        {if super_search_status_open}selected="selected"{/if}>
        Open
    </option>
    <option
        value="closed"
        {if super_search_status_closed}selected="selected"{/if}>
        Closed
    </option>
    <option
        value="Pending"
        {if super_search_status_Pending}selected="selected"{/if}>
        Pending
    </option>
</select>

In the event you wish to dynamically generate a list of categories with the Channel:Categories tag for example, and also allow array searching, there is a special template tag needed for this. The tag is: {exp:super_search:variables}, and it must be placed inside the other EE template tag (such as Channel:Categories). Your code might look something like this:

{exp:channel:categories
    style="linear"
    category_group="1"
}
    {exp:super_search:variables}
        <label for="category_{category_url_title}">{category_name}</label>
        <input
            type="checkbox"
            id="category_{category_url_title}"
            name="category[]"
            value="{category_url_title}"
            {if super_search_category_{category_url_title}}
                checked="checked"
            {/if}
        />
    {/exp:super_search:variables}
{/exp:channel:categories}

Form Fields

The following form fields are available for use in your search form and through the URI:

NOTE: only fields marked as searchable in the custom fields' settings in the EE CP can be searched upon. For information about third party add-on support, please visit this page.

author

<input type="text" name="author" value="Bob" />

This field allows your users to search for entries by author. It looks for username by default, unless overridden by the author_indicator parameter in the Results tag. Alternate options are screen name and member ID. Must be exact matches. Screen Name search terms should be wrapped with quotes to make sure screen names with spaces are properly recognized. If you wish to allow partial matches, specify yes in the partial_author parameter in the Results tag. This field cannot override its matching parameter available in the Results tag.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&author=Bob/

category[]

{exp:channel:categories
    style="linear"
    category_group="1"
}
    {exp:super_search:variables}
        <label for="category_{category_url_title}">
            <span>{category_name}</span>
            <input
                type="checkbox"
                id="category_{category_url_title}"
                name="category[]"
                value="{category_url_title}"
                {if super_search_category_{category_url_title}}checked="checked"{/if} />
        </label>
    {/exp:super_search:variables}
{/exp:channel:categories}

This field allows users to search on categories. Default behaviour is searching on category names. To switch this to category ID or URL titles, use the category_indicator parameter in the Results tag. If submitting multiple categories, be sure to name the field category[]. This field cannot override its matching parameter available in the Results tag. The contents of this parameter follow the same syntax as regular Super Search queries in the URI or through POST variables. For example:

  • category="Teeth" would fetch entries that belonged to the category of Teeth.
  • category="Teeth+Gums" would fetch entries that belonged either to the Teeth category or the Gums category.
  • category="Teeth&&Gums" query would fetch entries that belonged both to the Teeth category and the Gums category inclusively.
  • category="-Teeth" would fetch entries that do not belong to the Teeth category.
  • category="-Teeth+-Gums" would fetch entries that do not belong to the Teeth category or the Gums category.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&category=t_shirts+pants/

category-like

<input type="text" name="category-like" value="Pants" />

This field allows users to perform partial searches on categories. For example, a search for auto would turn up results for automobiles.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&category-like=Pants/

channel

<select name="channel[]" multiple="multiple">
    <option value="pants">Pants</option>
    <option value="tshirts">T-Shirts</option>
    <option value="sweats">Sweats</option>
</select>

This field allows your users to search on channel names. This field can partially override its matching parameter available in the Results tag, but only further narrowing the results from the values specified in the channel parameter in the Results tag. For example, if you have this parameter set: channel="products|locations", and the channel search query contains: products and blog, because blog was not specified in the channel parameter, it will be ignored, and just results from products channel will be searched upon. If submitting multiple channels, be sure to name the field channel[].

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&channel=pants+sweats/

customfield

<input type="text" name="summary" value="Bird is the Word" />

You can perform searches on any your custom fields, and on multiple custom fields at the same time. Just be sure that the field is marked as searchable in the custom fields' settings in the EE CP.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&summary=Bird+is+the+Word/

customfield-empty

<input type="text" name="price-empty" value="n" />

You can perform a search based on whether or not an entry's custom field has or doesn't have a value set for it. Specifying y means that only entries that have this field empty will be shown. Specifying n means that only entries that have a value for this field will be shown.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&price-empty=n/

customfield-exact

<input type="text" name="summary-exact" value="Bird is the Word" />

This field is a field type that behaves with special characteristics. Simply append the word -exact to the name of any of your custom fields and Super Search will return entries that match exactly against the search string. You can search on multiple exact custom fields at a time if you like. A user could search for Bird is the Word and see results where the custom field named summary contained that exact string Bird is the Word. So, if the field contained Haven't you heard that the Bird is the Word, while the phrase is in there, it will not be a match because the field contains more data that searched upon.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&summary-exact=Bird+is+the+Word/

customfield-from

<input type="text" name="price-from" value="20" />

This field allows you to search on a range of data. Used in conjunction with the customfield-to parameter, you can set a minimum value of where the data range should start from. This is particularly useful on numeric searches, like price ranges. Setting this to a value of 20 would only display entries that have a value of 20 or greater set for this field. Super Search will ignore things like commas, decimals and dollar signs from the field. When using this on a numerical field, you will want to make sure you've set the fields content settings to Decimal so that your range searches take place in a numerical fashion rather than textually.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&price-from=20/

customfield-to

<input type="text" name="price-to" value="100" />

This field allows you to search on a range of data. Used in conjunction with the customfield-from parameter, you can set a maximum value of where the data range should stop at. This is particularly useful on numeric searches, like price ranges. Setting this to a value of 100 would only display entries that have a value of 100 or less set for this field. Super Search will ignore things like commas, decimals and dollar signs from the field. When using this on a numerical field, you will want to make sure you've set the fields content settings to Decimal so that your range searches take place in a numerical fashion rather than textually.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&price-to=100/

customdatefield-from

<input type="text" name="customdatefield-from" value="201106" />

This field allows you to create date range searches on custom channel field dates. You construct date ranges from year, down to seconds, as a single number. 2011 will find entries with custom field dates from 2011 onward. 20110621 will find entries with custom field dates from June 21, 2011 onward. 20110621082345 will find entries with custom field dates from June 21, 2011 at 8:23:45 am onward. Used in conjunction with the customdatefield-to parameter.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&customdatefield-from=201106/

customdatefield-to

<input type="text" name="customdatefield-to" value="201107" />

This field allows you to create date range searches on custom channel field dates. You construct date ranges from year, down to seconds, as a single number. 2011 will find entries with custom field dates up to 2011. 20110721 will find entries with custom field dates up to July 21, 2011. 20110721082345 will find entries with custom field dates up to July 21, 2011 at 8:23:45 am. Used in conjunction with the customdatefield-from parameter.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&customdatefield-to=201107/

expiry_date-from

<input type="text" name="expiry_date-from" value="201106" />

This field allows you to create date range searches on channel entry expiry dates. You construct date ranges from year, down to seconds, as a single number. 2011 will find entries with expiry dates from 2011 onward. 20110621 will find entries with expiry dates from June 21, 2011 onward. 20110621082345 will find entries with expiry dates from June 21, 2011 at 8:23:45 am onward. When using this parameter, any entries that do NOT have an expiry date set will be automatically filtered out from the results. Used in conjunction with the expiry_date-to parameter.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&expiry_date-from=201106/

entry_date-to

<input type="text" name="entry_date-to" value="201107" />

This field allows you to create date range searches on channel entry dates. You construct date ranges from year, down to seconds, as a single number. 2011 will find entries with entry dates up to 2011. 20110721 will find entries with entry dates up to July 21, 2011. 20110721082345 will find entries with entry dates up to July 21, 2011 at 8:23:45 am. Used in conjunction with the entry_date-from parameter.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&entry_date-to=201107/

expiry_date-from

<input type="text" name="expiry_date-from" value="201106" />

This field allows you to create date range searches on channel entry expiry dates. You construct date ranges from year, down to seconds, as a single number. 2011 will find entries with expiry dates from 2011 onward. 20110621 will find entries with expiry dates from June 21, 2011 onward. 20110621082345 will find entries with expiry dates from June 21, 2011 at 8:23:45 am onward. When using this parameter, any entries that do NOT have an expiry date set will be automatically filtered out from the results. Used in conjunction with the expiry_date-to parameter.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&expiry_date-from=201106/

expiry_date-to

<input type="text" name="expiry_date-to" value="201107" />

This field allows you to create date range searches on channel entry expiry dates. You construct date ranges from year, down to seconds, as a single number. 2011 will find entries with expiry dates up to 2011. 20110721 will find entries with expiry dates up to July 21, 2011. 20110721082345 will find entries with expiry dates up to July 21, 2011 at 8:23:45 am. When using this parameter, any entries that do NOT have an expiry date set will be automatically filtered out from the results. Used in conjunction with the expiry_date-from parameter.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&expiry_date-to=201107/

group

<select name="group">
    <option value="Members">Members</option>
    <option value="Editors">Editors</option>
    <option value="Super Admins">Super Admins</option>
</select>

This field allows you to filter the results by entries authored by member(s) of a given member group. You can use member group titles or the group ID. This field cannot override its matching parameter available in the Results tag.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&group=Members/

inclusive_keywords

<input type="checkbox" name="inclusive_keywords" value="no" />
<label>Results can contain ANY of the words I search on</label>`

By default, Super Search will look for (and require) ALL terms searched upon when producing results. If you wish to override this, set this field to no. Default is yes.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&keywords=pizza+pie&inclusive_keywords=no/

keywords

The keywords field allows your users to perform a search on across all entries on your site. By default, keyword searches look into all searchable custom fields and titles. Please make sure that each custom field is marked as searchable in the custom fields' settings in the EE CP. Search terms are inclusive (so all words searched on must be present in the entry to show up as a valid result), search on words within words (a search for cat could return caterpillar), and also search into Solspace Tag add-on tags (if installed).

To tell the keyword search to only look into specific custom fields (instead of ALL searchable), see the search_in parameter. To disable the inclusive searching, you can pass the inclusive_keywords field with a value of no, or call the inclusive_keywords parameter directly within the Results template. To disable word within word searching, you can pass the search_words_within_words parameter with a value of no, or call the the search_words_within_words parameter directly within the Results template. To disable Solspace Tag add-on tag searching, call the ignore_tags_in_keywords parameter directly within the Results template.

To include keyword searching on author screen names and/or category names, specify a value of yes for the keyword_search_author_name and keyword_search_category_name parameters, respectively.

keyword_search_author_name

<input type="checkbox" name="keyword_search_author_name" value="yes" />

This field allows you to tell Super Search to also include searching on screen names of authors of entries. Any matches on the author name will show those entries as results. Since searches are inclusive by default, when searching with multiple keywords, only entries with keywords found in the title or searchable fields will be returned, regardless of whether the keywords match against the screen name of an author. You can override this by using the inclusive_keywords parameter in the Results tag and specifying a value of no.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&keywords=pie&keyword_search_author_name=yes/

keyword_search_category_name

<input type="checkbox" name="keyword_search_category_name" value="yes" />

This field allows you to tell Super Search to also include searching on category names of categories assigned to entries. Any matches on the category name will show those entries as results. Since searches are inclusive by default, when searching with multiple keywords, only entries with keywords found in the title or searchable fields will be returned, regardless of whether the keywords match against the category name(s). You can override this by using the inclusive_keywords parameter in the Results tag and specifying a value of no.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&keywords=pie&keyword_search_category_name=yes/

orderby

<input type="text" name="orderby" value="title+asc+price+desc" />

This field controls the order in which entries are retrieved by Super Search. Results can be ordered by:

  • channel_name: the short name for channel
  • channel_title: full name for channel
  • entry_date (default)
  • title
  • any custom channel field

Using this field you can set the default ordering rules of your search results page. To provide multiple ordering types, the syntax is to specify an order type and then the sort direction, and should look something like this: channel_title+asc+title+asc. If you forget to succeed a field by an asc or desc sort order, asc will be assumed. This field will override its matching parameter available in the Results tag.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&order=title+asc+price+desc/

redirect_post

<input type="checkbox" name="redirect_post" value="yes" />

By default, Super Search will redirect a POST search to contain the search query in the URI on the results page, similar to how it does on Google searches, etc. This allows your users to bookmark search queries, etc. To override this behaviour, specify this field with a value of no. Also available as a parameter in the Results tag to have it always forced.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&keywords=pie&redirect_post=no/

screen_name

<input type="text" name="screen_name" value="mitt" />

This field allows your users to search directly on screen names of authors of entries.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&screen_name=mitt/

search_in

<input type="text" name="search_in" value="title|body" />

This parameter allows your users to select which fields they which to search within. This field is paired up with the keywords field, and overrides default behaviour of searching within ALL searchable custom fields. Options are: title, custom_field_name, all, or a combination of title and any custom_field_name's, delimited by pipe character (|).

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&keywords=pie&search_in=title|body/

search_words_within_words

<input type="checkbox" name="search_words_within_words" value="no" />

This field allows your users to stop Super Search from searching on words within words. Default value is yes. For example, a user might want to perform a search on cat, but they don't want to see results for catalog.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&search_words_within_words=no/

site

<select name="site[]" multiple="multiple">
    <option value="site_1">Site 1</option>
    <option value="site_2">Site 2</option>
    <option value="site_3">Site 3</option>
</select>

This field allows your users to filter the search results by the MSM site short name your entries belong to. This field can partially override its matching parameter available in the Results tag, but only further narrowing the results from the values specified in the site parameter in the Results tag. For example, if you have this parameter set: site="site_1|site_3", and the site search query contains: site_1 and site_2, because site_2 was not specified in the site parameter, it will be ignored, and just results from site_1 channel will be searched upon. If submitting multiple site names, be sure to name the field site[].

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&site=site_1+site_3/

status

<select name="status">
    <option value="open">Open</option>
    <option value="closed">Closed</option>
</select>

This field allows your users to filter the search results by the status of your entries. This field cannot override its matching parameter available in the Results tag.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&status=open/

tags

<input type="text" name="tags" value="Cheese" />

You can search on one or more Solspace Tag tags in Super Search. This method looks for tags that EXACTLY match the values you specify. If you're looking for a looser method, use the tags-like field. You can also negate tags to exclude entries that are tagged with a certain tag. Just precede the tag name with a minus sign: pie+-cheese (look for pie, but NOT cheese). You can also do conjoined tag searching to find entries belonging to all of a given list of tags. Use the ampersand as the separator like this: pie&&cheese.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&tags=apples+oranges/

tags-like

<input type="text" name="tags-like" value="car" />

This field allows you to perform partial match searches on tags. So if an entry is tagged with carpet, a search of car will match that.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&tags-like=car/

title

<input type="text" name="title" value="To be or not to be" />

This field allows your users to search directly on entry titles.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&title=pie/

Also available is title-exact (display results by entries that exactly match the keywords specified), title-from and title-to (allows you to perform alphabetical range searches). So for example, you could list all entries that start with A - C by using this code:

From: <input type="text" name="title-from" />
To: <input type="text" name="title-to" />

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&title-from=a&title-to=c/

url_title

<input type="text" name="url_title" value="hello" />

This field allows your users to search directly on entry URL titles.

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&url_title=hello/

where

<select name="where">
    <option value="all">All</option>
    <option value="any">Any</option>
    <option value="exact">Exact</option>
    <option value="word">Word</option>
</select>

This field allows the user to easily specify how they want their keyword search to be performed. Use of this parameter will override inclusive_keywords and search_words_within_words features. Used in conjunction with the keywords field. Options are:

  • all - only results containing all of the specified words will be returned
  • any - results containing any of the specified words will be returned
  • exact - only results containing the entire matching phrase (case sensitive) will be returned
  • word - only results containing the exact phrase specified will be returned

The URI version of this search would look like this:

http://www.yoursite.com/search/results/search&keywords=bird+is+the+word&where=all/

Examples

The following are a few different examples of how you can use this tag:

Basic Search Form

The following code sample is an example of what a simple search form that populates previous search data might look like:

{exp:super_search:form
    return="supersearch/results"
    {if segment_2 == "saved"}
        search_id="{segment_3}"
    {/if}
}
    <h3>Search for Products:</h3>
    <p>
        <label for="keywords">Keywords:</label>
        <input
            type="text" name="keywords" id="keywords"
            value="{super_search_keywords}" />
    </p>
    <p>
        <label for="price-from">Price from:</label>
        <input
            type="text" name="price-from" id="price-from"
            value="{super_search_price-from}" />
        <label for="price-to">to:</label>
        <input
            type="text" name="price-to" id="price-to"
            value="{super_search_price-to}" />
    </p>
    <p><input type="submit" name="submit" value="Search!" /></p>
{/exp:super_search:form}

Advanced Search Form

The following code sample is a more elaborate example of a search form:

{exp:super_search:form
    return="supersearch/results"
    {if segment_2 == "saved"}
        search_id="{segment_3}"
    {/if}
}
    <h3>Search for Products:</h3>
    <p>
        <label for="keywords">Keywords:</label>
        <input
            type="text" name="keywords" id="keywords"
            value="{super_search_keywords}" />
    </p>
    <p>
        Category:
        {exp:channel:categories
            style="linear"
            category_group="1"
        }
            {exp:super_search:variables}
                <label for="category_{category_url_title}">
                    {category_name}
                </label>
                <input
                    type="checkbox"
                    id="category_{category_url_title}" name="category[]"
                    value="{category_url_title}"
                    {if super_search_category_{category_url_title}}
                        checked="checked"
                    {/if}/>
            {/exp:super_search:variables}
        {/exp:channel:categories}
    </p>
    <p>
        Sizes:
        <input
            type="checkbox" name="sizes[]" id="sizes_small"
            value="small"
            {if super_search_sizes_small}
                checked="checked"
            {/if}/>
        <label for="sizes_small">
            Small
        </label>
        <input
            type="checkbox" name="sizes[]" id="sizes_medium"
            value="medium"
            {if super_search_sizes_medium}
                checked="checked"
            {/if}/>
        <label for="sizes_medium">
            Medium
        </label>
        <input
            type="checkbox" name="sizes[]" id="sizes_large"
            value="large"
            {if super_search_sizes_large}
                checked="checked"
            {/if}/>
        <label for="sizes_large">
            Large
        </label>
    </p>
    <p>
        <label for="price-from">
            Price from:
        </label>
        <input
            type="text" name="price-from" id="price-from"
            value="{super_search_price-from}" />
        <label for="price-to">
            to:
        </label>
        <input
            type="text" name="price-to" id="price-to"
            value="{super_search_price-to}" />
    </p>
    <p>
        <input type="submit" name="submit" value="Search!" />
    </p>
{/exp:super_search:form}