Category: Trackers

Can be duplicated on tikiwiki.org

start and end time in tiki-calendar.php (add or edit mode) takes the GMT time, even if the current user is in local time.

This is not such a problem when adding an event because the user is expected to choose the time.

However, when someone edits an existing event, the start & end times are reverted back to GMT. When the user saves the event, the time is several hours off.

--

Related:
Also affects tiki-edit_article.php, tiki-edit_submission.php and tiki-view_tracker.php (when submitting a tracker)

To duplicate the bug, you must be in a different timezone than your server.

This is a duplicate of the bug report submitted by Xavi...

{syntax type="tiki" editor="plain"}
If you filter on a category field in trackers, you cannot edit any viewed tracker items. The system returns a SQL error because filterfield is set, and filtervalue is null. If you filter on other fields, you can save, with no errors.

I have traced the problem to the calling of trklib->list_items (this holds the query that fails). This function is used to call and order the other tracker items for easy pagination of the filtered tracker items after a save.

However, the real problem is that $_REQUST['filtervalue'] and $tryfiltervalue get lost in tiki-view_tracker_item.php when the save submit action is done on the form. Other URL query parameters appear to be stored as hidden fields on save action in tiki-view_tracker_item.

For whatever reason, non-array filtervalue fields (e.g. plain text fields) are remembered and thus the pagination and call to list_items works just fine.

However, when there is an array filtervalue (like there is with category fields), then filtervalue gets lost on the save action, and the save fails on a malformed query.

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

Email a periodic digest (report) of a tracker activity (new open, and changed to pending or closed).

For sites with low activity but high interest in the users on a specific tracker activity, such as Barter networks ( http://intercanvis.net and similar) such feature is needed for users, who register, but then, after a few months, they don't visit the tiki site any more to see notifications of changes (and they didn't know how to browse the categ. tree to select which categories to watch.

However, other (closed source) bartner software sends a monthly digest to registered users with new items added to each tracker. And this would be very welcome by users (usability)

You can't assign an empty category to the tracker category type field. This would come very handy in connection with the Autocheck-feature I RFEd before..
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=246&show=view&status=op&trackerId=5&sort_mode=f_41_desc

Top
|
|---1 Stuff
|
|---2 More Stuff

If you for example assign parentId=1, then you don't get a Checkbox with Stuff, but you get two boxes with Stuff and More Stuff - Tiki jumps back to the higher level, that's not empty.

I have a simple tracker with two fields:
* __Name __(type = text field)
* __Logo __(type = files)

I have 2 items in the tracker:
||Tracker ID|Name|Logo
1|Test1|{img fileId="1908" thumb="box"}
2|Test2|||

I have a simple wiki page with a TRACKERLIST plugin:
{CODE()}
{trackerlist trackerId="1" fields="1:2" sort_mode="f_1_asc" list_mode="y" wiki="TestingTPL"}
{CODE}

I have a simple wiki template page (__TestingTPL__):
{CODE()}
Name: {$f_1}
Logo: {if !empty($f_2)}{$f_2}{else}EMPTY{/if}
---
{CODE}

I __expect__ the output of the wiki page with the TRACKERLIST plugin to be:
{CODE()}
Name: Test1
Logo: {img fileId="1908" thumb="box"}
---
Name: Test2
Logo: EMPTY
{CODE}

But I actually get this:
{CODE()}
Name: Test1
Logo: {img fileId="1908" thumb="box"}
---
Name: Test2
Logo:
{CODE}

When I examine the generated HTML for __Test2__ it has the Logo field as __ nbsp;__

The FILES type field is being filled with ~np~nbsp; ~/np~ even when there is no uploaded file for the tracker item.

Trackers are the de facto way Tiki treats data collected from users. These are personal data that directly fall under ''__many__'' legislative and other regulations. Primarily the EU GDPR, but -here- more importantly under the PCI, if they contain credit card or other payment data like bank account numbers.

Under PCI DSS credit card data must not be kept in the same database as personal data. They must be separated on all levels of processing, from technical to organizational. They cannot be processed under group logins, logins to systems carrying card data must use personalized login accounts etc. et. al.

There is one problem with trackers here: To my knowledge all trackers are kept in one DB, which is the DB the Tiki runs from. In order to comply with PCI DSS it will be necessary to have trackers with card data in a separate DB...

https://www.pcisecuritystandards.org/

Thanks
hman

Hi Dev's!

First of all, sorry my english... Is not my natural language.

My fist post here!

I have another contribuition, but stay for another post. ;)

My setup:

Tiki 18.2
PHP 7.2.10-0ubuntu0.18.04.1
Linux 18.04 LTS

In a page with PLUGINTRACKER, if a itemID is passed in URL the follow error message is diplayed:

''Fatal error: Uncaught Error: [] operator not supported for string''

Cause:
In PHP 7+ (I cannot find exactly version) is more restritive in array initialization.

Source affected:
lib/wiki-plugins/wikiplugin_tracker.php

Solution:
In line 1498 the array __$filter__ is initialized as string, and utilized as array, causing the error. Below the affected source snippet with corretion (line 1498)

1495 } elseif (! empty($itemId)) {
1496 if (isset($fields) && empty($wiki) && empty($tpl)) {
1497 $fl = $fields;
1498 $filter = []; // $filter = ''; <- original
1499 foreach ($flds['data'] as $f) {
1500 if (in_array($f['fieldId'], $fl)) {
1501 $filter[] = $f;
1502 }
1503 }
1504 } else {

In my setup, after corretion the error do not more appear.

I hope have helped in something!

Salutes from Brazil!

I created a tracker with several fields, mainly rating, textareas, dropdown, user selector, date selector.
||
Id position name type options isMain Tbl vis Searchable Public Hidden Mandatory
291 0 Rating system -2,-1,0,1,2 - y - y - -
293 edit 20 Descricpión de la incidencia textarea 1,60,5,1000 y y y y n y remove
294 edit 21 Tipología de redacción colaborativa drop down elegir uno,documentos de ofimática solo... n y y y n y remove
295 edit 22 Comentarios textarea 1,60,5,1000 n y y y n n remove
297 edit 27 Dia jscalendar n y y y n n remove
296 edit 30 Informante user selector 1 n y y y n n remove||

Called all fields from a wiki TRACKER plugin (the data field and user selector are not shown through plugin, even if configured as "public"), and submit some data (required and visible fields).

Then I got this error:

{CODE()}
Warning: mysql error: Duplicate entry '240-296' for key 1 in query:

insert into `tiki_tracker_item_fields`(`itemId`,`fieldId`,`value`) values(?,?,?)


in /var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/tikidblib.php on line 134


Context:
File /tiki-index.php
Url /tiki-index.php?trackit=10&page=prova&refresh=1&track%5B293%5D=prueba&track%5B294%5D=Wiki&track%5B295%5D=prueba&authorfieldid=296&track%5B296%5D=Xavi&action=Envia-ho
Query:
insert into `tiki_tracker_item_fields`(`itemId`,`fieldId`,`value`) values(?,?,?)
Values:
0 240
1 296
2 Xavi
Message:
Error Message Duplicate entry '240-296' for key 1


array(6) {
[0]=>
array(6) {
["file"]=>
string(65) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/tikidblib.php"
["line"]=>
int(84)
["function"]=>
string(9) "sql_error"
["class"]=>
string(10) "trackerlib"
["type"]=>
string(2) "->"
["args"]=>
array(3) {
[0]=>
&string(80) "insert into `tiki_tracker_item_fields`(`itemId`,`fieldId`,`value`) values(?,?,?)"
[1]=>
&array(3) {
[0]=>
int(240)
[1]=>
int(296)
[2]=>
string(4) "Xavi"
}
[2]=>
&bool(false)
}
}
[1]=>
array(6) {
["file"]=>
string(75) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/trackers/trackerlib.php"
["line"]=>
int(619)
["function"]=>
string(5) "query"
["class"]=>
string(10) "trackerlib"
["type"]=>
string(2) "->"
["args"]=>
array(2) {
[0]=>
&string(80) "insert into `tiki_tracker_item_fields`(`itemId`,`fieldId`,`value`) values(?,?,?)"
[1]=>
&array(3) {
[0]=>
int(240)
[1]=>
int(296)
[2]=>
string(4) "Xavi"
}
}
}
[2]=>
array(6) {
["file"]=>
string(87) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/wiki-plugins/wikiplugin_tracker.php"
["line"]=>
int(69)
["function"]=>
string(12) "replace_item"
["class"]=>
string(10) "trackerlib"
["type"]=>
string(2) "->"
["args"]=>
array(4) {
[0]=>
&string(2) "10"
[1]=>
∫(0)
[2]=>
&array(1) {
["data"]=>
array(6) {
[0]=>
array(3) {
["fieldId"]=>
int(293)
["value"]=>
string(6) "prueba"
["type"]=>
int(1)
}
[1]=>
array(3) {
["fieldId"]=>
int(294)
["value"]=>
string(4) "Wiki"
["type"]=>
int(1)
}
[2]=>
array(3) {
["fieldId"]=>
int(295)
["value"]=>
string(6) "prueba"
["type"]=>
int(1)
}
[3]=>
array(3) {
["fieldId"]=>
int(296)
["value"]=>
string(4) "Xavi"
["type"]=>
int(1)
}
[4]=>
array(4) {
["fieldId"]=>
string(3) "296"
["value"]=>
string(4) "Xavi"
["type"]=>
string(1) "u"
["options"]=>
int(1)
}
[5]=>
array(2) {
["fieldId"]=>
bool(false)
["value"]=>
string(5) "prova"
}
}
}
[3]=>
&string(1) "o"
}
}
[3]=>
array(4) {
["file"]=>
string(63) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/tikilib.php"
["line"]=>
int(4117)
["function"]=>
string(18) "wikiplugin_tracker"
["args"]=>
array(2) {
[0]=>
&string(156) "Formulari per informar d'incidències durant la redacció colaborativa de la "Guia Erasmus", segons la tipologia de redacció colaborativa emprada"
[1]=>
&array(7) {
["trackerId"]=>
string(2) "10"
["fields"]=>
string(23) "291:293:294:295:297:296"
["action"]=>
string(8) "Envia-ho"
["showtitle"]=>
string(1) "y"
["showdesc"]=>
string(1) "y"
["showmandatory"]=>
string(1) "y"
["embedded"]=>
string(1) "y"
}
}
}
[4]=>
array(6) {
["file"]=>
string(63) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/tikilib.php"
["line"]=>
int(4399)
["function"]=>
string(11) "parse_first"
["class"]=>
string(7) "tikilib"
["type"]=>
string(2) "->"
["args"]=>
array(3) {
[0]=>
&string(752) "{img src="img/wiki_up/Categories-ADMIN-001.png" }

img src="img/wiki_up/Categories-ADMIN-001.png"

{TRACKER(trackerId=>10,fields=>291:293:294:295:297:296,action=>Envia-ho,showtitle=>y,showdesc=>y,showmandatory=>y,embedded=>y)}Formulari per informar d'incidències durant la redacció colaborativa de la "Guia Erasmus", segons la tipologia de redacció colaborativa emprada{TRACKER}

{TRACKERLIST(trackerId=>10,fields=>291:293:294:295:297:296,showtitle=>y,showlinks=>y,showdesc=>y,showinitials=>y,showstatus=>n,status=>opc,sort_mode=>asc,max=>3,filterfield=>294,filtervalue=>documentos de ofimática solo acesibles en local,exactvalue=>)}Notice{TRACKERLIST}"
[1]=>
&array(2) {
["data"]=>
array(0) {
}
["key"]=>
array(0) {
}
}
[2]=>
&array(2) {
["data"]=>
array(0) {
}
["key"]=>
array(0) {
}
}
}
}
[5]=>
array(6) {
["file"]=>
string(62) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/tiki-index.php"
["line"]=>
int(401)
["function"]=>
string(10) "parse_data"
["class"]=>
string(7) "tikilib"
["type"]=>
string(2) "->"
["args"]=>
array(2) {
[0]=>
&string(752) "{img src="img/wiki_up/Categories-ADMIN-001.png" }

img src="img/wiki_up/Categories-ADMIN-001.png"

{TRACKER(trackerId=>10,fields=>291:293:294:295:297:296,action=>Envia-ho,showtitle=>y,showdesc=>y,showmandatory=>y,embedded=>y)}Formulari per informar d'incidències durant la redacció colaborativa de la "Guia Erasmus", segons la tipologia de redacció colaborativa emprada{TRACKER}

{TRACKERLIST(trackerId=>10,fields=>291:293:294:295:297:296,showtitle=>y,showlinks=>y,showdesc=>y,showinitials=>y,showstatus=>n,status=>opc,sort_mode=>asc,max=>3,filterfield=>294,filtervalue=>documentos de ofimática solo acesibles en local,exactvalue=>)}Notice{TRACKERLIST}"
[1]=>
&string(1) "0"
}
}
}
{CODE}

{syntax type="tiki" editor="plain"}
I've just created a new page on a tiki 3.3 site with this content:
{CODE(wrap=1)}
{TRACKERLIST(trackerId="3",fields="41:42",sort="y",popup="43",stickypopup="n",showtitle="n",showlinks="y",showdesc="n",shownbitems="n",showinitials="n",showstatus="n",showcreated="n",showlastmodif="n",showfieldname="n",status="op",sort_mode="asc",max="15",more="n",moreurl="n",view="user",compute="42/sum:43/avg")}{TRACKERLIST}
{CODE}

That tracker exists, as well as fieldId's 41, 42 and 43.
And it produced this error:

{CODE(wrap=1)}
An error occured in a database query!

Context:
File tiki-index.php
Url tiki-index.php?page=Gradebook
Query:
SELECT tti.*, ttif.`value`, ttf.`type`, tti.`asc` as `sortvalue` FROM ( `tiki_tracker_items` tti INNER JOIN `tiki_tracker_item_fields` ttif ON tti.`itemId` = ttif.`itemId` INNER JOIN `tiki_tracker_fields` ttf ON ttf.`fieldId` = ttif.`fieldId`) INNER JOIN `tiki_tracker_item_fields` ttif0 ON (ttif0.`itemId` = ttif.`itemId`) WHERE tti.`trackerId` = ? and (`status`=? or `status`=?) AND ttif0.`fieldId`=? AND ttif0.`value`=? GROUP BY tti.`itemId` ORDER BY `sortvalue` asc
Values:
0 3
1 o
2 p
3 41
4 Xavi
Message:
Built query was probably:
SELECT tti.*, ttif.`value`, ttf.`type`, tti.`asc` as `sortvalue` FROM ( `tiki_tracker_items` tti INNER JOIN `tiki_tracker_item_fields` ttif ON tti.`itemId` = ttif.`itemId` INNER JOIN `tiki_tracker_fields` ttf ON ttf.`fieldId` = ttif.`fieldId`) INNER JOIN `tiki_tracker_item_fields` ttif0 ON (ttif0.`itemId` = ttif.`itemId`) WHERE tti.`trackerId` = '3' and (`status`='o' or `status`='p') AND ttif0.`fieldId`='41' AND ttif0.`value`='Xavi' GROUP BY tti.`itemId` ORDER BY `sortvalue` asc
{CODE}

---


Sorry, just testing once more the issue related to normal users loosing the ability edit their own items

When I try to set permissions for galleries or other objects manually, I get an error.

See [http://tikiwiki.org/tiki-view_forum_thread.php?topics_offset=10&topics_sort_mode=lastPost_desc&forumId=4&comments_parentId=22138|Forum Link] for an other post and a screenshot of the error.

On Tiki19
Last update from SVN (19.0svn): Thursday September 27, 2018 12:59:03 IDT - REV 67702 (InnoDB)

I create a first tracker after enabling the feature.

It show the following error:
Field tracker_id does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_tracker_id.

It shouldn’t show and error.
Eventually an info about re-indexing but would be better to do the job (first tracker is likely to be done by a new guy).

When using a mathematical field I created several times in the past a field to calculate the age of someone using:
{CODE()}(round (div (sub (date) childrenBirthDate) 31536000 ) 1){CODE}

In Tiki 20.1 (from Git; no revision number found) it thrown an error:
~pp~Divide by zero on "0"~/pp~

{CODE()}(sub (date) childrenBirthDate){CODE}
is not throwing the error.

The error is coming from a test at "lib/core/Math/Formula/Function/Div.php".

Updated 04/04/2020 {sign user="Bsfez" datetime="2020-03-04T19:59:04+00:00"}
After upgrading to Tiki21 the workaround is not useable anymore.
It forbid the index rebuilt operation to complete and therefore the Tiki is broken.
See: https://dev.tiki.org/item7304-Change-in-condition-inside-a-calculation-field-breaks-rebuilt-index-operation-and-calculation

---
Update 20/05/2020 {sign user="Bsfez" datetime="2020-05-20T09:07:12+00:00"}
Found the culprit ! (and it is not directly related to calculation ?)
I have in this tracker an item list field that get info from another tracker so I need to use trackerrender to display the original value and not the value of the dropdown item.
__It is not used for any calculation, it is the employee ID__
To display it I use:
{CODE()}
{FORMAT(name="id")}{display name="tracker_field_timeworkEmployeeId" format="trackerrender" default=""}{FORMAT}
{CODE}
Used that way I got the error:
~pp~Divide by zero on "0" ~/pp~

If I change the format for:
{CODE()}
{FORMAT(name="id")}{display name="tracker_field_timeworkEmployeeId_text" default=""}{FORMAT}
{CODE}

The error is gone.

This error message is from Tracker Mathematical Calculations.

This warning keeps popping up - can the warning be eliminated? Or, if I am incorrect and my mathematical calculation should instead be corrected, please advise.

{CODE(colors="tiki")}(round(div(div(date (sub futureDate (date)))60)60)1){CODE}

See more notes I added in the 'Forums' here - https://tiki.org/forumthread75298--Divide-by-Zero-warning

This is important because Tiki 21x is the latest LTS.

Adding Jonny and Victor as it seems you both tried to correct the issue.

thanks,
Mike

Weird issue, maybe too specific of the tiki 12 configuration for a local chapter of the World Social Forum in Catalonia.
But this is serious, and since might happen to other tikis, I report it before I forget what happened, and which manual workaround allowed us to keep going.

We have set up a Tiki site to gather information on workshops in a tracker. The Tracker (through a Wiki page with PluginTracker) also shows the registration fields, in order to get a user registered with the information of the workshop they want to propose.

That wiki page is shown through an iframe in from a wordpress (yes, this is real life; main site was created first with Wordpress, and they only want to use Tiki for the tracker system, so far).

http://www.forumsocialcatala.cat/fscat2014/inscripcio-tallers-fscat2014/

{GROUP(groups="Registered")}This is using this tiki url inside:
http://2014clean.forumsocialcatala.cat/Inscripcions?cookietab=2

inside plugin group since I don't want robots to crawl the tiki directly
{GROUP}

Once the form was submitted, Tiki displayed a page that an error occurred ("did you check your db is up & running", etc)
Apache logs don't show anything rellevant.
Tiki logs indicate that the database table

__dbname.index_52d52c9cad158__

was missing. Checking the mysql db directly, I saw that another similar db table name was there:

__dbname.index_5305ecc55cd29__

I did clear the Tiki caches many times, rebuild the serch index many times, changed from mysqlfts to lucene (clear caches and rebuild index each time) and back, a few times. Even disabled the unified search index. (clearing tiki caches also), and no way, each time the new item was attempted to get added to the Tiki site:
* that error page was shown
* the tiki logs showed the message that __dbname.index_52d52c9cad158__ was missing
* the user got added, but not the tracker item with the workshop information.

I only know that the system worked well until Feb 14th (the date of the last valid item in the tracker). After that, I svn updated to recent revisions yesterday (maybe to r49950ish or similar, I don't know for sure), and today svn-updated again, to r49974. And that mysql table either dissapeared, or was rebuilt to a different name, or the code decided to look for a different name of table at the database.

---
Update: I admit, that this is too of an edge case.
I have not been able to reproduce in a clone of that db in my localhost, so I close this bug report. I hope this issue doesn't happen to anyone else. {sign user="xavi" datetime="2014-03-05T12:56:35+00:00"}

Set a tracker to display items with a wiki page template.
Don't create the template so it is missing.

When viewing a tracker items popup this (ugly) error.

{CODE()}Fatal error: Uncaught exception 'SmartyException' with message 'Unable to load template file 'promo_tpl' in 'tracker_pretty_item.tpl'' in /var/www/sites/xxx/xxx/subdomains/www/html/vendor/smarty/smarty/distribution/libs/sysplugins/smarty_internal_templatebase.php on line 127 SmartyException: Unable to load template file 'promo_tpl' in 'tracker_pretty_item.tpl' in /var/www/sites/xxx/xxx/subdomains/www/html/vendor/smarty/smarty/distribution/libs/sysplugins/smarty_internal_templatebase.php on line 127 Call Stack: 0.0020 1106896 1. {main}() /var/www/sites/xxx/xxx/subdomains/www/html/tiki-view_tracker_item.php:0 0.2151 29471160 2. Smarty_Tiki->display() /var/www/sites/xxx/xxx/subdomains/www/html/tiki-view_tracker_item.php:723 0.2151 29471896 3. Smarty_Internal_TemplateBase->display() /var/www/sites/xxx/xxx/subdomains/www/html/lib/init/smarty.php:348 0.2151 29472056 4. Smarty_Tiki->fetch() /var/www/sites/xxx/xxx/subdomains/www/html/vendor/smarty/smarty/distribution/libs/sysplugins/smarty_internal_templatebase.php:374 0.2152 29475872 5. Smarty_Tiki->fetch() /var/www/sites/xxx/xxx/subdomains/www/html/lib/init/smarty.php:229 0.2154 29476112 6. Smarty_Internal_TemplateBase->fetch() /var/www/sites/xxx/xxx/subdomains/www/html/lib/init/smarty.php:254{CODE}

Should display the item with the tracker standard view (no template).
Eventually display a small error to admin only.

After clicking on the save button on a modal the user is redirected to the page "undefined".
This happen since Tiki21 and it is working fine in Tiki20.

Tested on : tiki-21.0.RC1

To reproduce:
#Login as Admin
#Enable trackers and button plugin
# Create a tracker with a few fields (in the fade I pasted the export for the tracker and the fields)
+ {FADE(label="Tracker export")}
[TRACKER]
adminOnlyViewEditItem = n
autoAssignCreatorGroup = n
autoAssignCreatorGroupDefault = n
autoAssignGroupItem = n
autoCopyGroup = n
autoCreateCategories = n
autoCreateGroup = n
defaultOrderDir = asc
defaultOrderKey = -1
defaultStatus = o
doNotShowEmptyField = n
fieldPrefix = contact
newItemStatus = o
oneUserItem = n
orderAttachments = created,hits,filesize
publishRSS = n
ratingOptions = -2,-1,0,1,2
saveAndComment = n
sectionFormat = flat
showAttachments = n
showComments = n
showCreated = n
showCreatedBy = n
showCreatedView = n
showLastComment = n
showLastModif = n
showLastModifBy = n
showLastModifView = n
showRatings = n
showStatus = n
showStatusAdminOnly = n
simpleEmail = n
useAttachments = n
useComments = n
useFormClasses = n
useRatings = n
userCanSeeOwn = n
userCanTakeOwnership = n
writerCanModify = n
writerCanRemove = n
writerGroupCanModify = n
writerGroupCanRemove = n
trackerId = 1
name = Contact
descriptionIsParsed = n
created = 1584087369
lastModif = 1584087369
{FADE}
+{FADE(label="Field Export")}
[FIELD1]
fieldId = 1
name = Name
permName = contactName
position = 10
type = t
options =
isMain = y
isTblVisible = y
isSearchable = n
isPublic = y
isHidden = n
isMandatory = y
description =
descriptionIsParsed = n
[FIELD2]
fieldId = 2
name = Country
permName = contactCountry
position = 20
type = y
options =
isMain = n
isTblVisible = n
isSearchable = n
isPublic = y
isHidden = n
isMandatory = n
description =
descriptionIsParsed = n
[FIELD3]
fieldId = 3
name = Date
permName = contactDate
position = 30
type = j
options =
isMain = n
isTblVisible = n
isSearchable = n
isPublic = y
isHidden = n
isMandatory = n
description =
descriptionIsParsed = n
[FIELD4]
fieldId = 4
name = Image
permName = contactImage
position = 40
type = FG
options = {"galleryId":0,"filter":"","count":0,"displayMode":"","displayParams":"","displayParamsForLists":"","displayOrder":"","deepGallerySearch":0,"replace":"n","browseGalleryId":0,"duplicateGalleryId":0,"indexGeometry":"","uploadInModal":"y","image_x":"","image_y":"","addDecriptionOnUpload":"n","requireTitle":"n"}
isMain = n
isTblVisible = n
isSearchable = n
isPublic = y
isHidden = n
isMandatory = n
description =
descriptionIsParsed = n
{FADE}
# Populate the tracker with a few items
# Edit a page and create a pluginList with an edit button
+ In my sample I used a table output __with fixed values for editing the item 1 only__ (pasted below)
+ I tested with a link and a button to be sure
+{FADE(label="PluginList content")}
{LIST()}
{filter field="tracker_id" content="1"}
{pagination max="1"}
{OUTPUT(template="table")}
{column field="reference_1" label="Name"}
{column field="reference_2" label="Country" mode=raw}
{column field="reference_3" label="Date"}
{column field="reference_4" label="Photo" mode=raw}
{column field="reference_5" label="link" mode=raw}
{column field="reference_6" label="button" mode=raw}
{OUTPUT}
{FORMAT(name="reference_1")}{display name="tracker_field_contactName"}{FORMAT}
{FORMAT(name="reference_2")}{display name="tracker_field_contactCountry" format=trackerrender}{FORMAT}
{FORMAT(name="reference_3")}{display name="tracker_field_contactDate" format=date}{FORMAT}
{FORMAT(name="reference_4")}{display name="tracker_field_contactImage" format=trackerrender}{FORMAT}
{FORMAT(name="reference_5")}<a href="tiki-tracker-update_item?trackerId=1&itemId=1&modal=1" class="btn btn-primary text-white click-modal">Edit</a>{FORMAT}
{FORMAT(name="reference_6")}{button href="tiki-tracker-update_item?trackerId=1&itemId=1&modal=1" _icon_name="edit" _class="btn btn-success text-white click-modal"}{FORMAT}
{LIST}
{FADE}

Your page should end with something like this:
{img fileId="1385" thumb="box"}

When you click on the link or the button you will have the "Update Item" modal.
*Close will bring back to the page (~~#090:GOOD~~)
*Preview won’t do nothing (~~#F90:I think it shouldn’t be here~~ don’t see how it will be used)
*Save will save but redirect the user to an "undefined" page (~~#F00:BROKEN~~)
+{img fileId="1386" thumb="box"}
+ Video : https://share.vidyard.com/watch/UCAew92XGPH4zHUQ3G2QbG?

Saving used to redirect to the page, same list, same result (if customSearch) in Tiki20.
Here a Tiki20 (using smarty template) with the same code for the button:
https://share.vidyard.com/watch/w8zwARp8C3X1aB4xFSiyma?

Should this be done with trackers with the new ((doc:Computed Tracker Field)) and deployed via the ((profile manager))?

tiki-admin_tracker_fields.php?trackerId=5

Select several fields

Choose "Export Selected"

And you will see only one field definition in the box

Export and the subsequent import of Field data is very valuable (and essential) for 'porting' a Tracker design from one TW instance to another.

But as the Tracker functionality has continued to expand, the amount of data that is made available in the Field import/export process has not kept up. e.g Description: Error message: etc. are not currently included.

This means that this data still needs to be typed in again and an existing Tracker design cannot be made available to another TW instance in a 'complete' way.



No longer relevant - 15th June 2013

Exporting a tracker does not work when selecting a custom default sort order field for the tracker.
Fields that do work :
itemId
Created
Lastmodif

All other fields will result in a csv file containing the error page html code.

It seems that the order by value in the SQL statement is not properly generated.


File tiki-export_tracker.php
Url tiki-export_tracker.php
Query:
select * from `tiki_tracker_items` tti where tti.`trackerId`=? order by `` desc

Values:
0 4
Message:

Built query was probably:
select * from `tiki_tracker_items` tti where tti.`trackerId`='4' order by `` desc

{syntax type="tiki" editor="plain"}
When exporting tracker items, the generated csv file contains a blank line after every 100 items.

...
100 "180";"48";"13-06-2005";""
101 "133";"1";"30-04-2005";"5"
102
103 "179";"47";"31-01-2005";"0"
104 "178";"46";"31-01-2005";""

Plugin TrackerIf doesn't seem to accept nesting so far, and we need it to allow customization of the interface to edit data with Pretty Trackers.

*If field_1 is A
** if field_2 is not empty, display value of field_2
** if field_3 is not empty, display value of field_3
** if field_4 is not empty, display value of field_4
** ...
* if field_1 is B
** if field_10 is not empty, display value of field_10
** if field_11 is not empty, display value of field_11
** if field_12 is not empty, display value of field_12
** ...

{CODE(ln="1")}
{TRACKERIF(test="(f_1='A')", ignore='n')}
{TRACKERIF(test="(f_2 ='')", ignore='n')} {ELSE} {$f_2|output} {TRACKERIF}
{TRACKERIF(test="(f_3 ='')", ignore='n')} {ELSE} {$f_3|output} {TRACKERIF}
{TRACKERIF(test="(f_4 ='')", ignore='n')} {ELSE} {$f_4|output} {TRACKERIF}
{TRACKERIF}
{TRACKERIF(test="(f_1='B')", ignore='n')}
{TRACKERIF(test="(f_10 ='')", ignore='n')} {ELSE} {$f_10|output} {TRACKERIF}
{TRACKERIF(test="(f_11 ='')", ignore='n')} {ELSE} {$f_11|output} {TRACKERIF}
{TRACKERIF(test="(f_12 ='')", ignore='n')} {ELSE} {$f_12|output} {TRACKERIF}
{TRACKERIF}
{CODE}

When using a user tracker to collect additional information per user during registration process, it would be great if you could specify to include that information in the user popup/mouseover.