Category: 21.x

Installer allows to set language for the tiki site admin in the first screen of tiki-install.php. This used to work for years. I tested in 20.x and 21.x and it doesn't change lang of the interface. Tested with Catalan and Spanish, in case it matters. No change, installer continues in step 2 in English.

We have no syntax for expressing we want an unlimited number of LIST plugin results.

Using mysql Full-Text indexation, one can express the idea with a huge number like so :
{CODE()}{LIST()}
{filter field="object_type" content="trackeritem" }
{filter field="tracker_id" exact="1"}
{pagination max="99999999"}
{OUTPUT(template=)}
{LIST}{CODE}

It is ugly but it does the job in an expressive way (people will understand 99999999 does not mean exactly 99999999).

Using Elascticsearch, the above will fail with an obscure error message « all shards failed » because Elascticsearch has a hard limit which defaults to 10000 but it can be changed at the server level.
See ''Results Per Query'' in [https://www.elastic.co/guide/en/app-search/current/limits.html]
So I need to use:
{CODE()}{LIST()}
{filter field="object_type" content="trackeritem" }
{filter field="tracker_id" exact="1"}
{pagination max="9999"}
{OUTPUT(template=)}
{LIST}{CODE}
Because "10000" looks like I really want "10000" rather than unlimited.

__It is bad that the LIST plugins need to be rewritten when one changes the unified search indexation method.__ Also, it is not obvious why it fails.

__SUGGESTION__ I feel we should allow for a real syntax for unlimited results such as :
{CODE(caption="SUGGESTED SYNTAX" theme="default")}{pagination max="-1"}{CODE}

Then if Tiki uses Elascticsearch searches it could look up the ''Results Per Query'' value (or assume 10000 for starters) when "-1" is encountered.
If Tiki uses "Mysql Full-Text search" if should not have a limit (or it should have a very high one).

After a fresh install on Ubuntu Server 20.04, the system menu (42) is missing and inaccessible if the admin tries to incorporate it in a module.

I have a search module which searches into the wiki pages.

On clicking "OK", I do get on tiki-listpages.php?find=mysearchword&go=OK and it displays for a short time the correct list of pages and the correct number of pages. Then the « I'm searching » spinner kicks in and the list of search result pages is replaced with the full list of all pages.

There is a demo here:
[https://showlistpages.winter.alsawiki.com]
Database available here : [https://showlistpages.winter.alsawiki.com/backups/dump_db.sql.gz]

At least in 21.x and trunk the sorting widgets in the header cells is now white on white and thus invisible.

e.g. here: ((doc:Tablesorter))

This seems to be a regression in the library (or bootstrap 4) as i'm also finding this in a custom implementation on a client site.

When I create a tabular from a tracker which has a field of type ''group selector'', I can't use it because this type of field does not seem to be implemented:
^Field mode not found: any mode for selectionrolesGroupe^

''selectionrolesGroupe'' being the permname of the field of type ''group selector'',

{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.

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.

I created a fairly basic tiki setup using a brand new Tiki 21 instance (aimed to be used in production next week)

I applied the Collaborative_community_12x profile.

When attempting to edit the registered group to remove the homepage, or select anonymous in the inheritance field, I can't save because this errors blocks the process:

^ Template Group children cannot have permission: Editors ^

I didn't select anything with editors at that level. Nor I did attempt to do anything with templated groups yet, but I was aiming to change basic options yet.

What's going on? Is this "templated groups" feature ready for production?
How can I disable the templated groups and roles options, in order to avoid their issues with basic behavior and setup of a basic Tiki site not requiring that level of complexity?

It should be optional, shouldn't it?
---
Reproduced cleanly in a brand new site at show2.t.o (on trunk since 21.x is not available yet at show2.t.o), and it's clearer to me that this is candidate to release blocker: too serious of an issue with a basic setup and expected change by tiki site admins willing to tweak the basic groups to their needs.

Steps to reproduce:
(1) Log in as admin here:
http://xavi-9794-7325.show2.tikiwiki.org/tiki-admingroups.php?group=Registered
u: admin
p: 12345

(2) Remove the contents of the homepage field and attempt to save. Error message is triggered.

HTH

This is a wish to create a show instance on to test out the Templated Groups feature - there may well be bugs...

Well, the setup all worked as described here ((dev:Templated Groups)), nice!

Settings → Users → ''Add or remove from a group'' option from the right-hand spanner

On a new Tiki it opens the "Change group assignments for selected users" modal which helps place the user in groups and set the default group. ''This is fine''.

On a Tiki with a lot of groups, the modal fails to show up and the javascript console reveals that Tiki tries to send the huge list of groups using method GET.
Unsurprisingly, this is met with « 414 Request-URI Too Long »
__This is not fine__ :-(

No show instance with hundreds of groups is necessary : I hope this can be fixed by changing the GET query into a POST.

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.

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

Text in a plugin alias body within ~np~~tc~~/np~tags ~np~~/tc~~/np~ appears in the page

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.

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.

I tried to install a Tiki21.x from git.
I could complete the composer installation on local and remote.

Both stop at the same point (waiting and pressing enter didn't help this time ?)

{CODE()}
-n Your choice [c]?
c
Local PHP version 74 >= to required PHP version 72 - good
You are running composer as "root", while "/Users/bernardsfez/.composer" is owned by "bernardsfez"
Warning: You forced the install of 1.10.26 via --1, but 2.5.4 is the latest stable version. Updating to it via composer self-update --stable is recommended.
You are already using composer version 1.10.26 (1.x channel).
Do not run Composer as root/super user! See https://getcomposer.org/root for details
You are using Composer 1 which is deprecated. You should upgrade to Composer 2, see https://blog.packagist.com/deprecating-composer-1-support/
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
Gathering patches from patch file.
Removing package adodb/adodb-php so that it can be re-installed and re-patched.
- Removing adodb/adodb-php (v5.22.2)
> Tiki\Composer\RestoreVendors::restore
> Tiki\Composer\CleanVendorAfterVendorBundledMigration::cleanLinks
Loading composer repositories with package information
Installing dependencies from lock file
Package operations: 203 installs, 0 updates, 0 removals
Gathering patches from patch file.
Gathering patches for dependencies. This might take a minute.
- Installing adodb/adodb-php (v5.22.2): Downloading (100%)
- Applying patches for adodb/adodb-php
../installer/composer-patches/adodb-php__remove_references_to_adodb_extension.patch (Remove references to ADOdb Extension)

{CODE}

On a Tiki21 created using git go at : tiki-admin.php?page=general
It shows : 21.0svn (InnoDB)
It should show information about Git.

^My Git detail module: GIT 21.x:ba642 Wednesday February 19, 2020 20:08:06 IST^

If ''tablesorter'' is active (pref -+ feature_jquery_tablesorter +-), the group management page is unusable except for Tikis with a small number of groups.

The reason is, there is no search box and no pagination. Therefore, there is no way of knowing if there are more hidden groups. And no way of accessing the hidden groups.

This can be experienced on [http://dev.tiki.org/tiki-admingroups.php] for instance.

Seems that Cypht patch is hardcoded to -+php+- command not taking into consideration there can be multiple php versions installed on the server with commands like -+php72+-.

On my CentOS server I get this:
{CODE()}
[luci@vm5163 tikitrunk]$ sh setup.sh -pphp72 composer
Local PHP version 72 >= to required PHP version 72 - good
You are already using composer version 1.9.0 (stable channel).
Gathering patches from patch file.
> Tiki\Composer\RestoreVendors::restore
> Tiki\Composer\CleanVendorAfterVendorBundledMigration::cleanLinks
Loading composer repositories with package information
Installing dependencies from lock file
Package operations: 1 install, 0 updates, 0 removals
Gathering patches from patch file.
Gathering patches for dependencies. This might take a minute.
- Installing components/bootstrap (3.4.1): Loading from cache
Package zendframework/zend-version is abandoned, you should avoid using it. Use ocramius/package-versions instead.
Generating autoload files
> ComponentInstaller\Installer::postAutoloadDump
Compiling component files
> Tiki\Composer\ThemeInstaller::setup
> Tiki\Composer\BootstrapCompiler::build
> Tiki\Composer\CleanVendors::clean
> Tiki\Composer\CleanVendorAfterVendorBundledMigration::clean
> Tiki\Composer\PatchCypht::setup
PHP Warning: require(/var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/vendor/paragonie/random_compat/lib/random.php): failed to open stream: No such file or directory in /var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/lib/framework.php on line 38
PHP Fatal error: require(): Failed opening required '/var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/vendor/paragonie/random_compat/lib/random.php' (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/lib/framework.php on line 38
Could not build Cypht package configuration. Check the output below and make sure minimum PHP version is available and executable as CLI.

Warning: require(/var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/vendor/paragonie/random_compat/lib/random.php): failed to open stream: No such file or directory in /var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/lib/framework.php on line 38

Fatal error: require(): Failed opening required '/var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/vendor/paragonie/random_compat/lib/random.php' (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/lib/framework.php on line 38

Script Tiki\Composer\PatchCypht::setup handling the post-install-cmd event terminated with an exception


[ErrorException]
copy(/var/www/clients/client1/web16/subdirs/tikitrunk/vendor_bundled/vendor/jason-munro/cypht/site/site.js): failed to open stream: No such file or directory


install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>]...

{CODE}

Enable multilingual, create a tracker create a text field and set it as mandatory.
You can’t save without filling the field. (good and normal)

Turn the field to multilingual and dont set title for other language.
You can’t save an item anymore.

While they can be a discussion about the logic, having a title in every language used in that case shouldn’t be mandatory and one should be use as default when other don’t exist.

I remember it was once useable, if you had at least one field with a value it was good enough to allow saving.


http://bsfez-11581-7539.show2.tikiwiki.org/tiki-view_tracker.php?trackerId=1
You can’t save an item with only one language title

Today button on date pickers not using time as well does nothing

Today in the https://tiki.org/Roundtable-Meeting-2020-09 we noticed that a plain registered user is not able to see the forum post "type" dropdown when starting a a new topic (the first message of a new forum thread). Reproduced with user @xavi . However, when listing the topics of a forum, the first column is shown for that same user (as well as anons) indicating the topic type: all say "normal" here:
https://tiki.org/forum4


However, a user with admin rights (for instance @xavidp ) is able to see the dropdown of topic type: Normal | Announce | Hot | Sticky | Deliberation.

Reproduced here:
https://tiki.org/tiki-view_forum.php?openpost=1&forumId=4&comments_threadId=0&comments_threshold=0&comments_offset=0&thread_sort_mode=lastPost_desc&comments_per_page=20

I've checked in the forum edition page, or forums control panel, or forum4 permissions, and I couldn't find anything to explain that behavior. Maybe some bug in some tpl or php code which control which permissions are needed to display that dropdown field?

The options: Open, Closed, no toggle no longe work.

I have a simple Tracker on a wiki page (no tpl, no FluidGrid, etc.), and the header displays (in the correct format, H1, H2, H3) however the 'Section Toggle' option stopped working.

br,
Mike

Up through Tiki 19.x my trackers have had assigned galleries to upload images too, and to browse from. Since Tiki 21.x that has stopped working.

In Tracker Field Type "Files", there are options to assign a gallery to upload file and images too, and there is an option to assign a gallery to browse from. This is how I have my tracker built, so when a user of the tracker uploads an image then the image automatically is stored in the assigned gallery. If the user wants to browse for the image on the server, then the assigned gallery is used to browse from.

At this point, those are no longer working, when a user uploads or browses, they have to manually choose the gallery to upload too, or to browse from.

I will create a show instance. Thank you.