The plugin has a core set of parameters, but because it also shares all the parameters available from the TRACKERLIST plugin, these additional parameters can be added to customise the look of the result (except the filterfield, exactvalue and filtervalue - using these parameters will overwrite the core filter selection)

The core set of parameters are as follows:

• trackerId: Id of the tracker
• filters is the list of fields that can be filtered with the format of their display.
  The fields are identified by their numeric Ids. All the fields must belong to the same tracker. After tiki>=8, the status can be a filter and must be entered as status or Status (Filter example: 3/d:Status/d)
  The Id can be followed by the character / and one of this format:
  • d: drop down list of all the values occurring for the field: only one value can be selected
  • r: radio buttons of all the values occurring for the field: only one value can be selected
  • m: multiple choice in the drop down list of all the values occurring for the field( a multiple choice acts as an OR between the values of the choice)
  • c: checkbox (multiple choice) in the drop down list of all the values occurring for the field
  • t: text entry (tiki >= 2.0): a text input where the user must enter a part of the text
    If the text contains % like a%. it will search all the values beginning with % (can also do %a or a%b%c) or a* or *a
  • T: text entry (tiki >= 2.0): a text input where the user must enter an exact value of the field
  • i: text entry + initial (tiki >=2.0): a list of initial that will directly filter on an initial. Note: if you use initial, not other field can be filtered
  • sqlsearch: advanced mysql search (tiki >= 5.0): a list of fields where a mysql advanced search will be done - Note: the search is done field content per field content: It means if you query A B and A is in a field and B in another one you will not find the item. The syntax will be (1:2)/sqlsearch means 'do a advanced mysqlsearch on fields 1 and 2.
  • > or < or >= or <=: comparison (tw >=6.0): the field will be compared using the format as operator. Ex: filters="1/>=" will find all the items with the field 1 bigger (for a numeric) or after (for a date) the value the user will give
  • range: range of values ( from and to search boxes shown). Timezone-aware fields like JsCalendar field are converted properly before being searched, so search is done in the correct timezone. Range filter can be used with any field - not only dates but it is most useful for dates and numeric fields. tiki >=16.2
• fields will show the fields displayed for the selected items
• action : name of the submit button - default is "filter" (tiki >= 1.9.8)
• noflipflop: will not show the flipflop to hide and display the list of filters. (tiki >=6.0)
• export_action: (tiki >= 6.0) if set to appropriate text e.g."Confirm CSV Download" this over-rides the normal trackerfilter approach and displays a button with the designated text that directly exports the set of fields specified as a CSV file. A filter to define a specific 'filter set' must be defined by using the filterfield, filtervalue/exactvalue parameters, formatted in the standard ways. Additional parameter options are (default|alternate):
  • export_itemid=y|n - includes the ItemId in the export
  • export_status=n|y - includes the status field in the export
  • export_modif=n|y - includes the modified date in the export
  • export_created=n|y - includes the creation date in the export
  • export_charset=UTF-8|ISO-8859-1 - defines the character set to be used for the export
• mapButtons=y|n - Display Mapview and Listview buttons (from Tiki6, requires Google Maps feature)
• url replace tracker item url with the url you input in the field. You can include the Item Id. This is very usefull combined with TrackerList and/or Pretty tracker to link the results of the tracker filter to another page (wiki or template) where the item will be displayed as single entity (using TrackerList plugin).
  Use Case : Search and display tracker item in wiki pages without any relation to the trackers usual design (buttons, pagination, etc)
  Set the plugin TrackerFilter in a wiki page to display and filter tracker item. Be sure it is working with the usual parameters and display items. Set the parameter Show Links to yes (showlinks="y") and in the parameter URL set the page that will be used to display the item once the item link is clicked with the following url="singleitem_tpl?itemId".
  Create a second wiki page named "singleitem_tpl". In this page set the plugin TrackerList with the Tracker Id parameter and set for Wiki Page (wiki="item_tpl").
  Create a third page named item_tpl that you are now free to design the way you want that will display the item fields.
  That way you can design all the way the page using wiki syntax and CSS and the user will never have the feeling he is looking at a tracker or at trackers items.

The full set of available parameters, the core TRACKERFILTER set and the additional ones from TRACKERLIST, are set out in the various TABS below:

• Info on 'filters' parameter field formats:
  • d: drop down list of all the values occurring for the field: only one value can be selected
  • r: radio buttons of all the values occurring for the field: only one value can be selected
  • m: multiple choice in the drop down list of all the values occurring for the field( a multiple choice acts as an OR between the values of the choice)
  • c: checkbox (multiple choice) in the drop down list of all the values occurring for the field
  • t: text entry: a text input where the user must enter a part of the text
    If the text contains % like a%. it will search all the values beginning with % (can also do %a or a%b%c) or a* or *a
  • T: text entry: a text input where the user must enter an exact value of the field
  • i: text entry + initial: a list of initial that will directly filter on an initial. Note: if you use initial, not other field can be filtered
  • sqlsearch: advanced mysql search (Tiki5): a list of fields where a mysql advanced search will be done - Note: the search is done field content per field content: It means if you query A B and A is in a field and B in another one you will not find the item. The syntax will be (1:2)/sqlsearch means 'do a advanced mysqlsearch on fields 1 and 2.
  • > or < or >= or <=: comparison (Tiki6): the field will be compared using the format as operator. Ex: filters="1/>=" will find all the items with the field 1 bigger (for a numeric) or after (for a date) the value the user will give
• Notes on the use of the export option:
  • if the export_action parameter is not empty then the basic functionality of the plugin is changed to allow designated fields and other parameters to be exported as a CSV file for ALL the tracker items with the substitution of the normal 'Filter' button by a custom button using the export_action text
  • the fields that are exported are those specified in the 'fields' parameter
  • other item values can be exported by setting the following parameters:
    • export_status is set to 'y' to show the status of the individual item in the CSV file (the default is 'n')
    • export_created is set to 'y' to show the item's creation date in the CSV file (the default is 'n')
    • export_modif is set to 'y' to show the item's modification date in the CSV file (the default is 'n')
    • export_charset can be set to the character set to be used in the export ie typically UTF-8 which is the default
  • Please note: if the export_action parameter is not empty then there is currently a problem with using the plugin editor, since for the export option there is no need to set the filters parameter - but for normal use this is a required parameter. This exception is allowed for in the main plugin code but at present the plugin editor does not recognise the exception and will not complete the 'Insert' until this parameter is entered. It is therefore recommended that edits to the trackerfilter plugin are carried direct in the main editor(s) when using the export option.
• url replace tracker item url with the url you input in the field. You can include the Item Id. This is very useful combined with TrackerList and/or Pretty tracker to link the results of the tracker filter to another page (wiki or template) where the item will be displayed as single entity (using TrackerList plugin).
  Use Case : Search and display tracker item in wiki pages without any relation to the trackers usual design (buttons, pagination, etc)
  Set the plugin TrackerFilter in a wiki page to display and filter tracker item. Be sure it is working with the usual parameters and display items. Set the parameter Show Links to yes ( showlinks="y" ) and in the parameter URL set the page that will be used to display the item once the item link is clicked with the following url="singleitem_tpl?itemId" .
  Create a second wiki page named "singleitem_tpl". In this page set the plugin TrackerList with the Tracker Id parameter and set for Wiki Page ( wiki="item_tpl" ).
  Create a third page named item_tpl that you are now free to design the way you want that will display the item fields.
  That way you can design all the way the page using wiki syntax and CSS and the user will never have the feeling he is looking at a tracker or at trackers items.

Note:
For a drop-down list, the values of the drop down list will be displayed, For the other field types, the values found in the database will be displayed.

As the data are filtered you can also perform calculation on the fly.

Here we add all the value of the last col.

{trackerfilter filters="273/d:431/d" displayList="y" noflipflop="y" trackerId="21" fields="273:268:269:435:431" showlinks="y" shownbitems="y" showcreated="n" showlastmodif="n" showlastmodifby="n" status="o" max="-1" editable="114" server="n" sortable="y" tsortcolumns="type:none|type:none|type:none|type:none|type:none" tsfilters="type:text|type:nofilter|type:nofilter|type:nofilter|type:nofilter"  tstotals=" | | | |type:col;formula:sum;label:total " tstotaloptions="ignore|ignore|ignore|ignore|#,###"}

It can be interesting to use the checkbox capacity of trackerlist to do some action on some filtered items:

{trackerfilter filters="82/d:84" fields="82:83" checkbox="85/to/Email to checked/send/soho-send_message.php/soho-send_message.tpl"}

You can also get directly connected to the message box

{trackerfilter filters="82/m:84" fields="82:83" checkbox="85/to/Email to checked/xxx/messu-compose.php"}

Imagine a tracker

A search page like this

{trackerfilter trackerId="1" filters="5:6:9:8/d:(2:1:3)/sqlsearch" showlinks="y" fields="5:2:1" wiki="tracker ideas"}

The page will look like

and when you click on filter you will have something like this