New: As an alternative to setting configuration options one by one, it is possible to apply a "Profile" to set the Tiki site up for a specific purpose, such as a company intranet, collaborative community, and so on. For more information on this "app store" approach to site configuration, please see http://profiles.tiki.org.To set configuration options "manually," continue with the instructions on this page.
For non-administrators (end users) wishing to learn how to use various features in Tiki, see Features.
Once installed, choose the features you would like to offer in your Tiki. Tiki has a wide variety of features to choose from; wiki, news article, blog, workflow management, forums, and much more. Be warned that the array of choices can be mind-boggling, so you might want to get acquainted with the Tiki community and find a mentor to advise you on your implementation and to lend a hand up the steepest parts of the learning curve.
for more info: Features Admin
Most of the main features have their own administrator panel, to configure that particular feature. Once you choose the features you want, then visit the appropriate admin page for each feature. In doc.tiki.org, most features have an admin page ((featurename admin)) which describes the configuration options available.
By default Tiki saves files from wiki attachments, image galleries, file galleries, trackers, userfiles, etc., in the database, but you might configure it to store them in your file tree in the server, so the database is kept as small as possible for backups, etc.
Needed perms on server:
The webserver needs to be able to read, write and execute files. Set those folders either as 755, 775, or 777, depending on your server configuration (try in this previously cited order)
We recommend adding the prefix "tiki_" to these folders you are going to create, so that it's easier for you to identify them. Therefore, you could use folder names as:
(remember, create the folder, and change permissions to 775 or whatever you need in your web hosting)
We will assume that when you log in to your server through ftp, you are in folder: /home/username/
Log in to your tiki, through the web browser, as admin, set the path in the following places:
NOTE: Forums can be configured one by one, and not necessarily in one folder for all of them
Forums, one by one:
If you see the root directory listing when trying to access your site, you may need to edit the .htaccess file or the httpd.conf file as follows:
Look for the line "DirectoryIndex ..." and make sure it includes "index.php".
You need to set each tiki installation with its own "Remember me Domain:", and this name must the same name used when rinning the script:
./setup.sh nobody root 02755 site1 site22
In this example, this screen for the first site should contain:
And the same configuration screen for the second site:
Once you have dictated what your Tiki is to be used for, establish by whom it shall be used.
Is your Tiki open to the public, or is it closed (even for viewing) to a select circle? A full array of options is available. Most Tiki installations start with three basic user types:
see: LDAP authentication.
In addition to the three basic groups above. You can create other groups, generally for one of the following reasons:
Themes are the "skins" of Tiki. Themes use a CSS framework to change the look and feel of all the elements of the site. Tiki comes with a number of themes installed. Tiki's themes affect appearance only, and not functionality. In other words, features work the same in all themes. (If there is a functionality difference between themes, this is a bug and should be reported and fixed.)
Themes can be applied globally, and also to specific categories of pages (which can correspond to user groups), to features, and associated with perspectives. And users can pick their own theme if they're in a group that has that permission.
For more information about Tiki's themes, please visit themes.tiki.org.
Since Tiki 13, several overall page layouts are available and can be selected on the Look and Feel admin page. The site administrator can choose to have a "classic" website layout with a page header containing a horizontal menu, all scrolling together, or a layout with a brand and navigation bar fixed to the top of the browser window, and so on. There are some variations of each of these. For more information, see https://themes.tiki.org/Layout+Templates.
In Tiki terminology, modules are containers that hold various kinds of information and functionality. Many are included initially, and custom modules can easily be made by site admins and editors. Modules contain things like menus, search forms, images, a Tiki plugin, etc. The classic arrangement is to have a center main content area with either a left or right column (or both) containing modules for added content and functionality, but modules can be loaded within a wiki page's content or in a blog post or wherever it is needed. Modules have many display parameters, can be sorted in any order and made visible/invisible for different user groups.
For example, to create your own menu to display in a module and assign it to a location in the page, please read the Menu HOWTO.
Once you have established all of the above you (and your users) are ready to start adding the content to your site.
See: features page for information on how to add/edit content in each of the features you are using.
To learn how to format the content of your wiki pages, read Using Wiki Pages