User:Aexoxea/Tiki Wiki CMS Groupware
Tiki Wiki CMS Groupware (referred herein as just "Tiki") is a web-based content management system with collaboration features written in PHP.
- 1 Package Tiki
- 2 Install and set up prerequisites
- 3 Configure Tiki
- 4 Updates
- 5 Security
- 6 Tips and Tricks
- 7 Troubleshooting
- 8 Miscellanea
- 9 See Also
Tiki ships both stable and long-term support releases (see versioning policy and release roadmap). Choose from one of the following, then make a package using the files on the linked page:
- For the latest stable release (18.x): Files Stable.
- For the latest long-term support release (18.x): Files LTS.
Install and set up prerequisites
Install the Tiki package that you made above.
Set up a web server
You need a running web server configured to use PHP and serve up files from
If not sure what to pick, choose Apache and follow the instructions below.
To use Tiki on Apache, you need to:
- Install Apache per instructions at Apache HTTP Server#Installation.
- Configure Apache to use PHP per instructions at Apache HTTP Server#PHP.
LoadModule alias_module modules/mod_alias.so(it is enabled by default on new installs).
- Add this line where appropriate (if unsure, place it at the end):
- Start/enable the Apache service per instructions at Apache HTTP Server#Configuration.
Set up a database server
Tiki supports either MariaDB or Oracle MySQL. If not sure what to pick, use MariaDB.
Either way, you need to install, set up and start/enable the database server per instructions at MySQL#Installation.
It is recommended to let Tiki create the database (and optionally -- but recommended for security reasons -- the database user account) that it will use. You will need to note down for later:
- The database server host name (if not on localhost),
- The username and password of a database user account (e.g.
root) with access to create new databases and new database user accounts.
If you need or want to create these manually instead, see Database - Manual creation below.
Set up PHP
PHP was pulled in as a dependency when Tiki was installed earlier.
You need to edit
/etc/php/php.ini (or equivalent) and, at a minimum:
- Set the default timezone (
date.timezone=, see PHP's List of Supported Timezones for valid options).
- Set the session data path (
session.save_path=, the default
"/tmp"works as a starting point).
- Enable the
pdo_mysqlextensions (each has its own
It is also recommended to:
- Enable the
zipextension (it is enabled by default on new installs).
- Enable the
gdextension, then install the package (or equivalent) it requires to work.
Once done, continue with Configure Tiki below.
Set up Tiki's files
Tiki ships with a setup script (
setup.sh) that updates its file permissions and downloads any necessary extra files using Composer.
If you're using the current version of PHP that ships in the main repositories, run this from a terminal:
# cd /usr/share/webapps/tikiwiki/ # sh setup.sh -u http -g http -n fix
-g options change the user and group of Tiki's files, so set these as appropriate (noting
http:http is the default user and group for most web servers).
If you're using an earlier version of PHP, you need to add the
-p option with the truncated program name, e.g. if using AUR:
# cd /usr/share/webapps/tikiwiki/ # sh setup.sh -u http -g http -p php70 -n fix
Run Tiki's install workflow
For new installs, a web-based workflow will start to guide you through the final configuration steps (including setting up the database). When this workflow is complete, Tiki is ready to use.
For updates, you'll first be prompted to enter the username and password for Tiki's database user account. When the web-based workflow appears, there will be a notice about upgrading. Follow the link under that notice; it will take you to the correct part of the workflow to upgrade the database. Run through the workflow from there; when complete, your Tiki is updated, and you should continue with After updating section.
See Tiki's Upgrade page for detailed information about updating between versions.
It is strongly recommended to:
- Make sure you have a backup in place, as Tiki does not support downgrades. Take a system backup of your Arch, follow one of Tiki's Backup recommendations, or ideally, do both.
- Close the site to non-admin users. This setting can be enabled by a Tiki admin user through the Control Panel (either General > Navigation or Security > Site Access).
- Revert to a built-in theme, as custom themes are not guaranteed to work between versions. This setting can be changed by a Tiki admin user through the Control Panel (Look & Feel > Theme).
Apply the update
Make the new package (see Package Tiki section) and install it.
This will work in most circumstances, but if you run into difficulties, remove the existing package, troubleshoot around what files are left behind under
/usr/share/webapps/tikiwiki/, then install the new package.
/usr/share/webapps/tikiwiki/contain uploaded files (e.g. images and attachments). The update process shouldn't impact these, but if you would prefer they be located elsewhere, there are options to do so. See File Storage below for details.
Once you've installed the new package successfully, continue with Configure Tiki section.
Log in to your site, check that everything is as it should be, and re-open the site when you're ready. Points to look out for include:
- Release notes. These exist for each major version under Tiki's "New in version" page.
.htaccessfile (or the file it's symlinked to, such as
_htaccess). If you've made custom changes, such as for SEFURLs, you may need to re-apply them.
- Feature defaults. New features will generally be set to default values, and features deemed 'unsafe' may have been reset to 'safe' values. Change these through the Control Panel etc. as needed.
- Custom themes. If you were using a custom theme (and it supports the updated version of Tiki), switch back to it and check if it works. Tip: Consider keeping a separate browser window open that shows the Look & Feel > Theme Control Panel in a built-in theme while testing. This way, you can revert easily if needed.
Tiki's Security documentation page describes the Security Control Panel and links to other security-related pages. The Security ArchWiki page complements this in respect of securing the underlying operating system.
Additionally, the Server Check script checks for a number of PHP functions that have security implications. If your use of Tiki doesn't need those functions (and nothing else on the server does either), you can disable them. This is done by adding them to the
disable_functions= directive under
/etc/php/php.ini (or equivalent) and reloading or restarting your web server as needed.
setup.sh script can be used after the initial configuration to lock down local file permissions.
/usr/share/webapps/tikiwiki/permissioncheck/usecases.txt shows the permission names that the script will accept, along with the numeric permission levels that are set for directories and files.
The script can be run interactively by just entering:
# cd /usr/share/webapps/tikiwiki/ # sh setup.sh
Alternatively, you can print help for the script by entering:
# cd /usr/share/webapps/tikiwiki/ # sh setup.sh -h
See Tiki's Permission Check page for more information.
Tips and Tricks
Tiki ships a Server Check PHP script that allows you confirm aspects of your web server, PHP and (optionally) database setup are compatible with Tiki, or will allow certain optional features of Tiki to be used or not.
The script is available:
- Before installation, as a separate download (upload it to a web server with PHP enabled and run it in a web browser, and it will tell you if things are configured OK or not).
- During installation, from the "Review the System Requirements" screen (see the link to "a detailed report about your server").
- After installation, as an administration tool (you'll need to be logged in to Tiki as an admin user to use it there).
File gallery indexing dependencies
If you want to use file gallery indexing, you need to do two things:
First, use the server check script to confirm that the
shell_exec PHP functions are enabled. If they aren't, remove them from the
disable_functions= directive under
/etc/php/php.ini (or equivalent) and reload or restart your web server as needed.
Second, install the following packages as desired:
|Package||Provides Binaries||Used For Types|
||Microsoft Office, RTF|
||Microsoft Word (OOXML)|
For convenience, the File Indexing file on the following page can be used to make and install a meta package that will pull in all packages that support indexing: Files Meta.
Tiki needs its own database (using a UTF-8 charset) and the ability to log in to a database user with full access to that database. If you can't or don't want to let Tiki create these during its install workflow, you can set these up manually, and just supply the details that Tiki needs directly (i.e. the host name if not on localhost, database name, user account name and password).
An example of doing this manually through the terminal (that should work in most cases, with bolded bits configurable) is:
$ mysql -u root -p mysql> CREATE DATABASE `tikiwiki` DEFAULT CHARACTER SET `utf8` COLLATE `utf8_unicode_ci`; mysql> CREATE USER `tikiwiki`@'localhost' IDENTIFIED BY 'password'; mysql> GRANT ALL PRIVILEGES ON `tikiwiki`.* TO `tikiwiki`@'localhost'; mysql> FLUSH PRIVILEGES; mysql> quit
~/.mysql_history. At a minimum, you should redact that part of the file when finished.
If you need or want to remove the Tiki database for any reason, you'll need to do so manually. An example of doing this through the terminal (which should work with the bolded bits set as appropriate) is:
$ mysql -u root -p mysql> DROP USER `tikiwiki`@'localhost'; mysql> DROP DATABASE `tikiwiki`; mysql> quit
Tiki is able to store uploaded files either in its database or on the file system. The pros and cons of each approach are covered on Tiki's File Storage page.
If storing uploaded files on the file system, by default these will be kept in directories under
/usr/share/webapps/tikiwiki/. There are a number of reasons why you might want to move them elsewhere. Again, the options to do so are outlined on Tiki's File Storage page, and on the related Control Panel pages for the specific features that accept file uploads.
/usr/share/webapps/tikiwiki/hierarchy, be sure appropriate web server options and local file permissions are set so they can be accessed (e.g. if using Apache, update the
/etc/httpd/conf/extra/tikiwiki.conffile so that the directories are included in the
open_basedirparameter, and make sure the directories are owned by
Timeout updating database on large sites
If you have a large site, PHP timeout values may be exceeded when updating the database (as part of updating Tiki to a new version) in the web-based workflow. Should this occur, you have two choices:
- Extend PHP's timeout values, then try again.
- Run the database update from the command line, then manually lock the installer (you should then be able to skip the web-based workflow, and continue from After updating):
# cd /usr/share/webapps/tikiwiki/ # php console.php database:update # touch db/lock
php in the command line example above if using a version from PHP from the AUR.
"Installer not locked" warning
A warning will appear in the Control Panel if the installer lock file is missing. This can occur if the Tiki package is uninstalled and reinstalled, or the package is updated but the web-based install workflow has not been gone through.
In circumstances where there is no need to go through the web-based install workflow, you need to manually create the lock file as suggested in the warning. The easiest way to do this from the command line is:
# touch /usr/share/webapps/tikiwiki/db/lock
If running Namcap on the made packages, you will get some or all of the following messages:
||Ignore: There are a number of empty directories in the package as shipped, and it's not clear which ones are safe to remove and which ones aren't. Consequently, they have all been left in place. You may wish to configure your web server to deny directory listings.|
||Ignore: All of the Font Awesome icon subdirectories have an equivalent |
||Ignore: It's not clear what's being referred to, or from where. In any case, all explicit requirements are satisfied by the package and instructions above.|
||Ignore: These scripts appear to be used to build releases of ADOdb (TBA for OpenID), and are not required for normal operation.|
||Ignore: Intl module is required (and this is also used to pull in PHP at the same time).|