Using debugging messages
Debugging messages are intended to help diagnose problems and/or help Moodle developers. If you have a problem with your Moodle site and ask for help in a Moodle.org forum, a developer may ask you to turn debug messages on, in order to locate the cause of the problem. By default Moodle does not show any error messages at all. If you are having problems (e.g. blank screens or incomplete screens) turning on debugging is usually the first thing to try.
Debugging messages can be enabled by an administrator in Debugging in the Site administration.
Debug messages and display debug messages
The options are:
- NONE: Do not show any errors or warnings (Default)
- MINIMAL: Show only fatal errors
- NORMAL: Show warnings, errors and notices
- ALL: Show all reasonable PHP debug messages
- DEVELOPER: extra Moodle debug messages for developers
- It is recommended that a record of error messages is kept, and for the admin to regularly monitor the error logs. This may be done by setting 'Debug messages' (debug) to Normal and leaving 'Display debug messages' (debugdisplay) off (unticked). Error messages are then recorded in the server logs.
- If 'Debug messages' is set to Developer on a production (public) site, it is recommended to copy and paste the debugging message obtained and then turn off Developer debugging. This is because debugging messages can give clues to a hacker as to the set-up of your site.
Debug email sending
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.
More tools for debugging outgoing mail
You can also use the config.php file to turn on more "tools" which will assist you with debugging the outgoing emails (and SMTP server configuration):
- Redirect all outgoing emails to a specific address:
// Divert all outgoing emails to this address to test and debug emailing features
// $CFG->divertallemailsto = 'email@example.com'; // NOT FOR PRODUCTION SERVERS!
- Turn on the CRON debugging and run CLI cron.php script.
// Force developer level debug and add debug info to the output of cron
// $CFG->showcrondebugging = true;
And then use SSH (or putty.exe, on windows) to run:
you@moodle-server(/var/www/html/moodle)# php admin/cli/cron.php
- Turn on verbose SMTP debugging and output it into system's error_log (code hack):
$mailer->SMTPDebug = 1; // 0 - no debug ... 4 - low level full debug $mailer->Debugoutput = "error_log";
The Performance info option determines whether performance info will be included in the footer of the standard theme (and some other themes). Performance info includes the time for the page to load, the amount of memory used to generate the page, cpu usage, load, and the record cache hit/miss ration.
If you add
to your config.php file, then it will also count database queries. (This has to be in config.php, because Moodle starts doing DB queries before it loads the config information in the database!)
To hide performance info from ordinary users, see the discussion Performance info only for admins?
Show origin of language strings
Be careful, read the warning.
Show page information
To show page information printed in the page footer.
What to do if you cannot get to the admin screens
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.
Try typing the URL directly
The debug settings are at the URL
http://.../admin/settings.php?section=debugging on your server. Sometimes that URL will work, even though the pages you need to go to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.
In config.php you can uncomment lines (delete the // at the start of the line) under Section 7 to enable debugging for all or just specific users:
// 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
// Force a debugging mode regardless the settings in the site administration
// @error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
// @ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
// $CFG->debug = (E_ALL | E_STRICT); // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
// $CFG->debugdisplay = 1; // NOT FOR PRODUCTION SERVERS!
// You can specify a comma separated list of user ids that that always see
// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay
// for these users only.
// $CFG->debugusers = '2';
Remember to comment those lines again (reinsert the // at the start of the line) when you have finished diagnosing your problem.
NOTE 1: do not try to modify the config database table directly, it will not work because the values are cached in MUC.
NOTE 2: if you find your config.php does not have the above settings (you have a cut down approx 30 lines config.php) look for a "config-dist.php" file that contains the full details. I would suggest transferring your details in the current config.php file you have into the full config file and renaming that one to "config.php".