History: Debug_Mode_Enabled
Preview of version: 14
This is an idea for a profile for troubleshooting, development and debugging
2- features known to be buggy in 3.0
Once you go in production, you should de-activate debugging/logging tools
Table of contents
Provides step-by-step instructions to solve common issues
- 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
- Clear all caches tiki-admin_system.php?do=all
De-activate unstable features
1- all experimental features2- features known to be buggy in 3.0
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: y # [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.
Once you go in production, you should de-activate debugging/logging tools
Todo
- 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