Developer tools: Difference between revisions

Latest revision as of 04:17, 6 March 2014

Developers of Moodle code have some special tools included in the Moodle package to assist them. Most of the tools should ONLY be used on test sites (not production sites). However there are a couple which may be used by a cautious administrator.

Debugging

Administration > Site administration > Development > Debugging

At certain times a site administrator will need to see more and/or a more complete error message. The default is to show NONE. These messages can also 1) be very confusing to teachers and students when they suddenly appear and 2) can reveal things about your Moodle and web server that should not be common knowledge. Thus use with care and for short periods of time. See Debugging for details.

Purge all caches

Administration > Site administration > Development > Purge all caches

Moodle can cache themes, language strings, filters and other bits of information that have been calculated and stored by the web browser. This link forces all user web browsers to refresh their screens of any information that Moodle has cached. Several modules that use cache have settings which will turn off caching for that module. Eliminating or purging caches slows performance.

Experimental features

Moodle includes a few experimental features which a cautious administrator may consider enabling. See Experimental settings for details.

@@ Line 1: / Line 1: @@
-{{Developer tools}}
+{{Managing a Moodle site}}
-<p class="note">'''Please refer to [[Page_notes#Developer tools|these notes]] before editing this page.'''</p>
+Developers of Moodle code have some special tools included in the Moodle package to assist them.  Most of the tools should ONLY be used on test sites (not production sites). However there are a couple which may be used by a cautious administrator.
-Settings > Site administration > Development
-Developers of Moodle code have some special links that are built into the standard Moodle package to assist them.  Most are of no interest to the average site administrator.
+===Debugging===
-These include:
+''Administration > Site administration > Development > Debugging''
-*[[Debugging]]
-*Web service test client
-*Purge all caches
-*Unit tests
-*Functional DB tests
-==Potential useful to non-developer==
+At certain times a site administrator will need to see more and/or a more complete error message.  The default is to show NONE. These messages can also 1) be very confusing to teachers and students when they suddenly appear and 2) can reveal things about your Moodle and web server that should not be common knowledge.  Thus use with care and for short periods of time. See [[Debugging]] for details.
-Most of the Development links should NOT be used by the average site administrator.   However, there are a couple of settings that might be useful for a cautious site administrator.
-===Debugging===
+===Purge all caches===
-At certain times a site administrator will need to see more and/or a more complete error message.  The default is to show NONE. These messages can also 1) be very confusing to teachers and students when they suddenly appear and 2) can reveal things about your Moodle and web server that should not be common knowledge.  Thus use with care and for short periods of time.
+''Administration > Site administration > Development > Purge all caches''
+Moodle can cache themes, language strings, filters and other bits of information that have been calculated and stored by the web browser.  This link forces all user web browsers to refresh their screens of '''any''' information that Moodle has cached.  Several modules that use cache have settings which will turn off caching for that module.  Eliminating or purging caches slows performance.
+==Experimental features==
+Moodle includes a few experimental features which a cautious administrator may consider enabling. See [[Experimental settings]] for details.
+==See also==
+*[http://youtu.be/HlVOcqeUHBs Moodle Administration Development settings]  MoodleBites video on YouTube
-===Purge all caches===
+[[es:Herramientas para desarrolladores]]
-One of the exceptions might be the "Purge all caches" link for those setting up a site for the first time.   Moodle can cache themes, language strings, filters and other bits of information that have been calculated and stored by the web browser.  This link forces all user web browsers to refresh their screens of '''any''' information that Moodle has cached.  Several modules that use cache have settings which will turn off caching for that module.  Eliminating or purging caches slows performance.

Documentation

Developer tools: Difference between revisions

Latest revision as of 04:17, 6 March 2014

Contents

Debugging

Purge all caches

Experimental features

See also