Like most everything else, your Tiki site preferences (such as which features you have enabled and the configuration settings for each feature) are stored in the database. You can configure and tweak all preferences simply by accessing the database.
{TIP()}This is especially helpful if your site ever "crashes" or you find yourself "locked out" of your Tiki.{TIP}

Changing Preferences

Nearly all of the settings and preferences that control your Tiki site are defined in the tiki_preferences table in the database.

phpmyadmin
The tiki_preferences table.

By simply changing the a setting from y to n (or vice-versa), you can usually undo any inadvertent damage and regain control of your site.
For example, if you accidentally enable the Use HTTPS login option on a site without SSL, you'll find yourself unable to log in (even as the Admin, since Tiki would be looking for a non-resistant HTTPS port. To "reset" the HTTPS option to disabled you can edit the https_login in the tiki_preferences table:

Admin: Login
The relationship between the Admin option and the database field.

In this example, you would change the field to disabled in order to "turn off" the Use HTTPS login option.
Other common options, that if inappropriately enabled, could "lock" your Tiki include:

  • Authentication method (auth_method)
  • SSL options
  • Intertiki options
  • Invalid syntax in custom code
  • Invalid syntax in custom modules


Fixing Modules

When creating a custom user module, Tiki allows you to include custom code, including PHP and Smarty syntax. In some instances, if you add invalid code (such as an improperly formed Smarty expression) your Tiki may display a blank screen.

In this case, you can edit your database (as explained previously) to temporarily deactivate the offending module. This will allow you access your Tiki and edit or correct the code in the module.

  1. Access the tiki_modules database table.
    phpMyAdmin
    The tiki_modules table.
  2. phpMyAdmin lists the currently active modules. Simply click Remove (Remove ) for the module to deactivate.
    phpMyAdmin
    Deactivating a module.

    {TIP()}This does not delete the module — Tiki simply deactivates it.{TIP}
  3. Reload your Tiki website.
  4. On the Admin: Modules page, edit the user module to correct the custom code.
    Admin: Modules
    Editng a user module.



Editing Custom Code

The Admin: Look and Feel page includes several areas in which you can add custom code, including PHP and Smarty synta). In some instances, if you add invalid code (such as an improperly formed Smarty expression) your Tiki may display a blank screen.

In this case, you can edit your database (as explained previously) to remove or correct the offending code. The following table identifies the appropriate database field in the tiki_preferences table for each custom code area on the Look and Feel page:

Look and Feel field tiki_preferences field
Custom HTML Content feature_custom_html_head_content
Secondary site menu custom code feature_secondary_sitemenu_custom_code
Custom Site Header sitemycode
Top Bar, Custom code feature_topbar_custom_code
Custom Center Column Header feature_custom_center_column_header
Custom Site Footer bot_logo_code
Custom End of Code feature_endbody_code

<HR>
Creative Commons
This guide is written by Rick Sapir and published by tikiforsmarties.com. This guide is Copyright © 2010-2014 by Rick Sapir under a Creative Commons Attribution-Share Alike 3.0 License. Some rights reserved.


Fair attribution includes a return link to http://twessentials.tikiforsmarties.com (for online use) and mention of primary author (Rick Sapir) and publisher (KeyContent.org).

Essentially, you are are free:

Share
to Share — to copy, distribute and transmit the work
Image
to Remix — to adapt the work


Under the following conditions:

Image
Attribution. You must attribute the work to me, as the original licensor, but not in any way that suggests that I endorse you or your use of the work. Fair attribution includes a return link to http://twessentials.tikiforsmarties.com (for online use) and mention of primary author (Rick Sapir) and publisher (KeyContent.org).
Image
Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license.


Please read http://creativecommons.org/licenses/by-sa/3.0/legalcode for the full license.

Please read Credits and Acknowledgments for full list of contributors to this project.

Images

The screen images are from Tiki Wiki CMS Groupware, from some versions between Version 6 up to Version 12, and are made available under the GNU Lesser General Public License, Version 2.1 (LGPL). Some pictures and images are from stock.xchng and are subject to the SXC Image License Agreement.

Trademarks

Tiki, Tiki Wiki CMS Groupware, and the Tiki logo are trademarks of the Tiki Software Community Association, used with permission. KeyContent.org and Tiki Essentials are unaffiliated with the Tiki Software Community Association.

Privacy

Please see Privacy Policy for information on how your personal information is treated when you access Tiki Essentials.