Category: 19.x

Windows 10
Tiki version 19. installed with InnoDb.
Wamp64 ver 3.1.0,
apache 2.4.27
php 7.19

Issue: Composer setup.exe installed fine, yet tiki-admin.php?page=packages&cookietab=4
Diagnose option: Install Composer----Failed
~~#F00: Error
There was a problem when installing Composer.
The "https://getcomposer.org/versions" file could not be downloaded: php_network_getaddresses: getaddrinfo failed: No such host is known.
failed to open stream: php_network_getaddresses: getaddrinfo failed: No such host is known.
~~
1. Composer downloaded and installed.
2. Logged off and log back in, to verify installation options were updated.
3. Shelled to D.O.S. and typed 'composer' and its help menu showed up immediately.
Verified PHP 7.19 was the path that would be utilized for PHP commands.
4. Verified CURL was active in the PHP extensions. Checked if 'git' was available, it wasn't.
5. Verified no proxy was running anywhere ( I don't utilize proxies, but checked just in case).
6. Ran TIKI / Diagnose/ Install composer and received the error.
7. Read information on github about the error but did not have issues relating to their troubles.
8. Backed up composer.json.dist and renamed the copy to composer.json which was
in the tiki root location.
9. Pressed the tiki install composer option, got same problem.
10. Deleted composer.json and got same problem (as if it wasn't looking for composer.json).

I was expecting that once composer was installed from Composer-Setup.exe,
the tiki / diagnose/install composer would execute the program utilizing proper install switches or at
least advise the admins that it can't be done on a local wamp64 server, or whatever the case may be.

When I access the 'Show Instance' I created (http://mikeua-11714-6595.show.tikiwiki.org/) for a bug I filed (https://dev.tiki.org/item6595-New-visual-menu-not-working-properly) it says:

"Lost Tiki database connection
Sorry but there seems to be a problem connecting to the system's database
This may only be a temporary problem, so please wait a while and click
to try and go back to the home page
If it persists you should contact your system administrator "

Has anyone else had problems with 'Show Instances'?

thanks,
Mike

On fresh install of 19.x the form on -+tiki-remind_password.php+- page is really ugly first impression.

See https://screenshots.firefox.com/3SNIvciKwFHlLJVF/demo.luciash.eu

Please use Bootstrap4 form classes to fix the tpl file to make it look nice.

https://wikisuite.org/tracker2 when I add an item, I get pop up but I can't save. Please see image.

It seems that what was achieved with profile
https://profiles.tiki.org/Hide+Fixed+Top+Nav+Bar+on+Scroll

up to Tiki18 (included) is no more working in Tiki 19.x, maybe due to changes related to the Bootstrap4 migration?

I.e.: Top module zone in dev.t.o and other *.t.o sites is no more hidable on scroll, nor topbar module zone gets sticky anymore.

I presume this is easy to fix (<30' ?) by some css & bootstrap 4 master in the tikiverse? (not me for sure)

Thanks

P.S: fyi, Work in progress to get the profile updated:
https://profiles.tiki.org/Hide+Fixed+Top+Nav+Bar+on+Scroll+19

Plugin Pivottable inserts wrong codes in params data, rows and cols through plugin helper ui. Reproduced in 18.x and 19.x as of Jan 19 2019

I selected the name of the tracker in the dropdown shown, and a few of the tracker fields I chose for rows and columns, and the codes inserted in the wiki page sayed later were not the expected ones for each type of field:

Example of codes inserted (which fails to show data nor columns or rows):
{CODE()}
{PIVOTTABLE(data="1" rows="1:2" cols="3" ...)} {PIVOTTABLE}
{CODE}

Expected code to be inserted
{CODE()}
{PIVOTTABLE(data="tracker:1" rows="permNameA:permNameB" cols="permNameC" ...)} {PIVOTTABLE}
{CODE}
---
Reproduced in the show instance for 18.x
u: admin
p: admin
http://xavi-9794-6937.show.tikiwiki.org/tiki-index.php?page=HomePage

A Group assignment to many users is lost repeatedly under unknown conditions

It's the third time I have to re-assign that groups to those users.
I have no clue why this happens :-(

The "Quick Admin" module is no longer assigned in default installs starting from {commit id=67387} (Tiki 19).

When I try to edit: https://doc.tiki.org/Items-List-and-Item-Link-Tracker-Fields

I get a 500 error.

When I try to edit and save a page on https://tiki.org I get a WSOD. Is it the same issue? {sign user="luci" datetime="2018-10-23T10:06:12+00:00"}

Not sure since when but access to Google fonts (the Lato web font) fails now on all tiki.org sites. This is reported in the Chrome browser console here:
{CODE()}
Access to font at 'https://fonts.gstatic.com/s/lato/v14/S6uyw4BMUTPHjx4wXg.woff2' from origin 'https://dev.tiki.org' has been blocked by CORS policy: Request header field x-client-data is not allowed by Access-Control-Allow-Headers in preflight response.
{CODE}

__Update__: seems it is back to normal. Works for me now. {sign user="luci" datetime="2018-11-26T13:03:39+00:00"}

Pivottable allows using activitystream as data source in Tiki19. But the edit plugin UI in Tiki doesn't allow the user to do so, it seems to be hardcoded to get some tracker in the first and compulsory field. Otherwise, it complains saying that that field is compulsory (even if you wrote activitystream in the text field), and it doesn't let you save the form.

Currently, there are four preference filters available in the Control Panel interfaces: "Basic", "Advanced", "Experimental" and "Unavailable".

As a user new to Tiki, I have on several occasions noted features that looked interesting, but which I have not enabled as I have subsequently found it is planned to deprecate them. In some cases this was obvious (e.g. a 'warning' icon with the deprecation message on hover next to the feature checkbox), in others it wasn't (i.e. I only found out about it from doc.t.o or related places).

On the assumption that it will help with planned deprecations if new installations don't enable and start using deprecated features, I would propose that a "Deprecated" preference filter be added, that relevant controls be assigned to it, and that it be disabled by default in new installations.

I understand the criteria for such might be controversial (indeed, I hope I'm not reigniting a heated discussion by posting this!) and so would understand if this is WONTFIXED. I also recognise that it is less appropriate for a new user to suggest criteria here than for those that have had Tiki installations for some time and/or are directly involved in development, which is why I haven't listed any in this initial report.

There is a parameter "Update Empty" in the tracker field type.
I don’t see any documentation about it but it is supposed to add auto-increment numbers to items in this tracker that don't have one yet.

I tried it on Tiki18 it didn’t filled the empty fields.

After testing it it seems a auto-increment number is added to empty fields if "itemId" is not the parameter selected. Would be nice to fill in this case too and not to have the admin to open and save each item.

{CODE()}
Update Empty
Add auto-increment numbers to items in this tracker that don't have one one. ********** N.B. This modifies data and there is no undo **********
{CODE}

As pointed out by Brendan/drsassafras ([https://tiki.org/forumthread69192-CSS-Compatibility-Issues?topics_offset=14]), the CSS files in trunk are missing vendor prefixes that Bootstrap 4 bootstrap.css normally has. This is because the Autoprefixer script isn't being used in Tiki's current stylesheets workflow. For better browser compatibility (so we aren't supporting only the latest browser versions), it would be good to integrate an Autoprefixer script in our workflow.

I found this script, which could be helpful: https://github.com/vladkens/autoprefixer-php . Or maybe there's another solution that works for the devs who compile SCSS to CSS.

Update: I added Release Blocker category to put this on the front burner. The solution doesn't have to be the script I found, but some solution is needed for Tiki 19 to have maximum browser support.

Update 3/16/2020: This isn't fixed in my local installation; I'd like us to have another look at it. {sign user="chibaguy" datetime="2020-03-16T06:54:46+00:00"}

Update 9/22/2020: This seems to be less an issue as legacy Edge and IE browser usage declines. I can't test IE10 and other instances of vendor prefixes aren't critical. I'm removing the blocker category and changing the status to pending for now, and will check again when we update to Bootstrap 5. {sign user="chibaguy" datetime="2020-09-21T16:21:02+00:00"}

Forum attachments used to work for me in the past.
This time, I tested using them again in a 19.x site on a clearos-based server, with extra php 7.1 added, etc (following documentation of wikisuite, etc)

I get error 500 when attempting to upload a small file (<100Kb) to a forum, either in db or file storage on disk. Folder at the server works for files uploaded to file galleries.
Error message:
{CODE(colors="shell" ln="1")}
[root@server user]# tail /var/opt/rh/rh-php71/log/php-fpm/www-error.log
thrown in /var/www/virtual/example.org/html/lib/comments/commentslib.php on line 121
[10-Dec-2018 11:27:09 Europe/Madrid] PHP Fatal error: Uncaught Error: Class 'Perm' not found in /var/www/virtual/example.org/html/lib/comments/commentslib.php:121
Stack trace:
#0 /var/www/virtual/example.org/html/lib/comments/commentslib.php(3939): Comments->add_thread_attachment(Array, '43', Array, 'Solicitud Audit...', 'application/msw...', 58880, 0, 0, Resource id #10, '')
#1 /var/www/virtual/example.org/html/comments.php(178): Comments->post_in_forum(Array, Array, Array, Array)
#2 /var/www/virtual/example.org/html/tiki-view_forum_thread.php(279): include_once('/var/www/virtua...')
#3 /var/www/virtual/example.org/html/route.php(316): include('/var/www/virtua...')
#4 {main}
thrown in /var/www/virtual/example.org/html/lib/comments/commentslib.php on line 121
{CODE}

We need to provide natural sorting of the -+Priority+- field in the bug tracker at dev.t.o
Example: click at sort bugs in the wishlist page by Priority in descending order:
https://dev.tiki.org/tiki-index.php?session_filters=y&tr_sort_mode1=f_138_desc&page=Wishlist

First, items with priority 90 are shown.

After that, items with priority 9 are shown. However, between 9 and 90 there are lots of priorities that should be shown before 9 is shown, if they were understood as numbers, not as characters.

See:
https://www.php.net/manual/en/function.natsort.php

Currently, getting the DISTINCT values of a field of a tracker is pretty hardcore. You need to go through the whole list of items of that tracker and do some tricks in a smarty template to finally get the distinct list of values of a field.

Would be nice to have some plugin to do that?

To help solve the problem of tall responsive wide tables or other content not being understood to be scrollable, one solution is to add a second scrollbar at the top of the scrollable area. A script to do this is at [https://github.com/avianey/jqDoubleScroll].

When doing a plugin list, we can sort the data. For tracker fields data, we can sort by comparing the texts of the fields. But for sorting by categories, this is not possible. The list will only be sorted by the category ID (asc or desc). It would be nice to be able to sort by category text.

I noticed this while using the tiki reference plugin. Thought it was something in the plugin creditor interface that was broken, but I now see that the plugin was successfully added. So there is nothing functional broken. However. The UI surrounding the adding of a plugin is certainly broken.

My original report:

Adding a tiki reference appears to be broken now. I get as far as adding a reference, but when I try to create one it just hangs on a grey screen. Then nothing.

Steps to reproduce:
Enable "Wiki references" preference
Edit a wiki page
Click the "Add Reference" icon
Add a Biblio Code and click save.
The screen now "hangs" on a greyed out screen.

When someone changes the Related-to field here I receive email notification like this:
{CODE()}
Item Modification

Tracker:
Bugs & Wish list
Item:
6887 WSOD (again) on tiki.org forum thread link

View the tracker item at:
https://dev.tiki.org/item6887-WSOD-again-on-tiki-org-forum-thread-link

Author: luciash d' being
Date: 01 Nov 18 11:51 CET

Status: Open
----------

----------


{CODE}

I added the related tracker item to the Related-to field on https://dev.tiki.org/item6887-WSOD-again-on-tiki-org-forum-thread-link
__As you can see it does not report the change on that field at all.__

Admins or Moderators should be able to manage (edit and delete) tags from the web interface.

https://tiki.org/forumthread67133

I guess we have similar tools/page we can reuse.

The multilike plugin, https://doc.tiki.org/Multilike expand the like function with options similar to a ranked like; Good,Great,Excellent
It display only a thumb-up for now. {icon name="thumbs-up"} / {icon name="thumbs-o-up"}

However it could be used easily for many other use case if it was possible for the admin to set the icon.

Ex: Like / Unlike
{icon name="thumbs-up"} / {icon name="thumbs-down"}

We should add a plugin parameter to set the icon used.

When I add the FancyTable tool in the toolbar, editing a page in wysiwyg is impossible because the striped "loading" bar just turns and never stops. One can never edit.

The browser devtools claim that « The requested URL /vendor_bundled/vendor/ckeditor/ckeditor/plugins/FancyTable/plugin.js was not found on this server. »

This file was probably never in any version of Tiki.

Going to Admin Categories > Bug on dev.tiki.org returns alerts on top of the page:
{CODE()}
ErrorErrorError
Tracker list_items ran out of memory after 0 items.Malformed search query: Parsing search query failed: "org.elasticsearch.common.ParsingException: [_na] query malformed, must start with start_object"Notice: invalid variable value: $_GET["maxRecords"] = undefined
{CODE}