Category: 26.x

clicking on svn update for a show2.t.o instance from a bug tracker in dev.t.o does apparently nothing

Reproduced with the show2.t.o instance linked to this bug report:
https://dev.tiki.org/item7332-Slides-in-21-x-Section-about-wiki-page-comments-wrongly-placed-on-top-of-all-slide-titles

----
I've been unable to svn update show2.t.o sites (20.x, 21.x...) through the button in the show2.t.o related field in dev.t.o/tracker5

Same with "destroy instance" which didn't work and no info was provided to the end user. I had to destroy them by hand at the show2.t.o server.{sign user="xavi" datetime="2022-01-22T22:39:53+00:00"}

I'm trying to create a Content Template that indicates intention to use markdown, like shown on this page (for example): [https://markdownthemes.tiki.org/tiki-pagehistory.php?page=Markdown+Plain&source=0]
After I put the following code at the top of that Template
{CODE(theme="default")}{syntax type=markdown}{CODE}
and then Save the template, this code disappears after I re-open for editing.
If the template is used in a Wiki Page, the above code is also invisible.
Unfortunately, the content of the template only shows as a binary blob in the database, so it can't be edited directly and cleaned up.

Checkbox are not visible on white background rows (alternate style)
You need to mouse hover to see them.

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

{syntax type="tiki" editor="plain"}
Should be a simple enough fix, "export only" fields (obviously) should bnot be needed as columns in the csv being imported.

The possibility of tagging individual files in file galleries is missing. This is both natural and necessary. Any archival / encyclopedic / knowledge base use of a wiki would need this. The tags feature inexplicably misses it.
Shouldn't be difficult to fix.

I am currently testing a __Tiki 24 trunk as a local office software__ on my work laptop.
The Tiki is still in the process of configuration, setup and testing.

I use a Mint/Ubuntu 18 Linux. I use a standart Apache2 / Mysql/PHP (7.4/8.0) installation, each part installed with the command line (not a prepacked Xampp/Lampp).
Side note to PHP version:
I could not install Tiki with PHP 8.0 (WSOD issue) and did install it then with PHP 7.4 running
Later when I installed a number of Packages, Tiki requested PHP 8.0 and it stopped working with PHP 7.4 (WSOD). Thus this Tiki 24-trunk is currently running on PHP 8.0

''I have also a number of file permission errors and some issue with a search index error message, which I will report later on in the forums or with another bug report.''

Tiki is installed __via SVN__ and runs in __/var/www/html/tiki__ .

One of several issues with my Tiki trunk installation is, that instantly after installing __Tesseract OCR in Tiki via Packages__, I get the following type of error messages:

{CODE()}
Fatal error: Uncaught thiagoalessio\TesseractOCR\TesseractNotFoundException: Error! The command "sh: 1: where: not found" was not found. Make sure you have Tesseract OCR installed on your system: https://github.com/tesseract-ocr/tesseract The current $PATH is /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin in /var/www/html/tiki/vendor/thiagoalessio/tesseract_ocr/src/FriendlyErrors.php:40 Stack trace: #0 /var/www/html/tiki/vendor/thiagoalessio/tesseract_ocr/src/TesseractOCR.php(85): thiagoalessio\TesseractOCR\FriendlyErrors::checkTesseractPresence() #1 /var/www/html/tiki/lib/ocrlib.php(278): thiagoalessio\TesseractOCR\TesseractOCR->executable() #2 /var/www/html/tiki/lib/ocrlib.php(208): ocrLib->newTesseract() #3 /var/www/html/tiki/tiki-check.php(1995): ocrLib->getTesseractLangs() #4 {main} thrown in /var/www/html/tiki/vendor/thiagoalessio/tesseract_ocr/src/FriendlyErrors.php on line 40
{CODE}

I have definitely Tesseract installed on my laptop, but I do not (yet) know the installation path:

{CODE()}
Torsten@Linux:/var/www/html/tiki$ tesseract
Usage:
tesseract --help | --help-extra | --version
tesseract --list-langs
tesseract imagename outputbase [options...] [configfile...]

OCR options:
-l LANG[+LANG] Specify language(s) used for OCR.
NOTE: These options must occur before any configfile.

Single options:
--help Show this help message.
--help-extra Show extra help for advanced users.
--version Show version information.
--list-langs List available languages for tesseract engine.
{CODE}

{syntax type="tiki" editor="plain"}
Displaying an image with an alt attribute is an accessibility problem, and the "article image" in Tiki's articles feature have no way of inputting the alt text. The page source shows -+ alt="" +- but it's empty because there's no form input when editing the article to specify it.

The comments sort order has been not great for a long time, possibly ever, i think we default to listing by comment date, but that breaks down if someone replies to an old comment, that one might be in page 2 so we miss new content.

I’ve been reading Reddit for a while now and I think they sort the threads by number of replies, which generally equates to the most interesting and popular ones rising to the top.

Shouldn’t be to hard to add (optionally of course), any volunteers? ?

When a new admin start setting up his Tiki he will likely put his own logo.

However there 0 control on the page or in the code code to limit the logo size but the 1170px width for the first container.
So if the admin pick a high resolution logo, it can use the 1170px width.

Result is not what is expected.
Having the "non power user" user in a situation he have to resize the logo and reupload it is "passé".
We should have some logical limit. (optional, changeable, whatever)

The ((tw:Roundtable Meetings|Tiki Roundtable Meetings)) are to be held __monthly every 3rd Thursday at 14h UTC__. Please make it possible to be able to do this in Tiki.

This should work with recurring events. So people in different time zones will see the event in their time, depending on daylight saving time (DST)

A form anonymous can fill is still very common and used in many website (tracker items, registration and contact form).
We are used to it for so many years that we don't see it, but for others, this is not a good image for Tiki.

On mobile and desktop it really look like unfinished work.
# The buttons colours are wrong:
* Submit should be primary
* Refresh captcha should be secondary
# Width and field should match.

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

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

On a tiki25 using tiki-check.php I see a new error that wasn't there (I'm not checking this page everyday so I don't know when it has been introduced) about Server compatibility:

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

I believe it is a false alarm introduced with changes
Everything is green (I have some of the few and usual yellow but no red) and my Tiki is working just fine.

My system:
PHP: 7.4.33
MariaDB: 10.5.18-MariaDB-0+deb11u1
Tiki Version: 25.2 (from git)
Server: Debian GNU/Linux 11 (bullseye)
Web Server: Apache
CPanel: Virtualmin

{syntax type="tiki" editor="plain"}
On a Tiki25 I have a test page to test stuff and I keep a long list of test and setting commented using the Tiki Comments.
~np~~~/np~tc~

On an updated Tiki25 and Tiki26 an error is now visible as it was not visible previously.
The error is also reported now in the console command.

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

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

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

{syntax type="tiki" editor="plain"}
At https://tiki.org/Community I see the following error:
"Data too long for column content..."

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

* It usually happen the first time I land on the page in the day
* If I reload it is gone
* It happen also on Next (signalled already)
* I see it on Mac OS Safari (not sure it is related)

See Oliver comments about cause.

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

The label Database username + the placeholder Database username are redundant, we should keep only the placeholder. (same for Database password).

Tiki offers a data type "email adress". This does basic syntax checking. Actually, it is VERY basic. It only checks is there is an at sign (@) in the string. A little bit more might be wished for, in order to reduce spam and clutter from anonymous users.

IMHO it should also be checked if a domain name is entered. So it should be detected whether there is a full stop after the at sign, and at minimum one letter before and after the full stop.

Now Tiki accepts a@b, IMHO it should at least check whether it is a@b.c (I would not recommend to check acutal TLDs, because they change too often nowadays.

Hi:

I wanted to test the new features coming along in BBB 2.3 & 2.4, so that I installed a new server with BBB 2.4. Everything from the BBB side did run smoothly, but the integration with tiki is not fully working as expected. I mean, after connectinng the tiki to bbb 2.4 server (providing the new url and bbb salt in the tiki control panel), I can see the recordings listed in the plugin bigbluebutton parsed content, but I'm never able to create a new meeting (when clicking to the create button shown by plugin bbb).

I had a look at the [https://docs.bigbluebutton.org/dev/api.html|bbb documentation], and I see that some changes are reported to the API in bbb 2.3 and 2.4.:
{CODE()}
Updated in 2.3:

create - Renamed keepEvents to meetingKeepEvents, removed joinViaHtml5, added endWhenNoModeratorDelayInMinutes
getDefaultConfigXML obsolete, not used in HTML5 client
setConfigXML obsolete, not used in HTML5 client

Updated in 2.4 (under development):

getDefaultConfigXML Removed, not used in HTML5 client
setConfigXML Removed, not used in HTML5 client
create - Added meetingLayout, activityReportTracking
{CODE}

I had a look i Tiki21 LTS, for instance, and I see that there are references to -+getDefaultConfigXML+- and -+setConfigXML+- in __lib/bigbluebuttonlib.php__

{CODE()}
(...)
173: $content = $this->performRequest('getDefaultConfigXML', ['random' => '1'], false);
(...)
192: $client = $tikilib->get_http_client($this->getBaseUrl('/api/setConfigXML.xml') . '?');
(...)
{CODE}

Could this be the reason why tiki is not creating the new room in the bbb-2.4-powered server?

If that hypothesis is confirmed, then we might hit a problem in the tiki community in the afew months whenever Fred Dixon and the BBB team upgrades the bbb instance we use in the "Tiki Roundtable Meetings" and TAG meetings, etc.

I can share the details of my bbb2.4 test server (url and salt) with any dev willing to debug and fix this issue.

I upgraded a Tiki from 24 to 25 after completing the installation I landed on the homepage with errors displayed :
-+Field searchable does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_searchable.+-
And many -+No results for query.+-

While this is normal, as I didn't ran the index:rebuild command, this is not very elegant and can be improved;

First, in such case a message with a link should be displayed about completing an action and not a page full of errors as that doesn't look good.

When the unified-index doesn't exist a modal warning over the page "Tiki detected that..." with an invitation to action "for your Tiki to work properly you must run rebuild command". If you have a small database you can run it from here else please use console.php.
A option to close the modal (admin choice to continue) and display the page.

Ideally the installer should automatically do such operation.
One difficulty is that we don't want run from the HTML the index:rebuild command to run on a large database as there are chances of timeout.

Tiki could suggest at the end of the installation process;
"You upgraded, before entering your new/upgraded Tiki you must run the index:rebuild command"

If possible a database size detection and offering suggestion;
"The Tiki installer script detected that your database size is: nnn"
We recommend:
* Small database => rebuild the index now
* Medium database => rebuild the index now
* Large database => rebuild the index using console.php

If the database size detection is not possible or too complicate (it may depend of server OS ?) we can simply give recommendation and offer to run the command for the user or suggest him to do it using console.php.

FYI, there is no machine learning category in the Feature drop down of this report form.
Anyhow I enabled machine learning in the control panel.
After clicking machine learning then list models in the from the system model
{img fileId="1942" thumb="box"}
I get a 404 error as shown in the image here.

I've been using OSX and MAMP to setup Tiki on my local computer since a while.

Since Tiki26 (using php8) after the install goes as expected I got a 500 error loading any Tiki page.
Seems it is because the "setlocale" command on "tiki-setup.php"

If I comment the following

{CODE()}
setlocale(LC_ALL, '');
{CODE}

Or if I set it with 'en_US.utf8'

{CODE()}
setlocale(LC_ALL, 'en_US.utf8');
{CODE}

Tiki load up correctly.

The hours displays on the tag meeting page are displayed using a 12 hours clock even if General Date and Time settings /tiki-admin.php?page=general and my own preferences /tiki-user_preferences.php#contentmytiki_user_preference-2 options are set to use a 24 hours clock.
IE: 4:00 is displayed as it should be 16:00

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

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

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

Adding any date and time using the 24 hours selector will change it to a 12 hours selected hour.

__Objective:__

The objective of my feature request is a more efficient way to create, to edit and to display Calendar event data, when used together with a Tracker.

This would be useful especially in the context of project management tools like Kanban (under heavy development) and Trackercalendar.

All features and functionality like Trackercalendar, Kanban, Calendar events, should provide different simple and versatile views, based on the very same Calendar item and thus be freely combined and happily created by simply filling one simple Tracker form.

__Use case example / context and problem:__

I got the idea whilst working on a Tiki 25.0vcs (InnoDB, git, ...) for a small personal private office project, where I test a bunch of features.

I made a 'Task' list with Tracker ... this is planned to be used together with Kanban.

The 'Task' list contains a field type 'date and time (calendar event)' which creates a calendar event when the Tracker item is created. As far as I understand, the Tracker item displays the Start date (and time) of the Calendar event, which is connected / related to the respective Tracker item.

This is working fine and it is even possible to switch the relation of the Tracker item to another existing calendar event.
The name of the Tracker item will be the title of the Calendar event (which is good!)

Sadly the actual date and time is the only data that seems to be displayed in the Tracker item so far.
Imho it would be important to have the option to share the same item description for the Tracker item and the Calendar event.

Currently I can create a Tracker field 'Textarea' in the Tracker and use it as description.
But there is no option, that this description textarea would be displayed as decription of the calendar item. Aswell it is not possible to display the Calendar event's description in the Tracker item.

When the Tracker item is created it is only possible to distinguish the Calendar item's start date.
Only after creation the Tracker item can be displayed and from there an edit-button pressed and then the details of the Calendar item edited, like Start date and End date, duration, description, participants, and all the other data of a calendar event.
This process needs to be simplyfied.
All these data details needs to be optionally displayed in the Tracker and in the Calendar, in a way that Tracker and Calendar just provide a different view on the same event.

__Following additional functionality would be required:__

# Add a Tracker field type ' Calendar event details' to display data from the Calendar event that is (currently) connected to the Tracker item.
+
# This Tracker field type shall have options (maybe comma separated list) to display the content of one or more Calendar event fields like End date, duration, description, participants, etcetera.
+
# It shall be possible that several Tracker fields of type ' Calendar event details' exist in one Tracker item. This way this field type could be used
** either similar to a field type "item list' (display several calendar details in one Tracker field)
** or similar to a field type 'dynamic item list', respectively 'item link' (display one Calendar event detail per Tracker field for more detailed display option)
+
# The Tracker field type 'Calendar event' should provide the option (to the user) to distiguish and completely fill out all Calendar event data details at the time of Tracker item creation.
+The user should not be required additional steps to reopen the event for then providing the Calendar details that he would have wanted to provide in the first place.
+
# For long time the Trackercalendar did use no calendar items but individual 'date and time' fields to create a calendar like planning tool for ressources. As far as I know the Trackercalendar was not any connected with the calendar feature. Imho it would be a good idea to create the start and end dates of the Trackercalender by using the field type 'Calendar event'

At tiki-admin_actionlog.php the admin need to check each box one by one and there are quite a few if you want to select all.
We should have a select all (while toggle will be ok but less adapted IMO).

It may have to do with the user interface.
It is not user-friendly and even reading the help online (good interface should be understandable without help) it is unclear how to use it until you tried a few times.

On Tiki 24 using the Classic Bootstrap layout with the default theme, the module were centered in LTR and RTL.

{img type="fileId" fileId="1890" thumb="box"}

{img type="fileId" fileId="1891" thumb="box"}

On Tiki 25 things changed (logo module?) and I believe it was wanted to align the modules to the "start" of the selected language.
LTR => left
RTL => right

While it look like justify-start for RTL (and I like better than centered or space between)
In LTR it look space between is applied (and that not a happy design on desktop)

I think the change (if it was intended) make sense in 2022 and modules should use "start".
What is set should be the same for LTR and RTL

Most fields seem to be not listing properly on next.tiki.org, e.g. https://next.tiki.org/tracker22 and https://next.tiki.org/tracker26

A significant regression...