Category: 25.x

On a Tiki 24 and Tiki 25 I use a tracker with 2 date tracker field (date picker).
* Start date
* End date

If I choose a start date and a end that is crossing a year it subtract a day from the start date and the end date.

See: {mediaplayer src="display1804"}

This was in use as is since Tiki21 or Tiki22 and they were no noticeable issues even after upgrading from Tiki24 to Tiki25. This is a regression from inside Tiki25 branch.

On a tracker I have items with an itemLink and a dynamicList depending of this itemLink.
Both are set to filter "open" items.

The itemLink (parent) has its parameter "Cascade actions" set to "No".

''Elements to cascade when the master is updated or deleted. Categories may conflict if multiple item links are used to different items attempting to manage the same categories. Same for status.''

At the time of the creation of an item I selected a value from a parent tracker for the itemLink and one of the possible value for the dynamicList.

At that time all items (children and parents included) were open.

As it is an "event" selection for a trackeritem. (holiday selection).
When the event time was over I close the parent item so user can't select it anymore knowing that the "Cascade actions" was set to "No". This was in use as is since Tiki21 or Tiki22 and they were no noticeable issues even after upgrading from Tiki24 to Tiki25.

Recently I have issues when rebuilding the index and I found out that all children values were gone.
The parent itemLink is now close.
The child itemLink has been lost its value (changing the filter doesn't allow to retrieve the previous value)
The dynamicList that is dependent of the itemLink above has also lost its value.

Rebuilding the index display an error about empty values. Reported at: https://dev.tiki.org/item8437-Trackers-Dynamic-List-field-Dynamic-List-fields-throws-error-when-rebuilding-the-index-if-its-parent-field-has-no-value

{mediaplayer src="display2073"}

https://doc.tiki.org/Dynamic-items-list

This field is looking to a value of another field "parent" to display a list of value(s).

In the following video you can see that the field 522 is a dynamic List field that depend of the field 521 to display a value.

The field 521 is not used for this item and has an empty value (which should be possible).

However the field 522 logic doesn't understand there are were the parent field can be empty.

{mediaplayer src="display2071"}

This is an interesting case that complete the diagnostic of a previous report (https://dev.tiki.org/item8440-Trackers-Dynamic-List-and-Item-Link-fields-Field-value-is-lost-after-parent-item-changed-status-cascade-parameter-not-applied)

In this case we have an item with a dynamic field, parameter status filter set to "all".
That rely on an item link in the same tracker, parameter status filter set to "all".

The parent item from the other tracker has been closed as it is not in use anymore.
The data is displayed correctly and nothing is lost however the index:rebuilt console command report a new "NOTICE" about Undefined index: REQUEST_METHOD.

It was ok before the Dynamic List field code was improved.

{mediaplayer src="display2076"}

I set a low importance for this report but it should help diagnosing what is going on with the dynamic list field.

On a Tiki24 and Tiki25 I use 2 trackers to create an item in a third tracker.

Tracker A : Store the holidays name, their start/end dates (user display)and an item list of days from Tracker B.
Tracker B : Store each date as item for a specific Holiday, The name (item link from tracker A) and the date selected.
Tracker C : Store orders, user select a Holiday (item link) and a list of available days is proposed (dynamic item list with items from Tracker B)

It has been used for years (since 2018 with the different Tiki versions)
It was working fine with Tiki25 in March 2023.
I suspect that a commit related to this tracker field was made the dynamic item list in Tracker C is not working (not populated) anymore.

https://gitlab.com/tikiwiki/tiki/-/merge_requests/2500
Now I beleive that it has been backported to Tiki24: https://gitlab.com/tikiwiki/tiki/-/merge_requests/2511


Test videoshoot using Tiki24.3 (last update in December). As we can see in that video the dynamic list field is populated properly (I don't even had to refresh the index)
{file type="gallery" fileId="2045" showicon="y"}

Test videoshoot using Tiki25 (last update 19/04/2023). As we can see in that video the dynamic list field is empty and not populated properly (I did rebuilt the index)
{file type="gallery" fileId="2046" showicon="y"}

I worked on a Tiki25 that wasn't updated since the 5th of April 2023.
The Search Indexer console.log wasn't displayed any error when rebuilding the index, see below:

^
2023-05-04T06:02:36+00:00 INFO (6): addDocument trackeritem 69 {"memoryUsage":"32.0 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:02:36+00:00 INFO (6): addDocument trackeritem 70 {"memoryUsage":"32.0 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:02:36+00:00 INFO (6): addDocument trackeritem 298 {"memoryUsage":"32.0 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:02:36+00:00 INFO (6): addDocument trackeritem 326 {"memoryUsage":"32.0 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:02:36+00:00 INFO (6): addDocument trackeritem 330 {"memoryUsage":"33.5 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:02:36+00:00 INFO (6): addDocument trackeritem 355 {"memoryUsage":"33.5 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:02:36+00:00 INFO (6): addDocument trackeritem 381 {"memoryUsage":"33.5 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:02:36+00:00 INFO (6): addDocument trackeritem 397 {"memoryUsage":"33.5 MiB","memoryAvail":"93.5 MiB"}
^

I Adrien Mbuya Maloba's avatar
[ENH] Index, Trackers-DynamicList field : Add to the search index the text of...


After I updated and added everything that was committed between the 5/04/2023 and the 4/05/2023 I have now new errors in: /temp/Search_Indexer_mysql_bernardsfez_tiki25_console.log about the DynamicList

^
2023-05-04T06:11:26+00:00 INFO (6): addDocument trackeritem 69 {"memoryUsage":"32.0 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:11:27+00:00 INFO (6): addDocument trackeritem 70 {"memoryUsage":"32.0 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:11:27+00:00 ERR (3): Field 169 / Running Solutions: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/home/xxx/public_html/lib/core/Tracker/Field/DynamicList.php","line":305}
2023-05-04T06:11:27+00:00 INFO (6): addDocument trackeritem 298 {"memoryUsage":"32.0 MiB","memoryAvail":"93.5 MiB"}
2023-05-04T06:11:27+00:00 ERR (3): Field 169 / Running Solutions: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/home/xxx/public_html/lib/core/Tracker/Field/DynamicList.php","line":305}
...
^

I suspect it is related to one of the recent commits: https://gitlab.com/tikiwiki/tiki/-/merge_requests?scope=all&state=merged&search=dynamic

---

__Update 2023-06-26:__
The error is still here, just moved two lines.

Case one:

{CODE()}
2023-06-26T11:29:47+03:00 INFO (6): addDocument trackeritem 714 {"memoryUsage":"41.7 MiB","memoryAvail":"81.5 MiB"}
2023-06-26T11:29:47+03:00 ERR (3): Field 189 / Rate: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:47+03:00 ERR (3): Field 181 / Employee id - Not sure it is needed: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:47+03:00 INFO (6): addDocument trackeritem 818 {"memoryUsage":"41.7 MiB","memoryAvail":"81.5 MiB"}
2023-06-26T11:29:47+03:00 ERR (3): Field 189 / Rate: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:47+03:00 ERR (3): Field 181 / Employee id - Not sure it is needed: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
{CODE}

This item is closed.
Field 189 (Status Filter = open, pending) is empty.
It is pointing to an item in another tracker that has been deleted.

This item is closed.
Field 181 (Status Filter = all) has a value.
It is pointing to an item in another tracker that has been deleted.

---

Case two:

{CODE()}
2023-06-26T11:29:48+03:00 INFO (6): addDocument trackeritem 552 {"memoryUsage":"42.2 MiB","memoryAvail":"81.5 MiB"}
2023-06-26T11:29:48+03:00 ERR (3): Field 320 / Holidays camps days: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:48+03:00 ERR (3): Field 469 / Kind of product: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:48+03:00 ERR (3): Field 317 / Cost: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:48+03:00 INFO (6): addDocument trackeritem 553 {"memoryUsage":"42.3 MiB","memoryAvail":"81.5 MiB"}
2023-06-26T11:29:48+03:00 ERR (3): Field 320 / Holidays camps days: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:48+03:00 ERR (3): Field 469 / Kind of product: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:48+03:00 ERR (3): Field 317 / Cost: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
{CODE}

This item is closed.
Field 320 (Status Filter = open) is empty.
It is pointing to an item in another tracker that has been closed.

Field 469 (Status Filter = all) is empty.
It is pointing to an item in another tracker that has been deleted.

Field 317 (Status Filter = open, pending) has a value.
It is pointing to an item in another tracker that has been closed.

Case three:

{CODE()}
2023-06-26T11:29:57+03:00 INFO (6): addDocument trackeritem 1547 {"memoryUsage":"43.6 MiB","memoryAvail":"79.5 MiB"}
2023-06-26T11:29:57+03:00 ERR (3): Field 454 / Child name: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:29:57+03:00 INFO (6): addDocument trackeritem 1548 {"memoryUsage":"43.6 MiB","memoryAvail":"79.5 MiB"}
2023-06-26T11:29:57+03:00 ERR (3): Field 454 / Child name: NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
{CODE}

This item is open.
Field 454 (Status Filter = all) has a value (2 values).
It is pointing to an item in another tracker that has been closed.

Case four:
(the user is using tracker2 to store information setup)
While no field is mentioned, it seems the error is reported for any users that have an empty value in an item list field (field118).

{CODE()}
2023-06-26T11:30:09+03:00 INFO (6): addDocument user גנון {"memoryUsage":"46.3 MiB","memoryAvail":"77.5 MiB"}
2023-06-26T11:30:09+03:00 ERR (3): NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:30:09+03:00 INFO (6): addDocument user ספז {"memoryUsage":"46.3 MiB","memoryAvail":"77.5 MiB"}
2023-06-26T11:30:09+03:00 ERR (3): NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
2023-06-26T11:30:09+03:00 INFO (6): addDocument user מושטקל {"memoryUsage":"46.3 MiB","memoryAvail":"77.5 MiB"}
2023-06-26T11:30:09+03:00 ERR (3): NOTICE: Undefined index: REQUEST_METHOD {"code":null,"file":"/Users/bernardsfez/Documents/Shocksite/www/htdocs/tsaharoniki.com_tiki25/lib/core/Tracker/Field/DynamicList.php","line":307}
{CODE}

On a Tiki 25 I have a tracker and I'm using a file tracker field.

Whit the option "File Count" doesn't limit if set to 1 (Maximum number of files to be attached on the field), I should be able to upload only one picture and there should be only one file attached.

But there is another option similar/related near the bottom of the options list.
"Replace Existing File" and if this option is set to no, "File Count" has no effect and as a result, I can upload many files and have many file attached.

We have an interface and logic issue here.
If "File Count" is set to 1, "Replace Existing File" should be always set to "yes" and display a warning, something like: "A file exist for this item, You will overwrite the previously uploaded file. Do you want to replace the existing file". (common expected user interface)

If "File Count" is set to anything but 1, "Replace Existing File" should be hidden.

We have 3 Group related fields for the tracker feature.
Seems each one do a bit of the other and have some broken or to be perfected mechanism.

We should merge functionalities and have a single field that do "anything" groups.

On a Tiki24 (any Tiki ;-) ) in a tracker, when you use a Mathematical field and save it with the Calculation parameter empty, on item save the field value displayed the following error :

-+Expecting "(" near ""+-

It is wrong and doesn't really help.

On a Tracker properties => notifications you have an option to send notifications "Copy activity to email".
This is great to "force/set" groups to receive an update on activities without asking them to do something (activate group watch or monitoring a tracker, etc).

However there are many cases where you don't want to flood users with information.
So there is a dilemma.

It could resolve easily splitting "item creation" and "item update".

In trackers we have a radio buttons field type.

It should be possible to have a default option selected in a way that when a user create or edit an item, in the tracker interface of in a form, an option is selected by default.

As per Tiki 25, this not possible and on first create, edit the field will stay blank.

---

For some reason, and like the dropdown field, it is not possible to have twice the same value for different labels.

IE: 0=uncomplete,1=done,2=welldone,0=notdone
The options displayed will be:
* 1=done
* 2=welldone
* 0=notdone

It should be possible to use twice the same value but a single label.

Beside, global, object, category and more permissions, a tracker may have it's own permissions options + each field may have Visible, Editable and more permissions.

However beside opening one by one the property of the tracker and each field admins can't know supplemental permissions have been added.

I suggest having a small icon (a lock ?) in a light/faded color to indicate extra permissions are active.

At tiki-admin.php?page=trackers, when you enable:
* Inline editing
** Tracker list inline editing

And print (tested on Chrome and Firefox) all the fields values are blank.

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

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

I have a Tiki running elasticSearch set to use the time zone Asia/Jerusalem and the sample on the settings page displays correct information.
{img fileId="1775" thumb="box"}

I have trackeritems with a date field (picker) to select dates.
For exemple I have an item (5761) with a human readable value of : 7/04/2022
{img fileId="1776" thumb="box"}

However the value displayed for this date displayed from the unified index ===is the 6/04/2022===
I can see it in the database
I can see it in the plugin list test tool
And of course in the plugin list used to display the value to the visitors

{img fileId="1778" thumb="box"}
{img fileId="1779" thumb="box"}
{img fileId="1780" thumb="box"}

The index is being rebuilt properly and I don't see any warning there:
{CODE()}2022-03-08T06:27:07+00:00 INFO (6): addDocument trackeritem 5761 {"memoryUsage":"33.4 MiB"}{CODE}

Additional informations:
When I call the value from a different trackers (using a Dynamic Items List) the value displayed for the date is correct:
{img fileId="1781" thumb="box"}

In my smarty template I use dates format:
{CODE()}
<span class="font-weight-bold">{tr}{$days.tracker_field_holidaycampsDayDay|date_format:"%A"}{/tr}</span> <span class="small">{$days.tracker_field_holidaycampsDayDay|date_format:"%d"}/{$days.tracker_field_holidaycampsDayDay|date_format:"%m"}</span>
{CODE}

This was working fine on Tiki23 and is a major regression

{syntax type="tiki" editor="plain"}
The edit icon for inline editing need space (too close on mobile)

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

Check the instance...

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

When the user toggle between status he sees the items with the status selected.
However, if he perform an action his previous selection is "forgotten" and he have to re-selected again.

{mediaplayer src="display2072"}

When you create trackers with lots of entries (like cataloging newspaper articles) you will soon find that Tiki's sorting options are far (!) too limited. There is just one sorting option. A second is implied, but undocumented (either it's creation date or it is ID, could not find out).

It would be a significant improvement (and VERY easy to create in SQL) if a second and third sort option could be integrated just like the first one: Select field, select order.

These should be hierarchical, so all elements should first be sorted by option 1, and within all results sorting should be by option 2.

So for the newspaper archive example: First sort by category/department/column (alphabetically ascending), and within that by page number (numerically ascending), and on page number by title (alphabetically ascending). Just like Excel does.

These must be three separate options with both field and order selection, do not make it a multiselect, because you might want to have differing sort orders for separate fields...

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

I found out that the Security Ticket string (Security ticket timed out) from tiki-confirm.js are not translated and not even added to lang/xx/language.js

I understand I can add them manually but isn't bad for consistency in general.
Couldn't we have those string added in the lang/xx/language.js file like it is done for the php translation ?

Even after the "Add default modules" button is clicked to add the modules, the button continues to display. Clicking the button again takes the admin to the admin-profiles page to find that the profile is already applied. The button should no longer display after the default modules are added, or should change to "Remove default modules". Also, IMO it would be good if there was a notice that the page is going to change/navigate to the admin-profiles page, maybe with a tooltip or helpblock text like "Apply Profile".

Also, the profile creates a wiki page called "Instructions - Admin UI Dashboard" that just contains a redirect to tiki-admin.php. This is confusing because there's no actual page, content-wise, and no instructions. Is this the stub of a feature that isn't finished yet?

Even when the new unified admin backend isn't turned on, adminui.css is active and imposes style details like link color that conflict with the active theme stylesheet in many cases.

I suggest the page elements of the new backend be given a unique parent class to distinguish them from, for example, the standard navbar that appears in the top or topbar zone when the new backend isn't active, so its CSS rules aren't erroneously applied.

Alternatively, adminui.css could just not be activated unless the feature is.

(Actually, IMO adminui.css (the visual rules like foreground and background colors, etc.) should be a theme (or two - light and dark) that can be selected, or a standard theme selected consistent with the "make it optional" rule. The adminui appearance could be the default for new installations, but could then be deselected for sites where maybe organization or corporate branding is a priority (and at sites that live on the wild side and don't need black and white menus ;-) ).

We need the footer at the bottom of the new Admin Unified Backend dashboard.

With a default Bootstrap menu in the footer, on the Unified Admin Backend page, menu item dropdowns drop down and the page isn't scrollable to reveal the dropdown.

With Smartmenus turned on, the dropdowns in the footer menu will scroll upward away from the bottom margin but only a few items can be seen because the dropdown is hidden or blocked by the div above the footer. It seems like maybe a z-index problem.

There are over 2000 prefs. Searching is critical.

When the menu is open, we have a nice search. Quick Access to that search should be always visible. Maybe a search-all-over-admin-panel action button in the top left?
{img type="src" src="tiki-download_item_attachment.php?attId=769"}

I updated a working Tiki25 today.
With an empty database I can run the Tiki and database:u console command work.

On my local__ (MAMP osx), if I try the same command but this time to update an existing database I have the following error:
{img fileId="2083"}

There is something wrong with the previous default value for the field "date_to" in the table "tiki_banning".
I fixed (temporary) by setting a new default for this field.
No more database error.

{mediaplayer src="display2084"}


This does not happen on a a remote server (debian11 + virtualmin).