Debugging: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
==Debugging in Moodle 1.7 onwards== | ==Debugging in Moodle 1.7 onwards== | ||
[[Category:Debugging]] | |||
The interface for Administration changed in Moodle 1.7 and more options were given for controlling how to handle PHP error messages. To access debug in Moodle 1.7 onwards, go to the Administration block, click on Server, and then click on Debugging. | The interface for Administration changed in Moodle 1.7 and more options were given for controlling how to handle PHP error messages. To access debug in Moodle 1.7 onwards, go to the Administration block, click on Server, and then click on Debugging. | ||
Revision as of 00:45, 24 May 2007
Debugging in Moodle 1.7 onwards
The interface for Administration changed in Moodle 1.7 and more options were given for controlling how to handle PHP error messages. To access debug in Moodle 1.7 onwards, go to the Administration block, click on Server, and then click on Debugging.
Debug messages - The administrator can select the types of error messages to be displayed or logged.
The options for debugging include:
- NONE: Do not show any errors or warnings
- MINIMAL: Show only fatal errors
- NORMAL: Show errors, warnings and notices
- ALL: Show all reasonable PHP debug messages
- DEVELOPER: extra Moodle debug messages for developers - If you turn this on, then PHP's error_reporting will be increased so that more warnings are printed. This is only useful for developers.
Display debug messages - There is an option to choose whether to display error messages or simply record them in the server logs.
Debug email sending - Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.
Performance info - 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.
