Category: Bug

{syntax type="tiki" editor="plain"}
When you duplicate a Wiki Page you have 2 additional options:
* Duplicate categories
* Duplicate tags

Both never worked for me as far as I can recall.
When I duplicate a page that are categorized and have tags the new page won't have them.

It should be fixed OR even removed as no one seems to use this (never worked for me since Tiki24 or even more)

It is giving a bad image of Tiki.

{syntax type="tiki" editor="plain"}
In a multilingual Tiki, my interface language is French and my Default admin language is English.
If I go to the scheduler page (admin area, tiki-admin_schedulers.php) it is displayed in French like the user interface and not in English like the admin interface.

{syntax type="tiki" editor="plain"}
A 50 is added into the url

{CODE()}
User: admin
Site: https://example.com/50 or more unsuccessful login attempts have been made. Your account has been suspended. Contact your site administrator to reactivate it.
{CODE}

If I create a file -+ themes/css/custom.css +- I can customise my Tiki whatever theme is currently being used. That is fine and very useful.

If afterwards I create a file -+ themes/mytheme/css/custom.css +-, the file contents of -+ themes/css/custom.css +- are completely ignored. This is contrary to user's expectations and caused a bug in at least one site I know of.
Both file contents should be taken into account.

{syntax type="tiki" editor="plain"}
On Tiki30 the meta description is using the website default metatag description and not the Article specific description as in Tiki27, 28 and 29.

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

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

{syntax type="tiki" editor="plain"}
At tiki-syslog.php it is possible to delete older logs by using the field "Clean logs older than".
This field is expecting a numeric value (the number of month) but it is possible to type anything, even text.

-+https://example.com/tiki-syslog.php?months=tikiwiki&clean=Clean+-
Then land on the "Please confirm action" dialog (without knowing what we confirm ?) and execute the action.

It should not be possible to type something else than a number and the user should be warned way ahead:
"You must enter a number of month..." or something like that.

SVG uploading can be blocked by admin, because there are certain security risks with them. But Tiki file galleries have a different problem with them. When admin uploads a SVG, a default thumbnail for the MIME type image/svg+xml is displayed (instead of the embedded thumbnail!). That's not optimal, but at least it works.

When a user uploads a SVG, something else happens: Thumbnail generation crashes. Instead of the default thumbnail a tiny error message is displayed in a window the size of the thumbnail. It reads:

{CODE(Colors="Tiki")}
Warning: imagecreatefromstring(): Data is not in a recognized format in MYHOME/htdocs/tiki-18.8/lib/images/gd.php on line 70

Warning: Cannot modify header information - headers already sent by (output started at MYHOME/tiki-18.8/lib/images/gd.php:70) in MYHOME/tiki-18.8/tiki-download_file.php on line 395

Warning: Cannot modify header information - headers already sent by (output started at MYHOME/tiki-18.8/lib/images/gd.php:70) in MYHOME/tiki-18.8/tiki-download_file.php on line 404

Warning: Cannot modify header information - headers already sent by (output started at MYHOME/tiki-18.8/lib/images/gd.php:70) in MYHOME/tiki-18.8/tiki-download_file.php on line 442
{CODE}

After that, something that looks like the header of the thumbnail follows

{CODE(Colors="Tiki")}
�PNG ((0000)) IHDR}�((0008))((0003))
{CODE}

and after that LOTS of binary garbage, possibly the entire rest of the file...

My Linux desktop (Linux Mint 19.3) a.k.a. Ubuntu Bionic Beaver with Cinnamon as desktop does display the embedded thumbnail. I'll have to figure out which binary compiles the thumbnails for image/svg+xml (does not have to be the same that is used for JPEG, PNG etc.).

I had posted this to the community, but did get no response so far, so I file it as a bug.

I have activated MyTiki and avatars. In order that everyone sees everyones avatar, I set (as admin) user info to public on all registered users.

First: Changing a users avatar with the switch users feature for admins changes the avatar of the admin...

Second: The preference user info = public is lost. I cannot see any regularity. I always click Save changes, and there is no error message. Also, all settings from MyTiki get lost. I activated all MyTiki checkboxes for all users, and they keep vanishing. It does not seem to be a caching issue.

When I set everything the way I want it and click Save Changes, the following information is immediately forgotten (and no errror message!):
- Country (but stragely location is not lost...)
- User information public reverts to private
- Mouse over user information shows info window (if user permits)
- All MyTiki settings

All other preferences are stored without error. I guess that some logic or permissions rule dictates that users cannot change some preferences.

If that is the case, these presets should be admin configurable somewhere and I did not find them? Anyhow, if users are not permitted to change some preferences, then users should not be presented a GUI to change them, or should get an error message that this preference is preset for them.

Thanks for your support
Hman

Hello, Bitnami developer here,

We are working on supporting the latest Tiki 22.

First, we would like to know if this version is considered stable since it is not shown on https://info.tiki.org/Download (we detected it from https://sourceforge.net/projects/tikiwiki/files/Tiki_22.x_Corona_Borealis/).


Apart from that, we are trying to follow the command-line installation following the documentation from http://doc.tiki.org/Manual-Installation. However, this version shows us only a small list of commands:

{MARKDOWN()}
```
php console.php list
Tiki Console Tool

Usage:
command [options] [arguments]

Options:
-h, --help Display this help message
-q, --quiet Do not output any message
-V, --version Display this application version
--ansi Force ANSI output
--no-ansi Disable ANSI output
-n, --no-interaction Do not ask any interactive question
--site=SITE Multi-Tiki instance
--as-user=AS-USER Run the command as a different Tiki user
-v|vv|vvv, --verbose Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

Available commands:
help Displays help for a command
list Lists commands
database
database:configure Database: Configure (write local.php)
dev
dev:fixbom Fix BOM and line endings for all files
installer
installer:lock Disable the installer
scss
scss:compile Compile SCSS theme files into CSS
translation
translation:englishupdate Fix English strings after modifying them.
translation:getstrings Update language.php files with new strings
vcs
vcs:update Update SVN to latest version & perform tasks for a smooth update.
```
{MARKDOWN}

Could you please share with us the exact commands that the installer should run to pass the installation?

Thanks in advance,

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 ?

The module "Tiki Assistant" (to help newbie admins) calls for an icon that does not exist (/img/icons/arrow_small.png). This is not configurable...

When editing a calendar event, some characters in the event title displays as HTML code, in the modal title. For example, John's "Birthday" displays as ~np~Johnĵs "Birthday" ~/np~.

The file is tiki-calendar_edit_item.tpl, I believe.

Also, the wrench/spanner icon at the right side of the modal title doesn't seem to do anything. Is it meant to be just an icon to indicate the edit screen is displaying? If so, it's misleading since other instances of this icon are clickable to produce a popup list of links, etc. IMO it should be removed if it is just an icon. Or if it is meant to be clickable, it doesn't seem to be working.

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

If have two Tikis running on 18.8 (before anyone asks: I cannot go to 21.x, because 21.x breaks my CSS layout...). As I discussed in the Forums before I started this bug report, one (the older) just recently stopped searching. Only when logged in as Admin I could see the reason behind that: A COLLATE clash...

{CODE(Colors="Tiki")}
Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '='

Die Abfrage war:
SELECT DISTINCT c.`title` AS name, LEFT(c.`data`, 240) AS data, p.`hits` AS hits, c.`commentDate` AS lastModif, CONCAT(p.`pageName`,': ',c.`title`) AS pageName,outputType ,p.`pageName` AS id1,c.`threadId` AS id2, MATCH(c.`title`,c.`data`) AGAINST ('Kämpfer' IN BOOLEAN MODE) AS relevance FROM `tiki_comments` c, `tiki_pages` p left join `tiki_output` on `tiki_output`.`entityId` = p.`pageName` WHERE c.`objectType` = 'wiki page' AND p.`pageName`=c.`object` AND MATCH(c.`title`,c.`data`) AGAINST ('Kämpfer' IN BOOLEAN MODE) ORDER BY relevance desc, p.`hits`

The built query was likely:
SELECT DISTINCT c.`title` AS name, LEFT(c.`data`, 240) AS data, p.`hits` AS hits, c.`commentDate` AS lastModif, CONCAT(p.`pageName`,': ',c.`title`) AS pageName,outputType ,p.`pageName` AS id1,c.`threadId` AS id2, MATCH(c.`title`,c.`data`) AGAINST ('Kämpfer' IN BOOLEAN MODE) AS relevance FROM `tiki_comments` c, `tiki_pages` p left join `tiki_output` on `tiki_output`.`entityId` = p.`pageName` WHERE c.`objectType` = 'wiki page' AND p.`pageName`=c.`object` AND MATCH(c.`title`,c.`data`) AGAINST ('Kämpfer' IN BOOLEAN MODE) ORDER BY relevance desc, p.`hits`
{CODE}

This older Tiki began YEARS ago (on 2.something?) and went through numerous updates, so far with no problems. The newer one started on 18 (or 12).

Interestingly, both databases have default collation set to utf8_general_ci.

When checking collation with
{CODE(Colors="Tiki")}
SHOW TABLE STATUS
{CODE}

I found that almost all tables were set to utf8_unicode_ci, but some were not (galaxia_workitems,index_628bfa7e573fa,index_pref_de,tiki_activity_stream_rules,tiki_addon_profiles,tiki_credits_usage,tiki_galleries_scales,tiki_goal_events,tiki_h5p_contents,tiki_h5p_contents_libraries,tiki_hp5_libraries,tiki_h5_libaries_cachedassets,tiki_h5_libraries_hub_cache,tiki_h5_libraries_languages,tiki_h5_libraries_libraries (!),tiki_hp5_results,tiki_h5p_tmpfiles,tiki_object_scores,tiki_output,tiki_scheduler,tiki_scheduler_run,tiki_search_queries (!),tiki_stats,tiki_tabular_formats,tiki_user_monitors).

Now that looks like a bug in one of the upgrader scripts.

However, a look at the tables of the newer Tiki showed that there was only one table that used the same collation as the database's default: index_pref_de. ''__All others were set to utf8_unicode_ci!__'' Now that would then be a bug in the installation procedure...

I am not a SQL expert, but I would like to recommend that Tiki sets the default collation to whatever Tiki shall use in the future and then leaves the default (i.e. not declare individual collation). Any individual collation definition is prone to be a future source of trouble...

With the following Tiki configuration:
|| Pref | value
wysiwyg_default | y
wysiwyg_htmltowiki | n
||

If I create a page which contains ~ hs~ (no space between ~ and hs), it works well as invisible hard spaces.
If I copy this page (from wiki → list pages → cogweel → copy), the new page displays ~ hs~ instead of white spaces.

The root cause is, the first page has attribute is_html=0 but the copy has is_html=1.

I installed a Tiki24 Alpha and it showed in the admin control panel the right VCS version (24.0 Alpha)
I then use the same installation with an existing database (update from a Tiki23) and now it show now VCS 23.2.

The version information should be updated accordingly to the Tiki version used.
{img fileId="1716" thumb="box"}
{img fileId="1715" thumb="box"}

Calling tiki-check.php (via the drop down menu of control panels) causes my rented webspace to crash. Literally. First, a 500 is thrown (internal server error), and afterwards the entire webspace goes offline for a couple of minutes! Eventually it does recover, but I have no idea by what mechanism of my ISP this happens. Probably a restart of the (assumed) Docker instance.

This can possibly lead to disturbing the online presence of other customers of the same ISP, depending on the grade of encapsulation of the ISP!

Something dangerous is happening inside tiki-check.php. This must never happen, because this spells out that there is something that can lead to a DOS, either involunaterily by co-admins not aware of the danger of the function, or even by attackers who somehow manage to do whatever tiki-check.php does when this happens. Possibly even by attacking other Tikis hosted by the same ISP, if the ISPs encapsulation is weak...

I therefore propose that tiki-check.php be split up into segments that can be called individually (this eases finding the culprit) and then to have an admin configurable set of functions, so admins can disable dangerous functions.

The installer supports a hardcoded maximum of 16 characters for the database username, while the database name itself is unrestricted in length.

This causes trouble in some when not most environments, especially hosting.
Most panels use a prefix for database user & name so a restriction in length can fastly cause trouble.

For example my company uses plesk and we have resellers that set the prefix of database-name / -user to a string with more than 16 characters, leaving no place for the actual "name". Also some customers set their "name" part to some lengthy strings. This already causes troubles on installation with tikiwiki through the installer.

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.

{syntax type="tiki" editor="plain"}
In recent Tiki versions, the breadcrumb ordered list has a "1." preceding it due to a recent commit related to ordered lists globally. I was looking into how to fix that (how to remove the "1."), when I noticed in my browser inspection tool that the breadcrumb ordered list is flagged as bad HTML because it contains content other than li elements - the item dividers. I checked the Bootstrap breadcrumbs doc page ([https://getbootstrap.com/docs/5.3/components/breadcrumb/]) and see how the dividers are added without breaking the ol / li structure (and also without displaying the "1.".

The breadcrumbs in Tiki would be improved by replacing the current Tiki HTML and CSS with the Bootstrap breadcrumb HTML and CSS.

I noticed this on a page in a wiki structure, which has the structure breadcrumb list at the top. I didn't check yet about other instances of breadcrumbs in Tiki.

__Update__: Checking again, it looks like the structure breadcrumb is already using the Bootstrap classes. One problem is that the item separators should be inserted using CSS ( -+.breadcrumb-item+.breadcrumb-item::before+- selector) rather than as they are now, where they become page content and disrupt the -+ol li+- structure. Also, the global rule to add the "1." is overpowering the -+list-style:none+- property of the -+.breadcrumb+- class, which needs to be fixed globally.

__Update 2__ : I committed a change to prevent the breadcrumb ol from having a "1." appended. The only thing to fix now is to update how the dividers or separators are inserted in the breadcrumb. It should be done via CSS rather than adding text between li elements. This is flagged as incorrect HTML.

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.

{syntax type="tiki" editor="plain"}
Call up the Configurations Wizard within a TikiWiki 27 environment and click through the individual areas in the left-hand area.

In many areas, the options on the corresponding right-hand side are invisible. For example "Set up Login"

Example links to the demo pages for comparison (you have to log in first):
Version 26: https://demo.tiki.org/26x/tiki-wizard_admin.php?&stepNr=3&url=%2F26x%2Ftiki-index.php
Version 27: https://27x.demo.tiki.org/tiki-wizard_admin.php?&stepNr=3&url=%2F26x%2Ftiki-index.php

Existing Forum entry: https://tiki.org/forumthread79549-TikiWIki-27-0-Configuration-Wizard-setting-options-not-visible

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.

When a wiki syntax field calls maketoc and the FADE plugin, the table of contents generated may contain bogus entries at the beginning. All the titles in the body of any call to FADE are taken into consideration by maketoc.

This bug is very similar to {wish id=5496}.

! Example

With the following field content, the TOC contains 2 headers, instead of just "Normal header":
{CODE(color="tiki")}
{maketoc}

! Normal header
This is a test page for the FADE plugin.

{FADE(label=Label)}
!! Header which should not be in the TOC
Lorem ipsum...
{FADE}
{CODE}

{syntax type="tiki" editor="plain"}
Auto TOC is gone since Tiki29x.
tested on demo too.


Can't post screenshot...