Category: Wiki Plugin (extends basic syntax)

To see example, go to
http://hrsms-11204-5084.show.tikiwiki.org

There are two trackers.

Tracker1 is for books, with title, author, publisher and date.

Tracker2 is for owners of the books. It ties an owner ID to the book ID.
''In my actual case, the tracker has a user field type and the "My Books" page filters based on the current user. To simplify the problem for demonstration, the owner field is a simple numeric type and there is no user field in tracker2.''

There are 6 entries in tracker 1.
The entries in tracker 2 are for two people John (owner #1) and Jane (owner #2).

Go to http://hrsms-11204-5084.show.tikiwiki.org/tiki-index.php?page=Book+Owners and click on John or Jane below to see the books they own. Each has four of the six books. But when using a trackerlist inside a pretty tracker, only one item is returned. There is no change whether or not the inner trackerlist also uses a pretty tracker.

{syntax type="tiki" editor="plain"}
Just see ((All Patches)): content that is to be mouse-overed is breaking the page.

And on ((DogFood)), there is no mouse-over

There's a problem with the trackerlist plugin output sometimes not displaying due to an inline "visibility:hidden" rule, when Table Sorter isn't being used.

This is the syntax for the plugin:

{CODE()}{trackerlist trackerId="5" fields="26:27:30" showlinks="y" shownbitems="y" status="opc" max="-1" sortable="y" tsfilters="y"}{CODE}

With Table Sorter activated, no problem, when

sortable="y" tsfilters="y", ok (and table sorter gadgets showing)
sortable="n" tsfilters="n", ok (and no sorter gadgets)
sortable="y" tsfilters="n", ok (legacy sorter gadgets showing)
sortable="n" tsfilters="y", ok (and no sorter gadgets)

But with Table Sorter deactivated, when

sortable="n" tsfilters="n", ok (and no sorter gadgets)
sortable="n" tsfilters="y", ok (and no sorter gadgets)
sortable="y" tsfilters="n", no display
sortable="y" tsfilters="y", no display

So it seems with Table Sorter off and sortable set to y in the trackerplugin, there's a problem. This inline rule comes from line 64 of wikiplugin_trackerlist.tpl.

{CODE()}<div id="wptrackerlist{$listTrackerId}-{$iTRACKERLIST}-div" {if $tsOn}style="visibility:hidden"{/if} class="ts-wrapperdiv">{CODE}

If I comment out the inline CSS and its if statement, the trackerlist table appears normally in all the cases that I tested. Seems like there must be an error here unless there is some case where the trackerlist table would need to be hidden, which seems unlikely.

{syntax type="tiki" editor="plain"}
Using Popup inside plugin trackerlist sends a very big & faulty html to the browser. The file for a tracker of less than 20 rows has 80 MB.
FF, IE and Chrome have big problems with it.
Sometimes a crippled table is shown, sometimes nothing.
Heavy load on cpu.
To let it be not too easy:
The same setup worked for a while. But now it produces always the same problem on 3 browsers on 2 computers.

I could upload the html-file if someone wants to see it. It contains kind of valid start but somewhere has tons of ////. Seems to be some recursive content.

trackerlist trackerId="1" fields="1:12:6:9" popup="7" showlinks="y" showstatus="y" status="opc"

Version 6.2 german

{CODE(caption="Current")}
{TRACKERLIST(trackerId=>1,fields=>1:2:3, filterfield=>1, filtervalue=>"A")}{TRACKERLIST}
{CODE}


{CODE(caption="Suggested")}
{TRACKERLIST(trackerId=>1,fields=>1:2:3, filterfield=>1, filtervalue=>"A" or "B")}{TRACKERLIST}
{CODE}

The following code would show the value for tracker item ID #62:
{CODE()}
{TRACKERLIST(trackerId=>7,fields=>59,itemId=>62)}{TRACKERLIST}
{CODE}

We don't always need the field names when using a trackerlist. Especially if we are just listing one field.

A new parameter could be added:

showfieldname=>y|n default to yes (which is current behavior)

This could be used in conjunction with [tiki-view_tracker_item.php?itemId=938|Trackerlist Plugin: get results for a specific tracker item ID]. In which case, the following code could be used in a wiki page to show the value of field #59 for tracker item ID #62:
{CODE()}
{TRACKERLIST(trackerId=>7,fields=>59,itemId=>62,showfieldname=>n)}{TRACKERLIST}
{CODE}

Wiki pages could be built to include these dynamic fields. And the values could be updated via the tracker. A bit like the dynamic variables feature.

{syntax type="tiki" editor="plain"}
Seen problem on ! and ^

Ex.:
http://dev.tikiwiki.org/tiki-index.php?page=WYSIWYG

As seen here:
http://dev.tikiwiki.org/tiki-pagehistory.php?page=All%20Bugs&compare=1&oldver=18&newver=19&diff_style=minsidediff

I would like a trackerlist plugin report with a list of all bugs which are in category 56, 172, 57 or 174.

In some other cases, I would like a trackerlist report which intersects two categories (ex.: bugs and 1.9x)

It would be nice to have an optional tpl=>foo.tpl argument to TRACKERLIST to specify a different formatting template. I would rather not mess with the code or the regular template in order to provide a different style of display. (in my case, it would be a display, for just this one tracker...

A table like: Dept, Title, Description, items_list
and another: Name, Title, Phone, Email, Street, Fax, etc

Could display as:

Dept:
Title
(list-of-people-with-that title)
Title2
(list-of-people-with-that title)
Title3
etc
Dept2:

Getting away from the usual 'table' display. I would only want that format for one specific view of one specific tracker... which makes it seem like specifying an alternate template for the display would be useful.

(This is, of course, a trivial change that I can do here locally, but others may find the feature useful, so it would be nice if it was standard.)

If the field used for sort_mode is an item link, any initial selected results in zero items returned.

Steps to reproduce:

1) Create trackers:

Tracker "Names", id=1
Text Field "Name", id=1
Values:
"Fitzgerald,F. Scott" id=4
"Follett,Ken" id=5
"Grisham,John" id=6

Tracker "Titles", id=2
Text Field "Title", id=2
Values:
"Great Gatsby, The" id=1
"Dangerous Fortune,A" id=2
"Painted House, A" id=3

Tracker "Books", id=3
Item Link Field (2,2) "Title", id=3
Item Link Field (1,1) "Author", id=4
Values:
"Great Gatsby, The","Fitzgerald,F. Scott" id=7
"Dangerous Fortune,A","Follett,Ken" id=8
"Painted House, A","Grisham,John" id=9

2) Add trackerlist plugins to wiki

{CODE()}{trackerlist (trackerId=1, fields=1, showinitials=y, sort_mode=f_1_asc) /}

{trackerlist (trackerId=2, fields=2, showinitials=y, sort_mode=f_2_asc) /}

{trackerlist (trackerId=3, fields=3:4, showinitials=y, sort_mode=f_3_asc) /}{CODE}

3) Filter on "F" - you will see two authors and no titles or books (expected)
4) Filter on "G" - you will see one author, and one title, but no books. The book should have been listed also.

I did step (2) above on the home page of the show.tiki instance. To rule out interference between the 3 plugin instances on the same page, I also create separate wiki pages "Names", "Titles", and "Books" on the show.tiki instance. The behavior was the same.

You can see another example on our site:
http://www.hrsms.org/home/References

When trying to find a workaround, unexpected behavior was found in TrackerFilter. When the filter is 3/i (intials for title), clicking on a letter results in all titles with the letter anywhere in the string being returned. I would expect only those beginning with that letter. This has been added to the show instance to demonstrate.

{syntax type="tiki" editor="plain"}
1. create a tracker
2. create a wiki page with {TRACKERLIST} plugin for this tracker

Result = it works!

3. duplicate tracker from #1
4. Add some items to it (as it will be empty)
5. create a wiki page with {TRACKERLIST} plugin for duplicate tracker
making sure to select correct tracker id and field ids.

Result = the headings for the duplicate tracker are displayed,
but NO items are displayed - even though items exist
in the duplicate tracker.

Note: The {TRACKER} plugin works for both the original and
duplicate tracker. This problem makes it difficult to
create a Pretty Tracker based on a duplicate tracker.

{syntax type="tiki" editor="plain"}
adding a category filter to a trackerlist plugin gives an SQL error

Followed the steps described in : https://doc.tiki.org/PluginTrackerCalendar‎

However, the events (tracker items) do not get displayed on the Calendar, which is displayed by calling the TrackerCalendar plugin on a wiki page.

Tried the same thing on demo.tiki.org/tiki12 but got the same result.

{syntax type="tiki" editor="plain"}
((Dynamic Filter)) is broken in 2.0RC2

On IRC:
13.08.2007 03:03:11 [nkoth_] marclaporte: The reason why items don't appear in the tracker for page=cache is because those items have no rating, and the default sort mode as set in the admin...trackers is rating. It can't sort stuff with no rating so those are not shown.


Nelson is right on. See the 4 attached screenshots, in order.

1- Unrated_but_Categorized_tracker_item.jpg
2- Dev_Tracker_theme1.jpg
3- Rated_and_Categorized_tracker_item.jpg
4- Dev_Tracker_theme2.jpg

These were taken on 2007-08-13, with latest BRANCH-1-9 __after__ Nelson Ko (nkoth)'s recent fix to templates/tiki-plugin_trackerlist.tpl

http://tikiwiki.cvs.sourceforge.net/tikiwiki/tiki/templates/tiki-plugin_trackerlist.tpl?view=log&sortby=date&pathrev=BRANCH-1-9

Possibly related to doc/devtools/cleanCatTrackers.php which Sylvie has been using to periodically clean trackers up.

null rating and 0 is not the same thing.

----

Can you please retest in currently supported Tiki versions (e.g. Tiki12, ...)? Willing to clear the list of valid bug reports on rating... {sign user="xavi" datetime="2014-02-07T09:51:44+00:00"}

Categories are multi-select fields. So sorting is not possible. Trackerlist plugin should not offer to sort (now with clickable title)

When using a tracker to collect emails, it's very important that there be no typo.

When creating a new tracker item and when there are drop-down choices, the first choice is a blank field. This is the appropriate behavior.

However, when the field is mandatory, the first item on the list is automatically chosen. This is not OK because we can't be sure this was the person's choice (or they just didn't notice)

Here is a trackerlist report example:

{CODE()} {TRACKERLIST(trackerId=>11,fields=>194:202:197:205, status=>c, sort_mode=>f_194_asc, showinitials=>n, max=>400, showlinks=>n, filterfield=>218, exactvalue=>y)}{TRACKERLIST}
{CODE}


Now, what if I want to filter by all trackers items which have a value higher than x in field 218?

When using image filed type in trackers, all is OK in view tracker mode. Ex.:
http://themes.tikiwiki.org/tiki-view_tracker.php?trackerId=2


However, when using trackerlist plugin, we get things like:
img/trackers/4a630f4699e5a75fafbefe595d4585b2

As you can see here:
http://themes.tikiwiki.org/tiki-index.php?page=TrackerListTestTrollparty

The new plugin manager in 3.0 is much more intuitive. It helps uses build plugins with a javascript plugin, documents each syntax, show mandatory fields in bold and offers a global link to the documentation.

This is precisely what we would need for the trackers field type helper.

When editing new wiki page (normal edit mode) and trying to insert a wiki plugin from the Help plugins icon it does nothing when finding the plugin you want and clicking the plugin icon.

{syntax type="tiki" editor="plain"}
At https://dev.tiki.org/Wishlist if you try to sort by "last modified" then to display "all" status.
It showed an error.

Demo during the team dev session of wednesday 20251126.

I added two (2) 'CustomSearch' to a single page in separate sections and separate div id's and different data, the search data and result keeps defaulting to the last CustomSearch on the page. below is the scenario:


{CUSTOMSEARCH}
{CODE(caption="Custom Search 1 & 2:")}{CUSTOMSEARCH( tpl="firstCustomSearch.tpl" id="first_search")}
{filter field="tracker_id" content="2"}
 {output template="templates/first-template.tpl" pagination="y"}   
//output data 1

{CUSTOMSEARCH}

//Some texts and logics seprating them here

//In another section

{CUSTOMSEARCH( tpl="secondCustomSearch.tpl" id="second_search")}
{filter field="tracker_id" content="4"}
 {output template="templates/second-template.tpl" pagination="y"}   
//output data 2

{CUSTOMSEARCH}{CODE}

//Output

Searches in first_search form field defaults to data on 'output data 2' and displays result also in it's custom_search_result div. With this, it skips the data and search on 'output data 1' entirely.

Perhaps, the fact that they share same js 'customsearch' variable picks the last one, not sure.

Also, the inclusion of 'destdiv' parameter with different id's (of course) resulting to respective output data section enters an infinite JQuery loading blocking the data from being populated on the page. While a rename of 'destdiv' parameter to say 'destinationdiv' (undeclared parameter name, yes) populates the display without the blocking but doesn't affect the behavior of Customsearch (of course).

I hope I've been clear enough with this succinct explanation.

Let me know if you would want an elaborate one.