Category: Less than 30-minutes fix

Because I keep finding bugs where translation is impossible due to missing tra(), tr() or tr in curly braces, I opened this new umbrella bug report.

Here I will add only newly found bugs, I will not integrate the already existing bug reports into this!

/lib/prefs/calendar.php has this on line 78:

{CODE(Colors="Tiki")}
'description' => 'Interval to show between minutes on time selectors',
{CODE}

Without tra(), the description cannot be translated into any language...

Tikiwiki 2.3 was upgraded to 4.0. Upgrade went well, DB connection was found, DB was upgraded, installer locked. TW4.0 is unable to connect to the MySQL5 DB it was able to upgrade seconds before. See: http://tikiwiki.org/tiki-view_forum_thread.php?topics_offset=1&forumId=6&comments_parentId=35478

Impossible to go to next or previous page in http://www.xxx/tiki-view_articles.php or http://www.xxx/tiki-listpages.php
tikiwiki 3.0 RC2

It took me some time to find out why I could not translate a particular string in /lib/prefs/freetags.php, and this is it:

{CODE(Colors="Tiki")}
'freetags_normalized_valid_chars' => [
'name' => tra('Valid characters pattern'),
'description' => tra('Click on the links below to set or clear a pattern to limit characters accepted in tags. '),
'type' => 'text',
'size' => '30',
'hint' => 'Useful to eliminate characters such as “,” which users can enter by mistake instead of a space.',
'default' => '',
],
{CODE}

This looks decent, it also carries calls to the tra() subroutine. But I could not catch it with this entry in custom.php:
{CODE(Colors="Tiki")}
"Useful to eliminate characters such as “,” which users can enter by mistake instead of a space." => "Nützlich, um Zeichen zu eliminieren wie Kommata, die Benutzer anstelle von Leeerzeichen eingeben können",
{CODE}

The string for pattern matching is exactly identical to it's declaration in the source code, but it was not caught. Until finally I pumped the string into GHex, to look at its real composition.

{CODE(Colors="Tiki")}
echo -n "Useful to eliminate characters such as “,” which users can enter by mistake instead of a space." | od -A n -t x1
55 73 65 66 75 6c 20 74 6f 20 65 6c 69 6d 69 6e
61 74 65 20 63 68 61 72 61 63 74 65 72 73 20 73
75 63 68 20 61 73 20 e2 80 9c 2c e2 80 9d 20 77
68 69 63 68 20 75 73 65 72 73 20 63 61 6e 20 65
6e 74 65 72 20 62 79 20 6d 69 73 74 61 6b 65 20
69 6e 73 74 65 61 64 20 6f 66 20 61 20 73 70 61
63 65 2e
{CODE}

So what's looking decent are actually Unicode characters

{CODE(Colors="Tiki")}
e2 80 9c 2c e2 80 9d
{CODE}

I have absolutely no idea how to escape that so PHP will find it in pattern matching... Devs, please do not use Unicode unless really really necessary...

There are text strings that resist being translated. But although they clearly show up on the admin UI, they cannot be found anywhere in the source code? How can that be?

Example: Stop words for unified search index (tiki-admin.php?page=search).

The preset value is
{CODE(Colors="Tiki")}
a,an,and,are,as,at,be,but,by,for,if,in,into,is,it,not,of,on,or,s,such,t,that,the,their,then,there,these,they,this,to,was,will,with
{CODE}

But a grep through the entirety of Tiki Wiki sources yields no hit?! These values must be defined somewhere... And stop words, if they are not reserved magic keywords i.e. reserved by PHP or MySQL, would be language dependant and thus in need of localization... IMHO.

In a Tiki 11 svn installation an upgrade notice is shown, which suggest to switch from Tiki 11.0 to Tiki 11.1 or do a major upgrade to Tiki 9.0 as follows:

-+Version 11.0 is no longer supported. A minor upgrade to 11.1 is required.+-
-+Version 11.1 is still supported. However, a major upgrade to 9.0 is available.+-

The computation and suggestion of the major upgrade version number is not correct. I'm not sure whether this problem is already fixed in a later version or not.

I see no other mechanism for proposing corrected localization files, so I post it as a feature request to I18N. While I am still deep into the main body of translation (so far I made > 2060 corrections and additions, and custom.php has grown to 1/4 the size of language.php, 231 kbytes, I have seen that there is a smaller file, language.js, that contains some spelling errors (old German spelling which is outdated since 1996, the big official reform of German spelling) and IMHO a wrong language level (addressing the user in the second person, using imperative). And since language.js is a lot smaller, I finished this one and hereby propose it to be included in future versions. This file was writen on Tiki 18.6.
Thanks
hman

Update PluginVersions to Bootstrap classes (missing tabbed-like display). Tab titles show up as if they were plain text. However, if you click on them, links do work indeed. It¡s just a question of missing css classes, I guess, to restore the intuitive display.

See:
https://doc.tiki.org/PluginVersions#Basic_example

And compare it with:
https://doc.tiki.org/pluginTabs#Example

These plugin was used in doc.t.o pages. It looks like a standard Plugin Tabs, but the difference is that when you click on a tab title, all sections with plugin tabs siwtch to that version, so that you can print a long page (ideally, a whole wiki structure) with the sections related to that version of the software set to display its contents in place.

Something like these css properties might be missing at __./themes/default/css/default.css__ in trunk:
{CODE(colors="css" ln="1")}
/* Versions plugin */
.versionav {
padding: 0;
border: 1;
margin-bottom: -1px;
border-color: #eeeeee #eeeeee #dddddd;
border-bottom: 1px solid #dddddd;
}

.versionav .button {
margin-bottom: -1px;
}

.highlight {
background-color: #f5f5f5;
color: #262626;
margin-bottom: -1px;
border-top: 1px solid #e2e2e2;
border-left: 1px solid #e2e2e2;
border-right: 1px solid #e2e2e2;
}
{CODE}

{syntax type="tiki" editor="plain"}
Error when trying to start the Tiki after Upgrade from 3.1 to 4.1. The installation and upgrade during installation reported "Success":

"System error.
The following error message was returned:

Champ 'version_minor' inconnu dans field listThe query was:

SELECT `page_id`, `pageName`, `hits`, `description`, `lastModif`, `comment`, `version`, `version_minor`, `user`, `ip`, `flag`, `points`, `votes`, `wiki_cache`, `cache_timestamp`, `pageRank`, `creator`, `page_size`, `lang`, `lockedby`, `is_html`, `created`, `wysiwyg`, `wiki_authors_style`, `comments_enabled` FROM `tiki_pages` WHERE `pageName`=?
Values:

1.UserPageadmin
The built query was likely:

SELECT `page_id`, `pageName`, `hits`, `description`, `lastModif`, `comment`, `version`, `version_minor`, `user`, `ip`, `flag`, `points`, `votes`, `wiki_cache`, `cache_timestamp`, `pageRank`, `creator`, `page_size`, `lang`, `lockedby`, `is_html`, `created`, `wysiwyg`, `wiki_authors_style`, `comments_enabled` FROM `tiki_pages` WHERE `pageName`='UserPageadmin'
"

upgrade all databases in a multitiki installation in a single go with console.php

with some param like "--site=all":
{CODE()}
php console.php d:u --site=all
{CODE}

The Webmail and Groupmail feature uses old Tiki icons (or plain text).

They should use the last Tiki icon generation (FontAwesome) and text links should be modernized accordingly.

Compare these 2 pages:
http://tiki.org/Community
http://next.tiki.org/Community

Go to the section "Contributors to this page" and mouseover the names one by one: Torsten Fabricius , Marc Laporte , Rick , Oliver Hertel , ...

userlist heading link color

table background and th link are set to white in tiki-list_users.tpl
Setting a.userlistheading to another color into theme css did not overide this

I have a tiki site that's running trunk 4.0. It has User Watches enabled, and the wiki feature also.

When I go to My Watches, I don't see anything that would allow me to globally set watches on all pages of the wiki.

Yet, if I enable User Watches Translsations and go to My Watches, then I see a picklist with a single element for watching creatino of any translation on the site.

Seems like a bug. I remember that I used to be able to globally set watches on all wiki pages (not just translations), and I think it was in the My Watches window.

When selecting a Machine Translation, the resulting page is "broken" -- the left & right columns appear after/under the center column.

Tested with 5.0SVN on http://info.tikiwiki.org with FiveAlive theme

To duplicate:

#Go to home page: http://info.tikiwiki.org/tiki-index.php?page=HomePage
#Select machine translation: __Spanish__
The left column in the Spanish translation is at the bottom of the page.

When importing tracker items from a utf-8 csv file, the first non-ascii character in a field dissapears (except when surrounded by apostrophes).

example:
123;čaj;abc;šaša;def

is imported as:
123;aj;abc;aša;def

but this works alright:
123;"čaj";abc;"šaša";def


The other characters are fine. Tried with a text field and radio button.
Using version 5.1.

{syntax type="tiki" editor="plain"}
In attempting upgrade from Tiki 27.1 running fine with PHP 8.4.4, Tiki 28.1 exhibits numerous warnings and deprecation warnings rather than displaying installation page:

PHP Deprecated: voku\helper\UTF8::extract_text(): Implicitly marking parameter $length as nullable is deprecated, the explicit nullable type must be used instead in C:\wwwroot\tiki\vendor_bundled\vendor\voku\portable-utf8\src\voku\helper\UTF8.php on line 1622
PHP Deprecated: voku\helper\UTF8::file_get_contents(): Implicitly marking parameter $offset as nullable is deprecated, the explicit nullable type must be used instead in C:\wwwroot\tiki\vendor_bundled\vendor\voku\portable-utf8\src\voku\helper\UTF8.php on line 1842
PHP Deprecated: voku\helper\UTF8::file_get_contents(): Implicitly marking parameter $max_length as nullable is deprecated, the explicit nullable type must be used instead in C:\wwwroot\tiki\vendor_bundled\vendor\voku\portable-utf8\src\voku\helper\UTF8.php on line 1842
PHP Deprecated: voku\helper\UTF8::getSupportInfo(): Implicitly marking parameter $key as nullable is deprecated, the explicit nullable type must be used instead in C:\wwwroot\tiki\vendor_bundled\vendor\voku\portable-utf8\src\voku\helper\UTF8.php on line 2580
PHP Deprecated: voku\helper\UTF8::html_entity_decode(): Implicitly marking parameter $flags as nullable is deprecated, the explicit nullable type must be used instead in

....

It is possible to watch for new articles here: tiki-user_watches.php

So why not add an "eye" in view articles and list articles?

I setup a webmail account and viewed mail box in tiki webmail. after that I sent two mails from another account with different subject and body. I viewed both of them in mail box and clicked one of them. after going back to mail box both mails was marked as read! so I selected witch I haven't read and marked it as unread, but both of them was marked as unread!

UserPages should be off by default, and activated per relevant profile.


Syntax should become:
{CODE()}User:XYZ{CODE}
instead of
{CODE()}((UserPageXYZ)){CODE}

__Done in new installs of Tiki4 but there is no migration script__


When User pages are activated, they should be much more obvious for users. (ex.: in MyTiki)


Same thing for ((doc:User Trackers))

When previewing an item, you get:

Notice: Undefined index: calendarId in /home/amette/public_html/tikiwiki-BRANCH-1-9/tiki-calendar.php on line 395

On saving, this comes double (with another line number) and at the first try I got a lot more about "Undefined index: places, people etc"

When using articles on a tiki 5 site, using a thenews.css-based theme style, we don't see the horizontal menu at the top bar.
On all the other tiki features, that menu is shown as expected.
You can reproduce that here:
http://intercanvis.net

versus


http://intercanvis.net/articles

When you use re captcha the Privacy Terms panel overlap (right) element of the page.
You can always scroll to see what is under unless you are at the bottom of the page where the footer and bottom_modules elements are under it.

When recaptcha is enable we should add a margin-bottom so it is always possible to see the footer content.

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

15.x: Improvements needed for mobile view of many *.t.o sites (dev, themes, doc, ...)

{img src="display1077" thumb="box" width="800"}

(1) No way to login at dev.t.o or doc.t.o, for instance, when browsing the page in the smartphone
(tested with Chrome on Android, but it seems to be reproduced with a browser on a desktop and making it narrow enough as a smartphone)

(2) There is no logo nor site name displayed in the top header of most *.t.o sites. OTher (non-tiki) bootstrap websites do display their logo and name when shown through smartphone. IS tehre anything that can be done in the Tiki side to fix this?

(3) Fullscreen button is shown on top of the button at the top layer to display the logo and site name. Therefore, clicking there, fires the fullscreen in some cases. And when in full screen, in a smartphone, I couldn't come back to normal display mode clicking at that button in the smartphone for some reason, I had to fix the param in the url to get back to normal.

(4) The submenu is not shown in dev.t.o and doc.t.o but it is shown in themes.t.o Why? How shall we edit the submenus so that they are shown in the smartphone display?

Thanks

12.x - 15.x: Tracker: filter items is broken when radio button with labels set (0=No,1=Yes,2=Dunno).

No matches are found when there are some items which met the intended criteria.

--It'll be-- reproduced in an attached intance --in short. Stay tuned!-- :-) {sign user="xavi" datetime="2016-02-09T12:21:27+00:00"}
Login in here:
http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1
u: admin
p: 12345

You will see the field TestRaduio, with some values (0, 1 and 2; their labels, in fact)

Try to filter by that field:
http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1&status=o&sort_mode=f__asc&filterfield=8&filtervalue%5B1%5D=&filtervalue%5B2%5D=&filtervalue_other=&filtervalue%5B3%5D=5+%28high%29&filtervalue%5B8%5D=0%3DNo&filter=Filter#
---
__Update:__ {sign user="xavi" datetime="2016-02-10T10:42:06+00:00"}
the problem is also found (and still unsolved) at teh trackerfilter level. Sorry, I tried for one hour, but I couldn't get the right syntax to port this type of fix there also. :-/
To reproduce, see it here:
http://xavi-9794-5810.show.tikiwiki.org/tiki-index.php?page=HomePage

__The issue is reproduced also for dropdown fields when labels are set, etc. See it reproduced with field "Priority" (Dropdown). __

__Reproduced also with "Dropdown with other" (field __Location__) in the tracker itself, but it works as expceted through Plugin TrackerFilter.__
Does work:
http://xavi-9794-5810.show.tikiwiki.org/tiki-index.php?page=HomePage

Doesn't work:
http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1&status=o&sort_mode=f__asc&filterfield=2&filtervalue%5B1%5D=&filtervalue%5B2%5D=0%3Droom+1.1+%2855+seats%29&filtervalue_other=&filtervalue%5B3%5D=5%3Dhighest&filtervalue%5B9%5D=y&filtervalue%5B10%5D%5B%5D=1&filter=Filter#

Multiselect seems to work well, as expected, in both tracker itself and plugin trackerfilter.