Category: Trackers

When I create a tracker field that whose label is composed of special characters (@@@@) or using exotic language those characters are omitted. In case of multilingual (all characters are exotic) only the "Field Prefix" is used. This result is an error (no error message, it fail) to create more than one field.

Meaning if I have a prefix like "survey" and I create fields like :

שם משפחה
שם פרטי
etc...

They all will have the same permaname, "survey" and this is not possible/allowed so after the first one is created it will fail.

This is a regression as previously the permaname in such case was built up using the field id (ie: survey_f12). I created an instance and it is easy to reproduce.

1/ An error should be displayed in case of duplicate permaname (note about omitted chars)
2/ In case all the character of a label are omitted it will better to put back the id as it was on previous version

{syntax type="tiki" editor="plain"}
When any tracker item such as a radiobutton or dropdown is set to editable by admin-only in the "Field is hidden?" tracker, the item is not visible through tracker plugin (only the name shows up)

Error appears in tiki 3.1 and after upgrade to 3.5 as well.

The same error happens when selecting "editable by admin only" in the dropdown menu or selecting a group in the "Editable by" box.

Using svn from May 8th. Last year it worked, afaik

The tracker field option "visible only by creator & admin" not working. I created a new item as a registered user, and that user cannot see that field on the items list.
http://moviments.net/cursos/tiki-view_tracker.php?trackerId=5&sort_mode=created_desc

I've changed the option to editable by admin only, in the mean time.

{syntax type="tiki" editor="plain"}
On a Tiki29 I'm using the trackers feature with the tracker field relations to link between 2 trackers.
If I read the tooltip, the online help and the documentation (https://doc.tiki.org/Relations-Tracker-Field) what is working to filter on a tracker should work with the tracker field relation "filter" parameter.

From the __tracker list items view__, I can use: type=trackeritem&tracker_id=2&_sort=tracker_field_actionsDate
This is working fine.

If I use this (and other variations) within __the filter field of the tracker field relations__, the html front and to insert/edit an item is broken for the tracker field relation.

I had a look at the code.
At lib/core/Tracker/Field/Relation.php I discovered (and updated the documentation)
By default the objects that can be selected are sorted using "title_asc" unless the "Format" field is not used.

If, in the options of the Relations tracker field, the "Format" field contain something, the option of the multiple select list of objects will use the first field in the "Format" field.

For exemple, using "({tracker_field_actionsDate}) {title}" will tell the sort to use the field "tracker_field_actionsDate".

BUT, the direction will stays "_asc" as this is hardcoded.
It should be possible:
# To select more precisely what field(s ?) should be used for sorting the objects
# It should be possible to use any direction, _asc or _desc.

In a tracker I can use a rules for an item link. (to hide a different field if the item link field contain one of several value for exemple).

If I set the parameter "Select multiple values" to yes, the rule is not working anymore.

The tracker fields table's ''overflow-x: hidden'' property isn't working because the table doesn't have a property ''"display: block"'' (or ''inline-block'' or ''flex''). This is noticeable when fixed-width is activated or when the browser viewport isn't wide.

As of Mar 8, 2026, the tracker fields table does display now . . . because the side columns have been removed along with all the pagetop navigation, etc. What was the plan here? If the original layout of the page could be restored and the display property of the table added, that issue would have been fixed.

I added this issue to the "Release Blocker" category because trackers are commonly used and the UI shouldn't be this broken.

On a tracker, when using the tracker field text prepend it works fine using the plugin tracker and trackerlist but not when using the plugin list.

Without using format=trackerrender the content for prepend or append doesn’t display in the plugin list.
IE : 16

Using format=trackerrender it will show the html code.
IE: 16~~#090:<span class="formunit">hr</span>~~

Using format=trackerrender and mode=raw it will show properly the append and prepend.
IE: 16~~#090:hr~~

But the content for prepend and append is displayed with the default value.
IE: NA~~#090:hr~~ (NA is the default value).

Tracker field text-area flow over the field name if using wysiwyg and same row=no in a tracker plugin.

{img fileId="1080" thumb="box"}

There is an instance to check it:
http://bsfez-11581-6093.show.tikiwiki.org/tiki-index.php

{flash type="url" movie="display287" width="866" height="277"}

To be used with Google Maps & Tiki Maps to show locations of tracker items.

For example, the venues of phpbeer.com:
http://phpbeer.com/tiki-view_tracker.php?trackerId=1

Text areas are nice. But wiki pages with history are even nicer.

Not sure how it could done though...

I'm scanning and editing items from the tracker 5.
The field "submitted by" is set on "Creator".
{img fileId="1609" thumb="box"}

At https://dev.tiki.org/tracker5 original submitted-by creator is displayed

At https://dev.tiki.org/User I see my user everywhere (field 54 => submitted-by)
{img fileId="1610" thumb="box"}

No more free time to test but it may be related to the item I close.

I have created an tracker with the google maps field.

When I try to add an location with the help from the "Google Map Locator" it doesn't have a "back" button and doesn't save any data back to the form/tracker.

URL generated by the tracker to Google Map Locator:
tiki-gmap_locator.php?for=item&itemId=&trackerId=&fieldId=3


{img src=show_image.php?name=map_locator_from_tracker.png&galleryId=1 }

At https://tiki.org/Contact-Us we have 2 fields with a regex validation.

__Subject__ that is a text field where validation using a regex code is working.

__Feedback__ that is a textarea using the same regex code (I know carriage return is missing I use the same pattern for comparison purpose) is not working even if entering a single english word.

An empty message error (orange background) is displayed and I can’t submit the form.
I removed it in the validation for now of course.

__To reproduce:__ Go to https://tiki.org/tracker24, fields, edit Subject field.
Copy regex pattern and set the same parameters to the Feedback field.
Go to https://tiki.org/Contact-Us try...

Tracker field with Multiple selection list cannot be displayed in mobile mode, in 12.x

(untested in 14.x)

See it reproduced in:
http://xavi-9794-5642.show.tikiwiki.org/tiki-index.php
u: admin
p: 12345

# Switch to mobile mode (see link at the bottom on central column of page).
# choose "case A", and then,
# try to see the values for the field: "Case A. Multiple Selection List". Only one is shown.

Create a tracker, create a field in the tracker of the type "items list", go see this tracker's items, see notices like:

Notice: Undefined offset: 2 in /lib/trackers/trackerlib.php on line 486

Notice: Undefined index: in /lib/trackers/trackerlib.php on line 486

{syntax type="tiki" editor="plain"}
For tracker items, displaying the item shows the current date and time for the fields "created" and "lastModif".

I have checked the DB values, and the proper values are stored in the database.

db values :
created : 1265627980
lastmodif : 1265627980

value : 2010-02-08, 11:19:40
Date displayed when viewing tracker item : vrijdag 12 Feb, 2010 10:16:22
(= current date / time)

when listing tracker items, the proper date is shown for all the tracker items.
The problem occurs only when viewing a tracker item.

tracker fields should have a description so we could provide users with an explanation on how to fill out the forms.

Plus: Using labels for accessibility

Ex.: Data type : what do my 5 choices mean?

Tracker fields need more attributes for presentation and usage. These new attributes should include:

* Editable by ...
+ Is the field editable? Who by (users/groups)? Non editable fields might include "assigned to" or "author" fields. It may be that users cannot assign calls, but the group "call handlers" can. __done in 1.9.x__
* Next Field to right
+ Move the "1," type option functionality into the field attributes so that any field can be placed n the right of any other field. Very useful for presentation! __great idea, not done__
* Viewable by ...
+ Much like "Editable by...", hide fields from some people. A support call, for example, may have a field called "work done" which the assignee uses as a notepad for other support staff. This may not be suitable for end-user viewing! __done in 1.9.x__

That said, Trackers are really good as they are ;-)

Tracker fields of Radio buttons and multiple selection pre-select value 0 when it's one of the options even if not manually set as default

Set as options for that tracker field: 1,2,3,4, and no value is pre-selected (expected behavior)

Set as options for that tracker field: 0,1,2,3,4, and value 0 is pre-selected (wrong behavior; no value should be preselected, since no value is repeated twice)

Workaround (for radio buttons): 0,1,2,3,4, ,
(note that a space is set as option, twice, after value 4).

For multiple selections this workaround is not valid, since value 0 is also pre-selected.

Reproduced here:
http://xavi-9794-5599.show.tikiwiki.org/tiki-view_tracker_item.php?itemId=1&cookietab=2

u: admin
p: 12345

See fields 5 (radio button) and 6 (multiple select)
---
{BOX()}
Update: {sign user="xavi" datetime="2015-03-26T09:37:35+00:00"}
Bug still alive, it seems jonny. I svn-up'ed to Thursday March 26, 2015 09:25:10 CET - REV 54744, and new items from your new tracker show a default value of "0" preseleected for the radio button, even if no value should be pre-selected according to the configuration.
See:
http://xavi-9794-5599.show.tikiwiki.org/tiki-ajax_services.php?controller=tracker&action=insert_item&trackerId=2&modal=1

And the radio button field definition ([http://xavi-9794-5599.show.tikiwiki.org/tiki-ajax_services.php?trackerId=2&fieldId=9&controller=tracker&action=edit_field]) still has as options: "0,1,2,3,4", so no pre-selection is expected, but "0" is pre-selected.
{BOX}

On Tiki23 in a tracker I set a "Text Field" and enter in the "Options for Text Field".
The parameter "Same Row" is the first (second if you use multilingual)

On the same tracker I set an "Text Area Field" and enter in the "Options for Text Area".
The parameter "Same Row" is at the bottom

This is not a good UX.
Things, like parameter names and positions, should be the same anywhere so the user feel comfortable and is not confused.

If I set a rule that check the content of a track field item link I can’t use the label of the option (displayed) and I need to indicate the value of the option (in the code).

IE :
<option value="5468">Paris</option>

Paris won’t work for the rules condition but "5468".

Tracker fields textarea content wiki parsing doesn't work the same as wiki page content parsing when using a page as a Smarty template with the ''wiki'' Smarty block. For example consider we have a textarea field and this wiki syntax in the page named "User Profile TPL":
{CODE()}{wiki}{$f_358}{/wiki}{CODE}

The code above indicates we want the field value to be wiki parsed using the Smarty wiki block.

This is the code to reproduce using PluginTrackerlist (I know it is not PluginList ;-) ... but the wiki parsing should behave everywhere in Tiki the same no matter what you prefer to use):
{CODE()}{trackerlist trackerId=38 list_mode=csv view=user wiki="User Profile TPL"}{CODE}

__The input:__
{CODE()}Lorem ipsum dolor sit amet, consectetur adipiscing elit. In quis orci ante. Aliquam sit "amet libero" vitae turpis mattis eleifend.

* meh 50%
* 123
* blah blah

Maecenas sodales felis sed magna cursus, eu ultrices metus scelerisque. Vivamus viverra ipsum aliquet commodo mollis.{CODE}

__The expected result:__
{HTML()}<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. In quis orci ante. Aliquam sit "amet libero" vitae turpis mattis eleifend.</p>
<ul>
<li>meh 50%
<li>123
<li>blah blah
</ul>
<p>Maecenas sodales felis sed magna cursus, eu ultrices metus scelerisque. Vivamus viverra ipsum aliquet commodo mollis.</p>{HTML}

__The actual result:__
{HTML()}<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. In quis orci ante. Aliquam sit """"amet libero"""" vitae turpis mattis eleifend.<br /><br />* meh 50<br />%* 123<br />* blah blah<br /><br />Maecenas sodales felis sed magna cursus, eu ultrices metus scelerisque. Vivamus viverra ipsum aliquet commodo mollis.{HTML}

__Reproduced on the show instance__: http://luci-199-7045.show.tikiwiki.org/
(use show:show as user:password and for admin login use admin:12345 to play with it)

In a tracker you can use field type Header to set informal text (https://doc.tiki.org/Header-Tracker-Field)

In tracker you can also use fields that are looking for information from other tracker and other field like item link, item list, dynamic item list, etc. (https://doc.tiki.org/Tracker-Field-Type)

For example, in dynamic item list I can actually for the parameter "Field ID (Other tracker)" fields from the other tracker that are field type header.

Displaying those field type in a selector doesn’t make sense.

Using 1.10cvs code from mid june 2007

I created several trackers. Enabled RSS for individual trackers. Created rss modules for two individual trackers (rss 1 and rss 2).
Granted common permissions for anon. (view, ...), and most tracker permissions for Registered group.

Added a call to rss plugin within a wiki page:
{CODE()}
{rss id=1}

{rss id=2}
{CODE}

When viewing the page as registered, I see:

^
Tiki RSS Feed Error Message: Permission denied you cannot view this section
^

Did I miss any special perm to be granted for registered? A bug?

(I granted all perms from tracker section - to them, or inherited from anonymous - except for tiki_p_admin_tracker)