Debugging - Historia wersji

Howardsmiller: /* In config.php */

2013-12-31T10:34:36Z

In config.php

← poprzednia wersja		Wersja z 10:34, 31 gru 2013
Linia 63:		Linia 63:

	<code php>		<code php>
			@error_reporting(E_ALL \| E_STRICT);
			@ini_set('display_errors', '1');
	$CFG->debug = (E_ALL \| E_STRICT);		$CFG->debug = (E_ALL \| E_STRICT);
	$CFG->debugdisplay = 1;		$CFG->debugdisplay = 1;
Linia 70:		Linia 72:
	// for these users only.		// for these users only.
	$CFG->debugusers = '2';		$CFG->debugusers = '2';
			</code>

			'''NOTE:''' Add these lines immediately before the line...
			<code php>
			require_once(dirname(__FILE__) . '/lib/setup.php');
	</code>		</code>

2013-12-02T18:17:33Z

← poprzednia wersja		Wersja z 18:17, 2 gru 2013
Linia 79:		Linia 79:

	* Developers can also use [http://xdebug.org/ XDEBUG] (Installed as a module on the Apache server) to further dig into the code, step by step using an [http://xdebug.org/docs/remote XDEBUG client application]. Probably, as part of their favorite IDE. For example: [http://php.netbeans.org/ NetBeans], [http://www.jetbrains.com/phpstorm/ phpStorm] or...		* Developers can also use [http://xdebug.org/ XDEBUG] (Installed as a module on the Apache server) to further dig into the code, step by step using an [http://xdebug.org/docs/remote XDEBUG client application]. Probably, as part of their favorite IDE. For example: [http://php.netbeans.org/ NetBeans], [http://www.jetbrains.com/phpstorm/ phpStorm] or...
	* [[Debugging/Bug fixing as knowledge creation]] Information posted by Tim Hunt in Planet Moodle 28 November 2013.

	[[es:Depuración]]		[[es:Depuración]]
	[[fr:Débogage]]		[[fr:Débogage]]

2013-12-02T16:51:23Z

added link to * Debugging/Bug fixing as knowledge creation Information posted by Tim Hunt in Planet Moodle 28 November 2013.

← poprzednia wersja		Wersja z 16:51, 2 gru 2013
Linia 79:		Linia 79:

	* Developers can also use [http://xdebug.org/ XDEBUG] (Installed as a module on the Apache server) to further dig into the code, step by step using an [http://xdebug.org/docs/remote XDEBUG client application]. Probably, as part of their favorite IDE. For example: [http://php.netbeans.org/ NetBeans], [http://www.jetbrains.com/phpstorm/ phpStorm] or...		* Developers can also use [http://xdebug.org/ XDEBUG] (Installed as a module on the Apache server) to further dig into the code, step by step using an [http://xdebug.org/docs/remote XDEBUG client application]. Probably, as part of their favorite IDE. For example: [http://php.netbeans.org/ NetBeans], [http://www.jetbrains.com/phpstorm/ phpStorm] or...
			* [[Debugging/Bug fixing as knowledge creation]] Information posted by Tim Hunt in Planet Moodle 28 November 2013.

	[[es:Depuración]]		[[es:Depuración]]
	[[fr:Débogage]]		[[fr:Débogage]]

2013-11-09T19:50:48Z

In the database

← poprzednia wersja		Wersja z 19:50, 9 lis 2013
Linia 75:		Linia 75:

	NOTE: do not try to modify the config database table directly, it will not work because the values are cached in MUC.		NOTE: do not try to modify the config database table directly, it will not work because the values are cached in MUC.

	~~===In the database===~~

	~~Using a tool like phpMyAdmin, execute the following SQL commands:~~

	~~<code sql>~~
	~~UPDATE mdl_config SET value = 2047 WHERE name = 'debug';~~
	~~UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';~~
	~~</code>~~

	~~To turn it back off, use the admin screens, or the commands:~~

	~~<code sql>~~
	~~UPDATE mdl_config SET value = 0 WHERE name = 'debug';~~
	~~UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';~~
	~~</code>~~

	~~(If you use a different database prefix, you will need to adjust those commands accordingly.)~~

	==See also==		==See also==

2013-11-09T19:50:27Z

In config.php

← poprzednia wersja		Wersja z 19:50, 9 lis 2013
Linia 73:		Linia 73:

	Remember to remove those lines again when you have finished diagnosing your problem.		Remember to remove those lines again when you have finished diagnosing your problem.

			NOTE: do not try to modify the config database table directly, it will not work because the values are cached in MUC.

	===In the database===		===In the database===

2013-11-09T19:49:27Z

In config.php

@@ Linia 63: / Linia 63: @@
 <code php>
-$CFG->debug = 2047;
+$CFG->debug = (E_ALL | E_STRICT);
 $CFG->debugdisplay = 1;
 // You can specify a comma separated list of user ids that that always see

2013-05-28T20:18:31Z

changing Settings to Administration

← poprzednia wersja		Wersja z 20:18, 28 maj 2013
Linia 1:		Linia 1:
	{{Developer tools}}		{{Developer tools}}
	Debugging messages can be enabled by an administrator in ''~~Settings~~ > Site administration > Development > Debugging''.		Debugging messages can be enabled by an administrator in ''Administration > Site 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.

2013-03-12T18:34:50Z

added link to spanish translation of page

← poprzednia wersja		Wersja z 18:34, 12 mar 2013
Linia 114:		Linia 114:
	* Developers can also use [http://xdebug.org/ XDEBUG] (Installed as a module on the Apache server) to further dig into the code, step by step using an [http://xdebug.org/docs/remote XDEBUG client application]. Probably, as part of their favorite IDE. For example: [http://php.netbeans.org/ NetBeans], [http://www.jetbrains.com/phpstorm/ phpStorm] or...		* Developers can also use [http://xdebug.org/ XDEBUG] (Installed as a module on the Apache server) to further dig into the code, step by step using an [http://xdebug.org/docs/remote XDEBUG client application]. Probably, as part of their favorite IDE. For example: [http://php.netbeans.org/ NetBeans], [http://www.jetbrains.com/phpstorm/ phpStorm] or...

			[[es:Depuración]]
	[[fr:Débogage]]		[[fr:Débogage]]

2012-12-11T22:22:34Z

← poprzednia wersja		Wersja z 22:22, 11 gru 2012
Linia 60:		Linia 60:
	===In config.php===		===In config.php===

	In ~~moodle/~~config.php you can add the lines:		In [[Configuration file\|config.php]] you can add the lines:

	<code php>		<code php>
Linia 74:		Linia 74:
	</code>		</code>

	~~For Moodle 2.0 the possible~~ settings are as follows:		Possible settings are as follows:

	<code php>		<code php>

2012-07-20T15:43:42Z

In config.php

← poprzednia wersja		Wersja z 15:43, 20 lip 2012
Linia 80:		Linia 80:
	// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!		// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!
	@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!		@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
	$CFG->debug = ~~38911~~; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!		$CFG->debug = 32767; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!
	// for Moodle 2.3, use: $CFG->debug = ~~32767~~;		// for Moodle 2.0 - 2.2, use: $CFG->debug = 38911;
	$CFG->debugdisplay = true; // NOT FOR PRODUCTION SERVERS!		$CFG->debugdisplay = true; // NOT FOR PRODUCTION SERVERS!