Debugging - Versionshistorik

Leonstr: Changed `to`


2021-07-27T12:35:33Z
Changed <code> to <syntaxhighlight>

				
				
				
				
				
				← Äldre version
				Versionen från 27 juli 2021 kl. 12.35
				
Rad 34:
Rad 34:
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): 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: * Redirect all outgoing emails to a specific address:
<code php> <syntaxhighlight lang="php">
// Divert all outgoing emails to this address to test and debug emailing features // Divert all outgoing emails to this address to test and debug emailing features
// $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS! // $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
</code> </syntaxhighlight>



* Turn on the CRON debugging and run CLI cron.php script. * Turn on the CRON debugging and run CLI cron.php script.
<code php> <syntaxhighlight lang="php">
// Force developer level debug and add debug info to the output of cron // Force developer level debug and add debug info to the output of cron
// $CFG->showcrondebugging = true; // $CFG->showcrondebugging = true;
</code> </syntaxhighlight>
And then use SSH (or putty.exe, on windows) to run: And then use SSH (or putty.exe, on windows) to run:
<code php> <syntaxhighlight lang="php">
you@moodle-server(/var/www/html/moodle)# php admin/cli/cron.php you@moodle-server(/var/www/html/moodle)# php admin/cli/cron.php
</code> </syntaxhighlight>



* Turn on verbose SMTP debugging and output it into system's error_log (code hack): * Turn on verbose SMTP debugging and output it into system's error_log (code hack):
As [https://moodle.org/mod/forum/discuss.php?d=316222#p1289850 suggested] on Moodle's discussion forums: As [https://moodle.org/mod/forum/discuss.php?d=316222#p1289850 suggested] on Moodle's discussion forums:
Open [https://github.com/moodle/moodle/blob/master/lib/moodlelib.php#L5379 lib/moodlelib.php L5379] and change it to: Open [https://github.com/moodle/moodle/blob/master/lib/moodlelib.php#L5379 lib/moodlelib.php L5379] and change it to:
<code php> <syntaxhighlight lang="php">
if (!empty($CFG->debugsmtp)) { if (!empty($CFG->debugsmtp)) {
     $mailer->SMTPDebug = 1;  // 0 - no debug ... 4 - low level full debug      $mailer->SMTPDebug = 1;  // 0 - no debug ... 4 - low level full debug
     $mailer->Debugoutput = "error_log";      $mailer->Debugoutput = "error_log";
} }
</code> </syntaxhighlight>
See more info about [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L314 SMTPDebug] parameters & [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L328 Debugoutput] parameters, See more info about [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L314 SMTPDebug] parameters & [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L328 Debugoutput] parameters,
Set-up mailcatcher (https://mailcatcher.me/). Set-up mailcatcher (https://mailcatcher.me/).
Rad 66:
Rad 66:



If you add If you add
<code php> <syntaxhighlight lang="php">
define('MDL_PERF', true); define('MDL_PERF', true);
define('MDL_PERFDB', true); define('MDL_PERFDB', true);
define('MDL_PERFTOLOG', true); define('MDL_PERFTOLOG', true);
define('MDL_PERFTOFOOT', true); define('MDL_PERFTOFOOT', true);
</code> </syntaxhighlight>
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 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!)



Rad 93:
Rad 93:



Full sample: Full sample:
<code php> <syntaxhighlight lang="php">
$CFG->dboptions = array ( $CFG->dboptions = array (
   //'logall'   => true,    //'logall'   => true,
Rad 99:
Rad 99:
   'logerrors'  => true,    'logerrors'  => true,
); );
</code> </syntaxhighlight>



==What to do if you cannot get to the admin screens== ==What to do if you cannot get to the admin screens==
Rad 113:
Rad 113:
In [[Configuration file|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: In [[Configuration file|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:



<code php> <syntaxhighlight lang="php">
//========================================================================= //=========================================================================
// 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!! // 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
Rad 128:
Rad 128:
// for these users only. // for these users only.
// $CFG->debugusers = '2'; // $CFG->debugusers = '2';
</code> </syntaxhighlight>



Remember to comment those lines again (reinsert the // at the start of the line) when you have finished diagnosing your problem. Remember to comment those lines again (reinsert the // at the start of the line) when you have finished diagnosing your problem.



Drcuriosity: Added a note about debugging() for developers, since it was hard to find details in search.
2021-06-03T05:15:45Z
Added a note about debugging() for developers, since it was hard to find details in search.

				
				
				
				
				
				← Äldre version
				Versionen från 3 juni 2021 kl. 05.15
				
Rad 138:
Rad 138:
==See also== ==See also==



* If you are a developer looking for usage information on the <tt>debugging()</tt> statement, try lib/weblib.php for documentation on how it is used, and lib/setuplib.php for definitions of which PHP error levels the <tt>DEBUG_*</tt> flags map to.
* 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]] [[es:Depuración]]
[[fr:Débogage]] [[fr:Débogage]]
[[de:Debugging]] [[de:Debugging]]



Danielneis: fix typo
2021-04-16T20:23:59Z
fix typo

				
				
				
				
				
				← Äldre version
				Versionen från 16 april 2021 kl. 20.23
				
Rad 87:
Rad 87:



===Debug SQL queries=== ===Debug SQL queries===
You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queires table: You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queries table:
* '''logall''' - log all queries - suitable only for developers, causes high server loads and NOT recommended for production. * '''logall''' - log all queries - suitable only for developers, causes high server loads and NOT recommended for production.
* '''logslow''' - log queries that take longer than specified number of seconds (float values are accepted). * '''logslow''' - log queries that take longer than specified number of seconds (float values are accepted).



Rwthornton: /* Enabling debugging */
2019-09-12T17:00:33Z
Enabling debugging

				
				
				
				
				
				← Äldre version
				Versionen från 12 september 2019 kl. 17.00
				
Rad 6:
Rad 6:
==Enabling debugging== ==Enabling debugging==



To enable debugging, go to ''Site administration > Development > Debugging" . To enable debugging, go to ''Site administration > Development > Debugging'' .



===Debug messages=== ===Debug messages===



Rwthornton: /* Enabling debugging */
2019-09-12T17:00:17Z
Enabling debugging

				
				
				
				
				
				← Äldre version
				Versionen från 12 september 2019 kl. 17.00
				
Rad 6:
Rad 6:
==Enabling debugging== ==Enabling debugging==



To enable debugging, go to Debugging in the Site administration. To enable debugging, go to ''Site administration > Development > Debugging" .



===Debug messages=== ===Debug messages===



Finns den 19 april 2019 kl. 12.37
2019-04-19T12:37:32Z


				
				
				
				
				
				← Äldre version
				Versionen från 19 april 2019 kl. 12.37
				
Rad 22:
Rad 22:
# 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. # 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. # 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.

===Display debug messages===

If you select this checkbox, the debug messages are displayed directly in the browser, otherwise they are stored in the server logs.



===Debug email sending=== ===Debug email sending===



Finns den 19 april 2019 kl. 12.34
2019-04-19T12:34:16Z


				
				
				
				
				
				← Äldre version
				Versionen från 19 april 2019 kl. 12.34
				
Rad 56:
Rad 56:
See more info about [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L314 SMTPDebug] parameters & [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L328 Debugoutput] parameters, See more info about [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L314 SMTPDebug] parameters & [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L328 Debugoutput] parameters,
Set-up mailcatcher (https://mailcatcher.me/). Set-up mailcatcher (https://mailcatcher.me/).

===Debug SQL queries=== 
You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queires table: 
* '''logall''' - log all queries - suitable only for developers, causes high server loads and NOT recommended for production. 
* '''logslow''' - log queries that take longer than specified number of seconds (float values are accepted). 
* '''logerrors''' - log all error queries. 

Full sample: 
<code php> 
$CFG->dboptions = array ( 
  //'logall'   => true, 
  'logslow'  => 5, 
  'logerrors'  => true, 
); 
</code> 



===Performance info=== ===Performance info===
Rad 87:
Rad 72:
To hide performance info from ordinary users, see the discussion [https://moodle.org/mod/forum/discuss.php?d=358032 Performance info only for admins?] To hide performance info from ordinary users, see the discussion [https://moodle.org/mod/forum/discuss.php?d=358032 Performance info only for admins?]



===Show origin of language strings=== ===Show origin of languages strings===



Helps with [[:dev:Translation|translation]] and also with [[Language customization]]. Sometimes <code>?strings=1</code> should be added; other times <code>&strings=1</code>. See the Wikipedia article [http://en.wikipedia.org/wiki/Query_string Query string] for details. Helps with [[:dev:Translation|translation]] and also with [[Language customization]]. Sometimes <code>?strings=1</code> should be added; other times <code>&strings=1</code>. See the Wikipedia article [http://en.wikipedia.org/wiki/Query_string Query string] for details.
Rad 96:
Rad 81:
===Show page information=== ===Show page information===
To show page information printed in the page footer. To show page information printed in the page footer.

===Debug SQL queries===
You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queires table:
* '''logall''' - log all queries - suitable only for developers, causes high server loads and NOT recommended for production.
* '''logslow''' - log queries that take longer than specified number of seconds (float values are accepted).
* '''logerrors''' - log all error queries.

Full sample:
<code php>
$CFG->dboptions = array (
  //'logall'   => true,
  'logslow'  => 5,
  'logerrors'  => true,
);
</code>



==What to do if you cannot get to the admin screens== ==What to do if you cannot get to the admin screens==



Finns den 29 mars 2019 kl. 10.08
2019-03-29T10:08:16Z


				
				
				
				
				
				← Äldre version
				Versionen från 29 mars 2019 kl. 10.08
				
Rad 138:
Rad 138:
[[es:Depuración]] [[es:Depuración]]
[[fr:Débogage]] [[fr:Débogage]]
[[de:Debugging]]



Nadavkav: /* Debug SQL queries */
2018-12-31T14:47:54Z
Debug SQL queries

				
				
				
				
				
				← Äldre version
				Versionen från 31 december 2018 kl. 14.47
				
Rad 59:
Rad 59:
===Debug SQL queries=== ===Debug SQL queries===
You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queires table: You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queires table:
* logerrors * '''logall''' - log all queries - suitable only for developers, causes high server loads and NOT recommended for production.
* logslow * '''logslow''' - log queries that take longer than specified number of seconds (float values are accepted).
* logall (be careful !!! logs all SQL queries and can slow the site, NOT recommended for production) * '''logerrors''' - log all error queries.
 
Full sample: Full sample:
<code php> <code php>
$CFG->dboptions = array ( $CFG->dboptions = array (
   'dbpersist' => 0,    //'logall'   => true,
   'dbport' => '',    'logslow'  => 5,
   'dbsocket' => '',    'logerrors'  => true,
   'logerrors' => '1', 
  'logslow' => '1', 
  //'logall' => '1', 
  'dbcollation' => 'utf8mb4_general_ci' 
); );
</code> </code>



Nadavkav: /* Debug email sending */
2018-12-31T14:41:19Z
Debug email sending

				
				
				
				
				
				← Äldre version
				Versionen från 31 december 2018 kl. 14.41
				
Rad 56:
Rad 56:
See more info about [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L314 SMTPDebug] parameters & [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L328 Debugoutput] parameters, See more info about [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L314 SMTPDebug] parameters & [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L328 Debugoutput] parameters,
Set-up mailcatcher (https://mailcatcher.me/). Set-up mailcatcher (https://mailcatcher.me/).

===Debug SQL queries===
You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queires table:
* logerrors
* logslow
* logall (be careful !!! logs all SQL queries and can slow the site, NOT recommended for production)
Full sample:
<code php>
$CFG->dboptions = array (
  'dbpersist' => 0,
  'dbport' => '',
  'dbsocket' => '',
  'logerrors' => '1',
  'logslow' => '1',
  //'logall' => '1',
  'dbcollation' => 'utf8mb4_general_ci'
);
</code>



===Performance info=== ===Performance info===

← Äldre version		Versionen från 27 juli 2021 kl. 12.35
Rad 34:		Rad 34:
	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):		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:		* Redirect all outgoing emails to a specific address:
	<~~code~~ php>		<syntaxhighlight lang="php">
	// Divert all outgoing emails to this address to test and debug emailing features		// Divert all outgoing emails to this address to test and debug emailing features
	// $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!		// $CFG->divertallemailsto = 'root@localhost.local'; // NOT FOR PRODUCTION SERVERS!
	</~~code~~>		</syntaxhighlight>

	* Turn on the CRON debugging and run CLI cron.php script.		* Turn on the CRON debugging and run CLI cron.php script.
	<~~code~~ php>		<syntaxhighlight lang="php">
	// Force developer level debug and add debug info to the output of cron		// Force developer level debug and add debug info to the output of cron
	// $CFG->showcrondebugging = true;		// $CFG->showcrondebugging = true;
	</~~code~~>		</syntaxhighlight>
	And then use SSH (or putty.exe, on windows) to run:		And then use SSH (or putty.exe, on windows) to run:
	<~~code~~ php>		<syntaxhighlight lang="php">
	you@moodle-server(/var/www/html/moodle)# php admin/cli/cron.php		you@moodle-server(/var/www/html/moodle)# php admin/cli/cron.php
	</~~code~~>		</syntaxhighlight>

	* Turn on verbose SMTP debugging and output it into system's error_log (code hack):		* Turn on verbose SMTP debugging and output it into system's error_log (code hack):
	As [https://moodle.org/mod/forum/discuss.php?d=316222#p1289850 suggested] on Moodle's discussion forums:		As [https://moodle.org/mod/forum/discuss.php?d=316222#p1289850 suggested] on Moodle's discussion forums:
	Open [https://github.com/moodle/moodle/blob/master/lib/moodlelib.php#L5379 lib/moodlelib.php L5379] and change it to:		Open [https://github.com/moodle/moodle/blob/master/lib/moodlelib.php#L5379 lib/moodlelib.php L5379] and change it to:
	<~~code~~ php>		<syntaxhighlight lang="php">
	if (!empty($CFG->debugsmtp)) {		if (!empty($CFG->debugsmtp)) {
	$mailer->SMTPDebug = 1; // 0 - no debug ... 4 - low level full debug		$mailer->SMTPDebug = 1; // 0 - no debug ... 4 - low level full debug
	$mailer->Debugoutput = "error_log";		$mailer->Debugoutput = "error_log";
	}		}
	</~~code~~>		</syntaxhighlight>
	See more info about [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L314 SMTPDebug] parameters & [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L328 Debugoutput] parameters,		See more info about [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L314 SMTPDebug] parameters & [https://github.com/moodle/moodle/blob/master/lib/phpmailer/class.phpmailer.php#L328 Debugoutput] parameters,
	Set-up mailcatcher (https://mailcatcher.me/).		Set-up mailcatcher (https://mailcatcher.me/).
Rad 66:		Rad 66:

	If you add		If you add
	<~~code~~ php>		<syntaxhighlight lang="php">
	define('MDL_PERF', true);		define('MDL_PERF', true);
	define('MDL_PERFDB', true);		define('MDL_PERFDB', true);
	define('MDL_PERFTOLOG', true);		define('MDL_PERFTOLOG', true);
	define('MDL_PERFTOFOOT', true);		define('MDL_PERFTOFOOT', true);
	</~~code~~>		</syntaxhighlight>
	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 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!)

Rad 93:		Rad 93:

	Full sample:		Full sample:
	<~~code~~ php>		<syntaxhighlight lang="php">
	$CFG->dboptions = array (		$CFG->dboptions = array (
	//'logall' => true,		//'logall' => true,
Rad 99:		Rad 99:
	'logerrors' => true,		'logerrors' => true,
	);		);
	</~~code~~>		</syntaxhighlight>

	==What to do if you cannot get to the admin screens==		==What to do if you cannot get to the admin screens==
Rad 113:		Rad 113:
	In [[Configuration file\|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:		In [[Configuration file\|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:

	<~~code~~ php>		<syntaxhighlight lang="php">
	//=========================================================================		//=========================================================================
	// 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!		// 7. SETTINGS FOR DEVELOPMENT SERVERS - not intended for production use!!!
Rad 128:		Rad 128:
	// for these users only.		// for these users only.
	// $CFG->debugusers = '2';		// $CFG->debugusers = '2';
	</~~code~~>		</syntaxhighlight>

	Remember to comment those lines again (reinsert the // at the start of the line) when you have finished diagnosing your problem.		Remember to comment those lines again (reinsert the // at the start of the line) when you have finished diagnosing your problem.

← Äldre version		Versionen från 3 juni 2021 kl. 05.15
Rad 138:		Rad 138:
	==See also==		==See also==

			* If you are a developer looking for usage information on the <tt>debugging()</tt> statement, try lib/weblib.php for documentation on how it is used, and lib/setuplib.php for definitions of which PHP error levels the <tt>DEBUG_*</tt> flags map to.
	* 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]]		[[es:Depuración]]
	[[fr:Débogage]]		[[fr:Débogage]]
	[[de:Debugging]]		[[de:Debugging]]

← Äldre version		Versionen från 16 april 2021 kl. 20.23
Rad 87:		Rad 87:

	===Debug SQL queries===		===Debug SQL queries===
	You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into ~~mdl_log_queires~~ table:		You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queries table:
	* '''logall''' - log all queries - suitable only for developers, causes high server loads and NOT recommended for production.		* '''logall''' - log all queries - suitable only for developers, causes high server loads and NOT recommended for production.
	* '''logslow''' - log queries that take longer than specified number of seconds (float values are accepted).		* '''logslow''' - log queries that take longer than specified number of seconds (float values are accepted).

← Äldre version		Versionen från 12 september 2019 kl. 17.00
Rad 6:		Rad 6:
	==Enabling debugging==		==Enabling debugging==

	To enable debugging, go to ''Site administration > Development > Debugging" .		To enable debugging, go to ''Site administration > Development > Debugging'' .

	===Debug messages===		===Debug messages===

← Äldre version		Versionen från 19 april 2019 kl. 12.37
Rad 22:		Rad 22:
	# 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.		# 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.		# 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.

			===Display debug messages===

			If you select this checkbox, the debug messages are displayed directly in the browser, otherwise they are stored in the server logs.

	===Debug email sending===		===Debug email sending===

← Äldre version		Versionen från 29 mars 2019 kl. 10.08
Rad 138:		Rad 138:
	[[es:Depuración]]		[[es:Depuración]]
	[[fr:Débogage]]		[[fr:Débogage]]
			[[de:Debugging]]

← Äldre version		Versionen från 31 december 2018 kl. 14.47
Rad 59:		Rad 59:
	===Debug SQL queries===		===Debug SQL queries===
	You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queires table:		You can add (turn ON) any of the following dboptions in your config.php files, which log different types of SQL queries into mdl_log_queires table:
	* ~~logerrors~~		* '''logall''' - log all queries - suitable only for developers, causes high server loads and NOT recommended for production.
	* logslow		* '''logslow''' - log queries that take longer than specified number of seconds (float values are accepted).
	* logall ~~(be careful !!! logs~~ all ~~SQL~~ queries and ~~can slow the site,~~ NOT recommended for production)		* '''logerrors''' - log all error queries.

	Full sample:		Full sample:
	<code php>		<code php>
	$CFG->dboptions = array (		$CFG->dboptions = array (
	'~~dbpersist~~' ~~=> 0,~~		//'logall' => true,
	~~'dbport'~~ => '',		'logslow' => 5,
	'~~dbsocket~~' => '',		'logerrors' => true,
	'logerrors' => ~~'1',~~
	~~'logslow' => '1'~~,
	~~//'logall' => '1',~~
	~~'dbcollation' => 'utf8mb4_general_ci'~~
	);		);
	</code>		</code>

Debugging - Versionshistorik

Leonstr: Changed to

Drcuriosity: Added a note about debugging() for developers, since it was hard to find details in search.

Danielneis: fix typo

Rwthornton: /* Enabling debugging */

Rwthornton: /* Enabling debugging */

Finns den 19 april 2019 kl. 12.37

Finns den 19 april 2019 kl. 12.34

Finns den 29 mars 2019 kl. 10.08

Nadavkav: /* Debug SQL queries */

Nadavkav: /* Debug email sending */

Leonstr: Changed `to`