Note: You are currently viewing documentation for Moodle 2.5. Up-to-date documentation for the latest stable version of Moodle may be available here: Debugging.

Debugging: Difference between revisions

From MoodleDocs
(location, formatting)
(introduction)
Line 1: Line 1:
Location: ''Administration > Server > Debugging''
Location: ''Administration > Server > Debugging''
Debugging messages are intended to 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.





Revision as of 17:52, 5 October 2007

Location: Administration > Server > Debugging

Debugging messages are intended to 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.


Debug messages

Template:Moodle 1.7From Moodle 1.7 onwards, further options are provided for controlling how to handle PHP error 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.