Category: Packages

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.

Composer packages can't be installed successfully through the web control panel in Tiki 23. Reproduced in dev.t.o, and also in two other servers.
In dev.t.o, the triangle icon shows up inndicating that the install failed.
In the other 2 servers, I saw a message indicating that composer.lock file was missing (on brand new tiki23 git installs, and therefore those packages could not be installed.

In all cases, running in the console (server side) the command -+composer update+- as root fixed the issue.

HTH

Composer 2.0 requires some changes to the organisation of the packages in vendor_bundled, at the moment we are getting warnings from composer install like this:

{CODE()}Deprecation warning: require.Sam152/Javascript-Equal-Height-Responsive-Rows is invalid, it should not contain uppercase characters. Please use sam152/javascript-equal-height-responsive-rows instead. Make sure you fix this as Composer 2.0 will error.{CODE}

which should be pretty simple to fix by changing the case of the package names, and

{CODE()}Deprecation warning: require.jquery/plugins/colorbox is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name should match "[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9]([_.-]?[a-z0-9]+)*". Make sure you fix this as Composer 2.0 will error.{CODE}

where we have three parts to the package, should also be ok to fix, but some may need upstream fixes which hopefully will be on their way.

!!! Another issue
Another issue is what to do about the other supported branches, 19.x, 18.x and 15.x - as they will presumably uptomatically update themselves to composer 2.0 when setup.sh is run, and then break. We need to devise a way to keep these old branches on composer 1.x.

I can't install media-alchemist due to several problems.. When attempted in 21.x through packages web control panel, this output is shown:
{CODE()}
Problem 1
- Conclusion: don't install media-alchemyst/media-alchemyst 0.5.5
- Conclusion: remove monolog/monolog 2.0.2
- Conclusion: don't install monolog/monolog 2.0.2
- Installation request for media-alchemyst/media-alchemyst ^0.5.4 -> satisfiable by media-alchemyst/media-alchemyst[0.5.4, 0.5.5].
- Conclusion: don't install monolog/monolog 2.0.2
- media-alchemyst/media-alchemyst 0.5.4 requires monolog/monolog ~1.0 -> satisfiable by monolog/monolog[1.0.0, 1.1.0, 1.10.0, 1.11.0, 1.12.0, 1.13.0, 1.13.1, 1.14.0, 1.15.0, 1.16.0, 1.17.0, 1.17.1, 1.17.2, 1.18.0, 1.18.1, 1.18.2, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.22.1, 1.23.0, 1.24.0, 1.25.0, 1.25.1, 1.25.2, 1.25.3, 1.4.0, 1.4.1, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.0.1, 1.0.2, 1.2.0, 1.2.1, 1.3.0, 1.3.1].
- Can only install one of: monolog/monolog[1.17.0, 2.0.2].
- Can only install one of: monolog/monolog[1.17.1, 2.0.2].
- Can only install one of: monolog/monolog[1.17.2, 2.0.2].
- Can only install one of: monolog/monolog[1.18.0, 2.0.2].
- Can only install one of: monolog/monolog[1.18.1, 2.0.2].
- Can only install one of: monolog/monolog[1.18.2, 2.0.2].
- Can only install one of: monolog/monolog[1.19.0, 2.0.2].
- Can only install one of: monolog/monolog[1.20.0, 2.0.2].
- Can only install one of: monolog/monolog[1.21.0, 2.0.2].
- Can only install one of: monolog/monolog[1.22.0, 2.0.2].
- Can only install one of: monolog/monolog[1.22.1, 2.0.2].
- Can only install one of: monolog/monolog[1.23.0, 2.0.2].
- Can only install one of: monolog/monolog[1.24.0, 2.0.2].
- Can only install one of: monolog/monolog[1.25.0, 2.0.2].
- Can only install one of: monolog/monolog[1.25.1, 2.0.2].
- Can only install one of: monolog/monolog[1.25.2, 2.0.2].
- Can only install one of: monolog/monolog[1.25.3, 2.0.2].
- Can only install one of: monolog/monolog[2.0.2, 1.17.0].
- Can only install one of: monolog/monolog[2.0.2, 1.17.1].
- Can only install one of: monolog/monolog[2.0.2, 1.17.2].
- Can only install one of: monolog/monolog[2.0.2, 1.18.0].
- Can only install one of: monolog/monolog[2.0.2, 1.18.1].
- Can only install one of: monolog/monolog[2.0.2, 1.18.2].
- Can only install one of: monolog/monolog[2.0.2, 1.19.0].
- Can only install one of: monolog/monolog[2.0.2, 1.20.0].
- Can only install one of: monolog/monolog[2.0.2, 1.21.0].
- Can only install one of: monolog/monolog[2.0.2, 1.22.0].
- Can only install one of: monolog/monolog[2.0.2, 1.22.1].
- Can only install one of: monolog/monolog[2.0.2, 1.23.0].
- Can only install one of: monolog/monolog[2.0.2, 1.24.0].
- Can only install one of: monolog/monolog[2.0.2, 1.25.0].
- Can only install one of: monolog/monolog[2.0.2, 1.25.1].
- Can only install one of: monolog/monolog[2.0.2, 1.25.2].
- Can only install one of: monolog/monolog[2.0.2, 1.25.3].
- Can only install one of: monolog/monolog[1.0.0, 2.0.2].
- Can only install one of: monolog/monolog[1.0.1, 2.0.2].
- Can only install one of: monolog/monolog[1.0.2, 2.0.2].
- Can only install one of: monolog/monolog[1.1.0, 2.0.2].
- Can only install one of: monolog/monolog[1.10.0, 2.0.2].
- Can only install one of: monolog/monolog[1.11.0, 2.0.2].
- Can only install one of: monolog/monolog[1.12.0, 2.0.2].
- Can only install one of: monolog/monolog[1.13.0, 2.0.2].
- Can only install one of: monolog/monolog[1.13.1, 2.0.2].
- Can only install one of: monolog/monolog[1.14.0, 2.0.2].
- Can only install one of: monolog/monolog[1.15.0, 2.0.2].
- Can only install one of: monolog/monolog[1.16.0, 2.0.2].
- Can only install one of: monolog/monolog[1.2.0, 2.0.2].
- Can only install one of: monolog/monolog[1.2.1, 2.0.2].
- Can only install one of: monolog/monolog[1.3.0, 2.0.2].
- Can only install one of: monolog/monolog[1.3.1, 2.0.2].
- Can only install one of: monolog/monolog[1.4.0, 2.0.2].
- Can only install one of: monolog/monolog[1.4.1, 2.0.2].
- Can only install one of: monolog/monolog[1.5.0, 2.0.2].
- Can only install one of: monolog/monolog[1.6.0, 2.0.2].
- Can only install one of: monolog/monolog[1.7.0, 2.0.2].
- Can only install one of: monolog/monolog[1.8.0, 2.0.2].
- Can only install one of: monolog/monolog[1.9.0, 2.0.2].
- Can only install one of: monolog/monolog[1.9.1, 2.0.2].
- Can only install one of: monolog/monolog[2.0.2, 1.0.0].
- Can only install one of: monolog/monolog[2.0.2, 1.1.0].
- Can only install one of: monolog/monolog[2.0.2, 1.10.0].
- Can only install one of: monolog/monolog[2.0.2, 1.11.0].
- Can only install one of: monolog/monolog[2.0.2, 1.12.0].
- Can only install one of: monolog/monolog[2.0.2, 1.13.0].
- Can only install one of: monolog/monolog[2.0.2, 1.13.1].
- Can only install one of: monolog/monolog[2.0.2, 1.14.0].
- Can only install one of: monolog/monolog[2.0.2, 1.15.0].
- Can only install one of: monolog/monolog[2.0.2, 1.16.0].
- Can only install one of: monolog/monolog[2.0.2, 1.4.0].
- Can only install one of: monolog/monolog[2.0.2, 1.4.1].
- Can only install one of: monolog/monolog[2.0.2, 1.5.0].
- Can only install one of: monolog/monolog[2.0.2, 1.6.0].
- Can only install one of: monolog/monolog[2.0.2, 1.7.0].
- Can only install one of: monolog/monolog[2.0.2, 1.8.0].
- Can only install one of: monolog/monolog[2.0.2, 1.9.0].
- Can only install one of: monolog/monolog[2.0.2, 1.9.1].
- Installation request for monolog/monolog (locked at 2.0.2) -> satisfiable by monolog/monolog[2.0.2].
{CODE}

When attempted through the command line with this command,
{CODE()}
php temp/composer.phar require --update-no-dev --prefer-dist media-alchemyst/media-alchemyst:^0.5.4
{CODE}

This is then the error message shown:
{CODE()}
root@computer: /var/www/html/21.x# php temp/composer.phar require --update-no-dev --prefer-dist media-alchemyst/media-alchemyst:^0.5.4
Do not run Composer as root/super user! See https://getcomposer.org/root for details
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Conclusion: don't install media-alchemyst/media-alchemyst 0.5.5
- Conclusion: remove monolog/monolog 2.0.2
- Conclusion: don't install monolog/monolog 2.0.2
- Installation request for media-alchemyst/media-alchemyst ^0.5.4 -> satisfiable by media-alchemyst/media-alchemyst[0.5.4, 0.5.5].
- Conclusion: don't install monolog/monolog 2.0.2
- media-alchemyst/media-alchemyst 0.5.4 requires monolog/monolog ~1.0 -> satisfiable by monolog/monolog[1.0.0, 1.1.0, 1.10.0, 1.11.0, 1.12.0, 1.13.0, 1.13.1, 1.14.0, 1.15.0, 1.16.0, 1.17.0, 1.17.1, 1.17.2, 1.18.0, 1.18.1, 1.18.2, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.22.1, 1.23.0, 1.24.0, 1.25.0, 1.25.1, 1.25.2, 1.25.3, 1.4.0, 1.4.1, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.0.1, 1.0.2, 1.2.0, 1.2.1, 1.3.0, 1.3.1].
- Can only install one of: monolog/monolog[1.17.0, 2.0.2].
- Can only install one of: monolog/monolog[1.17.1, 2.0.2].
- Can only install one of: monolog/monolog[1.17.2, 2.0.2].
- Can only install one of: monolog/monolog[1.18.0, 2.0.2].
- Can only install one of: monolog/monolog[1.18.1, 2.0.2].
- Can only install one of: monolog/monolog[1.18.2, 2.0.2].
- Can only install one of: monolog/monolog[1.19.0, 2.0.2].
- Can only install one of: monolog/monolog[1.20.0, 2.0.2].
- Can only install one of: monolog/monolog[1.21.0, 2.0.2].
- Can only install one of: monolog/monolog[1.22.0, 2.0.2].
- Can only install one of: monolog/monolog[1.22.1, 2.0.2].
- Can only install one of: monolog/monolog[1.23.0, 2.0.2].
- Can only install one of: monolog/monolog[1.24.0, 2.0.2].
- Can only install one of: monolog/monolog[1.25.0, 2.0.2].
- Can only install one of: monolog/monolog[1.25.1, 2.0.2].
- Can only install one of: monolog/monolog[1.25.2, 2.0.2].
- Can only install one of: monolog/monolog[1.25.3, 2.0.2].
- Can only install one of: monolog/monolog[2.0.2, 1.17.0].
- Can only install one of: monolog/monolog[2.0.2, 1.17.1].
- Can only install one of: monolog/monolog[2.0.2, 1.17.2].
- Can only install one of: monolog/monolog[2.0.2, 1.18.0].
- Can only install one of: monolog/monolog[2.0.2, 1.18.1].
- Can only install one of: monolog/monolog[2.0.2, 1.18.2].
- Can only install one of: monolog/monolog[2.0.2, 1.19.0].
- Can only install one of: monolog/monolog[2.0.2, 1.20.0].
- Can only install one of: monolog/monolog[2.0.2, 1.21.0].
- Can only install one of: monolog/monolog[2.0.2, 1.22.0].
- Can only install one of: monolog/monolog[2.0.2, 1.22.1].
- Can only install one of: monolog/monolog[2.0.2, 1.23.0].
- Can only install one of: monolog/monolog[2.0.2, 1.24.0].
- Can only install one of: monolog/monolog[2.0.2, 1.25.0].
- Can only install one of: monolog/monolog[2.0.2, 1.25.1].
- Can only install one of: monolog/monolog[2.0.2, 1.25.2].
- Can only install one of: monolog/monolog[2.0.2, 1.25.3].
- Can only install one of: monolog/monolog[1.0.0, 2.0.2].
- Can only install one of: monolog/monolog[1.0.1, 2.0.2].
- Can only install one of: monolog/monolog[1.0.2, 2.0.2].
- Can only install one of: monolog/monolog[1.1.0, 2.0.2].
- Can only install one of: monolog/monolog[1.10.0, 2.0.2].
- Can only install one of: monolog/monolog[1.11.0, 2.0.2].
- Can only install one of: monolog/monolog[1.12.0, 2.0.2].
- Can only install one of: monolog/monolog[1.13.0, 2.0.2].
- Can only install one of: monolog/monolog[1.13.1, 2.0.2].
- Can only install one of: monolog/monolog[1.14.0, 2.0.2].
- Can only install one of: monolog/monolog[1.15.0, 2.0.2].
- Can only install one of: monolog/monolog[1.16.0, 2.0.2].
- Can only install one of: monolog/monolog[1.2.0, 2.0.2].
- Can only install one of: monolog/monolog[1.2.1, 2.0.2].
- Can only install one of: monolog/monolog[1.3.0, 2.0.2].
- Can only install one of: monolog/monolog[1.3.1, 2.0.2].
- Can only install one of: monolog/monolog[1.4.0, 2.0.2].
- Can only install one of: monolog/monolog[1.4.1, 2.0.2].
- Can only install one of: monolog/monolog[1.5.0, 2.0.2].
- Can only install one of: monolog/monolog[1.6.0, 2.0.2].
- Can only install one of: monolog/monolog[1.7.0, 2.0.2].
- Can only install one of: monolog/monolog[1.8.0, 2.0.2].
- Can only install one of: monolog/monolog[1.9.0, 2.0.2].
- Can only install one of: monolog/monolog[1.9.1, 2.0.2].
- Can only install one of: monolog/monolog[2.0.2, 1.0.0].
- Can only install one of: monolog/monolog[2.0.2, 1.1.0].
- Can only install one of: monolog/monolog[2.0.2, 1.10.0].
- Can only install one of: monolog/monolog[2.0.2, 1.11.0].
- Can only install one of: monolog/monolog[2.0.2, 1.12.0].
- Can only install one of: monolog/monolog[2.0.2, 1.13.0].
- Can only install one of: monolog/monolog[2.0.2, 1.13.1].
- Can only install one of: monolog/monolog[2.0.2, 1.14.0].
- Can only install one of: monolog/monolog[2.0.2, 1.15.0].
- Can only install one of: monolog/monolog[2.0.2, 1.16.0].
- Can only install one of: monolog/monolog[2.0.2, 1.4.0].
- Can only install one of: monolog/monolog[2.0.2, 1.4.1].
- Can only install one of: monolog/monolog[2.0.2, 1.5.0].
- Can only install one of: monolog/monolog[2.0.2, 1.6.0].
- Can only install one of: monolog/monolog[2.0.2, 1.7.0].
- Can only install one of: monolog/monolog[2.0.2, 1.8.0].
- Can only install one of: monolog/monolog[2.0.2, 1.9.0].
- Can only install one of: monolog/monolog[2.0.2, 1.9.1].
- Installation request for monolog/monolog (locked at 2.0.2) -> satisfiable by monolog/monolog[2.0.2].

Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.

Installation failed, reverting ./composer.json to its original content.
root@computer:/var/www/html/21.x# php temp/composer.phar require --update-no-dev --prefer-dist monolog/monolog:^1.0.0
Do not run Composer as root/super user! See https://getcomposer.org/root
{CODE}
I could solve by means of downgrading the monolog/monolog package to 1.x, and then reinstalling through command line worked.
{CODE()}
root@computer:/var/www/html/21.x# php temp/composer.phar require --update-no-dev --prefer-dist monolog/monolog:^1.0.0
Do not run Composer as root/super user! See https://getcomposer.org/root for details
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies
Package operations: 22 installs, 1 update, 0 removals
- Installing symfony/polyfill-ctype (v1.14.0): Loading from cache
- Installing symfony/filesystem (v3.4.38): Downloading (100%)
- Installing symfony/polyfill-mbstring (v1.14.0): Loading from cache
- Installing symfony/debug (v4.4.5): Downloading (100%)
- Installing symfony/console (v3.4.38): Downloading (100%)
- Installing pimple/pimple (v1.0.2): Downloading (100%)
- Downgrading monolog/monolog (2.0.2 => 1.25.3): Downloading (100%)
- Installing evenement/evenement (v1.1.0): Downloading (100%)
- Installing alchemy/binary-driver (1.6.0): Downloading (100%)
- Installing swftools/swftools (0.3.2): Downloading (100%)
- Installing php-unoconv/php-unoconv (0.3.1): Downloading (100%)
- Installing php-mp4box/php-mp4box (0.3.0): Downloading (100%)
- Installing neutron/temporary-filesystem (2.4): Downloading (100%)
- Installing doctrine/cache (1.10.0): Downloading (100%)
- Installing php-ffmpeg/php-ffmpeg (0.5.1): Downloading (100%)
- Installing imagine/imagine (v0.6.3): Downloading (100%)
- Installing symfony/http-foundation (v2.5.4): Downloading (100%)
- Installing doctrine/collections (1.6.4): Downloading (100%)
- Installing phpexiftool/exiftool (10.10): Downloading (100%)
- Installing alchemy/phpexiftool (0.7.2): Downloading (100%)
- Installing alchemy/mediavorus (0.4.10): Downloading (100%)
- Installing alchemy/ghostscript (0.4.0): Downloading (100%)
- Installing media-alchemyst/media-alchemyst (0.5.5): Downloading (100%)
Package robloach/component-installer is abandoned, you should avoid using it. Use oomphinc/composer-installers-extender instead.
Writing lock file
Generating autoload files
> ComponentInstaller\Installer::postAutoloadDump
Compiling component files
root@computer:/var/www/html/21.x# php temp/composer.phar require --update-no-dev --prefer-dist media-alchemyst/media-alchemyst:^0.5.4
Do not run Composer as root/super user! See https://getcomposer.org/root for details
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies
Nothing to install or update
Package robloach/component-installer is abandoned, you should avoid using it. Use oomphinc/composer-installers-extender instead.
Generating autoload files
> ComponentInstaller\Installer::postAutoloadDump
Compiling component files
root@computer:/var/www/html/21.x#
{CODE}

In tiki-admin.php?page=packages#contenttabs_admin_admin_packages-2, when we want to install a package by clicking on the __Install__ button after a while we are sent to an error page.
This shows the error ~~#FF0000:Fatal error: Maximum execution time of 30 seconds exceeded in \vendor_bundled\vendor\symfony\process\Pipes\WindowsPipes.php on line 142
~~
The package does not install completely, because it will have a status __Missing__, at this moment we must click on the button __Fix Missing Packages__ for it to install completely.

This has happened even if we want to remove an already installed package.

{img fileId="1312"}
After the error has occurred
{img fileId="1313"}
Thanks!

When the required version of a package is updated, (say from 2.2 to 2.3) within ComposerPackages.yml, a previously installed package gets orphaned. The package cannot be updated and cannot be removed.

Desired behaviour: when a package name is the same, but a version requirement has changed, there should be an update button. Removal should also be an option.

On a working Tiki 24.x (253bcbb09b2f1c2df4bced1802f4c13cc0cf32be, 253bcbb0 · [FIX] PluginManager: move source code link with other general info · 1 day ago);

If I diagnose composer from the shell I have:
{CODE()}
tsaharoniki@server001:~/public_html$ ./temp/composer.phar diagnose
Checking composer.json: WARNING
License "LGPL-2.1" is a deprecated SPDX license identifier, use "LGPL-2.1-only" or "LGPL-2.1-or-later" instead
Checking platform settings: OK
Checking git settings: OK
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: OK
Checking github.com rate limit: OK
Checking disk free space: OK
__Checking pubkeys:
Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0 87719BA6 8F3BB723 4E5D42D0 84A14642
Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B 0C708369 153E328C AD90147D AFE50952__
OK
Checking composer version: OK
Composer version: 2.2.9
PHP version: 8.1.4
PHP binary path: /usr/bin/php8.1
OpenSSL version: OpenSSL 1.1.1d 10 Sep 2019
cURL version: 7.64.0 libz 1.2.11 ssl OpenSSL/1.1.1i
zip: extension present, unzip present, 7-Zip not available
{CODE}

I install the package mPDF (see the recording): {file type="gallery" fileId="1786" showicon="y"}

My Vendor folder is updated (today's date) and inside other folders have been updated or added
{CODE()}
drwxr-xr-x 8 tsaharoniki tsaharoniki 4096 Mar 27 13:25 vendor
tsaharoniki@server001:~/public_html$ cd vendor
-rw-r--r-- 1 tsaharoniki tsaharoniki 178 Mar 6 20:46 autoload.php
drwxr-xr-x 2 tsaharoniki tsaharoniki 4096 Mar 27 12:08 composer
drwxr-xr-x 3 tsaharoniki tsaharoniki 4096 Mar 27 12:08 mpdf
drwxr-xr-x 3 tsaharoniki tsaharoniki 4096 Mar 27 12:08 myclabs
drwxr-xr-x 3 tsaharoniki tsaharoniki 4096 Mar 6 20:46 npm-asset
drwxr-xr-x 3 tsaharoniki tsaharoniki 4096 Mar 27 12:08 paragonie
drwxr-xr-x 3 tsaharoniki tsaharoniki 4096 Mar 27 12:08 psr
drwxr-xr-x 3 tsaharoniki tsaharoniki 4096 Mar 27 12:08 setasign
{CODE}

In the file : vendor/composer/platform_check.php there is a check for PHP8

{CODE()}
if (!(PHP_VERSION_ID >= 80000)) {
$issues[] = 'Your Composer dependencies require a PHP version ">= 8.0.0". You are running ' . PHP_VERSION . '.';
}
{CODE}

This forbid the Tiki to run with PHP7.4.

On most of Virtual servers and Cpanel (tested on Server Debian10 running Virtualmin) you can select the PHP version that will be used for this domain. You can select a different PHP version than the one used by the server for the HTML backend.

It work usually fine.

However users don't have any option when this is about the PHP CLI. (php -v)

Developers have workaround like :
php74 console.php ...
sh setup -p /usr/...

It is usually fine for developers.

However for Admins (or power user) there is no option to select the PHP CLI version.
Like:
* tiki-check.php
* tiki-admin.php?page=packages
* ... ?

Packages run composer independently of the regular composer dependencies.

This creates a situation where package dependencies might conflict.

For example, if you install media alchemy, it requires Symfony console, so Symfony console gets installed via our main dependencies, (in vendor_bundled) also as a dependency of the packages install, (in vendor folder).

Now there two different versions of the same vendor that are both getting auto-loaded. Right now the Package-required Symfony console version is significantly older than that of the main Symfony Console and it overrides the one that Tiki has been tested with.

This, of course, provides a huge opportunity for difficult to find errors.

Perhaps as a solution, we can remove in a VendorsClean equivalent of packages, each dependency that the main composer has already installed. This way it won't severely cripple Tiki when new packages are installed.

When a package is enabled where the system requirements can not be met, it causes composer to fail to install all packages.

saml is one of our packages that is causing this blockage right now.

Perhaps it would be best to have composer check the system requirements have been met for a package before allowing it to be enabled since enabling it without the requirements will cause composer to fail badly.

To reproduce: enable saml, then try to install other packages.

I was getting timeouts when installing mPDF package through the web interface. So I switched to the CI and tried it there. I also got a timeout error with the following message:

The process "'/Applications/MAMP/bin/php/php7.2.14/bin/php' '/Users/drsassafras/Sites/trunk/temp/composer.phar' '--no-ansi' '--no-dev' '--prefer-dist' 'update' '-d' '/Users/drsassafras/Sites/trunk/' 'nothing'" exceeded the timeout of 300 seconds.

That makes sense why the timeout happened! I am running trunk with the dev packages and removing or adding them takes quite a bit of time.

Could packages check that one is not running a development environment before deciding to uninstall all those composer packages?

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

I recently upgraded a production tiki site from 21.x to 23.x in a new server, and when adding the missing composer packages in the new server, tiki became unusable after adding the google api client package:
{CODE()}
"google/apiclient ^2.2.2 Apache-2.0 wikiplugin_googlechart, wikiplugin_youtube"
{CODE}

This added from dependency on php 8.0, apparently, and since tiki23 .x uses php 7.4, tiki became broken: WSOD with just one text message saying:
{QUOTE()}
"Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.0.0".
{QUOTE}

I had to enter the server through ssh and remove all contents from the vendor folder plus the composer files in the root folder.
Dead end for a new tiki site admin not knowing all these tricky emergency measures, probably?

If a package is missing the help/warning information displays a link to the external missing package repository.

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

It is __important to note__ that we have already a similar mechanism when looking to a page (not the admin control panels) that display a message for admins (I hope for admins only ?)

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

---

At http://bsfez-11581-7999.show2.tikiwiki.org/tiki-admin.php?page=fgal&cookietab=6&highlight=feature_docs, enable "Use PDF.js".

It will display an alert (red background):

The first link "Missing tiki package :" with a link to : tiki-admin.php?page=packages

Then "npm-asset/pdfjs-dist-viewer-min" with a link to :https://asset-packagist.org/package/npm-asset/pdfjs-dist-viewer-min

It should display:
"A Tiki package is missing: Install mpdf/mpdf"
"Install mpdf/mpdf" should be a link to : tiki-admin.php?page=packages

1. Tells the user of a problem
2. Explain what is the problem
3. Suggest the user a way to solve the issue
4. Give the user the direction/action to solve the issue

That's the way a missing package should handled, anywhere.

I added "anywhere" because it seems we have different behaviours.
IE: Go to http://bsfez-11581-7999.show2.tikiwiki.org/tiki-admin.php?page=print
For the "PDF from URL" dropdown, select mPDF. The "PDF Orientation" error will show
"Missing tiki package: mpdf/mpdf" with parts with the same link. (not needed)

{file type="gallery" fileId="1771" showicon="y"}