Debugging - Revision history

Sylvaticus at 09:33, 18 April 2011

2011-04-18T09:33:33Z

← Older revision		Revision as of 09:33, 18 April 2011
Line 1:		Line 1:
	Location: ''Administration > Development > Debugging''		Location:
			''Administration > Development > Debugging'' (Moodle 2.x) - ''Administration > Server > Debugging'' (Moodle 1.x)

	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 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.

Sylvaticus: debugging is under development, not under server

2011-04-18T09:31:39Z

debugging is under development, not under server

← Older revision		Revision as of 09:31, 18 April 2011
Line 1:		Line 1:
	Location: ''Administration > ~~Server~~ > Debugging''		Location: ''Administration > Development > Debugging''

	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 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.

Howardsmiller: /* In config.php */

2010-12-22T09:25:58Z

In config.php

← Older revision		Revision as of 09:25, 22 December 2010
Line 70:		Line 70:
	</code>		</code>

	For Moodle 2.0 the possible settings are as follows:		{{Moodle 2.0}}For Moodle 2.0 the possible settings are as follows:

	<code php>		<code php>

Howardsmiller: /* In config.php */

2010-12-22T09:24:49Z

In config.php

← Older revision		Revision as of 09:24, 22 December 2010
Line 72:		Line 72:
	For Moodle 2.0 the possible settings are as follows:		For Moodle 2.0 the possible settings are as follows:

	<code php?		<code php>
	// Force a debugging mode regardless the settings in the site administration		// Force a debugging mode regardless the settings in the site administration
	// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!		// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!

Howardsmiller: /* In config.php */

2010-12-22T09:24:23Z

In config.php

@@ Line 68: / Line 68: @@
 $CFG->debug = 6143;
 $CFG->debugdisplay = 1;
 </code>

Fox: French link

2010-10-12T20:13:02Z

French link

← Older revision		Revision as of 20:13, 12 October 2010
Line 95:		Line 95:

	[[Category:Administrator]]		[[Category:Administrator]]

			[[fr:Débogage]]

TimHunt: /* How to turn on debugging */

2010-10-10T21:12:39Z

How to turn on debugging

← Older revision		Revision as of 21:12, 10 October 2010
Line 5:		Line 5:
	==How to turn on debugging==		==How to turn on debugging==

	Go into the admin screens, and look under Administration > Server > Debugging. Set the...		Go into the admin screens, and look under Administration > Server > Debugging (In Moodle 2.0 it is Site administration ▶ Development ▶ Debugging). Set the...

	* '''Debug messages''' to '''ALL''', and		* '''Debug messages''' to '''ALL''', and
	* '''Display debug messages''' to '''Yes'''.		* '''Display debug messages''' to '''Yes'''.

	(You '''must''' do both). There is rarely any advantage in going to Developer level.		(You '''must''' do both). There is rarely any advantage in going to Developer level, unless you are a developer, in which case it is strongly recommended.

	Once you have got the error message, and copied and pasted it somewhere, you are recommended to turn debugging back off again.		Once you have got the error message, and copied and pasted it somewhere, you are recommended to turn debugging back off again.

Howardsmiller: /* How to turn on debugging */ make clearer

2010-07-28T14:14:24Z

How to turn on debugging: make clearer

← Older revision		Revision as of 14:14, 28 July 2010
Line 5:		Line 5:
	==How to turn on debugging==		==How to turn on debugging==

	Go into the admin screens, and look under Administration > Server > Debugging. Set the ~~'''Debug messages''' to '''ALL''', and '''Display debug messages''' to '''Yes'''~~.		Go into the admin screens, and look under Administration > Server > Debugging. Set the...

	There is rarely any advantage in going to Developer level.		* '''Debug messages''' to '''ALL''', and
			* '''Display debug messages''' to '''Yes'''.

			(You '''must''' do both). There is rarely any advantage in going to Developer level.

	Once you have got the error message, and copied and pasted it somewhere, you are recommended to turn debugging back off again.		Once you have got the error message, and copied and pasted it somewhere, you are recommended to turn debugging back off again.

Howardsmiller at 12:12, 27 July 2010

2010-07-27T12:12:55Z

← Older revision		Revision as of 12:12, 27 July 2010
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.		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.

	==How to turn on debugging==		==How to turn on debugging==

	Go into the admin screens, and look under Administration > Server > Debugging. Set the '''Debug messages''' to '''ALL''', and '''Display debug messages''' to '''Yes'''.		Go into the admin screens, and look under Administration > Server > Debugging. Set the '''Debug messages''' to '''ALL''', and '''Display debug messages''' to '''Yes'''.

			There is rarely any advantage in going to Developer level.

	Once you have got the error message, and copied and pasted it somewhere, you are recommended to turn debugging back off again.		Once you have got the error message, and copied and pasted it somewhere, you are recommended to turn debugging back off again.

Howardsmiller: /* In config.php */

2010-07-27T12:08:59Z

In config.php

← Older revision		Revision as of 12:08, 27 July 2010
Line 56:		Line 56:
	$CFG->debug = 2047;		$CFG->debug = 2047;
	$CFG->debugdisplay = 1;		$CFG->debugdisplay = 1;
			</code>

			Or even more debugging messages:

			<code php>
	$CFG->debug = 6143;		$CFG->debug = 6143;
	$CFG->debugdisplay = 1;		$CFG->debugdisplay = 1;