https://docs.moodle.org/310/en/api.php?action=feedcontributions&feedformat=atom&user=VicentinaMoodleDocs - User contributions [en]2026-05-10T09:25:28ZUser contributionsMediaWiki 1.43.5https://docs.moodle.org/310/en/index.php?title=Debugging&diff=90397Debugging2011-09-25T20:12:45Z<p>Vicentina: /* Try typing the URL directly */</p>
<hr />
<div>{{Developer tools}}<br />
<br />
Location: ''Settings > Site administration > Development > Debugging''<br />
<br />
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. <br />
<br />
==Debugging settings==<br />
Here are the settings on the Debugging page:<br />
<br />
===Debug messages===<br />
The default is none, your choices are:<br />
<br />
;NONE : Do not show any errors or warnings (Default) <br />
;ALL : Show all reasonable PHP debug messages<br />
;MINIMAL : Show only fatal errors<br />
;NORMAL : Show warnings, errors and notices<br />
;DEVELOPER : extra Moodle debug messages for developers<br />
<br />
There is rarely any advantage in going to Developer level, unless you are a developer, in which case it is strongly recommended.<br />
<br />
Once you have got the error message, and copied and pasted it somewhere. HIGHLY RECOMMENDED to turn Debug back to NONE. Debug messages can give clues to a hacker as to the setup of your site.<br />
<br />
===Display debug messages===<br />
<br />
There is an option to choose whether to display error messages or simply record them in the server logs.<br />
<br />
===Debug email sending===<br />
<br />
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.<br />
<br />
===Performance info===<br />
<br />
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.<br />
<br />
If you add<br />
<code php><br />
define('MDL_PERF', true);<br />
define('MDL_PERFDB', true);<br />
define('MDL_PERFTOLOG', true);<br />
define('MDL_PERFTOFOOT', true);<br />
</code><br />
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!<br />
<br />
===Show origin of language strings===<br />
Helps translators.<br />
<br />
===Show validator links===<br />
Be careful, read the warning.<br />
<br />
===Show page information===<br />
To show page information printed in the page footer.<br />
<br />
==What to do if you cannot get to the admin screens==<br />
<br />
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.<br />
<br />
===Try typing the URL directly===<br />
<br />
The debug settings are at the URL <code><nowiki>http://nte-coxim.freewebclass.com/admin/settings.php?section=debugging</nowiki></code> on your server. Sometimes that URL will work, even though the pages you need to go to to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.<br />
<br />
===In config.php===<br />
<br />
In moodle/config.php you can add the lines:<br />
<br />
<code php><br />
$CFG->debug = 2047; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
Or even more debugging messages:<br />
<br />
<code php><br />
$CFG->debug = 6143; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
For Moodle 2.0 the possible settings are as follows:<br />
<br />
<code php><br />
// Force a debugging mode regardless the settings in the site administration<br />
// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!<br />
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debug = 38911; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debugdisplay = false; // NOT FOR PRODUCTION SERVERS!<br />
<br />
// You can specify a comma separated list of user ids that that always see<br />
// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay<br />
// for these users only.<br />
$CFG->debugusers = '2';<br />
</code><br />
<br />
Remember to remove those lines again when you have finished diagnosing your problem.<br />
<br />
===In the database===<br />
<br />
Using a tool like phpMyAdmin, execute the following SQL commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 2047 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
To turn it back off, use the admin screens, or the commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 0 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
(If you use a different database prefix, you will need to adjust those commands accordingly.)<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=91031 Debugging Turned on to Developer Mode on 1.8.2] forum discussion including instructions on how to turn debugging off<br />
* 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...<br />
<br />
[[Category:Site administration]]<br />
<br />
[[fr:Débogage]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Debugging&diff=90396Debugging2011-09-25T20:10:36Z<p>Vicentina: /* In config.php */</p>
<hr />
<div>{{Developer tools}}<br />
<br />
Location: ''Settings > Site administration > Development > Debugging''<br />
<br />
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. <br />
<br />
==Debugging settings==<br />
Here are the settings on the Debugging page:<br />
<br />
===Debug messages===<br />
The default is none, your choices are:<br />
<br />
;NONE : Do not show any errors or warnings (Default) <br />
;ALL : Show all reasonable PHP debug messages<br />
;MINIMAL : Show only fatal errors<br />
;NORMAL : Show warnings, errors and notices<br />
;DEVELOPER : extra Moodle debug messages for developers<br />
<br />
There is rarely any advantage in going to Developer level, unless you are a developer, in which case it is strongly recommended.<br />
<br />
Once you have got the error message, and copied and pasted it somewhere. HIGHLY RECOMMENDED to turn Debug back to NONE. Debug messages can give clues to a hacker as to the setup of your site.<br />
<br />
===Display debug messages===<br />
<br />
There is an option to choose whether to display error messages or simply record them in the server logs.<br />
<br />
===Debug email sending===<br />
<br />
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.<br />
<br />
===Performance info===<br />
<br />
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.<br />
<br />
If you add<br />
<code php><br />
define('MDL_PERF', true);<br />
define('MDL_PERFDB', true);<br />
define('MDL_PERFTOLOG', true);<br />
define('MDL_PERFTOFOOT', true);<br />
</code><br />
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!<br />
<br />
===Show origin of language strings===<br />
Helps translators.<br />
<br />
===Show validator links===<br />
Be careful, read the warning.<br />
<br />
===Show page information===<br />
To show page information printed in the page footer.<br />
<br />
==What to do if you cannot get to the admin screens==<br />
<br />
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.<br />
<br />
===Try typing the URL directly===<br />
<br />
The debug settings are at the URL <code><nowiki>http://.../admin/settings.php?section=debugging</nowiki></code> on your server. Sometimes that URL will work, even though the pages you need to go to to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.<br />
<br />
===In config.php===<br />
<br />
In moodle/config.php you can add the lines:<br />
<br />
<code php><br />
$CFG->debug = 2047; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
Or even more debugging messages:<br />
<br />
<code php><br />
$CFG->debug = 6143; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
For Moodle 2.0 the possible settings are as follows:<br />
<br />
<code php><br />
// Force a debugging mode regardless the settings in the site administration<br />
// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!<br />
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debug = 38911; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debugdisplay = false; // NOT FOR PRODUCTION SERVERS!<br />
<br />
// You can specify a comma separated list of user ids that that always see<br />
// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay<br />
// for these users only.<br />
$CFG->debugusers = '2';<br />
</code><br />
<br />
Remember to remove those lines again when you have finished diagnosing your problem.<br />
<br />
===In the database===<br />
<br />
Using a tool like phpMyAdmin, execute the following SQL commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 2047 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
To turn it back off, use the admin screens, or the commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 0 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
(If you use a different database prefix, you will need to adjust those commands accordingly.)<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=91031 Debugging Turned on to Developer Mode on 1.8.2] forum discussion including instructions on how to turn debugging off<br />
* 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...<br />
<br />
[[Category:Site administration]]<br />
<br />
[[fr:Débogage]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90249Configuration file2011-09-25T03:12:16Z<p>Vicentina: </p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://nte-coxim.freewebclass.com/nte-coxim/moodle';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://cvs.moodle.org/moodle/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Debugging&diff=90042Debugging2011-09-22T07:17:10Z<p>Vicentina: /* In config.php */</p>
<hr />
<div>{{Developer tools}}<br />
<br />
Location: ''Settings > Site administration > Development > Debugging''<br />
<br />
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. <br />
<br />
==Debugging settings==<br />
Here are the settings on the Debugging page:<br />
<br />
===Debug messages===<br />
The default is none, your choices are:<br />
<br />
;NONE : Do not show any errors or warnings (Default) <br />
;ALL : Show all reasonable PHP debug messages<br />
;MINIMAL : Show only fatal errors<br />
;NORMAL : Show warnings, errors and notices<br />
;DEVELOPER : extra Moodle debug messages for developers<br />
<br />
There is rarely any advantage in going to Developer level, unless you are a developer, in which case it is strongly recommended.<br />
<br />
Once you have got the error message, and copied and pasted it somewhere. HIGHLY RECOMMENDED to turn Debug back to NONE. Debug messages can give clues to a hacker as to the setup of your site.<br />
<br />
===Display debug messages===<br />
<br />
There is an option to choose whether to display error messages or simply record them in the server logs.<br />
<br />
===Debug email sending===<br />
<br />
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.<br />
<br />
===Performance info===<br />
<br />
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.<br />
<br />
If you add<br />
<code php><br />
define('MDL_PERF', true);<br />
define('MDL_PERFDB', true);<br />
define('MDL_PERFTOLOG', true);<br />
define('MDL_PERFTOFOOT', true);<br />
</code><br />
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!<br />
<br />
===Show origin of language strings===<br />
Helps translators.<br />
<br />
===Show validator links===<br />
Be careful, read the warning.<br />
<br />
===Show page information===<br />
To show page information printed in the page footer.<br />
<br />
==What to do if you cannot get to the admin screens==<br />
<br />
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.<br />
<br />
===Try typing the URL directly===<br />
<br />
The debug settings are at the URL <code><nowiki>http://.../admin/settings.php?section=debugging</nowiki></code> on your server. Sometimes that URL will work, even though the pages you need to go to to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.<br />
<br />
===In the database===<br />
<br />
Using a tool like phpMyAdmin, execute the following SQL commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 2047 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
To turn it back off, use the admin screens, or the commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 0 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
(If you use a different database prefix, you will need to adjust those commands accordingly.)<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=91031 Debugging Turned on to Developer Mode on 1.8.2] forum discussion including instructions on how to turn debugging off<br />
* 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...<br />
<br />
[[Category:Site administration]]<br />
<br />
[[fr:Débogage]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Debugging&diff=90039Debugging2011-09-22T07:02:19Z<p>Vicentina: /* Try typing the URL directly */</p>
<hr />
<div>{{Developer tools}}<br />
<br />
Location: ''Settings > Site administration > Development > Debugging''<br />
<br />
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. <br />
<br />
==Debugging settings==<br />
Here are the settings on the Debugging page:<br />
<br />
===Debug messages===<br />
The default is none, your choices are:<br />
<br />
;NONE : Do not show any errors or warnings (Default) <br />
;ALL : Show all reasonable PHP debug messages<br />
;MINIMAL : Show only fatal errors<br />
;NORMAL : Show warnings, errors and notices<br />
;DEVELOPER : extra Moodle debug messages for developers<br />
<br />
There is rarely any advantage in going to Developer level, unless you are a developer, in which case it is strongly recommended.<br />
<br />
Once you have got the error message, and copied and pasted it somewhere. HIGHLY RECOMMENDED to turn Debug back to NONE. Debug messages can give clues to a hacker as to the setup of your site.<br />
<br />
===Display debug messages===<br />
<br />
There is an option to choose whether to display error messages or simply record them in the server logs.<br />
<br />
===Debug email sending===<br />
<br />
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.<br />
<br />
===Performance info===<br />
<br />
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.<br />
<br />
If you add<br />
<code php><br />
define('MDL_PERF', true);<br />
define('MDL_PERFDB', true);<br />
define('MDL_PERFTOLOG', true);<br />
define('MDL_PERFTOFOOT', true);<br />
</code><br />
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!<br />
<br />
===Show origin of language strings===<br />
Helps translators.<br />
<br />
===Show validator links===<br />
Be careful, read the warning.<br />
<br />
===Show page information===<br />
To show page information printed in the page footer.<br />
<br />
==What to do if you cannot get to the admin screens==<br />
<br />
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.<br />
<br />
===Try typing the URL directly===<br />
<br />
The debug settings are at the URL <code><nowiki>http://nte-coxim.freewebclass.com/admin/settings.php?section=debugging</nowiki></code> on your server. Sometimes that URL will work, even though the pages you need to go to to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.<br />
<br />
===In config.php===<br />
<br />
In moodle/config.php you can add the lines:<br />
<br />
<code php><br />
$CFG->debug = 2047; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
Or even more debugging messages:<br />
<br />
<code php><br />
$CFG->debug = 6143; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
For Moodle 2.0 the possible settings are as follows:<br />
<br />
<code php><br />
// Force a debugging mode regardless the settings in the site administration<br />
// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!<br />
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debug = 38911; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debugdisplay = true; // NOT FOR PRODUCTION SERVERS!<br />
<br />
// You can specify a comma separated list of user ids that that always see<br />
// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay<br />
// for these users only.<br />
$CFG->debugusers = '2';<br />
</code><br />
<br />
Remember to remove those lines again when you have finished diagnosing your problem.<br />
<br />
===In the database===<br />
<br />
Using a tool like phpMyAdmin, execute the following SQL commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 2047 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
To turn it back off, use the admin screens, or the commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 0 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
(If you use a different database prefix, you will need to adjust those commands accordingly.)<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=91031 Debugging Turned on to Developer Mode on 1.8.2] forum discussion including instructions on how to turn debugging off<br />
* 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...<br />
<br />
[[Category:Site administration]]<br />
<br />
[[fr:Débogage]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90031Configuration file2011-09-21T15:16:17Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://nte-coxim.freewebclass.com is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90030Configuration file2011-09-21T15:14:55Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://nte-coxim.freewebclass.com.view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90029Configuration file2011-09-21T15:14:15Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://nte-coxim.freewebclass.com.php?"view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90028Configuration file2011-09-21T15:12:56Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file "http://nte-coxim.freewebclass.com/moodle/config-dist.php?"view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90027Configuration file2011-09-21T15:09:57Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://nte-coxim.freewebclass.com/script/moodle/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90026Configuration file2011-09-21T15:08:56Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://nte-coxim.freewebclass.com/moodle/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90025Configuration file2011-09-21T15:08:14Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://nte-coxim.freewebclass.com/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=90024Configuration file2011-09-21T15:06:15Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://nte-coxim.freewebclass.com/moodle/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=89970Configuration file2011-09-20T11:21:53Z<p>Vicentina: /* Enabling password salting */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://nte-coxim.frewebclass.com/nte-coxim/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?><br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://cvs.moodle.org/moodle/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
$CFG->cachetype = ‘internal’;<br />
$CFG->wwwroot = 'http://nte-coxim.freewebclass.com';<br />
$CFG->dirroot = '/var/www/nte-coxim.freewebclass.com/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=89946Configuration file2011-09-20T02:36:09Z<p>Vicentina: /* Enabling password salting */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.nte-coxim.frewebclass.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?><br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://cvs.moodle.org/moodle/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
$CFG->cachetype = ‘internal’;<br />
$CFG->wwwroot = 'http://nte-coxim.freewebclass.com';<br />
$CFG->dirroot = '/var/www/nte-coxim.freewebclass.com/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=89945Configuration file2011-09-20T02:34:03Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://cvs.moodle.org/moodle/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
$CFG->cachetype = ‘internal’;<br />
$CFG->wwwroot = 'http://nte-coxim.freewebclass.com';<br />
$CFG->dirroot = '/var/www/nte-coxim.freewebclass.com/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Installation_FAQ&diff=89943Installation FAQ2011-09-20T00:29:28Z<p>Vicentina: /* What & where are Moodle's configuration settings stored? */</p>
<hr />
<div>{{Template:Installing Moodle}}<br />
<br />
== System information needed for Installation problems forum ==<br />
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Use this template to copy and paste into your post:<br />
* Server Operating System name (version also if possible): <br />
* Browser name (version also if possible):<br />
* Moodle version:<br />
* Moodle install type? (New/Upgrade):<br />
* Moodle config.php attached?(Y/N):<br />
* Phpinfo attached? (Y/N):<br />
<br />
For the last two items, try to include the following in your post as an attachment:<br />
* A copy of your phpinfo output as shown in your browser (see the instructions above for an explanation of how to obtain this, or see [[phpinfo]]).<br />
* A copy of the Moodle configuration file (with secret info like database password deleted, of course). This is located in the main Moodle directory (by default called moodle), and is named config.php<br />
<br />
Copy and paste both of these into a single text file (using vi, Notepad, etc) and attach this to your post. If your PC is a Windows box and config.php looks messy (line breaks missing or in the wrong places) in Notepad, try Wordpad.<br />
<br />
If you cannot provide your phpinfo, try to copy & paste and complete these in your post:<br />
* Webserver (e.g. Apache/IIS) version:<br />
* Database server (e.g. MySQL, PostgreSQL) version:<br />
* PHP version:<br />
<br />
For installation on web hosting accounts: contact your support desk who should be able to tell you this information.<br />
<br />
: '''Security Warning''': Make sure you edit any files and delete any passwords before posting onto the forum.<br />
<br />
[[#top|Top]]<br />
<br />
==PHP - is it installed and what version do I have?==<br />
<br />
Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:<br />
<br />
<code php><br />
<?PHP phpinfo() ?><br />
</code><br />
<br />
If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.<br />
<br />
[[#top|Top]]<br />
<br />
<?xml version='1.0' encoding='utf-8'?><br />
<!--<br />
DEBUG: Content-Type: application/xhtml+xml <br />
--><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="pt-br" xml:lang="pt-br"><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<link rel="stylesheet" type="text/css" href="http://nte-coxim.freewebclass.com/theme/standard/styles.php" /><br />
<link rel="stylesheet" type="text/css" href="http://nte-coxim.freewebclass.com/theme/standardwhite/styles.php" /><br />
<meta name="description" content="<br />
" /><br />
<!--[if IE 7]><br />
<link rel="stylesheet" type="text/css" href="http://nte-coxim.freewebclass.com/theme/standard/styles_ie7.css" /><br />
<![endif]--><br />
<!--[if IE 6]><br />
<link rel="stylesheet" type="text/css" href="http://nte-coxim.freewebclass.com/theme/standard/styles_ie6.css" /><br />
<![endif]--><br />
<br />
<br />
<title>Online Courses - Distance Learning - Núcleo de Tecnologias Educacionais</title><br />
<meta name="description" content="Free Web Hosting for Online Classes, Distance Learning and Online Courses offered by worldwide."><br />
<META Name="Keywords" Content="internet degree, online university, distance learning, online education, distance education, online courses"><br />
<br />
<link rel="shortcut icon" href="http://nte-coxim.freewebclass.com/theme/standardwhite/favicon.ico" /><br />
<!--<style type="text/css">/*<![CDATA[*/ body{behavior:url(http://nte-coxim.freewebclass.com/lib/csshover.htc);} /*]]>*/</style>--><br />
<br />
<script type="text/javascript" src="http://nte-coxim.freewebclass.com/lib/javascript-static.js"></script><br />
<script type="text/javascript" src="http://nte-coxim.freewebclass.com/lib/javascript-mod.php"></script><br />
<script type="text/javascript" src="http://nte-coxim.freewebclass.com/lib/overlib/overlib.js"></script><br />
<script type="text/javascript" src="http://nte-coxim.freewebclass.com/lib/overlib/overlib_cssstyle.js"></script><br />
<script type="text/javascript" src="http://nte-coxim.freewebclass.com/lib/cookies.js"></script><br />
<script type="text/javascript" src="http://nte-coxim.freewebclass.com/lib/ufo.js"></script><br />
<script type="text/javascript" src="http://nte-coxim.freewebclass.com/lib/dropdown.js"></script> <br />
<br />
<script type="text/javascript" defer="defer"><br />
//<![CDATA[<br />
setTimeout('fix_column_widths()', 20);<br />
//]]><br />
</script><br />
<script type="text/javascript"><br />
//<![CDATA[<br />
function openpopup(url, name, options, fullscreen) {<br />
var fullurl = "http://nte-coxim.freewebclass.com" + url;<br />
var windowobj = window.open(fullurl, name, options);<br />
if (!windowobj) {<br />
return true;<br />
}<br />
if (fullscreen) {<br />
windowobj.moveTo(0, 0);<br />
windowobj.resizeTo(screen.availWidth, screen.availHeight);<br />
}<br />
windowobj.focus();<br />
return false;<br />
}<br />
<br />
function uncheckall() {<br />
var inputs = document.getElementsByTagName('input');<br />
for(var i = 0; i < inputs.length; i++) {<br />
inputs[i].checked = false;<br />
}<br />
}<br />
<br />
function checkall() {<br />
var inputs = document.getElementsByTagName('input');<br />
for(var i = 0; i < inputs.length; i++) {<br />
inputs[i].checked = true;<br />
}<br />
}<br />
<br />
function inserttext(text) {<br />
text = ' ' + text + ' ';<br />
if ( opener.document.forms['theform'].message.createTextRange && opener.document.forms['theform'].message.caretPos) {<br />
var caretPos = opener.document.forms['theform'].message.caretPos;<br />
caretPos.text = caretPos.text.charAt(caretPos.text.length - 1) == ' ' ? text + ' ' : text;<br />
} else {<br />
opener.document.forms['theform'].message.value += text;<br />
}<br />
opener.document.forms['theform'].message.focus();<br />
}<br />
<br />
function getElementsByClassName(oElm, strTagName, oClassNames){<br />
var arrElements = (strTagName == "*" && oElm.all)? oElm.all : oElm.getElementsByTagName(strTagName);<br />
var arrReturnElements = new Array();<br />
var arrRegExpClassNames = new Array();<br />
if(typeof oClassNames == "object"){<br />
for(var i=0; i<oClassNames.length; i++){<br />
arrRegExpClassNames.push(new RegExp("(^|\\s)" + oClassNames[i].replace(/\-/g, "\\-") + "(\\s|$)"));<br />
}<br />
}<br />
else{<br />
arrRegExpClassNames.push(new RegExp("(^|\\s)" + oClassNames.replace(/\-/g, "\\-") + "(\\s|$)"));<br />
}<br />
var oElement;<br />
var bMatchesAll;<br />
for(var j=0; j<arrElements.length; j++){<br />
oElement = arrElements[j];<br />
bMatchesAll = true;<br />
for(var k=0; k<arrRegExpClassNames.length; k++){<br />
if(!arrRegExpClassNames[k].test(oElement.className)){<br />
bMatchesAll = false;<br />
break;<br />
}<br />
}<br />
if(bMatchesAll){<br />
arrReturnElements.push(oElement);<br />
}<br />
}<br />
return (arrReturnElements)<br />
}<br />
//]]><br />
<br />
</script><br />
</head><br />
<br />
<body class="course course-1 notloggedin dir-ltr lang-pt_br_utf8" id="site-index"><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<style type="text/css"> <br />
#blockblockA {position:absolute;top:0px;left:0px;background-color:#E7E8E8;width:100%;height:100%;}<br />
#blockblockA td {text-align:center;width:100%;height:100%;}<br />
#blockblockA td p {font: bold 20px Arial;color:#333333;}<br />
#blockblockA td div {font: bold 13px Arial;color:#333333;}<br />
#blockblockB {visibility:invisible;display:none;}<br />
<br />
</style><br />
<br />
<noscript><br />
<style type="text/css"><br />
#blockblockA {visibility:invisible!important;display:none!important;}<br />
#blockblockA td {visibility:invisible!important;display:none!important;}<br />
#blockblockA td p {visibility:invisible!important;display:none!important;}<br />
#blockblockB {visibility:visible!important;display:block!important;}<br />
</style><br />
</noscript><br />
<br />
<br />
<script type="text/javascript" src="http://freewebclass.com/advertisement.js"></script><br />
<br />
<br />
<table id="blockblockA"><tr><td><br />
<br />
<!-- DISPLAY HTML CODE HERE --><br />
<table width="500" border="0" align="center" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF"><br />
<tr><br />
<br />
<td width="500" style="border:1px solid #D9DADA; padding:25px;"><br />
<p>FreeWebClass.com is supported by advertisements.</p><br />
<p>Please disable Advertising Blocking Software in your browser to view this website.</p><br />
<p>You can use FreeWebClass.com without advertisement by <a href="http://freewebclass.com" target="_blank">subscribing to Plus or Pro account</a>.</p><br />
<p>For more information please visit <a href="http://freewebclass.com" target="_blank">http://freewebclass.com</a> or email support@freewebclass.com. Thank you.</p><br />
</td><br />
</tr><br />
</table><br />
<br />
<!-- DISPLAY HTML CODE HERE --><br />
<br />
<div align="right">&nbsp;</div><br />
<br />
</td></tr></table><br />
<br />
<span id="blockblockB"><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<script type="text/javascript"><br />
<br />
var _gaq = _gaq || [];<br />
_gaq.push(['_setAccount', 'UA-7416464-17']);<br />
_gaq.push(['_setDomainName', '.freewebclass.com']);<br />
_gaq.push(['_trackPageview']);<br />
<br />
(function() {<br />
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;<br />
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';<br />
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);<br />
})();<br />
<br />
<br />
</script><br />
<br />
<br />
<br />
<br />
<br />
<script type="text/javascript"><br />
<br />
var _gaq = _gaq || [];<br />
_gaq.push(['_setAccount', 'UA-3485212-63']);<br />
_gaq.push(['_setDomainName', '.freewebclass.com']);<br />
_gaq.push(['_trackPageview']);<br />
<br />
(function() {<br />
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;<br />
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';<br />
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);<br />
})();<br />
<br />
</script><br />
<br />
<div id="page"><br />
<a class="skip" href="#maincontent">Ir para o conteúdo principal</a><br />
<br />
<div id="header-home" class=" clearfix"> <h1 class="headermain">Núcleo de Tecnologias Educacionais</h1><br />
<br />
<div class="headermenu"><div class="logininfo">Você ainda não se identificou (<a href="http://nte-coxim.freewebclass.com/login/index.php">Acesso</a>)</div><form action="http://nte-coxim.freewebclass.com/course/jumpto.php" method="get" id="chooselang" class="popupform"><div><label for="chooselang_jump"><span class="accesshide " >Idioma</span></label><select id="chooselang_jump" name="jump" onchange="self.location=document.getElementById('chooselang').jump.options[document.getElementById('chooselang').jump.selectedIndex].value;"><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=af_utf8">Afrikaans (af)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ar_utf8">عربي (ar)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ast_utf8">Asturianu (ast)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=be_utf8">Беларуская (be)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=bg_utf8">Български (bg)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=bn_utf8">বাংলা (bn)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=bs_utf8">Bosanski (bs)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ca_utf8">Català (ca)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=cs_utf8">Čeština (cs)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=cy_utf8">Cymraeg (cy)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=da_utf8">Dansk (da)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=de_du_utf8">Deutsch - Du (de_du)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=de_utf8">Deutsch (de)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=dv_utf8">ދިވެހި (dv)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=dz_utf8">Dzongkha (dz)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=el_utf8">Ελληνικά (el)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=en_us_utf8">English (en_us)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=en_utf8">English (en)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=es_ar_utf8">Español - Argentina (es_ar)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=es_mx_utf8">Español - Mexico (es_mx)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=es_utf8">Español - Internacional (es)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=et_utf8">Eesti (et)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=eu_utf8">Euskara (eu)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=fa_utf8">فارسی (fa)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=fi_utf8">Suomi (fi)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=fil_utf8">Filipino (fil)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=fr_ca_utf8">Français - Canada (fr_ca)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=fr_utf8">Français (fr)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ga_utf8">Gaeilge (ga)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=gl_utf8">Galego (gl)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=gu_utf8">ગુજરાતી (gu)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=he_utf8">עברית (he)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=hi_utf8">िहन्दी (hi)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=hr_utf8">Hrvatski (hr)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=hu_utf8">magyar (hu)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=hy_utf8">Հայերեն (hy)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=id_utf8">Indonesian (id)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=is_utf8">&Iacute;slenska (is)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=it_utf8">Italiano (it)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ja_utf8">日本語 (ja)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ka_utf8">ქართული (ka)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=kk_utf8">Қазақша (kk)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=km_utf8">ខ្មែរ (km)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=kn_utf8">ಕನ್ನಡ (kn)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ko_utf8">한국어 (ko)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=la_utf8">Latin (la)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=lo_utf8">Laotian (lo)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=lt_utf8">Lietuvių (lt)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=lv_utf8">Latviešu (lv)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=mi_tn_utf8">Māori - Tainui (mi_tn)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=mi_wwow_utf8">Māori - Waikato (mi_wwow)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=mk_utf8">Македонски (mk)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ml_utf8">മലയാളം (ml)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=mn_utf8">Монгол (mn)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=mr_utf8">मराठी (mr)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ms_utf8">Bahasa Melayu (ms)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=nl_utf8">Nederlands (nl)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=nn_utf8">Norsk - nynorsk (nn)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=no_gr_utf8">Norsk (no_gr)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=no_utf8">Norsk - bokmål (no)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=pl_utf8">Polski (pl)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=pt_br_utf8" selected="selected">Português - Brasil (pt_br)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=pt_utf8">Português - Portugal (pt)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ro_utf8">Română (ro)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ru_utf8">Русский (ru)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=si_utf8">සිංහල (si)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=sk_utf8">Slovenčina (sk)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=sl_utf8">Sloven&#353;&#269;ina (sl)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=sm_utf8">Samoan (sm)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=so_utf8">Soomaali (so)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=sq_utf8">Shqip (sq)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=sr_cr_bo_utf8">Српски (sr_cr_bo)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=sr_cr_utf8">Српски (sr_cr)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=sr_lt_utf8">Srpski (sr_lt)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=sv_utf8">Svenska (sv)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ta_lk_utf8">தமிழ் (ta_lk)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ta_utf8">Tamil (ta)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=th_utf8">Thai (th)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=tl_utf8">Tagalog (tl)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=to_utf8">Tongan (to)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=tr_utf8">Türkçe (tr)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=uk_utf8">Українська (uk)</option><br />
<br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=ur_utf8">اردو (ur)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=uz_utf8">O'zbekcha (uz)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=vi_utf8">Vietnamese (vi)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=zh_cn_utf8">简体中文 (zh_cn)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=zh_tw_utf8">正體中文 (zh_tw)</option><br />
<option value="http://nte-coxim.freewebclass.com/index.php?lang=zu_utf8">isiZulu (zu)</option><br />
<br />
</select><input type="hidden" name="sesskey" value="lQrVAJCaBm" /><div id="noscriptchooselang" style="display: inline;"><input type="submit" value="Vai" /></div><script type="text/javascript"><br />
//<![CDATA[<br />
document.getElementById("noscriptchooselang").style.display = "none";<br />
//]]><br />
</script></div></form></div><br />
</div> <hr /><br />
<!-- END OF HEADER --><br />
<br />
<br />
<br />
<table border="0" align="center" cellpadding="0" cellspacing="0" bgcolor="#fafafa"><br />
<tr><br />
<td style="padding-top:10px;"><br />
<br />
<script type="text/javascript"><!--<br />
google_ad_client = "ca-pub-1015063944539735";<br />
/* FreeWebClass.com */<br />
google_ad_slot = "6525208159";<br />
google_ad_width = 728;<br />
google_ad_height = 90;<br />
//--><br />
<br />
</script><br />
<script type="text/javascript"<br />
src="http://pagead2.googlesyndication.com/pagead/show_ads.js"><br />
</script><br />
<br />
</td><br />
</tr><br />
</table><br />
<br />
<div id="content" class=" clearfix"><br />
<br />
<table id="layout-table" summary="layout"><br />
<tr><br />
<td style="width: 210px;" id="left-column"><div><a href="#sb-1" class="skip-block">Saltar Menu Principal</a><div id="inst1" class="block_site_main_menu sideblock"><div class="header"><div class="title"><input type="image" src="http://nte-coxim.freewebclass.com/pix/t/switch_minus.gif" id="togglehide_inst1" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar o bloco Menu Principal', 'Esconder o bloco Menu Principal'); return false;" alt="Esconder o bloco Menu Principal" title="Esconder o bloco Menu Principal" class="hide-show-image" /><h2>Menu Principal</h2></div></div><div class="content"><br />
<br />
<ul class='list'><br />
<li class="r0"><div class="icon column c0"><img src="http://nte-coxim.freewebclass.com/mod/assignment/icon.gif" class="icon" alt="" /></div><div class="column c1"><a title="Tarefas" href="http://nte-coxim.freewebclass.com/mod/assignment/view.php?id=15">Atividade 1 – Enviando Mensagens </a></div></li><br />
<li class="r1"><div class="icon column c0"><img src="http://nte-coxim.freewebclass.com/mod/forum/icon.gif" class="icon" alt="" /></div><div class="column c1"><a title="Fóruns" href="http://nte-coxim.freewebclass.com/mod/forum/view.php?id=38">Projeto "Rede de Leituras"</a></div></li><br />
</ul><br />
</div></div><script type="text/javascript"><br />
//<![CDATA[<br />
elementCookieHide("inst1","Mostrar o bloco Menu Principal","Esconder o bloco Menu Principal");<br />
//]]><br />
</script><span id="sb-1" class="skip-block-to"></span></div></td><td id="middle-column"><span id="maincontent"></span><div><div class="generalbox sitetopic box"><br />
<div style="text-align: center;"><img width="230" vspace="0" hspace="0" height="171" border="0" title="mmm" alt="mmm" src="http://nte-coxim.freewebclass.com/file.php/1/logo_NTE.jpg" /> </div></div><h2 class="headingblock header ">Cursos disponíveis</h2><ul class="unlist"><li><div class="coursebox clearfix"><div class="info"><div class="name"><a title="Clique para entrar neste curso" href="http://nte-coxim.freewebclass.com/course/view.php?id=4">Projeto "Rede de Leituras"</a></div></div><div class="summary"></div></div></li><br />
<li><div class="coursebox clearfix"><div class="info"><div class="name"><a title="Clique para entrar neste curso" href="http://nte-coxim.freewebclass.com/course/view.php?id=3">Uso Pedagógico do Google Docs</a></div></div><div class="summary"><br /><br />
<table width="100%" border="1"><tbody><tr><td width="50%" valign="top" style="color: rgb(0, 0, 255); font-weight: bold;">Oficina Google Docs - Para Professores das STE's/jurisdição NTE/Coxim<br /></td></tr></tbody></table> </div></div></li><br />
<br />
</ul><br />
<br /></div></td><td style="width: 210px;" id="right-column"><div><a href="#sb-2" class="skip-block">Saltar Acesso</a><div id="inst16" class="block_login sideblock"><div class="header"><div class="title"><input type="image" src="http://nte-coxim.freewebclass.com/pix/t/switch_minus.gif" id="togglehide_inst16" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar o bloco Acesso', 'Esconder o bloco Acesso'); return false;" alt="Esconder o bloco Acesso" title="Esconder o bloco Acesso" class="hide-show-image" /><h2>Acesso</h2></div></div><div class="content"><br />
<form class="loginform" id="login" method="post" action="http://nte-coxim.freewebclass.com/login/index.php"><div class="c1 fld username"><label for="login_username">Nome de usuário</label><input type="text" name="username" id="login_username" value="a5a1e19" /></div><div class="c1 fld password"><label for="login_password">Senha</label><input type="password" name="password" id="login_password" value="" /></div><div class="c1 btn"><input type="submit" value="Acesso" /></div></form><br />
<div class="footer"><div><a href="http://nte-coxim.freewebclass.com/login/signup.php">Cadastramento de usuários</a></div><div><a href="http://nte-coxim.freewebclass.com/login/forgot_password.php">Perdeu a senha?</a></div></div></div></div><script type="text/javascript"><br />
//<![CDATA[<br />
elementCookieHide("inst16","Mostrar o bloco Acesso","Esconder o bloco Acesso");<br />
//]]><br />
</script><span id="sb-2" class="skip-block-to"></span><a href="#sb-3" class="skip-block">Saltar Usuários Online</a><div id="inst18" class="block_online_users sideblock"><div class="header"><div class="title"><input type="image" src="http://nte-coxim.freewebclass.com/pix/t/switch_minus.gif" id="togglehide_inst18" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar o bloco Usuários Online', 'Esconder o bloco Usuários Online'); return false;" alt="Esconder o bloco Usuários Online" title="Esconder o bloco Usuários Online" class="hide-show-image" /><h2>Usuários Online</h2></div></div><div class="content"><div class="info">(últimos 5 minutos)</div><div class="info">Nenhum</div></div></div><script type="text/javascript"><br />
<br />
//<![CDATA[<br />
elementCookieHide("inst18","Mostrar o bloco Usuários Online","Esconder o bloco Usuários Online");<br />
//]]><br />
</script><span id="sb-3" class="skip-block-to"></span><a href="#sb-4" class="skip-block">Saltar Calendário</a><div id="inst4" class="block_calendar_month sideblock"><div class="header"><div class="title"><input type="image" src="http://nte-coxim.freewebclass.com/pix/t/switch_minus.gif" id="togglehide_inst4" onclick="elementToggleHide(this, true, function(el) {return findParentNode(el, 'DIV', 'sideblock'); }, 'Mostrar o bloco Calendário', 'Esconder o bloco Calendário'); return false;" alt="Esconder o bloco Calendário" title="Esconder o bloco Calendário" class="hide-show-image" /><h2>Calendário</h2></div></div><div class="content"><div id="overDiv" style="position: absolute; visibility: hidden; z-index:1000;"></div><script type="text/javascript" src="http://nte-coxim.freewebclass.com/calendar/overlib.cfg.php"></script><br />
<div class="calendar-controls"><a class="previous" href="index.php?cal_m=8&amp;cal_y=2011" title="Mês anterior"><span class="arrow ">&#x25C4;</span><span class="accesshide " >&nbsp;Mês anterior</span></a><span class="hide"> | </span><span class="current"><a href="http://nte-coxim.freewebclass.com/calendar/view.php?view=month&amp;course=1&amp;cal_d=1&amp;cal_m=9&amp;cal_y=2011">setembro 2011</a></span><span class="hide"> | </span><a class="next" href="index.php?cal_m=10&amp;cal_y=2011" title="Próximo mês"><span class="accesshide " >Próximo mês&nbsp;</span><span class="arrow ">&#x25BA;</span></a><br />
<span class="clearer"><!-- --></span></div><br />
<table class="minicalendar" summary="Tabela de dados, setembro 2011 Calendário"><tr class="weekdays"><th scope="col"><abbr title="Domingo">Dom</abbr></th><br />
<th scope="col"><abbr title="Segunda-feira">Seg</abbr></th><br />
<br />
<th scope="col"><abbr title="Terça-feira">Ter</abbr></th><br />
<th scope="col"><abbr title="Quarta-feira">Qua</abbr></th><br />
<th scope="col"><abbr title="Quinta-feira">Qui</abbr></th><br />
<th scope="col"><abbr title="Sexta-feira">Sex</abbr></th><br />
<th scope="col"><abbr title="Sábado">Sáb</abbr></th><br />
</tr><tr><td class="dayblank">&nbsp;</td><br />
<td class="dayblank">&nbsp;</td><br />
<td class="dayblank">&nbsp;</td><br />
<td class="dayblank">&nbsp;</td><br />
<td class="day">1</td><br />
<td class="day">2</td><br />
<br />
<td class="weekend day">3</td><br />
</tr><tr><td class="weekend day">4</td><br />
<td class="day">5</td><br />
<td class="day">6</td><br />
<td class="day">7</td><br />
<td class="day">8</td><br />
<td class="day">9</td><br />
<td class="weekend day">10</td><br />
</tr><tr><td class="weekend day">11</td><br />
<br />
<td class="day">12</td><br />
<td class="day">13</td><br />
<td class="day">14</td><br />
<td class="day">15</td><br />
<td class="day">16</td><br />
<td class="weekend day">17</td><br />
</tr><tr><td class="weekend day">18</td><br />
<td class="day today eventnone"><span class="accesshide " >Hoje segunda, 19 setembro </span><a href="#" onmouseover="return overlib('Nenhum evento', CAPTION, 'Hoje segunda, 19 setembro');" onmouseout="return nd();">19</a></td><br />
<br />
<td class="day">20</td><br />
<td class="day">21</td><br />
<td class="day">22</td><br />
<td class="day">23</td><br />
<td class="weekend day">24</td><br />
</tr><tr><td class="weekend day">25</td><br />
<td class="day">26</td><br />
<td class="day">27</td><br />
<td class="day">28</td><br />
<br />
<td class="day">29</td><br />
<td class="day">30</td><br />
<td class="dayblank">&nbsp;</td></tr></table></div></div><script type="text/javascript"><br />
//<![CDATA[<br />
elementCookieHide("inst4","Mostrar o bloco Calendário","Esconder o bloco Calendário");<br />
//]]><br />
</script><span id="sb-4" class="skip-block-to"></span></div></td><br />
</tr><br />
</table><br />
<br />
</div><div id="footer"><hr /><p class="helplink"></p><div class="logininfo">Você ainda não se identificou (<a href="http://nte-coxim.freewebclass.com/login/index.php">Acesso</a>)</div><div class="sitelink"><a title="Moodle" href="http://moodle.org/"><img style="width:100px;height:30px" src="pix/moodlelogo.gif" alt="moodlelogo" /></a></div></div><br />
</div><br />
<br />
</body><br />
</html><br />
<br />
==Downloading previous releases of Moodle==<br />
It is possible to download previous versions of Moodle that are not found on the [http://download.moodle.org Standard Moodle Download page]. There are zip and tgz compressed located at <nowiki>http://download.moodle.org/stable[version_number]</nowiki> (see links below). <br />
<br />
{| style="width:75%; height:75px" border="0"<br />
|- <br />
| 2.0 Versions || [http://download.moodle.org/stable19 1.9 Versions] || [http://download.moodle.org/stable18 1.8 Versions] <br />
|- <br />
|[http://download.moodle.org/stable17 1.7 Versions] || [http://download.moodle.org/stable16 1.6 Versions] || [http://download.moodle.org/stable15/ 1.5 Versions] <br />
|-<br />
| [http://download.moodle.org/stable14 1.4 Versions] || [http://download.moodle.org/stable13 1.3 Versions] || <br />
|}<br />
<br />
You can download previous releases by using wget, lynx or curl with this URL:<br />
<nowiki>http://download.moodle.org/stable[version_number]</nowiki>. <br />
:For example: to download Moodle version 1.5, use <nowiki>http://download.moodle.org/stable15</nowiki>. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.<br />
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:<br />
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki><br />
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac pacakges], use either of these URLs (depending on whether you need the Intel or PPC package):<br />
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki><br />
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki><br />
* '''Using CVS''': You can also use CVS to download older releases and incremental releases of the Moodle generic packages, e.g. Moodle 1.5.4 - see the [[CVS_for_Administrators | CVS documentation]].<br />
<br />
[[#top|Top]]<br />
<br />
== How to enable and check PHP error logs==<br />
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[PHP error logs]].<br />
<br />
==Email copies are not being sent from my forums==<br />
<br />
You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on.<br />
<br />
Basically, you need to set up a process to regularly call the script <code><nowiki>http://yoursite/admin/cron.php</nowiki></code>. Please refer to the [[Cron|cron instructions]].<br />
<br />
Tips:<br />
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...<br />
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page<br />
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.<br />
<br />
[[#top|Top]]<br />
<br />
==I can't log in - I just stay stuck on the login screen==<br />
<br />
This may also apply if you are seeing “Your session has timed out. Please login again” and cannot log in.<br />
<br />
The following are possible causes and actions you can take (in no particular order):<br />
<br />
* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.<br />
* Sessions may not be configured properly on the server. You can test this by calling the script <nowiki>http://yourserver/moodle/lib/session-test.php</nowiki>.<br />
* If your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in. <br />
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.<br />
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].<br />
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)<br />
* Try deleting cookies on your computer and/or try another browser or another client computer<br />
* In Site Administration > Server > Session handling, try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser. <br />
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This feature was optional since Moodle 1.6 but has been applied by default since 1.9.7. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values. <br />
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?<br />
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations. <br />
* You are using the correct username and password, yes?<br />
<br />
If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it see [[Administration FAQ]]<br />
<br />
[[#top|Top]]<br />
<br />
==I log in but the login link doesn't change. I am logged in and can navigate freely.==<br />
<br />
Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.<br />
<br />
[[#top|Top]]<br />
==Uploaded files give "File not found"==<br />
<br />
For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.<br />
<br />
Your web server needs to be configured to allow the part of the URL after a script name to be passed directly to the script. This is usually enabled in Apache 1, but is usually disabled by default in Apache 2. To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory (see [[Installing Moodle]] for more details):<br />
<br />
'''AcceptPathInfo''' on<br />
<br />
Note, this will ONLY work for Apache versions 2.x.<br />
<br />
For IIS you need to configure URL rewriting. This feature is not available in IIS 6 so you need to install a 3rd party IIS extension - see http://msdn.microsoft.com/en-us/library/ms972974.aspx. <br />
<br />
IIS 7 now comes with the new URL Rewrite Module so a 3rd part extension is no longer required if you are running IIS 7. See http://learn.iis.net/page.aspx/734/url-rewrite-module for more details.<br />
<br />
Once you've got URL rewriting working the recommended rewriting rule is:<br />
<br />
'''RewriteRule''' ^([^\?]+?\.php)(\/.+)$ $1\?file=$2 [QSA]<br />
<br />
In theory you could try to use path info on IIS too, but it is not reliable, especially when using unicode file names.<br />
<br />
If you are unable to configure your server properly then you can switch Moodle to use an alternative method. The major disadvantages is that you will not be able to use SCORM packages at all and some Adobe Flash and Java applets will not work either.<br />
<br />
To use this alternative method, you should change the ''slasharguments'' variable. For moodle versions < 1.7, this is located in the Operating System section of ''Administration > Configuration > [[admin/config|Variables]]''. In later versions, this option is located in ''Site Administration > Server > HTTP''. You should now be able to access your uploaded files.<br />
<br />
'''See also''':<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=145422 Troubleshooting Guide - 404 Errors] forum discussion.<br />
<br />
[[#top|Top]]<br />
<br />
==Why are all my pages blank?==<br />
<br />
Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (Note some operating systems use single slashes instead of double slashes shown here)<br />
<br />
<code php><br />
$CFG->dirroot = "d:\\inetpub\\sites\\www.yoursite.com\\web\\moodle";<br />
</code><br />
<br />
Another reason might be that PHP has not been configured to support MySQL. This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].<br />
<br />
To determine if MySQL support is your problem, insert this as the second line in your ''config.php'' file<br />
<br />
<code php><br />
phpinfo();<br />
</code><br />
<br />
then reload the web page. Examine the output closely to see if MySQL is supported. If not, look for a package you are missing.<br />
<br />
[[#top|Top]]<br />
<br />
== Why is a particular page blank or incomplete? ==<br />
<br />
*'''Check your web server log files!!''' <br />
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.<br />
<br />
*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".<br />
<br />
*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.<br />
<br />
*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.<br />
<br />
'''See also''':<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion<br />
<br />
==Installation hangs when setting-up database tables==<br />
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there. <br />
<br />
See [[Unexpected installation halts]] for more about solutions that involve:<br />
*Checking for MySQL limits<br />
*Checking the .htaccess files <br />
*Code customizations issues<br />
*Checking memory limit <br />
*Upgrade incrementally<br />
*Fix fopen function<br />
<br />
[[#top|Top]]<br />
<br />
==Why can't I upload a new image into my profile?==<br />
<br />
If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:<br />
*The permissions associated with the role you are using are preventing you from changing your profile picture.<br />
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > [[PHP info]]'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.<br />
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]<br />
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.<br />
<br />
If Moodle thinks GD is not installed, then you will need to '''install the GD library'''. <br />
*On Unix you may need to re-compile PHP with arguments something like this:<br />
<br />
./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd <br />
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf <br />
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars <br />
--enable-versioning --with-zlib<br />
<br />
* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:<br />
extension=php_gd2.dll<br />
<br />
:Windows users should see the [[Installing AMP|installation instructions]] for further help. <br />
<br />
3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.<br />
<br />
'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.<br />
<br />
== Why doesn't my Moodle site display the time and date correctly? ==<br />
<br />
Each language requires a specific language code (called a '''locale''' code) to allow dates to be displayed correctly. The language packs contain default standard codes, but sometimes these don't work on Windows servers.<br />
<br />
You can find the correct locale codes for Windows on these two pages: [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_language_strings.asp Language codes] and [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_country_strings.asp Country/region] codes (e.g. "esp_esp" for spanish)<br />
<br />
These new locale codes can be entered on the Administration >> Configuration >> [[admin/config|Variables]] page, where they override the ones in the currently chosen language pack.<br />
[[#top|Top]]<br />
== How do I uninstall Moodle?==<br />
<br />
'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:<br />
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):<br />
<pre>sql>DROP DATABASE moodle;</pre><br />
:In the above example replace 'moodle' with the name of the moodle database you created when installing.<br />
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.<br />
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.<br />
<br />
'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:<br />
*Open cmd.exe and navigate to this directory within your installation directory:<br />
<pre>server/mysql/bin</pre><br />
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):<br />
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre><br />
*Enter your database password at the prompt (the default is "" [blank]).<br />
*Enter "y" to confirm the database drop.<br />
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.<br />
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.<br />
<br />
==Migrating Moodle to a new site or server==<br />
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the admin/replace.php script, your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.<br />
<br />
[[#top|Top]]<br />
==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==<br />
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:<br />
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php). <br />
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.<br />
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].<br />
<br />
[[#top|Top]]<br />
==Maximum upload file size - how to change it?==<br />
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].<br />
<br />
If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server. <br />
<br />
For more help see:<br />
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]<br />
*[[Installing_Moodle#Recheck_PHP_settings]]<br />
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]<br />
*[[Site_policies#Maximum_uploaded_file_size]]<br />
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650<br />
<br />
[[#top|Top]]<br />
<br />
==How do I install Moodle on Windows Vista?==<br />
<br />
See [[Installing Moodle on Windows Vista]].<br />
<br />
==Moodle claims PHP float handling is not compatible==<br />
<br />
The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".<br />
<br />
[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.<br />
<br />
You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.<br />
<br />
Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding <br />
ini_set('precision', 14);<br />
to your config.php file, and report your success in MDL-18253.<br />
<br />
==When upgrading Moodle claims my database is not UTF8 when I'm sure it is==<br />
<br />
The symptom is that you are upgrading a post-1.6 Moodle to a newer version. The Environment check tells you that your database is not UTF8 and refuses to upgrade. <br />
<br />
The database may not have it's character encoding set quite correctly. You can safely try this command on the database<br />
<br />
ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;<br />
<br />
(Change 'moodle' for the name of your database). You need to copy this into your MySQL client program that comes packaged with it. <br />
<br />
Alternatively, you maybe adding a new clean install Moodle version to an existing web server and the UTF8 check error will not allow you to proceed. Use [[phpMyAdmin]] to help you. This web client is available as a plugin for Moodle or through your web hosting control panel. Using this program, create an empty database (for example moodle199) and make sure "MySQL connection collation" is a utf8 entry, such as utf8_general_ci. Go back to the Moodle installation screen with the check error, hit the previous button on the bottom and make sure the databae has the same name as your new empty database (for example moodle199). <br />
<br />
If your Moodle site is version 1.5 or older then it's telling the truth. <br />
<br />
[[#top|Top]]<br />
<br />
== How do I run multiple instances of Moodle without duplicating base code? ==<br />
<br />
See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].<br />
<br />
== What is FreeTDS and how can I use it in my installation? ==<br />
[[FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.<br />
<br />
== How do I install a plugin? ==<br />
<br />
Please see [[Installing contributed modules or plugins]].<br />
<br />
== See also ==<br />
<br />
* [[Installing Moodle]]<br />
* [[Upgrading FAQ]]<br />
* [[Errors FAQ]]<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]<br />
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]<br />
<br />
[[Category:FAQ]]<br />
[[Category:Installation]]<br />
<br />
[[es:FAQ Instalación]]<br />
[[fr:FAQ d'installation]]<br />
[[nl:Installatie FAQ]]<br />
[[ja:インストールFAQ]]<br />
[[ru:FAQ по установке]]<br />
[[pl:Instalacja FAQ]]<br />
[[de:Installation FAQ]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Debugging&diff=89938Debugging2011-09-19T21:09:38Z<p>Vicentina: /* In config.php */</p>
<hr />
<div>{{Developer tools}}<br />
<br />
Location: ''Settings > Site administration > Development > Debugging''<br />
<br />
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. <br />
<br />
==Debugging settings==<br />
Here are the settings on the Debugging page:<br />
<br />
===Display debug messages===<br />
<br />
There is an option to choose whether to display error messages or simply record them in the server logs.<br />
<br />
===Debug email sending===<br />
<br />
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.<br />
<br />
===Performance info===<br />
<br />
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.<br />
<br />
If you add<br />
<code php><br />
define('MDL_PERF', true);<br />
define('MDL_PERFDB', true);<br />
define('MDL_PERFTOLOG', true);<br />
define('MDL_PERFTOFOOT', true);<br />
</code><br />
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!<br />
<br />
===Show origin of language strings===<br />
Helps translators.<br />
<br />
===Show validator links===<br />
Be careful, read the warning.<br />
<br />
===Show page information===<br />
To show page information printed in the page footer.<br />
<br />
==What to do if you cannot get to the admin screens==<br />
<br />
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.<br />
<br />
===Try typing the URL directly===<br />
<br />
The debug settings are at the URL <code><nowiki>http://.../admin/settings.php?section=debugging</nowiki></code> on your server. Sometimes that URL will work, even though the pages you need to go to to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.<br />
<br />
===In config.php===<br />
<br />
In moodle/config.php you can add the lines:<br />
<br />
<code php><br />
$CFG->debug = 2047; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
Or even more debugging messages:<br />
<br />
<code php><br />
$CFG->debug = 6143; <br />
$CFG->debugdisplay = 1;<br />
$CFG->cachetype = ‘internal’;<br />
</code><br />
<br />
For Moodle 2.0 the possible settings are as follows:<br />
<br />
<code php><br />
// Force a debugging mode regardless the settings in the site administration<br />
// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!<br />
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debug = 38911; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debugdisplay = true; // NOT FOR PRODUCTION SERVERS!<br />
<br />
// You can specify a comma separated list of user ids that that always see<br />
// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay<br />
// for these users only.<br />
$CFG->debugusers = '2';<br />
</code><br />
<br />
Remember to remove those lines again when you have finished diagnosing your problem.<br />
<br />
===In the database===<br />
<br />
Using a tool like phpMyAdmin, execute the following SQL commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 2047 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
To turn it back off, use the admin screens, or the commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 0 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
(If you use a different database prefix, you will need to adjust those commands accordingly.)<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=91031 Debugging Turned on to Developer Mode on 1.8.2] forum discussion including instructions on how to turn debugging off<br />
* 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...<br />
<br />
[[Category:Site administration]]<br />
<br />
[[fr:Débogage]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Debugging&diff=89935Debugging2011-09-19T20:52:19Z<p>Vicentina: /* Debug messages */</p>
<hr />
<div>{{Developer tools}}<br />
<br />
Location: ''Settings > Site administration > Development > Debugging''<br />
<br />
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. <br />
<br />
==Debugging settings==<br />
Here are the settings on the Debugging page:<br />
<br />
===Display debug messages===<br />
<br />
There is an option to choose whether to display error messages or simply record them in the server logs.<br />
<br />
===Debug email sending===<br />
<br />
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.<br />
<br />
===Performance info===<br />
<br />
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.<br />
<br />
If you add<br />
<code php><br />
define('MDL_PERF', true);<br />
define('MDL_PERFDB', true);<br />
define('MDL_PERFTOLOG', true);<br />
define('MDL_PERFTOFOOT', true);<br />
</code><br />
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!<br />
<br />
===Show origin of language strings===<br />
Helps translators.<br />
<br />
===Show validator links===<br />
Be careful, read the warning.<br />
<br />
===Show page information===<br />
To show page information printed in the page footer.<br />
<br />
==What to do if you cannot get to the admin screens==<br />
<br />
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.<br />
<br />
===Try typing the URL directly===<br />
<br />
The debug settings are at the URL <code><nowiki>http://.../admin/settings.php?section=debugging</nowiki></code> on your server. Sometimes that URL will work, even though the pages you need to go to to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.<br />
<br />
===In config.php===<br />
<br />
In moodle/config.php you can add the lines:<br />
<br />
<code php><br />
$CFG->debug = 2047; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
Or even more debugging messages:<br />
<br />
<code php><br />
$CFG->debug = 6143; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
For Moodle 2.0 the possible settings are as follows:<br />
<br />
<code php><br />
// Force a debugging mode regardless the settings in the site administration<br />
// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!<br />
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debug = 38911; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debugdisplay = true; // NOT FOR PRODUCTION SERVERS!<br />
<br />
// You can specify a comma separated list of user ids that that always see<br />
// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay<br />
// for these users only.<br />
$CFG->debugusers = '2';<br />
</code><br />
<br />
Remember to remove those lines again when you have finished diagnosing your problem.<br />
<br />
===In the database===<br />
<br />
Using a tool like phpMyAdmin, execute the following SQL commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 2047 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
To turn it back off, use the admin screens, or the commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 0 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
(If you use a different database prefix, you will need to adjust those commands accordingly.)<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=91031 Debugging Turned on to Developer Mode on 1.8.2] forum discussion including instructions on how to turn debugging off<br />
* 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...<br />
<br />
[[Category:Site administration]]<br />
<br />
[[fr:Débogage]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Configuration_file&diff=89932Configuration file2011-09-19T20:19:29Z<p>Vicentina: /* The config-dist.php file */</p>
<hr />
<div>The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br />
<br />
<br />
==Sample config.php file==<br />
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. Here is a sample config.php file to work from.<br />
<br />
'''WARNING''': You may want to edit the config.php file directly if, for example, you change you database password or change servers completely. If you do so, be very careful that there are no spaces or line breaks after the final "?>" in the file. If there are such spaces, you may get blank pages.<br />
<br />
<pre><?php /// Moodle Configuration File <br />
<br />
unset($CFG);<br />
<br />
$CFG->dbtype = 'mysql';<br />
$CFG->dbhost = 'localhost';<br />
$CFG->dbname = 'moodle17';<br />
$CFG->dbuser = 'moodleuser';<br />
$CFG->dbpass = 'xxxxxx';<br />
$CFG->dbpersist = false;<br />
$CFG->prefix = 'mdl_';<br />
<br />
$CFG->wwwroot = 'http://www.mymoodle.com/moodle';<br />
$CFG->dirroot = '/var/www/moodle';<br />
$CFG->dataroot = '/var/moodledata';<br />
$CFG->admin = 'admin';<br />
<br />
$CFG->directorypermissions = 00777; // try 02777 on a server in Safe Mode<br />
<br />
$CFG->unicodedb = true; // Database is utf8<br />
<br />
require_once("$CFG->dirroot/lib/setup.php");<br />
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br />
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br />
?></pre><br />
<br />
==Enabling password salting==<br />
<br />
See [[Password salting]].<br />
<br />
==Including passwords in backups==<br />
<br />
Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br />
<br />
If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br />
<br />
$CFG->includeuserpasswordsinbackups<br />
<br />
==Changing default block layout for new courses==<br />
<br />
See [[Block layout]].<br />
<br />
==Changing default theme directory location==<br />
The location of theme directorys may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.<br />
<br />
For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br />
<pre><br />
$CFG->wwwroot = 'http://my.moodle.site.edu';<br />
$CFG->dirroot = '/var/www/my.moodle.site.edu/public_html';<br />
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';<br />
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';<br />
</pre><br />
<br />
==The config-dist.php file==<br />
<br />
The config-dist.php file http://cvs.moodle.org/moodle/config-dist.php?view=markup is the template file. It contains the usual settings of a config.php file, with lots of additional settings that don't currently have a UI for them. To use these settings you have to add them to the configuration file.<br />
$CFG->cachetype = ‘internal’;<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br />
<br />
[[Category: Administrator]]<br />
<br />
[[de:Konfigurationsdatei]]<br />
[[fr:Fichier de configuration]]<br />
[[ja:設定ファイル]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Debugging&diff=89931Debugging2011-09-19T19:57:25Z<p>Vicentina: /* Debug messages */</p>
<hr />
<div>{{Developer tools}}<br />
<br />
Location: ''Settings > Site administration > Development > Debugging''<br />
<br />
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. <br />
<br />
==Debugging settings==<br />
Here are the settings on the Debugging page:<br />
<br />
===Debug messages===<br />
The default is none, your choices are:<br />
<br />
;'MDL_PERF', true : Do not show any errors or warnings (Default) <br />
;'MDL_PERFDB', true : Show all reasonable PHP debug messages<br />
;'MDL_PERFTOLOG', true : Show only fatal errors<br />
;'MDL_PERFTOFOOT', true : Show warnings, errors and notices<br />
;NONE : extra Moodle debug messages for developers<br />
<br />
There is rarely any advantage in going to Developer level, unless you are a developer, in which case it is strongly recommended.<br />
<br />
Once you have got the error message, and copied and pasted it somewhere. HIGHLY RECOMMENDED to turn Debug back to NONE. Debug messages can give clues to a hacker as to the setup of your site.<br />
<br />
===Display debug messages===<br />
<br />
There is an option to choose whether to display error messages or simply record them in the server logs.<br />
<br />
===Debug email sending===<br />
<br />
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.<br />
<br />
===Performance info===<br />
<br />
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.<br />
<br />
If you add<br />
<code php><br />
define('MDL_PERF', true);<br />
define('MDL_PERFDB', true);<br />
define('MDL_PERFTOLOG', true);<br />
define('MDL_PERFTOFOOT', true);<br />
</code><br />
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!<br />
<br />
===Show origin of language strings===<br />
Helps translators.<br />
<br />
===Show validator links===<br />
Be careful, read the warning.<br />
<br />
===Show page information===<br />
To show page information printed in the page footer.<br />
<br />
==What to do if you cannot get to the admin screens==<br />
<br />
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.<br />
<br />
===Try typing the URL directly===<br />
<br />
The debug settings are at the URL <code><nowiki>http://.../admin/settings.php?section=debugging</nowiki></code> on your server. Sometimes that URL will work, even though the pages you need to go to to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.<br />
<br />
===In config.php===<br />
<br />
In moodle/config.php you can add the lines:<br />
<br />
<code php><br />
$CFG->debug = 2047; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
Or even more debugging messages:<br />
<br />
<code php><br />
$CFG->debug = 6143; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
For Moodle 2.0 the possible settings are as follows:<br />
<br />
<code php><br />
// Force a debugging mode regardless the settings in the site administration<br />
// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!<br />
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debug = 38911; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debugdisplay = true; // NOT FOR PRODUCTION SERVERS!<br />
<br />
// You can specify a comma separated list of user ids that that always see<br />
// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay<br />
// for these users only.<br />
$CFG->debugusers = '2';<br />
</code><br />
<br />
Remember to remove those lines again when you have finished diagnosing your problem.<br />
<br />
===In the database===<br />
<br />
Using a tool like phpMyAdmin, execute the following SQL commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 2047 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
To turn it back off, use the admin screens, or the commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 0 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
(If you use a different database prefix, you will need to adjust those commands accordingly.)<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=91031 Debugging Turned on to Developer Mode on 1.8.2] forum discussion including instructions on how to turn debugging off<br />
* 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...<br />
<br />
[[Category:Site administration]]<br />
<br />
[[fr:Débogage]]</div>Vicentinahttps://docs.moodle.org/310/en/index.php?title=Debugging&diff=89930Debugging2011-09-19T19:50:40Z<p>Vicentina: /* Debug messages */</p>
<hr />
<div>{{Developer tools}}<br />
<br />
Location: ''Settings > Site administration > Development > Debugging''<br />
<br />
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. <br />
<br />
==Debugging settings==<br />
Here are the settings on the Debugging page:<br />
<br />
===Debug messages===<br />
The default is none, your choices are:<br />
<br />
;NONE : Do not show any errors or warnings (Default) <br />
;NONE : Show all reasonable PHP debug messages<br />
;NONE : Show only fatal errors<br />
;NONE : Show warnings, errors and notices<br />
;NONE : extra Moodle debug messages for developers<br />
<br />
There is rarely any advantage in going to Developer level, unless you are a developer, in which case it is strongly recommended.<br />
<br />
Once you have got the error message, and copied and pasted it somewhere. HIGHLY RECOMMENDED to turn Debug back to NONE. Debug messages can give clues to a hacker as to the setup of your site.<br />
<br />
===Display debug messages===<br />
<br />
There is an option to choose whether to display error messages or simply record them in the server logs.<br />
<br />
===Debug email sending===<br />
<br />
Determines whether or not to enable verbose debug information during sending of email messages to SMTP server.<br />
<br />
===Performance info===<br />
<br />
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.<br />
<br />
If you add<br />
<code php><br />
define('MDL_PERF', true);<br />
define('MDL_PERFDB', true);<br />
define('MDL_PERFTOLOG', true);<br />
define('MDL_PERFTOFOOT', true);<br />
</code><br />
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!<br />
<br />
===Show origin of language strings===<br />
Helps translators.<br />
<br />
===Show validator links===<br />
Be careful, read the warning.<br />
<br />
===Show page information===<br />
To show page information printed in the page footer.<br />
<br />
==What to do if you cannot get to the admin screens==<br />
<br />
If the error is stopping you even getting to the admin screens to turn on debugging, then you can set the debugging setting manually.<br />
<br />
===Try typing the URL directly===<br />
<br />
The debug settings are at the URL <code><nowiki>http://.../admin/settings.php?section=debugging</nowiki></code> on your server. Sometimes that URL will work, even though the pages you need to go to to get there (for example the site front page) do not. So it is worth trying to enter that URL directly.<br />
<br />
===In config.php===<br />
<br />
In moodle/config.php you can add the lines:<br />
<br />
<code php><br />
$CFG->debug = 2047; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
Or even more debugging messages:<br />
<br />
<code php><br />
$CFG->debug = 6143; <br />
$CFG->debugdisplay = 1;<br />
</code><br />
<br />
For Moodle 2.0 the possible settings are as follows:<br />
<br />
<code php><br />
// Force a debugging mode regardless the settings in the site administration<br />
// @error_reporting(1023); // NOT FOR PRODUCTION SERVERS!<br />
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debug = 38911; // DEBUG_DEVELOPER // NOT FOR PRODUCTION SERVERS!<br />
$CFG->debugdisplay = true; // NOT FOR PRODUCTION SERVERS!<br />
<br />
// You can specify a comma separated list of user ids that that always see<br />
// debug messages, this overrides the debug flag in $CFG->debug and $CFG->debugdisplay<br />
// for these users only.<br />
$CFG->debugusers = '2';<br />
</code><br />
<br />
Remember to remove those lines again when you have finished diagnosing your problem.<br />
<br />
===In the database===<br />
<br />
Using a tool like phpMyAdmin, execute the following SQL commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 2047 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 1 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
To turn it back off, use the admin screens, or the commands:<br />
<br />
<code sql><br />
UPDATE mdl_config SET value = 0 WHERE name = 'debug';<br />
UPDATE mdl_config SET value = 0 WHERE name = 'debugdisplay';<br />
</code><br />
<br />
(If you use a different database prefix, you will need to adjust those commands accordingly.)<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=91031 Debugging Turned on to Developer Mode on 1.8.2] forum discussion including instructions on how to turn debugging off<br />
* 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...<br />
<br />
[[Category:Site administration]]<br />
<br />
[[fr:Débogage]]</div>Vicentina