• when filterfield is a dropdown box, exactvalue must be the text of the item in the drop down list without quotation marks
• when filterfield is a category, exactvalue must be the numeric id (without quotation marks) of the category item to filter the list
• when filterfield is a checkbox, exactvalue is y or n

Please note that there might be a bug in Tiki 9.x and later versions, which causes filterfield work when fields param is missing only for Admin users. To make it work for other Groups, you need to set fields param and explicitly name all fields you want to display. For example:

{trackerlist trackerId="2" list_mode="csv" fields="17:42:43:44:47" filterfield="44" exactvalue="y" tplwiki="Template page for a Slide"}

After tw>=2.0 filterField can specify a list of fieldIds. In this case filtervalue and exactvalue must be synchronised to filter the value of each field

• Example: filterfield=1:2, filtervalue=this:that

will filter the items with the field 1 'like' this and field 2 like 'that'

• Example: filterfield=1:2, exactvalue=this:that

will filter items with the field 1 equals to 'this' and field 2 equals to 'that'

• Example: filterfield=1:2, filtervalue=:this, exactvalue=that

will filter items with field 1 equals to 'that' and field 2 likes 'this'

• Example: FieldId 1 is the itemId fields (auto-increment itemId) filterfield=1, notfield(1) and with an url containing itemId will give all the items except the onde defined in the url

Filtering on item list fields

Note that for filtering on item list fields through filterfield, it is important to ensure that fields contain the filterfield id as well. This is because of the special way item list fields are filtered due to its special nature.

Also, if there are multiple items in the value of filterfield, the value you should attempt to match against is item1,item2,item3 if using exactvalue. If you are using filtervalue which does partial matching, from Tiki 6.2, you can match against ",item1,item2,item3,". This is to avoid ambiguity in certain cases. For example, if you are trying to match for a number like "32" in a sequence of numbers like "132,32,321" it can be ambiguous since you might accidently get those that match "21,132". To solve this, from Tiki 6.2, you can set the filtervalue to ",32," to make sure you match only those sequences that include 32 and not things like 132.

Its params are: fieldId/postName/Title/Submit/ActionUrl/tpl/(empty)|radio|dropdown

• fieldId is the field Id whose value will be posted to the action
• postName is the name of the post
• Title is the title of the button
• Submit is the name of the submit button
• ActionUrl is the script that will be called on the submit
• tpl is an optional template that be inserted before the submit button that will also be returned
• radio or dropdown. If this param is left blank/empty, multiple checkbox will be used instead.

Example:

checkbox="6/to/Email to the checked/submit/messu-compose.php//"

in this example the fieldId 6 is the user name as messu-compose.php accepts to as param, and multiple checkboxes will be shown on the left to select one or more user to send a message to.

You want to be able from a TRACKERLIST page to select an item and to go on another page where you can modify your item. We will call this page UpdateItem. We will suppose that the field 1 is a main field (it display a link to the item.
To do so use the parameter url in TRACKERLIST

{TRACKERLIST(....fields=1, showlinks=y, url="tiki-index_raw.php?page=UpdateItem&itemId=") /}

The page UpdateItem needs just to use a regular TRACKER plugin. If itemId is present in the URL, it will be automatically prefilled with the value of the item.

tw>= 2.0
It is possible to control how an item is displayed in a page by using a smarty template or a wiki page containing smarty code. In the case of a wiki page containing smarty code, keep in mind that this page should be kept editable only by trusted users, such as other site admins.

For instance in a page (named 'list of items in tracker 5') for example, you have

{TRACKERLIST(trackerId=5, fields=30:31, showcreated=y, wiki=tpl for each item in tracker 5) /}

where fieldId=30 and fieldId=31 are 2 fields of the trackerId 5
In the page named 'tpl for each item in tracker 5', you will have

http://doc.tiki.org/tiki-editpage.php?page=PluginTrackerList&hdr=5
{$f_30} : {$f_31}{tr} was created in {/tr}__{$f_created|tiki_short_date}__

PS: the wiki page 'tpl for each item in tracker 5' needs the perm tiki_p_use_as_template for anonymous (or registered, depending on your case) to be displayed, and tiki_p_edit for admins, in order to prevent any users to add any smarty code in it, which might be unsafe.
When displayed, the page 'list of items in tracker 5' will look like this

324: foobar was created on __Thu 23/10/08__
 311: toto was created in __Wed 23/10/07__

There is no more table (if you did not recreate them in 'tpl for each item in tracker 5' for course). Of course the name of the 'template' page is whatever you want - you need only to give the good reference in the param 'wiki'
PS: $f_created and $f_lastmodif have been introduced in tw>= 3.0. They display the integer value of the associated date. $f_status and $f_status_input in tw>=5.0. $f_status will output o or p or c. $f_status_input will output the status select box.
Tip: you can use {$f_created|date_format:"%I:%M %p"} or {$f_created|tiki_short_date}

You can use also a template file in the file system

{TRACKERLIST(trackerId=5, fields=30:31, showcreated=y, tpl=B) /}

and create a templates/B.tpl. In this case no permissions are required.

No Pretty Tracker

• If you do not use pretty tracker for instance a TRACKERLIST with no url param and a param showlinks=y, each time you click on an item link you will go to tiki-view_traker_item.php and you will see pagiantion between item.
• If you are using TRACKERLIST with the url param equals to "page&itemId" for instance and if you want that each item displays a pagination to the next/previous item you need to have showpagination=y in the TRACKERLIST params
• THis pagination is very convenient when you are using TRACKERFILTER or use some specific filtering of TRACKERLIST as only the filtered items are in the pagination

With Pretty Tracker (starting with Tiki11)

• If using custom templates for display (pretty trackers), use tr_offset instead of itemId. Here's an example of how this can be used:

1. Use PluginTrackerList to list items from a tracker.
   1. Set the url parameter to url="ItemPageName&tr_offset". This will cause title fields in the list to be links to this page
2. ItemPageName will consist of another instance of PluginTrackerList.
   1. This time the fields parameter should include the field IDs that should appear on the individual item page.
   2. showpagination should be set to y so that pagination with be shown
   3. The wiki or tpl parameter will be set to the custom template page that has been created to display single tacker items from this tracker. Since the tr_offset parameter was set when calling this page, only one item will be shown.

• tr_user: if &tr_user=username is set in the URL request, the plugin loads the specified user item(s) (trackerId must be specified)

Since Tiki6.0, it is possible to 'nest' plugins - meaning another plugin can be invoked in the template file where smarty code is used to assign parameters which are defined by the first trackerlist.

• WARNING: will only work if the first (or any level except the last) trackerlist delivers one item

For example:
If a 'first level' plugin such as:

{trackerlist trackerId="2" view="page" max="1" fields="43:50" filterfield="43" exactvalue="Test Reference" wiki="insert_location tpl" status="opc" ignoreRequestItemId="y"}

is used in a wiki page, and the wiki template "insert_location tpl" has within it a second level plugin such as:

{trackerlist trackerId="30" fields="75:907" list_mode="n" filterfield="75" exactvalue="{$f_50}" wiki="stdlocmap tpl"}

where the wiki template "stdlocmap tpl" is as follows:

{$f_75}
{$f_907}

Then the result is that the original page will display the field values f_75 and f_907 from the second tracker (id# 30) where the item is defined by a match between a designated value in the tracker and the same value in the second tracker.

This allows you to display global information about a numeric field like the sum of all the values or the average.

Tiki6: The items shown by the tracker list (e.g., filtered with the parameters "filtervalue" or "exactvalue") are the only ones used for the computation (average or sum), and not all the items in the same tracker.

{TRACKERLIST(trackerId=5, fields=12:15:142:466, compute=142:466/avg) /}

will give something like

If you want to use sum and average on the same field use compute=146/sum:146/avg

Decimals in values are indicated with the dot (".") and not with the comma (",").

If your tracker has a field named 'page' and if the url contains the param 'page', TRACKERLIST will automatically filter the items that have the value of the page url param equal to the page item filed value.

For instance, you have a user tracker with a field Town, you have another tracker listing all the bakeries. This tracker has also a field Town. You want to display all the bakeries in the town of your user. For this you can use

{trackerlist trackerId="5" fields="21:23:24" filterfield="20" exactvalue="field(38,user,7)"}

where 5 is the trackerId of the bakery, 20 is the fieldId of Town in the tracker bakery, 38 is the fieldId of the Town in the user tracker 7.

You can use as many filters you want. For instance, you can filter on the Town and the nationality with the type of bakery...

With the same principle, you can display all the items of the user tracker that have the same Town than the user. or the same Town and same age that the user.

With the parameter calendarfielddate, you can display the list of the items in a calendar view. See Module calendar_new. The plugin collects all the items of the period and displays in a popup the items. The display is either the pretty tracker template specified by the param wiki or the value of main field.The calendarfieldate can contain either a single date field or 2 date fields.
Example:

Has been produced by a user module containing the code:

!!!Formations à venir
{TRACKERLIST(trackerId=11, ignoreRequestItemId=y, fields=56:58, url="formation&itemId", showlinks=y, filterfield=56, exactvalue="greaterequal(now)", calendarfielddate=56, calendarviewmode=month, calendarstickypopup=y, wiki=trackerCalendrierFormation, calendarviewnavbar=n, wiki=trackerFormationCalendrier, calendarviewnavbar=partial) /}
{TRACKERLIST(trackerId=11, ignoreRequestItemId=y, fields=56:58, url="formation&itemId", showlinks=y, filterfield=56, exactvalue="greaterequal(now)", calendarfielddate=56, calendarviewmode=month, calendarstickypopup=y, wiki=trackerCalendrierFormation, calendarviewnavbar=n, calendardelta=month, wiki=trackerFormationCalendrier) /}

http://dev.tiki.org/All+Bugs (see page source to see how the plugin is used to generate the report)

• This page no longer exists. Any other examples?

• To add data to the tracker via a form in a wiki page: PluginTracker
• To create a report in a wiki page: PluginTrackerFilter, PluginTrackerItemField, PluginTrackerStat
• And also PluginVote
• Pretty Tracker
• PluginR uses PluginTrackerList to use data from trackers within R scripts.