Category: 24.x

Hello, especially the Admin UI revamp team.

I love the new Tiki Admin UI, whilst I am quite massively missing a few nice ideas or our old one. When I supported the idea of a more WP-like approach, I never thought we would lose the old feature tiles panel, which has a lot of advantages in respect of time saving.

I suggest, that we could put it into a module and then add it to the list of standard admin modules, that can be optionally loaded into the admin dashboard.

Aswell there are a number of administration places, where the new admin dashboard style is not yet applied. I assume that is just a matter of time and ressources.

Comments welcome.
Best regards,
Torsten
---

Uploading an animaged gif image file that shows a bug reproduced is not an easy task tin dev.t.o.
I had to do that because the record rtc feature is not usable yet, and I wanted to reproduce the issue visually. I did that in an animated gif. I edited the corresponding [item7795|bug report], and uploaded the gif file throught the toolbar icon to "Choose or upload images".
I got the image uploaded (to the default location, I didn't change it, expecting "happy path"), but the wiki syntax automatically inserted seems to not be adapted to displaying gif images.
I recall that any plugin img param that attempts to resize the image converts it to png (or Tiki used to do so years ago), so that I removed the param to make a zoombox, I just left the param to indicate the fileId. But nothing was displayed in the parsed textarea of the tracker item once saved.

Similarly, going to the view file (icon shown from the since last visit module) showed nothing, which might trigger the falsse sensation that the file upload failed.
https://dev.tiki.org/file1?fileId=1562&view=page

But it didn't fail.
If you use the oldish syntax to display the image as an image, then it displays properly, as it can be reproduced here:
https://dev.tiki.org/item7795-Cannot-use-Record-RTC-page-self-refreshed-before-accepting-perm-to-record

Couldn't we get that plugin img when using fileId param to automati8cally display the gif image as image when the plugin notices that it's a gif image indeed?
Somehow...
HTH

The global navbar color assigned on tiki-admin.php?page=look is ''always'' applied, so when assigning a menu module and giving it a parameter like "navbar_class=navbar navbar-expand-lg navbar-light bg-light", when the global pref is "dark", this is the result in the page source: -+ <nav class="navbar navbar-expand-lg navbar-light bg-light navbar-dark bg-dark" role="navigation"> +-

The combination of color classes causes problems for link colors, etc.

There are times when, because of the theme colors, both navbar-dark and navbar-light are needed, like when the topbar zone has a dark background and the page footer has a light background, so when a per-module color parameter is specified on admin-modules, it should __replace__ the Look and Feel global setting, not be added to it.

In a Tiki24.x using ElasticSearch, if you partially configure or misconfigure the Goal feature at tiki-admin.php?page=community&cookietab=2&highlight=goal_enabled#contentadmin_community-2 you won't be able to complete index rebuild command.

To reproduce, simply enable "Goal, recognition and rewards" and try -+php console.php i:r -p+- in the shell.

You will have the following error.

{CODE()}
% php console.php i:r -p
[2023-04-04 09:01] Started rebuilding index...

Unified search
--------------

Engine: Elastic, version 7.14
3 mins/4 mins [====================>-------] -- Processing activity documentsA error was encountered while running a command
Argument 1 passed to Search_Type_Json::__construct() must be of the type array, string given, called in /Users/bernardsfez/Documents/Shocksite/www/htdocs/wiki-to-yes.org_tiki24/lib/core/Search/Elastic/TypeFactory.php on line 81 on line 13 of /Users/xxx/Documents/xxx/www/htdocs/xxx_tiki24/lib/core/Search/Type/Json.php
{CODE}

The index rebuilt should complete and throw an error/warning/notice about the feature not being configured correctly.

They would be nice to have easy to setup “predefined schedules” delivered within Tiki by default.
Rebuild sitemap, rebuilt-index, ping to an external service, etc...

We could also implement some mechanism for them to be turned on and off via preferences.
IE (TBD):
In Admin => Search => Indexes;
Do you want to allow the scheduler to rebuild the index on a regular basis ?
Every nnn minutes (1440 = a day)

At https://tiki.org/tiki-syslog.php we have a link to "Log SQL".
If we click on it we have the following error.

{CODE()}
×
Error
This feature is disabled: adodb
{CODE}

The link shouldn't be displayed if the feature is disabled.

Seems it is back...

On fresh install (new db) after filling admin new password and email you are redirected to the wizard.

If you close it (toggling show on start) you are redirected to -+tiki-index.php?page=HomePage+-, the HomePage

It show an error:
Error

Page not found
HomePage

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

First visit for new admin experience is critical...

---
{FADE(label="Previous report - Tiki16" icon="y")}
On fresh install (new db) after filling admin new password and email you should be redirected to the HomePage (showing the wizard by default).

However, I soon as you submit the admin information you are redirected to an error page:
Error

Page not found
HomePage

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

If I refresh the page or if I type mydomain/HomePage in the URL bar, page it is still not found.

If I click on the "Home" item of the menu I’m redirect to tiki-index.php and I can see the homepage.
From this point HomePage exist and can be accessed entering the address in the url bar from wiki page list, etc.

The wizard is lost in space.
{FADE}

If you click (two times...) in order to sort the Wishlist by modification date descending (btw., IMHO this should be the default...), the alleged latest edits are reported to be from Dec. 21. I have opened modified two other bug reports this year, and the list of recent changes shows them, but somehow they are not listed at the top of the Wishlist, at least not above Dec. 21 ?! See screenshot...

Thanks
hman

1. The {include page=“name”} command is tremendously useful for naive wiki users who add content. It lets them create macros and re-use them at will.

So I suggest that this might deserve an alias {macro } and deserve a description in the wiki syntax help.

Also a slight simplification. If there is no ‘page=”name”’ text but there is {macro “name”} then use “name” anyway.

Any user could do {macro “myheader”} at the top and {macro “myfooter”} at the bottom and {macro “myusualrant”} wherever they want. They just have to make an orphan wiki page for each macro they want.

2. This is so useful and flexible that you might deprecate the “apply content template” thing on the Properties tab. It is hardly any easier to use, and it allows the user to choose only one macro at the beginning. It should keep working for the users who have already used it, but there’s no particular reason for anyone to use it again.

3. To really put the icing on the cake, you might let admins have two macros for each user page, one at the top and one at the bottom. These should not be visible when the user edits the page. So for each page category, the admin could decorate it a special way. Some might automatically get polls or other info visible. Or dancing bunnies, or whatever. It lets admins customize user wiki pages without coding, in ways that are hard to do without coding now. Without annoying users with the displayed calls on their edit pages which they might edit wrongly.

At /categories and https://dev.tiki.org/tiki-admin_categories.php we can see the categories list.
It is a bit stiff and when you have a lot of categories and start to open them to see the child categories the UI/UX is not very good.

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

I've been thinking about this quite a lot lately.

When I create a ticket and I type the first letter of my ticket, I'm suggested previous and existing ticket based on a filtering of my typing. But this is not useable at all and likely no-one look at it. As proof, we have a lot of duplication. See my screenshot below this is not useable.

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

At the admin search preferences I entered "alias" and it didn't returned aliases.
Something that should have been done to be user friendly.

May be by extension is concerns all murals form of a term ?

In history, a user can view pages, version after version, to find a change.
He can do it using the left and right arrows when viewing a page.

In the top nav bar (t_navbar) the buttons doesn't refers to the actual page he is previewing (displayed) but to the actual version of the page published.

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

# It is a bit confusing for most users are expecting unspecified-target actions to be applied to what they see.
## First button label should be changed to "Go back to the actual page (last version)"
## Second button label should be changed to "Edit actual page (last version)" (or eventually removed)
# To view the source of this version of the page (if I'm looking for a plugin code or some syntax), I have to remember the page version number, go back to the page, go back to history and view the source (if available).
## A "View this version page source" is missing

Gary may be consulted for better wording. ;-)

Installed a Tiki from git 836e12ee and ran Composer.
Got some warnings:

{CODE()}
Could not scan for classes inside "vendor/adodb/adodb-php/" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/h5p/h5p-core" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/h5p/h5p-editor" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/pear/xml_rpc" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/smarty/smarty/libs/sysplugins/smarty_security.php" which does not appear to be a file nor a folder
{CODE}

{CODE()}
Package container-interop/container-interop is abandoned, you should avoid using it. Use psr/container instead.
Package montefuscolo/xmpp is abandoned, you should avoid using it. No replacement was suggested.
Package symfony/inflector is abandoned, you should avoid using it. Use EnglishInflector from the String component instead.
Package zendframework/zend-version is abandoned, you should avoid using it. Use ocramius/package-versions instead.
Package zendframework/zendservice-akismet is abandoned, you should avoid using it. No replacement was suggested.
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
Package sensiolabs/security-checker is abandoned, you should avoid using it. Use https://github.com/fabpot/local-php-security-checker instead.
{CODE}

May be it could be cleaned ?

I installed a brand new Tiki24 and below the "do you want to lock your Tiki installation" I saw the following
{CODE()}
Upgrading and running into encoding issues?
We can try to fix it, but make sure you have backups, and can restore them.
Oops. You need to make sure client charset is forced to UTF-8. Reset the database connection to continue.
{CODE}

It doesn't really make sense, it is wrong (the db is UTF-8, utf8mb4_unicode_ci) and un-consistent.
It also propose 0 action.

I guess some conditions or logic are wrong.

This is the second Tiki24 I install from new files (git clone) and update the database in the last 48h that shows the issue. (one on my local OSX, another one a Debian10 Virtualmin)

On database update it keep coming back on the Tiki Installer Security Precaution page.
Then it is in loop as long as I keep being on the tiki-install.php.

If I then jump directly to the Homepage I can see an incomplete installed Tiki.
I have to complete manually using the console (see the workaround I added)

---
Update 2022-08-14
Just tried again on a Debian10 Virtualmin and this time the installation wasn't stuck on the Tiki Installer Security Precaution page. BUT seems it didn't complete the final stages (index rebuilt...).
I completed manually again and this fixed the issue.

There are places Tiki ask to confirm "an" action but the action is not stated.
User should be told "what" is to be confirmed.

Here a video from Calendar, delete event.
{file type="gallery" fileId="1696" showicon="y"}

When "jQuery Select2 Select Boxes" _placeholder and _firstlabel are lost.
This is pretty bad when you create display in a modern way without wasting space for a label outside the field to be filled.
It displays instead "Select an Option".

-+{select _field="tracker_field_something" _trackerId="10" _firstlabel="pick somethingt" class="form-control"}+-

{img fileId="1783" thumb="box"}
{img fileId="1784" thumb="box"}

*.tiki.org sites send out notifications to users who have become inactive or have been deleted causing bounces which are often not detected.

For example, group category or tracker watches can generate a lot of mail failures which we need to prevent.

Hi all, I have been using tikiwiki since it was about v14 and have seen it use more and more compute resource. I recently pulled a production site from AWS as the compute bills where starting to get out of hand. I think I would have a hard time convincing small sme's to fork out hundreds of euro each month for in-house tikiwiki hosting. Any thoughts are welcome. I have tried disabling various features but it still takes up cpu time. This isn't a complaint, I love tikiwiki , but if tikiwiki increase in size it will become a software suite for large corporations ONLY. Cheers, Kevin.

On the tracker 5 when you edit an item you can't type the first letter of an option in the "Resolution status" dropdown to jump to the option.

You use a search field, but the more "natural" type first letters option should work too.

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

https://github.com/blueimp/jQuery-File-Upload

As of 2024-01-19, Tiki is using version 9.34.0 (2019-07)
https://gitlab.com/tikiwiki/tiki/-/blob/master/vendor_bundled/composer.lock

Version 10.32 (2021-09) is available from https://github.com/blueimp/jQuery-File-Upload/tags and is presumably the last one.

https://stackoverflow.com/questions/71526727/blueimp-jquery-fileupload-github-marked-as-readonly-archived

Alternative candidates: https://github.com/search?q=file+upload&type=repositories&s=stars&o=desc

I have two current Tiki master instances on my localhost and in both, when I try to activate the module "Last actions", I get a system error:

"You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'order by `lastModif` desc LIMIT 10 OFFSET 0' at line 1

The query was:
select a.* from `tiki_actionlog` a join `tiki_actionlog_conf` c on a.`action` = c.`action` and a.`objectType` = c.`objectType` and (c.`status` = 'v') where order by `lastModif` desc

The built query was likely:
select a.* from `tiki_actionlog` a join `tiki_actionlog_conf` c on a.`action` = c.`action` and a.`objectType` = c.`objectType` and (c.`status` = 'v') where order by `lastModif` desc"

Jonny said in the Matrix chat that the query is missing the -+where+- clause.

At https://tiki.org/tiki-syslog.php we have a link to "Export through Action Log".
It is displayed even if the feature "feature_actionlog" is disabled

The link shouldn't be displayed if the feature is disabled.

---

If the purpose is to show a new admin it is possible to see more logs then we should add an informative/help/tooltip text and not a link that is not active.

When you have a diagram in a wiki page (made with ((doc:PluginDiagram)) ), if you have permission to edit it, you see a link to "Edit Diagram" at the bottom right corner of the diagram displayed in the wiki page.

When you show that page content through ((doc:PluginSlideshow)), then you expect tiki to hide those links to edit wiki sections, edit plugins inline, etc. (which work well, they are hidden in the slideshow), but the diagram still shows the label and link to "Edit Diagram", and it should be hidden when you are inside the presentation.
---
Issue still confirmed in 24.x
Reproduced here:
http://xavi-9794-6688.show2.tikiwiki.org/tiki-slideshow.php?page=Tiki+Wiki+CMS+Groupware#/7
u: admin
p: 12345