Category: 25.x
Show subcategories objects| Name | Type |
|---|---|
| slideshow fails to work if no plugin slideshow call in wiki page but just automatic link at the page bottom | tracker item |
|
Slideshow; Content is not displayed the same depending on the browser used (content may be truncated)
Using slideshow on a wiki page in Tiki25 is a different experience depending on your browser. Here on OSX 13.1 {img fileId="1952" thumb="box"} {img fileId="1953" thumb="box"} {img fileId="1954" thumb="box"} While content is fully displayed in Safari, in the other browsers it is truncated at the bottom due content/font size. In short, when you have more content than a page can display (height) it is not accessible. It should be somehow possible to "scroll" or open a second (sub)slide with the missing content. |
tracker item |
|
Slideshows based on structures
Slideshows can only be done based on a page and its headings. The proposition is to be able to do slideshows based on structures (without having to move through a structure and select slideshow on every page). |
tracker item |
|
Software Bill of Materials (SBOM) becoming mandatory for Tiki
{syntax type="tiki" editor="plain"} On May 12, the US President issued an Executive Order that binds US agencies that software purchased needs a Software Bill of Materials (SBOM). [https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/|Executive Order on Improving the Nation’s Cybersecurity] A SBOM is a comprehensive (!) list of ALL dependencies. You have to list every (!) module, tool, library, whatever that Tiki relies on in a predefined, machine readable format. If you do not provide a SBOM, no US agency or office will be allowed to use Tiki. The reasoning behind that is simple and clear: Unknown dependencies cause unknown cyber risks. As they are unknown, the impact of those can range from negligible to catastrophic. All dependencies must be tracked. If software that Tiki depends on does not get updated, features might break, or even worse, impose direct security threats through Zero Day exploits. Oh well, looking at some popular tool's outdated version history, you might not even need "0days" to break into other vendor's software, where the user (or admin) might not even be aware of the dependency. Or the depency of some other dependency. Log4j was the last warning to the industry (and in this regard, Tiki must be considered to be part of the industry). The machine readable format of SBOM makes it possible to discover the depencies of the dependencies. Nestings of a dozen or more levels are not uncommon... Now the president took action. Tiki should react, IMHO. Tiki must react, or Tiki won't be usable by officials anymore. |
tracker item |
|
Admin Interface; Some Admin actions reload on a page outside the admin Control Panels
{syntax type="tiki" editor="plain"} Verified also on Tiki25, login as Admin, go to settings, Control Panels, go to /tiki-admin.php?page=search, click on the rebuilt index button it open a modal. All this is the control panel area. If you validate the action and rebuild the index you will be thrown outside the Control Panels area (/tiki-search-rebuild). {img fileId="1664" thumb="box"} {img fileId="1663" thumb="box"} This is related to the action page itself. If you use the top admin bar rebuild-index you will be also exited from the Tiki administration pages. List of pages/actions with the issue: * Control panel, go to /tiki-admin.php?page=search, click on the rebuilt index button it open a modal, validate the action (/tiki-search-rebuild) * Control panel, go to /tiki-admin.php?page=general, tab navigation, Sitemap protocol click on the play button => tiki-admin_sitemap.php * Control panel, go to tiki-admin.php?page=textarea#contentadmin_textarea-2, click on the link tiki-plugins.php * Control panel, go to tiki-admin.php?page=metatags, translate metatag throw you out of the admin to tiki-preference_translate.php May be all top menu action links throw out of the admin area... * Control panel, top menu tools, Server check * Control panel, top menu Access, Permissions * Control panel, top menu Access, Groups * Control panel, Editing, Plugin approval (tiki-plugins.php) * ... |
tracker item |
|
Stop indent thread discussion at some point (comments replies)
As you can see in this comment's item, the discussions comes to a point it is hard to read and most of the screen space is wasted. https://dev.tiki.org/tiki-view_tracker_item.php?itemId=7838&threadId=9696 We should add a new preferences so we can limit indentation on thread reply. It should be optional It should be have a threshold field (after 5 replies stop indenting) It should be set "enable" by default (with 5 replies) It is important to test with a setting of 2 (after the first post, all replies have the same single step indent) This happens on comments under or added to another feature, not in forums. |
tracker item |
|
Structure (House Lft Top Rit) navigator disappears when (turn off page title is active).
1. I have (show page title set to yes in the user preference). 2. I have a structure as a menu item in a module. 3. For each page in the structure I go to edit> properties > Show Page title = Off. 4. Page by page as I set this option the "House Navigation widget" disappeared. 5.In effect Two features are being controlled by one user preference. {img fileId="2126" thumb="box"} |
tracker item |
|
Structure inserted in page is not displayed unless you specify it
Check https://dev.tiki.org/How-to-release vs https://dev.tiki.org/How-to-release?structure=Developer+Documentation |
tracker item |
|
Structures; Improve the icons of the structure object action
The icon in the structure action strip are confusing and can be improved. {img fileId="1819" thumb="box"} The first one suggest a "search" and/or addition of page while in fact it is to view the page. The fa-search-plus should be replaced. As we are using the "eye" icon that is naturally the "View" symbol for Watches we should be creative. The icon should be without a + sign. Even a hand-point-up will make better sense. |
tracker item |
|
svn update on show2.t.o instance from dev.t.o does apparently nothing
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"} |
tracker item |
|
Table, List Execute; Checkbox are not visible on white background rows
Checkbox are not visible on white background rows (alternate style) You need to mouse hover to see them. {img fileId="1920" thumb="box"} |
tracker item |
|
Tabular formats "export only" fields are required for import
{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. |
tracker item |
|
Tag file in file galleries
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. |
tracker item |
|
Tesseract OCR - uncaught / not found fatal error
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} |
tracker item |
|
tiki 25.1 Database 'xxxx'. Unable to connect to database (when 25.0 will connect)
Trying to install tiki 25.1. New clean directory next to 25.0. Only changed apache2 sites available config paths from /25.0 to /25.1 Copied local.php from 25.0/db to 25.1/db Restarted apache2, cleared browser cache. PHP 7.4.33 (cli) (built: Feb 14 2023 18:31:54) ( NTS ) Is there something missing from 25.1 ? |
tracker item |
|
Tiki admin look and feel, upload logo should also take care of the size of the logo
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) |
tracker item |
|
Tiki Captcha, UI; The captcha fields width and buttons colouring don't match form element design
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"} |
tracker item |
|
tiki-check.php; New error about Server compatibility seems wrong
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 |
tracker item |
|
Tiki Comments, Errors; Missing fields are now reported from within tiki commented (tc) blocks on the wiki page and in the console
{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"} |
tracker item |
|
Tiki community HomePage show a "Data too long" error
{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. |
tracker item |
|
Tiki Install, UI; Redundancy is not require and not nice on the security page
{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). |
tracker item |
|
Tiki tracker email adress type: Checking too loose
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. |
tracker item |
|
Tiki unable to create new meetings in BBB2.4+
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. |
tracker item |
|
Tiki upgrade; after a new installation Tiki should warn nicely the admin he needs to rebuild the index (or do it)
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. |
tracker item |
|
tiki-admin_menu_options.php menu title and url field are now mis-aligned
The layout of the menu fields was ok in 25.2 but now in 25.3 the url field is under the label field as you can see in the attachment. Actually since about tiki 20 the label and url field have been made too short making it difficult to read the full text strings as they get covered by the edit widget. |
tracker item |
It seems as if some library (or something) is missing to allow passing slides forward, because the first slide is shown, and it works to hiughlight bullet points, but when the time to move to the 2nd slide comes, nothing happens and slideshow stays in the first.
If you go to list slides, and attempt to click at any from that list, it seems as if the slideshow systems wants to take you there, but it comes back to the first slide very quickly.
Reproduced in this show2.t.o instance attached to another bug report:
http://xavi-9794-7332.show2.tikiwiki.org/tiki-index.php?page=Tiki%20Wiki%20CMS%20Groupware
u: admin
p: 12345
Once you edit that page, and add a simple call to plugin slideshow inside (no params needed), and tiki caches cleared (just in case), then it works as expected:
{CODE()}
{slideshow}
{CODE}