PluginList format control block


The FORMAT control block is used to create individually formatted objects that can then be used in any of the individual OUTPUT methods.

Available filters

Name Description Boolean Sample Tiki Version
default Display a default value or a default file when no value is available no "empty", "1140" (fileId) -
format format the displayed value to something different that the db value (human readable) no "trackerrender", "date", "objectlink", etc. (see format parameters here) -
editable Make the field editable so the value can be changed from the results display. Inline editing (found in admin control panels => trackers) must be enable. Must be used in conjunction with the trackerrender format (see above) and may require mode="raw" when using it with the table output template} editable="inline" -


Note that in some cases the field that will be displayed has its own behavior and it can clash with the format you selected.
IE: A tracker field that is a "title" is pre-formatted as a link. If you set the format as "objectlink" (or you set the display inside a link) the display will end broken as Tiki will try to display a link inside a link.

For the default parameter, it's important to remember that the tracker field "Files" works a bit differently than the others with this parameter. The tracker field Files expect an Id from the File Gallery. When most of the other fields type will display the text of the default parameters the default for "Files" must be an existing file in a gallery. The file can be an "anonymous" portrait file or a plain white image or an image with only the text "Not Available", etc. Whatever you feel right for your usage.

Basic example

In most of the examples shown in PluginList output control block and PluginList advanced output control block you will see a FORMAT control block have been used. E.g. in the example shown for Table output as below, two FORMAT control blocks are used:

Sample using the default table formatting
Copy to clipboard
{LIST()} {filter type="trackeritem"} {filter content="water"} {OUTPUT(template="table")} {column field="title_link" sort="title" label="Title" mode="raw"} {column field="description" label="Description"} {column field="event_date" sort="tracker_field_18" label="Event Date"} {OUTPUT} {FORMAT(name="title_link")}{display name="title" format="objectlink"}{FORMAT} {FORMAT(name="event_date")}{display name="tracker_field_18" format="date"}{FORMAT} {LIST}


The first FORMAT control block defines an object with the name title_link that is displayed in a specific way - this object reference is then used in the column control block in the body of the table OUTPUT. Similarly the second FORMAT control block defines the event_date object which is also used in a column control block.

A similar use of the FORMAT control block allows the normal set of Smarty variables, eg {user} etc, to be made available in Smarty templates - for example:

Format example to reference a normal smarty variable
Copy to clipboard
{FORMAT(name="theuser")} { {user} } {FORMAT}
 Note
The double brackets ( {{}} ) around user should have no spaces between them. Spaces are used here only to keep the user variable from being interpreted.

This creates a reference object theuser with the userId of the current user which can then be invoked in a server stored smarty template using the variable {$row.theuser}.

Examples of the use of the FORMAT control block (format and default value)

Copy to clipboard
{LIST()} {filter field="tracker_id" content="1"} {filter field="tracker_status" content="o"} {OUTPUT()} {DIV(class="h3")}{display name="name"}{DIV} {display name="photo"}%%% {display name="email"} {OUTPUT} {FORMAT(name="name")}{display name="tracker_field_userName"}{FORMAT} {FORMAT(name="photo")}{display name="tracker_field_userPhoto" format="trackerrender" default="1140"}{FORMAT} {FORMAT(name="location")}{display name="tracker_field_userLocation" format="trackerrender" default="Unknown"}{FORMAT} {LIST}


Default parameter applied on the "photo" field will display a default generic image if not file found.
Default parameter applied on the "location" field will display the text "Unknown" if the field is empty.

Example with comments


You might want to display all comments, and this script will retrieve them:

Wiki Output Sample
Copy to clipboard
{LIST(cache="n")} {filter type="comment"} {pagination max="10"} {OUTPUT( template="table")} {column field="title"} {column field="comment_content"} {column field="object_link" mode="raw"} {column field="date"} {OUTPUT} {FORMAT( name="object_link")} {display name="object_id" format="objectlink"} {FORMAT} {sort mode="date_desc"} {LIST}

The FORMAT control block defines an object with the name object_link which is displayed in such a way that it is object_id which is displayed and formatted as objectlink; which makes the id clickable. This object reference is then used in the column control block in the body of the OUTPUT table.
This gives us the following result:

Title Comment Thread Id Date
MIssing fields This doc is missing several fields compared to my 1.8.6 install LDAP Group DN: similar to User DN but both should be called User or Group RDN LDAP Group Attribute: LDAP Group OC: LDAP Member Attribute: LDAP Member Is DN: \\Greg 146 2005-11-03 03:57:45
Page needs to discuss link aliasing This page needs a subsection explaining how to create aliased wiki links. 145 2005-10-30 05:15:34
Re: Demo movie > I created a quick demo movie that shows the two methods to create a new page. It might be nice to link to it from this page (let folks actually see how to create and edit pages). I like the demo movie, but I would prefer to have a movie that separate the role of a user with the one of an administrator. Adding modules to a site is done by an administrator. I see the tutorials mainly from a User point of view. May be there will be some tutorials from an administrator point of view but I don't want to mix the two roles. 144 2005-10-26 12:16:57
Demo movie I created a quick demo movie that shows the two methods to create a new page. It might be nice to link to it from this page (let folks actually see how to create and edit pages). 143 2005-10-24 13:47:43
Restricting 'other' files I have added this to the end of my rewrite rules, as a safety net against users retrieving/running sql, perl, tpl, shell, etc from any directory in tikiwiki. tiki-download-file.php handles other files stored in the galleries. Comments welcome. RewriteRule !\.(?i:php|gif|jpe?g|png|tiff?|pdf|css|js|csv|rtf)$ - [[F]] 142 2005-10-20 19:28:55
ALT works too! Need to mention that the ALT element works as well. For example: 141 2005-10-18 01:25:03
Re: list problems You can't breakup a numbered list with non-numbered paragraphs — the list will restart. For example, you can't have: 1. Step One 2. Step Two Some text here 3. Step three Instead, TIKI will reset the count at: 1. Step tree. This should be mentioned in the doc 140 2005-10-18 01:23:16
Create Page is confusing The current TIKI concept of how to create a new page is very confusing to new users — you have to already be editing an existing wiki page in order to create a new one. This is (IMHO) very anti-user friendly. This section should mention the two ways to create a new page: 1. Using the quick_edit module to create a new page from scratch 2. Using the MyNewPage method, docuemented here. 139 2005-10-18 01:18:48
Re: I'm still unsure what trackers do. Trackers appear to be designed to allow you to, well, track things. I'm sure that the original intent was to track bugs in the software, but they've made it an open ended system where you can track whatever you want. One bit of documentation I read said it is more of a forms editor, so you can devise trackers to collect any kind of information that you want, but all items appear to get the status of open, pending, or closed, so there is still a notion of "tracking" regardless of the content. We have just set up a tracker to help us track the production status of items in our application. Since they can exist on many layers (hand coded files, database objects and procedures, input data files, generated templates, etc.) it's hard to make sure that everything has been pushed from development to test to production. We're just setting it up, but it looks like will work well without me having to go find yet another package to do this sort of thing. 138 2005-09-29 15:16:48
I'm still unsure what trackers do. I've heard people talk about trackers but still not clear - is this a mini database tool for holding and sorting data input by users or is it a tool to program database queries with? the name suggests the latter, but the function seems to be the former. suppose i want to create a page in my tiki that displays how many wiki pages contain the word "beer", with who edited that word in and when? can i do that with a tracker or with something else? 137 2005-09-27 22:33:02


We see that this only gives us the information about the object (the comment in this case), but what if I want to have more information before visiting the comment?

One way to do this is to add a column which indicates the item being commented on. It is typically a wiki page or tracker item which is clickable and takes me there.

So let's make some changes and see what we have:

Wiki Output Sample
Copy to clipboard
{LIST(cache="n")} {filter type="comment"} {pagination max="10"} {OUTPUT( template="table")} {column field="contributors"} {column field="title"} {column field="comment_content"} {column field="parent_object_title" mode="raw"} {column field="object_link" mode="raw"} {column field="date"} {OUTPUT} {FORMAT( name="object_link")} {display name="object_id" format="objectlink"} {FORMAT} {FORMAT( name="parent_object_title")} {display name="parent_object_type"}: {display name="wikiplugin_objectlink" format="wikiplugin" type="parent_object_type" id="parent_object_id"} {FORMAT} {sort mode="date_desc"} {LIST}

Here we have just added a new column whose label is "Parent Object".
The new FORMAT control block formats the parent_object_title field, which is the title of the comment's parent object, then with {display} tag we first display the name of the parent object, which is stored in the parent_object_type field. For example, if the parent object is a trackeritem, it will display "trackeritem:", and finally we display the link to the parent object, using the wikiplugin_objectlink plugin. This plugin allows you to create a link to a Tiki object according to its type and its identifier. Here you specify the link format as "wikiplugin", the object type as parent_object_type, and the object id as parent_object_id. For example, if the parent object is a trackeritem with id 1, this will generate a link to "tiki-view_tracker_item.php?itemId=1".
So you get a field that displays the name and link of the comment's parent object. For example, if the comment is linked to an item called "This is my first item", you display "trackeritem: This is my first item".
This gives us the following result:

Title Comment Parent Object Thread Id Date
MIssing fields This doc is missing several fields compared to my 1.8.6 install LDAP Group DN: similar to User DN but both should be called User or Group RDN LDAP Group Attribute: LDAP Group OC: LDAP Member Attribute: LDAP Member Is DN: \\Greg wiki page: LDAP authentication 146 2005-11-03 03:57:45
Page needs to discuss link aliasing This page needs a subsection explaining how to create aliased wiki links. wiki page: Wiki-Syntax Links 145 2005-10-30 05:15:34
Re: Demo movie > I created a quick demo movie that shows the two methods to create a new page. It might be nice to link to it from this page (let folks actually see how to create and edit pages). I like the demo movie, but I would prefer to have a movie that separate the role of a user with the one of an administrator. Adding modules to a site is done by an administrator. I see the tutorials mainly from a User point of view. May be there will be some tutorials from an administrator point of view but I don't want to mix the two roles. wiki page: Tutorial - Editing Wiki Pages 144 2005-10-26 12:16:57
Demo movie I created a quick demo movie that shows the two methods to create a new page. It might be nice to link to it from this page (let folks actually see how to create and edit pages). wiki page: Tutorial - Editing Wiki Pages 143 2005-10-24 13:47:43
Restricting 'other' files I have added this to the end of my rewrite rules, as a safety net against users retrieving/running sql, perl, tpl, shell, etc from any directory in tikiwiki. tiki-download-file.php handles other files stored in the galleries. Comments welcome. RewriteRule !\.(?i:php|gif|jpe?g|png|tiff?|pdf|css|js|csv|rtf)$ - [[F]] wiki page: Apache Clean URLs 142 2005-10-20 19:28:55
ALT works too! Need to mention that the ALT element works as well. For example: wiki page: Wiki-Syntax Images 141 2005-10-18 01:25:03
Re: list problems You can't breakup a numbered list with non-numbered paragraphs — the list will restart. For example, you can't have: 1. Step One 2. Step Two Some text here 3. Step three Instead, TIKI will reset the count at: 1. Step tree. This should be mentioned in the doc wiki page: Wiki-Syntax Lists 140 2005-10-18 01:23:16
Create Page is confusing The current TIKI concept of how to create a new page is very confusing to new users — you have to already be editing an existing wiki page in order to create a new one. This is (IMHO) very anti-user friendly. This section should mention the two ways to create a new page: 1. Using the quick_edit module to create a new page from scratch 2. Using the MyNewPage method, docuemented here. wiki page: Using Wiki Pages 139 2005-10-18 01:18:48
Re: I'm still unsure what trackers do. Trackers appear to be designed to allow you to, well, track things. I'm sure that the original intent was to track bugs in the software, but they've made it an open ended system where you can track whatever you want. One bit of documentation I read said it is more of a forms editor, so you can devise trackers to collect any kind of information that you want, but all items appear to get the status of open, pending, or closed, so there is still a notion of "tracking" regardless of the content. We have just set up a tracker to help us track the production status of items in our application. Since they can exist on many layers (hand coded files, database objects and procedures, input data files, generated templates, etc.) it's hard to make sure that everything has been pushed from development to test to production. We're just setting it up, but it looks like will work well without me having to go find yet another package to do this sort of thing. wiki page: Trackers 138 2005-09-29 15:16:48
I'm still unsure what trackers do. I've heard people talk about trackers but still not clear - is this a mini database tool for holding and sorting data input by users or is it a tool to program database queries with? the name suggests the latter, but the function seems to be the former. suppose i want to create a page in my tiki that displays how many wiki pages contain the word "beer", with who edited that word in and when? can i do that with a tracker or with something else? wiki page: Trackers 137 2005-09-27 22:33:02

Using Font Awesome icons instead of content depending on the value of the field content


Tweaking the sample above and using font awesome (integrated in Tiki) you can display corresponding icons for a content.
In this demo case we have a tracker with a "gender" field that hold 2 values, "male" or "female". There is a "male" and a "female" icon in Font Awesome and as both use the same term we can assign it to a div type icon and class.

Copy to clipboard
{LIST()} {filter field="tracker_id" content="42"} {OUTPUT(template="table")} {column label="Title" field="title" sort="title"} {column label="Gender" field="gender"} {OUTPUT} {FORMAT(name="gender")}{DIV(type=i class=fa fa-{display name="tracker_field_gender"})}{DIV}{FORMAT} {LIST}

Editable inline sample using the table template

Copy to clipboard
{column label="First Name" field="firstName" mode=raw} ... {FORMAT(name="firstName")}{display name="tracker_field_firstName" format=trackerrender editable=inline}{FORMAT}

Editable inline sample in a smarty (or wiki) template

In this wikiplugin embedded in a smarty (or wiki) template the field is set to be editable inline (note: format="trackerrender" is required ad well as the Inline editing (found in admin control panels=>trackers)

Copy to clipboard
{wikiplugin _name=list} {literal} {filter content="2" field="tracker_id"} {output(template="mytemplate.tpl")} {ALTERNATE()} empty {ALTERNATE} {FORMAT(name="name")}{display name="tracker_field_name" editable="inline" format="trackerrender" default=""}{FORMAT} {/literal} {/wikiplugin}


So the 2nd column uses a FORMAT plugin where the contents of the field in question, tracker_field_data, is used as the class for a div but the default (used if the data field is empty) is set to be the bootstrap class "hidden" so the contents, the check mark, only appears if there is some data.

Obviously if the data is the name of some other class weird stuff might happen, but for most usual cases, it works as expected and saves having to make a new smarty template just for this simple list.

(Tip and example taken from a message from JonnyB in the developers list - thanks!)

Using Font Awesome icons instead of content depending on the value of the field content


Tweaking the sample above and using font awesome (integrated in Tiki) you can display corresponding icons for a content.
In this demo case we have a tracker with a "gender" field that hold 2 values, "male" or "female". There is a "male" and a "female" icon in Font Awesome and as both use the same term we can assign it to a div type icon and class.

Copy to clipboard
{LIST()} {filter field="tracker_id" content="42"} {OUTPUT(template="table")} {column label="Title" field="title" sort="title"} {column label="Gender" field="gender"} {OUTPUT} {FORMAT(name="gender")}{DIV(type=i class=fa fa-{display name="tracker_field_gender"})}{DIV}{FORMAT} {LIST}

It will display a
if the content of the field = male and a
if the content of the field = female.


When you use a template to display your plugin list you want other item related or linked to the item to open using the same template (or another it doesn't matter) but not to open the trackers built-in system. For this you need to enable the Alias feature and set it to use the template to display the tracker item, "record-" for this sample.

When you use an item link to link an item to other item (related, friend of, etc.) this is a kind of a problem.
Item link has 2 option to display and item link. Value and Link.
Value display the id of the content (ie: 6).
Link display the value of the content linked to the tracker item (ie: Bernard).

Your link should be like:

Copy to clipboard
[record-6|Bernard]

So it open the item "Id6" in the "record-" template showing the value "Bernard" for the link.
To achieve this you need to create and use 2 row.

Copy to clipboard
{FORMAT(name="name")}{display name="tracker_field_contact" format=trackerrender}{FORMAT} {FORMAT(name="id")}{display name="tracker_field_contact"}{FORMAT}


The first one with format=trackerrender will display the content of the tracker Item Link field as it is shown in the tracker (Bernard).
The second one without the format=trackerrender will show the real value for this field (6).

The assemble your link as follow:

Copy to clipboard
[record-{display name="id"}|{display name="name"}]

It will complete the trick and open the item 6 using the record- template while the link displayed will show the right value, Bernard.

Using smarty to format variables (from Tiki 26+)

Instead of using wiki format, you can specify template or tplwiki arguments to refer to a smarty template stored in a file or a wiki page. See PluginList-output-control-block#Parameters for more info on accepted values.

All the LIST Plugin control blocks