Search Engine Internals Reference

Example: <input type="text" name="in_hobbies" value="diving">

in_field performs search "in" a field. For instance, if someone types "scuba diving and collecting stamps" in his/her profile hobbies field, then since the "diving" word is inside this field, this user will be in the results.

This field also accepts "any" variable in the value field. For instance adding this line would list all profiles that include "diving" word in any field:
<input type=hidden name=in_any value="diving">

Example: <input type="text" name="innot_hobbies" value="diving">

innot_field performs negative search "in" a field. This is mostly useful on "and" searches to disregard some entries. For instance, the tag above will help us disregard all profiles who have 'diving' word in their 'hobbies' field.

If you would like to use this alone, you need to set attitude to maximum.

This field also accepts "any" variable in the value field. For instance adding this line would list all profiles that include "diving" word in any field:
<input type=hidden name=in_any value="diving">

Example:
<select name="if_gender">
  <option>male
  <option>female
</select>

if_field looks for an exact comparision with the database entry. That means, the words entered to the search form must be exactly same as the data in the database. For instance, when we would like to do a search in male profiles, "if_gender" value should be "male". This is mostly used for the 'and' or 'or' type of searches.

Example: <input type="hidden" name="ifnot_image1" value=" ">

ifnot_field performs negative search "in" a field. This is mostly useful on "and" searches to disregard some entries. For instance, the hidden input tag above will disregard all entries with no value on their image1 field. In short add this line into a search will make the search to only perform in profiles with picture. Instead of a hidden field, it can also be a check box like this: <input type="checkbox" name="innot_image1" value=" "> With Picture

If you would like to use this alone, you need to set attitude to maximum.

Example:
<select name="infield">
  <option selected value="any">Any Keyword
  <option>login
  <option>email
  <option>age
  <option>state
</select>
<input type="text" name="words" size="15" value="">

There some things you can't do with "in_field", infield-words is basically a wrapper for the in_field. For instance, the example above performs a search inside the selected field.

Example:
<select name="iffield">
  <option selected value="any">Any Keyword
  <option>login
  <option>email
  <option>age
  <option>state
</select>
<input type="text" name="words" size="15" value="">

There some things you can't do with "if_field", iffield-words is basically a wrapper for the if_field. For instance, the example above performs an exact-word search inside the selected field.

Example:
<select name="from_age">
  <option>20
  <option>30
  <option>40
</select>

from_field provides numerical search. If the database entry is larger than the selected/entered number, then the profile will show up in the profiles.

Example:
<select name="to_age">
  <option>20
  <option>30
  <option>40
</select>

to_field provides numerical search. If the database entry is smaller than the selected/entered number, then the profile will show up in the profiles.

Example: <input type=hidden name=attitude value="maximum">

This field is being used combined with other queries. It changes the behaviour of the internal decisions. For instance, it is being used in "or" searches.

If we have a search form that includes gender and state selection:

Example: <input type=hidden name=sortby value="lastname">

Sortby sorts the results with a database field. To sort users latest modified first, you can add a line like this:
<input type=hidden name=sortby value="date">

Example: <input type=hidden name=noweight value="yes">

This makes a change in the search internals. Each profile is giving a weight depending on their suitability. If you don't use "sortby", then the results will be listed in weight order. This variable can be used to disable internal weight decisions.

Example: <input type=hidden name=reverse value="yes">

When you add this line into the form, the listing will be reversed. For instance, if you are sorting users by age, you can add reverse=yes to list oldest member first. If you are listing users by date, again you can use reverse=yes to list latest entries first format.

Example: <input type=hidden name=rpp value="20">

Results per page (rpp) defines the number of results that will be listed in each page.

Example: search.cgi?in_any=test&page=2

Page variable defines the page number of the search results.

Example: <input type=hidden name="temp_page" value="search_picture">

This variable defines the result page template. This template should be in %tempz hash of "default.cfg" configuration file. In this example, this is the line in the %tempz hash:
   'search_picture' => "templates/search/t_search_picture.htm",

Exception: The admin search template, requires admin password to be used.

Example: <input type=hidden name="temp_table" value="search_table_picture">

This variable defines the result page template per user. This template should be in %tempz hash of "default.cfg" configuration file. In this example, this is the line in the %tempz hash:
   'search_table_picture' => "templates/search/t_search_table_picture.htm",

Exception: The admin search table template, requires admin password to be used.