Category: 26.x

{syntax type="tiki" editor="plain"}
Attaching a file/image to a trackeritem is quite critical and in 2023 for Tiki trackers to compete.

However browsing an image in a Tiki file gallery is absolutely not user friendly.

On desktop, the modal is not very pretty and the way images are displayed is awkward (2023 standards) it hard to see what image is selected and where is the way to validate the selection.
Unless you have a few images (no more than 7) you will need to scroll up and then down to see what you are doing.

The "image selected" name and the "Validate your selection" button should be always visible.
The "Select" button name is really confusing should be changed for "Validate selection", "Select this file"...

{mediaplayer src="display2144"}

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.

In trackers where you set an Item Link or an Item List fields in a way that it may display a single value.
(user specific, pre-selection, etc). It would be a good addition to have an option that allow this single value to be automatically selected.

For example:
I have a tracker that store kids name and a tracker to store orders.
In the tracker for orders, I select a family name and an item link field (to the tracker kids) display the kids name with the same family name.

Most of the time there is only one value, one kid name.
To fully complete properly the order the Kid should be selected (not just displayed).
Instead of having the user to select this unique value displayed it would be nice to have a way to auto-select this unique option.

''The end-user point of view;
When you have several value it make sense to the end-user to select one. But when you have one value displayed the end-user feels it is selected already. This is stronger when using a mobile where the interface really look like it is selected.''

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".

''I have the feeling this is a regression as I recall such case where previously handled properly''

I can set a name for a tracker field that will turn into the "Field Prefix". (productssolutionsdetailsandoption)
When I create a tracker field this field permaname will use the tracker field prefix. (productssolutionsdetailsandoptionIllustration)
The index process will add the tracker field prefix. (tracker_field_productssolutionsdetailsandoptionIllustration)

But it won't be able to index such long name.
Or the limit should be changed (to what ? unlimited...) 🤔
Or ahead limiting and warning about the prefix/field length.

{img fileId="2141"}

{img fileId="2142"}

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.

On a Tiki24, on a tracker when you have a rating tracker field an error is be displayed all over the site for all groups (anon included).

The rating system seems to work, but the error (false alarm?) is displayed everywhere and doesn't allow to keep it in place. The error is related to the old and deprecated "trackerfield_starsystem" (hard to find now as it is Experimental)

The error is also displayed (and a problem?) if rebuilding the index.

To fix the error (so it is not displayed) the admin has to enable this deprecated field.??‍♂️

The actual Rating field shouldn't depend on a deprecated and experimental option.

In general, Tiki shouldn't display everywhere an error like this. Eventually the admin or the tracker editor should see the error, but not anonymous or other groups.

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

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

Tiki is mainly about Wiki page and Tracker (Tiki can do many things, but let's not debate too much about this) ?

User data safety is critical, therefore we have an auto-save feature for Wiki page editing to protect as much as possible the user content editing.
I would like to see the same feature for tracker items.

Some mechanism that "auto-saves" the tracker editing content at regular intervals.
''Sometimes it take a lot of time to complete items. (lots of fields, text-area, etc)''

Some things to think about:
* Tracker editing (modal/regular) and inline tracker editing
* Indexation of the fields content (auto-saved or not ?)
* ...

This is not as easy as the Wiki page auto-save feature, but is valuable as a lot of data and content are now added using trackers.

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 ?

Wiki > List Pages, then check boxes next to Pages that I want to delete. Choose "Remove" action from the drop-down.
Result is an error message: "No action was selected. Please select an action before clicking OK."
This happens every single time.

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"}

If you change a listing, like on the Wishlist, and change sorting order, the URL gets an additional mention of the sort order.

But it's reversed, compared to the actual setting. So if you want to sort the Wishlist by modification date, descending (which IMHO should be the default), so the latest are listed at the top, the URL states

{CODE(Colors="Tiki")}
https://dev.tiki.org/Wishlist#sort_mode=modification_date_asc
{CODE}

ASC=Ascending. If you change sorting to ascending, the URL states _desc...

If you go at https://tiki.org/forumthread79200-Tables-and-file-upload-on-26-1 and pass your mouse over the username of the post publisher you will see a modal with a never ending loading wheel.
At some point an error will be displayed in the DOM.

{img type="src" src="https://i.ibb.co/3cgC6r6/Screenshot-2023-10-28-at-9-03-03.png" thumb="box"}

We have a few places where with placeholders and help text for link that shows "http://".
They should display more modern link usage: "https://".

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