Debugging - Revision history

Rwthornton: /* Enabling debugging */

2019-09-12T17:00:33Z

Enabling debugging

← Older revision		Revision as of 17:00, 12 September 2019
Line 6:		Line 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

← Older revision		Revision as of 17:00, 12 September 2019
Line 6:		Line 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 at 12:37, 19 April 2019

2019-04-19T12:37:32Z

← Older revision		Revision as of 12:37, 19 April 2019
Line 22:		Line 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 at 12:34, 19 April 2019

2019-04-19T12:34:16Z

@@ Line 56: / Line 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,
 Set-up mailcatcher (https://mailcatcher.me/).
 ===Performance info===
@@ Line 87: / Line 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?]
-===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.
@@ Line 96: / Line 81: @@
 ===Show page information===
 To show page information printed in the page footer.
 ==What to do if you cannot get to the admin screens==

Finns at 10:08, 29 March 2019

2019-03-29T10:08:16Z

← Older revision		Revision as of 10:08, 29 March 2019
Line 138:		Line 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

← Older revision		Revision as of 14:47, 31 December 2018
Line 59:		Line 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

@@ Line 56: / Line 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,
 Set-up mailcatcher (https://mailcatcher.me/).
 ===Performance info===

Nadavkav: /* More tools for debugging outgoing mail */

2018-06-12T13:13:15Z

More tools for debugging outgoing mail

← Older revision		Revision as of 13:13, 12 June 2018
Line 27:		Line 27:
	Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.		Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.

	==== More tools for debugging outgoing mail ====		==== More tools for debugging outgoing mail (SMTP) ====
	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:

Nadavkav: /* More tools for debugging outgoing mail */

2018-06-12T13:12:45Z

More tools for debugging outgoing mail

← Older revision		Revision as of 13:12, 12 June 2018
Line 54:		Line 54:
	}		}
	</code>		</code>
	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/).

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

Tsala: rewording

2017-12-11T13:20:24Z

rewording

← Older revision		Revision as of 13:20, 11 December 2017
Line 2:		Line 2:
	==Using debugging messages==		==Using debugging messages==

	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 enable debugging i.e. turn debugging messages on, in order to locate the cause of the problem. If you are having problems such as a blank screen or incomplete screens, then turning on debugging is usually the first thing to try.

	==~~Debugging settings~~==		==Enabling debugging==

	~~Debugging messages can be enabled by an administrator in~~ Debugging in the Site administration.		To enable debugging, go to Debugging in the Site administration.

	===Debug ~~messages and display debug~~ messages===		===Debug messages===

	The options are:		The options are: