Loading...
 

System configuration


System configuration allows for system administrators to set some preferences using the file system rather than the Tiki database. Some preferences are hidden by default on Tiki. You can un-hide them and create your own set by providing an .ini file. This file can be used in several Tikis allowing administrators to have a central configuration for different Tiki installations.

Introduced in Tiki8


Preferences configured through system files cannot be adjusted via Tiki interface. They will appear disabled.

New in Tiki10: Option to load the modules from a static files ( in profile YAML format like Module Handler. Search for "Module file" in the admin panel.

New in Tiki11: A file db/preconfiguration.php can contain database credentials which are suggested at first Tiki installation. This allows providers of Virtual Servers to preconfigure mysql with different random passwords and usernames before the customers access the Tiki installer.

New in Tiki15: Due to changes in Zend libraries, it is no longer possible to have hierarchical setting of configurations as before. In addition, configuration names can no longer contain dots. For example, client1.example.com will not work. Use client1 instead. Old configurations may not be usable in Tiki 15 and have to be rewritten.


New in Tiki20: Hide classes of preferences that are disabled

New in Tiki20: Permit to hide preferences from admin panel

New in Tiki22: Risky preferences are now hidden by default (System Administrator can un-hide)


List Slides
System configuration System configuration allows for system administrators to set some preferences using the file system rather than the Tiki database. Some preferences are hidden by default on Tiki . You can un-hide them and create your own set by providing an .ini file. This file can be used in several Tikis allowing administrators to have a central configuration for different Tiki installations. Introduced in Tiki8 Preferences configured through system files cannot be adjusted via Tiki interface. They will appear disabled. New in Tiki10 : Option to load the modules from a static files ( in profile YAML format like Module Handler . Search for "Module file" in the admin panel. New in Tiki11 : A file db/preconfiguration.php can contain database credentials which are suggested at first Tiki installation. This allows providers of Virtual Servers to preconfigure mysql with different random passwords and usernames before the customers access the Tiki installer. New in Tiki15 : Due to changes in Zend libraries, it is no longer possible to have hierarchical setting of configurations as before. In addition, configuration names can no longer contain dots. For example, client1.example.com will not work. Use client1 instead. Old configurations may not be usable in Tiki 15 and have to be rewritten. New in Tiki20 : Hide classes of preferences that are disabled New in Tiki20 : Permit to hide preferences from admin panel New in Tiki22 : Risky preferences are now hidden by default (System Administrator can un-hide)