Please see: https://packages.tiki.org/

The interface for Packages is located at the site's tiki-admin.php?page=packages page. The Packages admin page has four sections, displayed in tabs — Packages Installed, Install Other Packages, Packages Bundled, and Diagnose. These sections are described below:

This list shows packages that have been installed via this feature. The details for each package include package name, version required, status, and version installed, plus a remove button for each. The version required is the minimum version required by Tiki, so the version installed must be that version or a newer one. If the Packages feature hasn't been used yet, then of course the list will be empty.

The status column shows a success icon () if the package is installed, or a warning icon () if it is missing. If the package is missing, you can click the "Fix Missing Packages" button that is displayed and Tiki will try to install the package again.

If for some reason, the web-based package installer is not working for you, you can use the FTP alternative explained at: https://packages.tiki.org/

This section shows packages that are available to be selected and installed.

Some examples include:

• PhantomJS and CasperJS
• mPDF
• Expose
• SAML

Install Other Packages

Note: It may happen that mxGraph is not available on this list, so to add it to your Tiki installation, follow this link, it contains all the information you will need to add a package if it is not available for installation through the graphical interface.

Install Other Packages section feedback

Other information

Currently those that are available are listed in the local composer.json file and fetched from https://packagist.org.

This section lists the external software packages that are bundled with the core Tiki files, so are available for use in a fresh Tiki site. This list is for information purposes only and there's no interface here to make changes.

Packages Bundled

The "Diagnose Composer" button can be clicked to run Composer and test the output. If Composer isn't found for some reason, there will be a message to that effect.

Diagnose Composer - Composer Not Found

Normally, Composer will be found and run, and so some information will be shown here.

Diagnose Composer - OK

Your requirements could not be resolved to an installable set of packages

If you run into errors such as the following, try uninstalling and re-installing the packages

= Composer execution output:

Errors:
./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 mpdf/mpdf v8.0.5
    - Conclusion: don't install mpdf/mpdf v8.0.4
    - Conclusion: don't install mpdf/mpdf v8.0.3
    - Conclusion: don't install mpdf/mpdf v8.0.2
    - Conclusion: don't install mpdf/mpdf v8.0.1
    - Conclusion: don't install mpdf/mpdf v8.0.0
    - Conclusion: don't install mpdf/mpdf v8.0.5
    - Conclusion: don't install mpdf/mpdf v8.0.4
    - Conclusion: don't install mpdf/mpdf v8.0.3
    - Conclusion: don't install mpdf/mpdf v8.0.2
    - Conclusion: don't install mpdf/mpdf v8.0.1
    - Conclusion: remove setasign/fpdi 1.6.2
    - Installation request for mpdf/mpdf ^8.0.0 -> satisfiable by mpdf/mpdf[v8.0.0, v8.0.1, v8.0.2, v8.0.3, v8.0.4, v8.0.5].
    - Conclusion: don't install setasign/fpdi 1.6.2
    - mpdf/mpdf v8.0.0 requires setasign/fpdi ^2.1 -> satisfiable by setasign/fpdi[v2.1.0, v2.2.0, v2.3.0, v2.1.1].
    - Can only install one of: setasign/fpdi[v2.1.0, 1.6.2].
    - Can only install one of: setasign/fpdi[v2.1.1, 1.6.2].
    - Can only install one of: setasign/fpdi[v2.2.0, 1.6.2].
    - Can only install one of: setasign/fpdi[v2.3.0, 1.6.2].
    - Can only install one of: setasign/fpdi[1.6.2, v2.1.0].
    - Can only install one of: setasign/fpdi[1.6.2, v2.2.0].
    - Can only install one of: setasign/fpdi[1.6.2, v2.3.0].
    - Installation request for setasign/fpdi (locked at 1.6.2) -> satisfiable by setasign/fpdi[1.6.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.

Initially, the focus will be files at https://packagist.org/, but later this feature is intended to be expanded to include importing themes, libraries formerly hosted at mods.tiki.org, language files, and more.

• See also https://dev.tiki.org/Composer-Web-Installer
• Profiles
• “Packaging” Composer packages
• About Tiki Packages in Tiki 18.0 LTS and why I support this project. And mods.tiki.org can now be scheduled for retirement (Marc Laporte).
• https://gitlab.com/tikiwiki/tiki-packages-build

• Composer Web Installer
• Package