History: Debug_Mode_Enabled
Preview of version: 35
This is a profile for troubleshooting, development and debugging. It is a bit like going into Safe mode
Once you go in production, you should de-activate debugging/logging tools
You should also empty all *.tpl.php files in templates_c/
2- features known to be buggy in 3.0
Table of contents
Provides step-by-step instructions to solve common issues
Things to check/try
- Running latest stable version? tiki-admin.php?page=general
- Is database up to date? A note will appear on tiki-admin.php if DB structure is out of sync with Tiki version (3.0 and up)
- Is your database corrupt? -> Repair database
- Clear all Tiki caches tiki-admin_system.php?do=all
- Clear your browser cache with Ctrl-F5 (i.e. hold down the Control key and then press F5)
- Clear your browser cookies (search the web for docs about your specific browser)
- Try another browser
- Are your perms ok? Run sh setup.sh if you have shell access. When you update your files, via SVN or otherwise, the file permissions may no longer be OK.
- Logout & log back in
- Check integrity of your files
- If you changed a server setting, did you restart Apache?
- Change the theme (especially if you are using custom theme)
- Try to reproduce the problem on a Tiki demo site. If you can reproduce, then, please report a bug
Activate debugging/logging tools
YAML
Copy to clipboard
preferences: error_reporting_level: 2047 #Full error_reporting_adminonly: n #Not just for admins because we could be testing as Anonymous smarty_notice_reporting: y log_sql: y #logging sql queries log_mail: y #logging sent email log_tpl: y #add comments in templates (if you click view source, you can see which tpl was used to create it feature_debug_console: n # [http://dev.tikiwiki.org/Debugger+Console|Debugger Console] smarty_security: y # it was required to turn off for debug console, but now we can restore. feature_bot_bar_debug: y use_minified_scripts: n # to use compressed version of scripts, when available for faster performance but not so useful for debugging. style: thenews.css feature_wiki_1like_redirection: n #Tiki tries to be smart but this can be annoying because it prevents error messages on typos
Once you go in production, you should de-activate debugging/logging tools
I am locked out of Tiki
and I can't go to profiles to enable Debug Mode- Go to phpMyAdmin (or the equivalent)
- Find the table
tiki_preferences - Edit the values from above.
- Example: error_reporting_level -> 2047
You should also empty all *.tpl.php files in templates_c/
Todo in this profile.
- Add/include or link to direct instructions on how to apply a profile.
- Add permanent links to things often used when debugging (which would be moveable and always available)
- tiki-admin_system.php?do=all
- Debug console
- etc
Questions about this profile
- Should a Debug page be included to local tiki for easy linking?
- Yes, and also provides feedback to user
- Should profile switch to thenews.css ?
- Done because some people may not know how to change, or the page may be inaccessible
- So people need to switch back after.
De-activate unstable features
1- all experimental features2- features known to be buggy in 3.0