Plugin Tracker List

1. Javascript must be enabled
   • Enabled by default at Admin > Features > Programmer (tab)
2. jQuery Sortable Tables must be activated
   • Enable at Admin > Features > Interface (tab)
3. For the server parameter to work for a plugin, ajax must be enabled
   • Enable at Admin > Features > Interface (tab)

• 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.

{trackerlist ....fields="1" showlinks="y" url="tiki-index.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.

'Pretty Trackers' (param tpl or wiki)
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 display the integer value of the associated date. $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.

How to have a pagination between the items accessed by TRACKERLIST (tiki>=6)

No Pretty Tracker

• If you do not use pretty tracker for instance a TRACKERLIST with no url parameter and parameter showlinks=y , each time you click on an item link you will go to tiki-view_traker_item.php and you will see pagination between item.
• If you are using TRACKERLIST with the url parameter equal 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
• 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 is 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.

URL Params

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

Nested plugins in 'pretty' templates
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.

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 (",").