https://docs.moodle.org/25/en/api.php?action=feedcontributions&feedformat=atom&user=Dougiamas 2026-05-16T17:58:57Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/25/en/index.php?title=Caching&diff=106383 2013-08-20T05:51:04Z

<p>Dougiamas: /* Performance advise for Moodle 2.5 with load-balanced web servers */</p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> (Note to doc editors, we need contributions below:)<br /> <br /> ===Language string cache===<br /> <br /> This is a cache of calculated strings which are originally pulled from language files. <br /> <br /> In Moodle 2.5, this<br /> * expects shared cache<br /> * if not shared, must be manually purged after any language string change such as editing of local lang packs, updating of lang packs during upgrade, installation or uninstallation of languages<br /> <br /> In Moodle 2.6 and later, this<br /> * works fine with local or shared node caches, you don't have to do anything special.<br /> <br /> ===Database meta information===<br /> <br /> This is a cache of database structure information.<br /> <br /> * requires shared cache<br /> * if not shared, caches need to be invalidated after any DB structure change including creation of temporary tables<br /> <br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> <br /> This is a cache of texts (forum posts, resources, intros etc etc) from all parts of Moodle, after it has been cleaned of possible malicious data.<br /> <br /> In Moodle 2.5,<br /> * this expects a shared cache<br /> * if not shared, must be manually purged after every upgrade or change of $CFG-&gt;allowobjectembed setting<br /> <br /> In Moodle 2.6 and later, <br /> * this works fine with local or shared node caches, you don't have to do anything special.<br /> <br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> * What is cached:- Record entries from 'event_subscriptions' table, representing various calendar subscriptions.<br /> * When the cache is updated:- When a calendar subscription is updated or deleted.<br /> * How often it is hit:- Everytime a calendar subscription detail is fetched.<br /> * When should the cache be purged completely:- This should not be needed.<br /> <br /> ===YUI Module definitions===<br /> <br /> ===Plugin types===<br /> <br /> * expects shared cache<br /> * must be purged after every core upgrade or plugin installation, upgrade or uninstallation<br /> <br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Other performance advice for load-balanced web servers==<br /> <br /> # In Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcached instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html<br /> # In Moodle 2.6 onwards make sure you set $CFG-&gt;localcachedir to some local directory in config.php (for each node). This will speed up some of the disk caching that happens outside of MUC, such as themes, javascript, libraries etc.<br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> * [https://moodle.org/mod/forum/discuss.php?d=222250 Putting cachedir on local disks in cluster]<br /> * [https://moodle.org/mod/forum/discuss.php?d=232122 moodle cachestore_file]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=106382 2013-08-20T05:45:11Z

<p>Dougiamas: /* HTML Purifier - cleaned content */</p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> (Note to doc editors, we need contributions below:)<br /> <br /> ===Language string cache===<br /> <br /> This is a cache of calculated strings which are originally pulled from language files. <br /> <br /> In Moodle 2.5, this<br /> * expects shared cache<br /> * if not shared, must be manually purged after any language string change such as editing of local lang packs, updating of lang packs during upgrade, installation or uninstallation of languages<br /> <br /> In Moodle 2.6 and later, this<br /> * works fine with local or shared node caches, you don't have to do anything special.<br /> <br /> ===Database meta information===<br /> <br /> This is a cache of database structure information.<br /> <br /> * requires shared cache<br /> * if not shared, caches need to be invalidated after any DB structure change including creation of temporary tables<br /> <br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> <br /> This is a cache of texts (forum posts, resources, intros etc etc) from all parts of Moodle, after it has been cleaned of possible malicious data.<br /> <br /> In Moodle 2.5,<br /> * this expects a shared cache<br /> * if not shared, must be manually purged after every upgrade or change of $CFG-&gt;allowobjectembed setting<br /> <br /> In Moodle 2.6 and later, <br /> * this works fine with local or shared node caches, you don't have to do anything special.<br /> <br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> * What is cached:- Record entries from 'event_subscriptions' table, representing various calendar subscriptions.<br /> * When the cache is updated:- When a calendar subscription is updated or deleted.<br /> * How often it is hit:- Everytime a calendar subscription detail is fetched.<br /> * When should the cache be purged completely:- This should not be needed.<br /> <br /> ===YUI Module definitions===<br /> <br /> ===Plugin types===<br /> <br /> * expects shared cache<br /> * must be purged after every core upgrade or plugin installation, upgrade or uninstallation<br /> <br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Performance advise for Moodle 2.5 with load-balanced web servers==<br /> <br /> Performance advice: if you are running Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcache instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html. <br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> * [https://moodle.org/mod/forum/discuss.php?d=222250 Putting cachedir on local disks in cluster]<br /> * [https://moodle.org/mod/forum/discuss.php?d=232122 moodle cachestore_file]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=106381 2013-08-20T05:44:36Z

<p>Dougiamas: /* HTML Purifier - cleaned content */</p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> (Note to doc editors, we need contributions below:)<br /> <br /> ===Language string cache===<br /> <br /> This is a cache of calculated strings which are originally pulled from language files. <br /> <br /> In Moodle 2.5, this<br /> * expects shared cache<br /> * if not shared, must be manually purged after any language string change such as editing of local lang packs, updating of lang packs during upgrade, installation or uninstallation of languages<br /> <br /> In Moodle 2.6 and later, this<br /> * works fine with local or shared node caches, you don't have to do anything special.<br /> <br /> ===Database meta information===<br /> <br /> This is a cache of database structure information.<br /> <br /> * requires shared cache<br /> * if not shared, caches need to be invalidated after any DB structure change including creation of temporary tables<br /> <br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> <br /> This is a cache of texts (forum posts, resources, intros etc etc) from all parts of Moodle, after it has been cleaned of possible malicious data.<br /> <br /> In Moodle 2.5, this<br /> * expects shared cache<br /> * if not shared, must be manually purged after every upgrade or change of $CFG-&gt;allowobjectembed setting<br /> <br /> In Moodle 2.6 and later, this<br /> * works fine with local or shared node caches, you don't have to do anything special.<br /> <br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> * What is cached:- Record entries from 'event_subscriptions' table, representing various calendar subscriptions.<br /> * When the cache is updated:- When a calendar subscription is updated or deleted.<br /> * How often it is hit:- Everytime a calendar subscription detail is fetched.<br /> * When should the cache be purged completely:- This should not be needed.<br /> <br /> ===YUI Module definitions===<br /> <br /> ===Plugin types===<br /> <br /> * expects shared cache<br /> * must be purged after every core upgrade or plugin installation, upgrade or uninstallation<br /> <br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Performance advise for Moodle 2.5 with load-balanced web servers==<br /> <br /> Performance advice: if you are running Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcache instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html. <br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> * [https://moodle.org/mod/forum/discuss.php?d=222250 Putting cachedir on local disks in cluster]<br /> * [https://moodle.org/mod/forum/discuss.php?d=232122 moodle cachestore_file]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=106380 2013-08-20T05:43:26Z

<p>Dougiamas: /* Language string cache */</p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> (Note to doc editors, we need contributions below:)<br /> <br /> ===Language string cache===<br /> <br /> This is a cache of calculated strings which are originally pulled from language files. <br /> <br /> In Moodle 2.5, this<br /> * expects shared cache<br /> * if not shared, must be manually purged after any language string change such as editing of local lang packs, updating of lang packs during upgrade, installation or uninstallation of languages<br /> <br /> In Moodle 2.6 and later, this<br /> * works fine with local or shared node caches, you don't have to do anything special.<br /> <br /> ===Database meta information===<br /> <br /> This is a cache of database structure information.<br /> <br /> * requires shared cache<br /> * if not shared, caches need to be invalidated after any DB structure change including creation of temporary tables<br /> <br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> <br /> This is a cache of texts (forum posts, resources, intros etc etc) from all parts of Moodle, after it has been cleaned of possible malicious data.<br /> <br /> * expects a shared cache<br /> * if not shared, must be purged after every upgrade or change of $CFG-&gt;allowobjectembed setting<br /> * starting in 2.6 this will be fully compatible with local node caches<br /> <br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> * What is cached:- Record entries from 'event_subscriptions' table, representing various calendar subscriptions.<br /> * When the cache is updated:- When a calendar subscription is updated or deleted.<br /> * How often it is hit:- Everytime a calendar subscription detail is fetched.<br /> * When should the cache be purged completely:- This should not be needed.<br /> <br /> ===YUI Module definitions===<br /> <br /> ===Plugin types===<br /> <br /> * expects shared cache<br /> * must be purged after every core upgrade or plugin installation, upgrade or uninstallation<br /> <br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Performance advise for Moodle 2.5 with load-balanced web servers==<br /> <br /> Performance advice: if you are running Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcache instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html. <br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> * [https://moodle.org/mod/forum/discuss.php?d=222250 Putting cachedir on local disks in cluster]<br /> * [https://moodle.org/mod/forum/discuss.php?d=232122 moodle cachestore_file]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=106379 2013-08-20T05:42:48Z

<p>Dougiamas: /* Language string cache */</p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> (Note to doc editors, we need contributions below:)<br /> <br /> ===Language string cache===<br /> <br /> This is a cache of calculated strings which are originally pulled from language files. <br /> <br /> In Moodle 2.5, this<br /> * expects shared cache<br /> * if not shared, must be manually purged after any language string change such as editing of local lang packs, updating of lang packs during upgrade, installation or uninstallation of languages<br /> <br /> In Moodle 2.6, this<br /> * works fine with local or shared node caches, you don't have to do anything special.<br /> <br /> ===Database meta information===<br /> <br /> This is a cache of database structure information.<br /> <br /> * requires shared cache<br /> * if not shared, caches need to be invalidated after any DB structure change including creation of temporary tables<br /> <br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> <br /> This is a cache of texts (forum posts, resources, intros etc etc) from all parts of Moodle, after it has been cleaned of possible malicious data.<br /> <br /> * expects a shared cache<br /> * if not shared, must be purged after every upgrade or change of $CFG-&gt;allowobjectembed setting<br /> * starting in 2.6 this will be fully compatible with local node caches<br /> <br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> * What is cached:- Record entries from 'event_subscriptions' table, representing various calendar subscriptions.<br /> * When the cache is updated:- When a calendar subscription is updated or deleted.<br /> * How often it is hit:- Everytime a calendar subscription detail is fetched.<br /> * When should the cache be purged completely:- This should not be needed.<br /> <br /> ===YUI Module definitions===<br /> <br /> ===Plugin types===<br /> <br /> * expects shared cache<br /> * must be purged after every core upgrade or plugin installation, upgrade or uninstallation<br /> <br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Performance advise for Moodle 2.5 with load-balanced web servers==<br /> <br /> Performance advice: if you are running Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcache instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html. <br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> * [https://moodle.org/mod/forum/discuss.php?d=222250 Putting cachedir on local disks in cluster]<br /> * [https://moodle.org/mod/forum/discuss.php?d=232122 moodle cachestore_file]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=106378 2013-08-20T05:19:20Z

<p>Dougiamas: /* Cache definition configuration */</p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> (Note to doc editors, we need contributions below:)<br /> <br /> ===Language string cache===<br /> <br /> This is a cache of calculated strings which are originally pulled from language files. <br /> <br /> * expects shared cache<br /> * if not shared, must be manually purged after any language string change such as editing of local lang packs, updating of lang packs during upgrade, installation or uninstallation of languages<br /> * starting in 2.6 this will be fully compatible with local node caches<br /> <br /> ===Database meta information===<br /> <br /> This is a cache of database structure information.<br /> <br /> * requires shared cache<br /> * if not shared, caches need to be invalidated after any DB structure change including creation of temporary tables<br /> <br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> <br /> This is a cache of texts (forum posts, resources, intros etc etc) from all parts of Moodle, after it has been cleaned of possible malicious data.<br /> <br /> * expects a shared cache<br /> * if not shared, must be purged after every upgrade or change of $CFG-&gt;allowobjectembed setting<br /> * starting in 2.6 this will be fully compatible with local node caches<br /> <br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> * What is cached:- Record entries from 'event_subscriptions' table, representing various calendar subscriptions.<br /> * When the cache is updated:- When a calendar subscription is updated or deleted.<br /> * How often it is hit:- Everytime a calendar subscription detail is fetched.<br /> * When should the cache be purged completely:- This should not be needed.<br /> <br /> ===YUI Module definitions===<br /> <br /> ===Plugin types===<br /> <br /> * expects shared cache<br /> * must be purged after every core upgrade or plugin installation, upgrade or uninstallation<br /> <br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Performance advise for Moodle 2.5 with load-balanced web servers==<br /> <br /> Performance advice: if you are running Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcache instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html. <br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> * [https://moodle.org/mod/forum/discuss.php?d=222250 Putting cachedir on local disks in cluster]<br /> * [https://moodle.org/mod/forum/discuss.php?d=232122 moodle cachestore_file]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=106312 2013-08-08T06:13:09Z

<p>Dougiamas: /* Cache definition configuration */</p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> (Note to doc editors, we need contributions below:)<br /> <br /> ===Language string cache===<br /> <br /> * What is cached:<br /> * When the cache is updated:<br /> * How often it is hit:<br /> * When should the cache be purged completely:<br /> <br /> ===Database meta information===<br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> ===YUI Module definitions===<br /> ===Plugin types===<br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Performance advise for Moodle 2.5 with load-balanced web servers==<br /> <br /> Performance advice: if you are running Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcache instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html. <br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=106311 2013-08-08T05:25:37Z

<p>Dougiamas: /* Language string cache */</p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> ===Language string cache===<br /> <br /> * What is cached:<br /> * When the cache is updated:<br /> * How often it is hit:<br /> * When should the cache be purged completely:<br /> <br /> ===Database meta information===<br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> ===YUI Module definitions===<br /> ===Plugin types===<br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Performance advise for Moodle 2.5 with load-balanced web servers==<br /> <br /> Performance advice: if you are running Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcache instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html. <br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=106310 2013-08-08T05:24:58Z

<p>Dougiamas: </p> <hr /> <div>{{Performance}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> Since Moodle 2.4, Moodle has provided a caching plugin framework to give administrators the ability to control where Moodle stores cached data. For most Moodle sites the default configuration should be sufficient and it is not necessary to change the configuration. For larger Moodle sites with multiple servers, administrators may wish to use memcached, mongodb or other systems to store cache data. The cache plugin screen provides administrators with the ability to configure what cache data is stored where. <br /> <br /> === Types of cache ===<br /> <br /> Moodle uses three types of cache to store cached data:<br /> * Request cache - The request cache is available for the duration of every page request. It is not shared between users and is used and cleared on every Moodle request.<br /> * Session cache - The session cache is available through a users session in Moodle. It is not shared between users, but persists for a single user throughout their session (i.e. from when they logon til when they log off)<br /> * Application cache - The application cache is a shared cache which is available for every request. It can be shared between users and the cached data can be kept indefinitely if required.<br /> <br /> ==== Cache types and multiple-server systems ====<br /> <br /> If you have a system with multiple front-end web servers, the application cache must be shared between the servers. In other words, you cannot use fast local storage for the application cache, but must use shared storage or some other form of shared cache such as a shared memcache.<br /> <br /> The same applies to session cache, unless you use a 'sticky sessions' mechanism to ensure that within a session, users always access the same front-end server.<br /> <br /> ===Installed cache stores===<br /> <br /> This section of the administrator screen displays cache plugins which are installed on the system. It lists what the capabilities of each plugin, what type of cache they provide and provides allows a cache store to be added to the system.<br /> <br /> ===Configured store instances===<br /> <br /> This section of the administrator screen displays cache stores which have been added to the system. It gives the ability to change the cache configuration and purge the cached data.<br /> <br /> ===Cache lock instances===<br /> <br /> Moodle supports different mechanisms for 'locking' access to the various cache stores. At present there is only one option and it is not used, so it can safely be ignored.<br /> <br /> ===Known cache definitions===<br /> <br /> Known cache definitions displays the caches which are in use by Moodle. Each item is an area of Moodle which is using caching. It gives the administrator the ability to configure an individual area of Moodle to use a different cache backend. For example, an administrator of a Moodle cluster may choose to make language string definitions be cached on a dedicated memcached server by using the memcached cache backend. See the section below for more information about configuring these.<br /> <br /> ==Cache definition configuration==<br /> <br /> Each different cache can be configured independently, allowing admins to &quot;tune&quot; their setup for particular systems. <br /> <br /> By default these caches are all set to use files, which is usually fine on a small one-server system.<br /> <br /> On a cluster, however, these defaults can cause problems because shared filesystems are slow, so in these cases we recommend you use a faster shared caching backend like memcached instead. Note that most of these caches operating under the assumption that they are shared.<br /> <br /> In some cases you can choose to use a non-shared cache like the local filesystem however in these instances you be careful to purge caches MANUALLY as part of system administration.<br /> <br /> The following reference is intended to help you understand how each caching definition works so you can tune appropriately:<br /> <br /> ===Language string cache===<br /> <br /> What is cached:<br /> When the cache is updated:<br /> How often it is hit:<br /> When should the cache be purged completely:<br /> <br /> <br /> ===Database meta information===<br /> ===Event invalidation===<br /> ===Question definitions===<br /> ===HTML Purifier - cleaned content===<br /> ===Config settings===<br /> ===Course group information===<br /> ===Calendar subscriptions===<br /> ===YUI Module definitions===<br /> ===Plugin types===<br /> ===Plugin list Application===<br /> ===Plugin info - base===<br /> ===Plugin info - activity modules===<br /> ===Plugin info - blocks===<br /> ===Plugin info - filters===<br /> ===Plugin info - repositories===<br /> ===Plugin info - portfolios===<br /> ===Course categories tree===<br /> ===Course categories lists for particular user===<br /> ===Course categories records===<br /> ===List of course contacts===<br /> ===Repositories instances data===<br /> <br /> <br /> ==Stores used when no mapping is present==<br /> <br /> This section displays the default cache stores which should be used by Moodle for each type of Moodle cache. If a mapping for a cache definition does not exist then this default store will be used instead.<br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==Performance advise for Moodle 2.5 with load-balanced web servers==<br /> <br /> Performance advice: if you are running Moodle 2.4 onwards with load-balanced web servers, don't use the default caching option that stores the data in moodledata on a shared network drive. Use memcache instead. See Tim Hunt's article on http://tjhunt.blogspot.de/2013/05/performance-testing-moodle.html. <br /> <br /> ==See also==<br /> <br /> Using Moodle forum discussions:<br /> * [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] <br /> * [https://moodle.org/mod/forum/discuss.php?d=226123 Status of MUC?]<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104891 2013-05-09T11:49:31Z

<p>Dougiamas: /* New themes suited to all screen sizes */</p> <hr /> <div>{{Main page}}<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights a few of the most interesting!<br /> <br /> Full details of the release, with technical information, can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes].<br /> <br /> (Click any screenshot below to see it enlarged)<br /> <br /> ==For teachers and students:==<br /> <br /> ===Badges===<br /> [[Badges]] are a nice way to acknowledge good work, and it's now possible for teachers to award course badges based on a variety of chosen criteria. These badges are fully compatible with [http://openbadges.org/ Mozilla Open Badges]. See the [[Badges|Badges documentation]] for more information.<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> This blog post has some interesting reflection on when badges might be most appropriate: [http://alex.halavais.net/ozbadge The Badges of Oz]<br /> <br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that non-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:showmoreshowless.png|thumb|&quot;Show more&quot; (and &quot;show less&quot; options]]<br /> |}<br /> <br /> The rich text editor is collapsed and can be expanded:<br /> <br /> {|<br /> |[[File:collapsedassignment.png|thumb|Formatting options collapsed and box is narrow]]<br /> |[[File:expandedassignment.png|thumb|Formatting options shown and box expanded]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Reports moved to the Administration block===<br /> <br /> Reports have moved and can now be seen in the newly named ''Administration'' block, (formerly ''Settings''.)<br /> <br /> {|<br /> |[[File:reportsinadmin.png|thumb|Administration block with Reports]]<br /> |}<br /> === Quickly &quot;Jump to..&quot; another section===<br /> If you're using the 'one section per page' setting, you can now move to other sections from a drop down menu:<br /> {|<br /> |[[File:jumpto25.png|thumb|The 'jump to' drop down menu returns]]<br /> |}<br /> ===Drag and drop media and text onto the course page===<br /> You can now drag an image or some text onto your course page and choose whether to display it embedded in a label or as a clickable resource. See the [[Label|Label documentation]] for more information.<br /> <br /> {|<br /> | [[File:dragdrop1.png|thumb|Drag an image onto your course page]]<br /> |[[File:dragdrop2.png|thumb|Choose &quot;add image..&quot;]]<br /> |[[File:dragdrop3.png|thumb|And here it is!]]<br /> |}<br /> <br /> {|<br /> |[[File:textdragdrop1.png|thumb|Text selected from a Word document is dragged over]]<br /> |[[File:textdragdrop2.png|thumb|Choose &quot;add a label&quot; (or page if you prefer)]]<br /> |[[File:textdragdrop3.png|thumb|And here it is!]]<br /> |}<br /> <br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Assignment enhancements===<br /> Along with neater options for choosing submission and feedback types, resubmitting options are much improved. See the [[Assignment|Assignment documentation]] for more information.<br /> <br /> {|<br /> | [[File:assignmentandfeedbackcondensed.png|thumb|Neater assignment set up screen]]<br /> | [[File:attemptsreopened.png|thumb|New settings for resubmissions]]<br /> |}<br /> <br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ===Search the list of enrolled users===<br /> A new search box makes finding users in very large courses much easier:<br /> <br /> {|<br /> | [[File:Searchenrolledusers.png|thumb|A search facility allows teachers to search for specific users.]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;'''Bootstrapbase'''&quot; that implements the basics, and a new usable theme called ''''''Clean'''''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. It also (along with ''Afterburner'') allows you to upload a logo directly from the file picker.<br /> <br /> The Bootstrap framework allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Clean theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Clean theme on smaller screen; note position of Navigation block]]<br /> | [[File:filepickerlogo.png|thumb|Add your logo from the file picker in Clean theme]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to [[Installing add-ons|install add-ons]] from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the [https://moodle.org/plugins Moodle plugins directory]:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]<br /> |}<br /> <br /> ==See also==<br /> <br /> * [[:Category:New features|Category:New features]] - list of pages documenting new features in Moodle 2.5</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104890 2013-05-09T11:47:56Z

<p>Dougiamas: </p> <hr /> <div>{{Main page}}<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights a few of the most interesting!<br /> <br /> Full details of the release, with technical information, can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes].<br /> <br /> (Click any screenshot below to see it enlarged)<br /> <br /> ==For teachers and students:==<br /> <br /> ===Badges===<br /> [[Badges]] are a nice way to acknowledge good work, and it's now possible for teachers to award course badges based on a variety of chosen criteria. These badges are fully compatible with [http://openbadges.org/ Mozilla Open Badges]. See the [[Badges|Badges documentation]] for more information.<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> This blog post has some interesting reflection on when badges might be most appropriate: [http://alex.halavais.net/ozbadge The Badges of Oz]<br /> <br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that non-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:showmoreshowless.png|thumb|&quot;Show more&quot; (and &quot;show less&quot; options]]<br /> |}<br /> <br /> The rich text editor is collapsed and can be expanded:<br /> <br /> {|<br /> |[[File:collapsedassignment.png|thumb|Formatting options collapsed and box is narrow]]<br /> |[[File:expandedassignment.png|thumb|Formatting options shown and box expanded]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Reports moved to the Administration block===<br /> <br /> Reports have moved and can now be seen in the newly named ''Administration'' block, (formerly ''Settings''.)<br /> <br /> {|<br /> |[[File:reportsinadmin.png|thumb|Administration block with Reports]]<br /> |}<br /> === Quickly &quot;Jump to..&quot; another section===<br /> If you're using the 'one section per page' setting, you can now move to other sections from a drop down menu:<br /> {|<br /> |[[File:jumpto25.png|thumb|The 'jump to' drop down menu returns]]<br /> |}<br /> ===Drag and drop media and text onto the course page===<br /> You can now drag an image or some text onto your course page and choose whether to display it embedded in a label or as a clickable resource. See the [[Label|Label documentation]] for more information.<br /> <br /> {|<br /> | [[File:dragdrop1.png|thumb|Drag an image onto your course page]]<br /> |[[File:dragdrop2.png|thumb|Choose &quot;add image..&quot;]]<br /> |[[File:dragdrop3.png|thumb|And here it is!]]<br /> |}<br /> <br /> {|<br /> |[[File:textdragdrop1.png|thumb|Text selected from a Word document is dragged over]]<br /> |[[File:textdragdrop2.png|thumb|Choose &quot;add a label&quot; (or page if you prefer)]]<br /> |[[File:textdragdrop3.png|thumb|And here it is!]]<br /> |}<br /> <br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Assignment enhancements===<br /> Along with neater options for choosing submission and feedback types, resubmitting options are much improved. See the [[Assignment|Assignment documentation]] for more information.<br /> <br /> {|<br /> | [[File:assignmentandfeedbackcondensed.png|thumb|Neater assignment set up screen]]<br /> | [[File:attemptsreopened.png|thumb|New settings for resubmissions]]<br /> |}<br /> <br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ===Search the list of enrolled users===<br /> A new search box makes finding users in very large courses much easier:<br /> <br /> {|<br /> | [[File:Searchenrolledusers.png|thumb|A search facility allows teachers to search for specific users.]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;'''Bootstrapbase'''&quot; that implements the basics, and a new usable theme called ''''''Clean'''''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. It also (along with ''Afterburner'') allows you to upload a logo directly from the file picker) <br /> <br /> Bootstrapbase allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Clean theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Clean theme on smaller screen; note position of Navigation block]]<br /> | [[File:filepickerlogo.png|thumb|Add your logo from the file picker in Clean theme]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to [[Installing add-ons|install add-ons]] from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the [https://moodle.org/plugins Moodle plugins directory]:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]<br /> |}<br /> <br /> ==See also==<br /> <br /> * [[:Category:New features|Category:New features]] - list of pages documenting new features in Moodle 2.5</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Course_completion_settings&diff=104804 2013-05-06T15:01:09Z

<p>Dougiamas: /* Completion dependencies */</p> <hr /> <div>{{Course completion}}<br /> In order to use the course completion features, it has to be enabled in the site administration settings before the course completion link will appear in the course administration menu. There are also settings which need to be reviewed in the course administration settings. You should also install the [[Course completion status block]] and the [[Self completion block]] to view reports and use some of the features of course completion.<br /> <br /> <br /> ==Completion tracking settings==<br /> The following settings may be found in ''Settings &gt; Course administration &gt; Completion tracking'':<br /> <br /> ===Overall criteria type aggregation===<br /> Choose here how you wish to mark the course complete -whether you want ''Any'' or ''All'' of the requirements that follow to count towards completion.<br /> <br /> :'''All''' means just that, every condition that has been checked. The most restrictive setting.<br /> : '''Any''' means any one of those conditions that have been specified.<br /> <br /> ===Completion dependencies===<br /> *This setting allows you to make &quot;the completion of another course&quot; as a condition for completing the course you are currently working in. This does not block the student from your current course; it simply means that the current course will not be marked complete until the first course has been marked complete. Thus, completion of the current course is dependent upon completion of an earlier course. Just select one or more courses in the &quot;Courses available box&quot;.<br /> <br /> *If completion tracking has not been set for any other courses yet then a message will appear as in (1). If completion tracking has been set elsewhere then the display changes to (2):<br /> <br /> {|<br /> |[[File:completionnotset.png|thumb|No other courses have completion tracking set]]<br /> |[[File:completiondependencies.png|thumb|Available course to be completed before the current course is marked complete]]<br /> |}<br /> <br /> ===Manual self completion===<br /> If you check the box in this link, then students can mark the course as complete themselves. In order to do this, the [[Self completion block]] must also be added to the course.<br /> <br /> ===Manual completion by===<br /> This setting allows users with selected roles to mark the course as complete. If used, put a check mark next to the role that can mark the course as complete. The roles listed are ones for which the capability [[Capabilities/moodle/course:markcomplete|Mark users as complete in course completion]] is allowed.<br /> <br /> Select the Aggregation method &quot;All&quot; when every role that is marked here must put a check mark in the course completion report in order for the student's course to be marked complete. <br /> <br /> Select the Aggregation method &quot;Any&quot; when one or more of the roles that are marked here have put a check mark in the course completion report in order for the student's course to be marked complete.<br /> <br /> ===Activities completed===<br /> This setting will show a list of activities which have [[Activity completion]] setting defined. Put a check next to the ones which should count towards course completion. <br /> <br /> The &quot;All&quot; aggregation method means that each of the checked activities must meet their Activity completion settings.<br /> <br /> The &quot;Any&quot; aggregation method means that at least one of the checked activities must meet their Activity completion settings.<br /> <br /> ===Date===<br /> If you check the ''Enable'' box you can then set a date, after which the course will be declared complete..<br /> <br /> ===Duration after enrolment===<br /> If you check the ''Enable'' box you can then choose a number of days after enrolment upon which the course will be marked complete.<br /> <br /> ===Grade===<br /> If you check the ''Enable'' box you can set a passing grade for the course.<br /> <br /> ===Unenrolment===<br /> If you check the box ''Completion on unenrolment'' then the student's course will be complete once they have unenrolled.<br /> <br /> ==Course administration settings==<br /> ''Course administration &gt; Edit settings''<br /> <br /> *Student Progress<br /> **Completion tracking must be enabled<br /> **Completion tracking begins after enrollment (best practice is to check this).<br /> <br /> ==Site administration settings==<br /> ''Site administration &gt; Advanced features &gt; Enable completion tracking'' (check enabled).<br /> <br /> The above settings can be set as defaults for the site in ''Settings &gt; Site administration &gt; Courses &gt; Course default settings''. <br /> :''Tip:'' The [[Cron]] trigger default for course completion is every 10 minutes. This is not usually what the Teachers and Students expect. The length of time can be impacted by the server cron schedule and by the code found in /lib/completionlib.php under &quot;Cache expiry time&quot;.<br /> <br /> ==Course completion capabilities==<br /> <br /> There are two capabilities, both of which are allowed for the default roles of manager, teacher and non-editing teacher:<br /> <br /> *[[Capabilities/report/completion:view|View course completion report]]<br /> *[[Capabilities/moodle/course:markcomplete|Mark users as complete in course completion]]<br /> <br /> [[Category:Site administration]]<br /> <br /> [[eu:Ikastaro-osaketaren_jarraipenaren_ezarpenak]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Installing_Moodle&diff=104677 2013-05-02T09:32:05Z

<p>Dougiamas: /* Create the (moodledata) data directory */</p> <hr /> <div>{{Template:Installing Moodle}}<br /> ''This page explains how to install Moodle. If you are an expert and/or in a hurry try [[Installation Quickstart]].''<br /> <br /> If you just want to try Moodle on a standalone machine there are 'one-click' installers for Windows (see [[Complete install packages for Windows]]) and for OSX (see [[Complete Install Packages for Mac OS X]]). These are unsuitable for production servers. <br /> <br /> == Requirements ==<br /> <br /> Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). If in doubt, this is the safest combination (if for no other reason than being the most common). There are other options - see the Software section that follows:<br /> <br /> The basic requirements for Moodle are as follows:<br /> <br /> === Hardware === <br /> * Disk space: 160MB free (min) plus as much as you need to store your materials. 5GB is probably a realistic minimum. <br /> * Backups: at least the same again (at a remote location preferably) as above to keep backups of your site<br /> * Memory: 256MB (min), 1GB or more is strongly recommended. The general rule of thumb is that Moodle can support 10 to 20 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination and the type of use. 'Concurrent' really means web server processes in memory at the same time (i.e. users interacting with the system within a window of a few seconds). It does NOT mean people 'logged in'.<br /> <br /> === Software ===<br /> * An operating system (!). Anything that runs the following software; although the choice will most likely depend on the performance you need and the skills you have available. Linux and Windows are the most common choices (and good support is available). If you have a free choice, Linux is generally regarded to be the optimal platform. Moodle is also regularly tested with Windows XP/2000/2003, Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems.<br /> * Web server. Primarily [[Apache]] or [[IIS]]. Not fully tested (or supported) but should work are [http://www.lighttpd.net/ lightttpd], [http://nginx.org/ nginx], [http://www.cherokee-project.com/ cherokee], zeus and [http://litespeedtech.com/ LiteSpeed]. Moodle will refuse to install on any other web server. Your web server needs to be correctly configured to serve PHP files.The version is not critical but try to use the newest web server build available to you. <br /> * [[PHP]] - The minimum version is currently 5.3.2. A number of extensions are required; see the [[PHP]] page for full details. Installation will halt at the environment check if any of the required extensions are missing.<br /> * A database. MySQL and PostgreSQL are the primary development database, the most comprehensively tested and have extensive documentation and support. Oracle and MSSQL are fully supported (note that optional plugins may be untested with these databases) but documentation and online help are not as comprehensive as MySQL/PostgreSQL. If in doubt use MySQL (more documentation) or PostgreSQL (better stability/performance). You will need the appropriate PHP extension (configured if need be) for your chosen database.<br /> ** [[MySQL]] - minimum version 5.1.33<br /> ** [[PostgreSQL]] - minimum version 8.3<br /> ** [[MSSQL]] - minimum version 9.0<br /> ** [[Oracle]] - minimum version 10.2<br /> ** [[SQLite]] - minimum version 2.0<br /> * Minimum browser for accessing Moodle: Firefox 4, Internet Explorer 8, Safari 5, Google Chrome 11, Opera 9<br /> <br /> == Set up your server ==<br /> <br /> ...or desktop computer, if you are just evaluating Moodle. There are lots of possibilities for installing the basic server software depending on your particular choices. Some links and pointers are at [[Installing AMP]]<br /> <br /> If you are using a hosted server all this should be done for you. However, (especially on shared hosting) make sure you understand or find out how to change PHP settings (e.g. file upload maximums). This can vary a huge amount from host to host.<br /> <br /> == Download and copy files into place ==<br /> <br /> '''IMPORTANT: While there are now a number of places you can get the Moodle code, you are strongly advised to obtain Moodle from moodle.org. If you run into problems it will be a great deal easier to support you.'''<br /> <br /> You have two options:<br /> * Download your required version from http://moodle.org/downloads and unzip/unpack...<br /> * '''OR''' Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):<br /> &lt;pre&gt;<br /> $ git clone -b MOODLE_24_STABLE git://git.moodle.org/moodle.git <br /> &lt;/pre&gt;<br /> ...this fetches a complete copy of the Moodle repository and then switches to the 2.4 Stable branch (latest weekly build). For a fuller discussion see [[Git for Administrators]]. <br /> <br /> Either of the above should result in a directory called '''moodle''', containing a number of files and folders. <br /> <br /> You can either place the whole folder in your web server documents directory, in which case the site will be located at '''&lt;nowiki&gt;http://yourwebserver.com/moodle&lt;/nowiki&gt;''', or you can copy all the contents straight into the main web server documents directory, in which case the site will be simply '''&lt;nowiki&gt;http://yourwebserver.com&lt;/nowiki&gt;'''. See the documentation for your system and/or web server if you are unsure. <br /> <br /> :''Tip:'' If you are downloading Moodle to your local computer and then uploading it to your hosted web site, if possible upload the compressed file and decompress at the remote end (check your 'file manager'). Failing that, watch FTP progress carefully for errors or missed files.<br /> <br /> * '''Secure the Moodle files:''' It is vital that the files are not writeable by the web server user. For example, on Unix/Linux (as root):<br /> &lt;pre&gt;<br /> # chown -R root /path/to/moodle<br /> # chmod -R 0755 /path/to/moodle<br /> &lt;/pre&gt;<br /> (files are owned by the administrator/superuser and are only writeable by them - readable by everyone else)<br /> <br /> == Create an empty database ==<br /> <br /> Next create a new, empty database for your installation. You need to find and make a note of following information for use during the final installation stage:<br /> * '''dbhost''' - the database server hostname. Probably ''localhost'' if the database and web server are the same machine, otherwise the name of the database server<br /> * '''dbname''' - the database name. Whatever you called it, e.g. ''moodle'' <br /> * '''dbuser''' - the username for the database. Whatever you assigned, e.g. ''moodleuser'' - do not use the root/superuser account. Create a proper account with the minimum permissions needed.<br /> * '''dbpass''' - the password for the above user<br /> <br /> If your site is hosted you should find a web-based administration page for databases as part of the control panel (or ask your administrator). For everyone else or for detailed instructions, see the page for your chosen database server:<br /> * [[MySQL]]<br /> * [[PostgreSQL]]<br /> * [[MSSQL]]<br /> * [[Oracle]]<br /> <br /> == Create the (''moodledata'') data directory ==<br /> <br /> Moodle requires a directory to store all of its files (all your site's uploaded files, temporary data, session data etc.). The web server needs to be able to write to this directory. On larger systems consider how much free space you are going to use when allocating this directory. <br /> <br /> '''IMPORTANT:''' This directory must '''NOT''' be accessible directly via the web. This would be a serious security hole. Do not try to place it inside your web root or inside your Moodle program files directory. Moodle will not install. It can go anywhere else convenient. <br /> <br /> Here is an example (Unix/Linux) of creating the directory and setting the permissions for '''anyone''' on the server to write here. This is only appropriate for Moodle servers that are not shared. Discuss this with your server administrator for better permissions that just allow the web server user to access these files.<br /> <br /> &lt;pre&gt;<br /> # mkdir /path/to/moodledata<br /> # chmod 0777 /path/to/moodledata<br /> &lt;/pre&gt;<br /> <br /> If your server supports ACL it is recommended to set following permissions, for example if your Apache server uses account www-data:<br /> &lt;pre&gt;<br /> # chmod -R +a &quot;www-data allow read,delete,write,append,file_inherit,directory_inherit&quot; /path/to/moodledata<br /> &lt;/pre&gt;<br /> If you are planning to execute PHP scripts from the command line you should set the same permissions for the current user:<br /> &lt;pre&gt;<br /> $ sudo chmod -R +a &quot;`whoami` allow read,delete,write,append,file_inherit,directory_inherit&quot; /path/to/moodledata<br /> &lt;/pre&gt;<br /> <br /> ==== Securing moodledata in a web directory ====<br /> <br /> If you are using a hosted site and you have no option but to place 'moodledata' in a web accessible directory. You may be able to secure it by creating an .htaccess file in the 'moodledata' directory. This does not work on all systems - see your host/administrator. Create a file called .htaccess containing only the following lines:<br /> &lt;pre&gt;<br /> order deny,allow<br /> deny from all<br /> &lt;/pre&gt;<br /> <br /> == Start Moodle install ==<br /> It's now time to run the installer to create the database tables and configure your new site. The recommended method is to use the command line installer. If you cannot do this for any reason (e.g. on a Windows server) the web based installer is still available.<br /> <br /> === Command line installer ===<br /> <br /> It's best to run the command line installer as your system's web user. You need to know what that is - see your system's documentation (e.g. Ubuntu/Debian is 'www-data', Centos is 'apache')<br /> <br /> * Example of using the command-line installer (as root - substitute 'www-data' for your web user):<br /> &lt;pre&gt;<br /> # chown www-data /path/to/moodle<br /> # cd /path/to/moodle/admin/cli<br /> # sudo -u www-data /usr/bin/php install.php<br /> # chown -R root /path/to/moodle<br /> &lt;/pre&gt;<br /> The chowns allow the script to write a new config.php file. More information about the options can be found using <br /> &lt;pre&gt;<br /> # php install.php --help<br /> &lt;/pre&gt;<br /> <br /> You will be asked for other settings that have not been discussed on this page - if unsure just accept the defaults. For a full discussion see [[Administration via command line]]<br /> <br /> === Web based installer ===<br /> To run the web installer script, just go to your Moodle's main URL using a web browser.<br /> <br /> The installation process will take you through a number of pages. You should be asked to confirm the copyright, see the database tables being created, supply administrator account details and supply the site details. The database creation can take some time - please be patient. You should eventually end up at the Moodle front page with an invitation to create a new course. <br /> <br /> It is very likely that you will be asked to download the new config.php file and upload it to your Moodle installation - just follow the on-screen instructions. <br /> <br /> ==Final configuration==<br /> <br /> === Settings within Moodle ===<br /> There are a number of options within the Moodle Site Administration screens (accessible from the 'Site administration' tab in the 'Settings' block. Here are a few of the more important ones that you will probably want to check:<br /> * ''Settings &gt; Site administration &gt; Plugins &gt; Message Outputs &gt; Email'': Set your smtp server and authentication if required (so your Moodle site can send emails). The support contact for your site is also set on this page. <br /> * ''Settings &gt; Site administration &gt; Server &gt; System paths'': Set the paths to du, dot and aspell binaries.<br /> * ''Settings &gt; Site administration &gt; Server &gt; HTTP'': If you are behind a firewall you may need to set your proxy credentials in the 'Web proxy' section.<br /> * ''Settings &gt; Site administration &gt; Location &gt; Update timezones'': Run this to make sure your timezone information is up to date.<br /> <br /> === Remaining tasks ===<br /> <br /> * '''Configure Cron''': Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].<br /> * '''Set up backups''': See [[Site backup]] and [[Automated course backup]].<br /> * '''Check mail works''': [[Add a new user|Create a test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not, check the settings in ''Settings &gt; Site administration &gt; Plugins &gt; Message outputs &gt; Email''. Don't be tempted to skip this step (clue: email is used to recover lost passwords, including the administrator password when you forget it!)<br /> * '''Secure your Moodle site''': Read the [[Security recommendations]].<br /> <br /> === Installation is complete :) ===<br /> <br /> * Create a new course: You can now [[Adding a new course|create a new course]] and have a play ;-)<br /> <br /> === If something goes wrong... ===<br /> <br /> Here are some things you should try...<br /> <br /> * Check the [[Installation FAQ]]<br /> * Check your file permissions carefully. Can your web server read (but not write) the Moodle program files? Can your web server read and write your Moodle data directory?<br /> * Check your database permissions. Have you set up your database user with the correct rights and permissions for your configuration (especially if the web server and database server are different machines)?<br /> * If you are having trouble creating a [[Configuration file]] (config.php), you can do it manually by copying config-dist.php (in the root of the Moodle program directory) to config.php, editing it and setting your database/site options there. Installation will continue from the right place. <br /> * Once you have a config.php (see previous tip) you can edit it to turn on debugging (in section 8). This may give you extra information to help track down a problem. If you have access, check your web server error log(s).<br /> * Re-check your php.ini / .htaccess settings. Are they appropriate (e.g. memory_limit), did you edit the correct php.ini / .htaccess file and (if required) did you re-start the web server after making changes?<br /> * Did you include any non-core (optional) plugins, themes or other code before starting the installation script? If so, remove it and try again (it may be broken or incompatible).<br /> * Explain your problem in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]. '''PLEASE''' list your software versions; explain what you did, what happened and what error messages you saw (if any); explain what you tried. There is no such thing as 'nothing', even a blank page is something!<br /> <br /> == Platform specific instructions ==<br /> <br /> '''Note:''' Much of this information is provided by the community. It may not have been checked and may be out of date. Please read in conjunction with the above installation instructions.<br /> <br /> * [[Windows installation]]<br /> ** [[Installing Moodle on SmarterASP.NET]]<br /> * [[Unix or Linux Installation]]<br /> * [[Mac Installation]]<br /> * [[Amazon EC2 Cloud Services Installation]]<br /> <br /> == See also ==<br /> <br /> * [http://moodle.org/mod/forum/discuss.php?d=182086 New Video Tutorial- How to Install Moodle on Shared Hosting via cPanel (Not Fantastico)]<br /> * [http://moodle.org/mod/forum/discuss.php?d=199542 Video Tutorial - Install Moodle on a Virtual Box from scratch] <br /> <br /> [[es:Instalaci%C3%B3n_de_moodle]]<br /> [[de:Installation von Moodle]]<br /> [[fr:Installation de Moodle]]<br /> [[ja:Moodleのインストール]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104564 2013-04-29T08:36:32Z

<p>Dougiamas: /* Badges */</p> <hr /> <div>{{Main page}}<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights a few of the most interesting!<br /> <br /> Full details of the release, with technical information, can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes].<br /> <br /> (Click any screenshot below to see it enlarged)<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that non-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:showmoreshowless.png|thumb|&quot;Show more&quot; (and &quot;show less&quot; options]]<br /> |}<br /> <br /> The rich text editor is collapsed and can be expanded:<br /> <br /> {|<br /> |[[File:collapsedassignment.png|thumb|Formatting options collapsed and box is narrow]]<br /> |[[File:expandedassignment.png|thumb|Formatting options shown and box expanded]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Reports are in the Administration block===<br /> Reports have moved and can now be seen in the newly named ''Administration'' block, (formerly ''Settings''.)<br /> <br /> {|<br /> |[[File:reportsinadmin.png|thumb|Administration block with Reports]]<br /> |}<br /> <br /> ===Badges===<br /> [[Badges]] are a nice way to acknowledge good work, and it's now possible for teachers to award course badges based on a variety of chosen criteria. These badges are fully compatible with [http://openbadges.org/ Mozilla Open Badges].<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> This blog post has some interesting reflection on when badges might be most appropriate: [http://alex.halavais.net/ozbadge The Badges of Oz]<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Assignment enhancements===<br /> Along with neater options for choosing submission and feedback types, resubmitting options are much improved:<br /> <br /> {|<br /> | [[File:assignmentandfeedbackcondensed.png|thumb|Neater assignment set up screen]]<br /> | [[File:attemptsreopened.png|thumb|New settings for resubmissions]]<br /> |}<br /> <br /> ===Drag and drop media onto the course page===<br /> You can now drag an image or some text onto your course page and choose whether to display it embedded in a label or as a clickable resource.<br /> <br /> {|<br /> | [[File:dragdrop1.png|thumb|Drag an image onto your course page]]<br /> |[[File:dragdrop2.png|thumb|Choose &quot;add image..&quot;]]<br /> |[[File:dragdrop3.png|thumb|And here it is!]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ===Search the list of enrolled users===<br /> A new search box makes finding users in very large courses much easier:<br /> <br /> {|<br /> | [[File:Searchenrolledusers.png|thumb|A search facility allows teachers to search for specific users.]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;'''Bootstrapbase'''&quot; that implements the basics, and a new usable theme called ''''''Clean'''''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. It also (along with ''Afterburner'') allows you to upload a logo directly from the file picker) <br /> <br /> Bootstrapbase allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Clean theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Clean theme on smaller screen; note position of Navigation block]]<br /> | [[File:filepickerlogo.png|thumb|Add your logo from the file picker in Clean theme]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]<br /> |}<br /> <br /> ==See also==<br /> <br /> * [[:Category:New features|Category:New features]] - list of pages documenting new features in Moodle 2.5</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104330 2013-04-22T15:04:19Z

<p>Dougiamas: </p> <hr /> <div>{{Main page}}<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights a few of the most interesting!<br /> <br /> Full details of the release, with technical information, can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes].<br /> <br /> (Click any screenshot below to see it enlarged)<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that non-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Badges===<br /> Badges are a nice way to acknowledge good work, and it's now possible for teachers to award course badges based on a variety of chosen criteria. These badges are fully compatible with [http://openbadges.org/ Mozilla Open Badges].<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;'''Bootstrap'''&quot; that implements the basics, and a new usable theme called ''''''Simple'''''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. <br /> <br /> Bootstrap allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]<br /> |}<br /> <br /> ==See also==<br /> <br /> * [[:Category:New features|Category:New features]] - list of pages documenting new features in Moodle 2.5</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104073 2013-04-15T07:27:11Z

<p>Dougiamas: </p> <hr /> <div>{{Main page}}<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights some of the most useful and coolest. Click any screenshot to see it enlarged.<br /> <br /> Full details of the release, with technical information, can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes].<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that non-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Badges===<br /> Badges are a nice way to acknowledge good work, and it's now possible for teachers to award course badges based on a variety of chosen criteria. These badges are fully compatible with [http://openbadges.org/ Mozilla Open Badges] and you can easily push your <br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;'''Bootstrap'''&quot; that implements the basics, and a new usable theme called ''''''Simple'''''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. <br /> <br /> Bootstrap allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]<br /> |}<br /> <br /> ==See also==<br /> <br /> * [[:Category:New features|Category:New features]] - list of pages documenting new features in Moodle 2.5</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104072 2013-04-15T07:25:30Z

<p>Dougiamas: /* For teachers and students: */</p> <hr /> <div>{{Main page}}<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights some of the most useful and coolest. Click any screenshot to see it enlarged. The full details with technical information can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes].<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that non-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Badges===<br /> Badges are a nice way to acknowledge good work, and it's now possible for teachers to award course badges based on a variety of chosen criteria. These badges are fully compatible with [http://openbadges.org/ Mozilla Open Badges] and you can easily push your <br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;'''Bootstrap'''&quot; that implements the basics, and a new usable theme called ''''''Simple'''''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. <br /> <br /> Bootstrap allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]<br /> |}<br /> <br /> ==See also==<br /> <br /> * [[:Category:New features|Category:New features]] - list of pages documenting new features in Moodle 2.5</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104041 2013-04-12T04:54:13Z

<p>Dougiamas: /* New themes suited to all screen sizes */</p> <hr /> <div>=So what's new in Moodle 2.5?=<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights some of the most useful and coolest. Click any screenshot to see it enlarged. The full details with technical information can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes]<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that on-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Badges===<br /> It's now possible for teachers to award course badges based on chosen criteria. These badges may also connect with [http://openbadges.org/ Mozilla Open Badges]<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;'''Bootstrap'''&quot; that implements the basics, and a new usable theme called ''''''Simple'''''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. <br /> <br /> Bootstrap allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104040 2013-04-12T04:53:59Z

<p>Dougiamas: /* New themes suited to all screen sizes */</p> <hr /> <div>=So what's new in Moodle 2.5?=<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights some of the most useful and coolest. Click any screenshot to see it enlarged. The full details with technical information can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes]<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that on-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Badges===<br /> It's now possible for teachers to award course badges based on chosen criteria. These badges may also connect with [http://openbadges.org/ Mozilla Open Badges]<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;'''Bootstrap'''&quot; that implements the basics, and a new usable theme called '''Simple''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. <br /> <br /> Bootstrap allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104039 2013-04-12T04:53:24Z

<p>Dougiamas: /* A new theme suited to all screen sizes */</p> <hr /> <div>=So what's new in Moodle 2.5?=<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights some of the most useful and coolest. Click any screenshot to see it enlarged. The full details with technical information can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes]<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that on-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Badges===<br /> It's now possible for teachers to award course badges based on chosen criteria. These badges may also connect with [http://openbadges.org/ Mozilla Open Badges]<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===New themes suited to all screen sizes===<br /> <br /> Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called &quot;bootstrap&quot; that implements the basics, and a new usable theme called '''Simple''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. <br /> <br /> Bootstrap allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104038 2013-04-12T04:11:06Z

<p>Dougiamas: /* Forms are much shorter */</p> <hr /> <div>=So what's new in Moodle 2.5?=<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights some of the most useful and coolest. Click any screenshot to see it enlarged. The full details with technical information can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes]<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users! <br /> <br /> We've made changes so that on-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Badges===<br /> It's now possible for teachers to award course badges based on chosen criteria. These badges may also connect with [http://openbadges.org/ Mozilla Open Badges]<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===A new theme suited to all screen sizes===<br /> &quot;Bootstrap&quot; is a theme which changes according to the screensize of the device used - on smaller screens for example, blocks move to the bottom, freeing up space for the main content at the top:<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104037 2013-04-12T04:10:12Z

<p>Dougiamas: /* Forms are much shorter */</p> <hr /> <div>=So what's new in Moodle 2.5?=<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights some of the most useful and coolest. Click any screenshot to see it enlarged. The full details with technical information can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes]<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Some of our forms have been getting rather long and, for new users we know they can be daunting! We've made changes so that on-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Badges===<br /> It's now possible for teachers to award course badges based on chosen criteria. These badges may also connect with [http://openbadges.org/ Mozilla Open Badges]<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===A new theme suited to all screen sizes===<br /> &quot;Bootstrap&quot; is a theme which changes according to the screensize of the device used - on smaller screens for example, blocks move to the bottom, freeing up space for the main content at the top:<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=New_features&diff=104036 2013-04-12T04:09:44Z

<p>Dougiamas: /* Set-up forms are much shorter */</p> <hr /> <div>=So what's new in Moodle 2.5?=<br /> Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights some of the most useful and coolest. Click any screenshot to see it enlarged. The full details with technical information can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes]<br /> <br /> ==For teachers and students:==<br /> <br /> ===Forms are much shorter===<br /> <br /> Some of our forms have been getting rather long and, for new users, daunting! We've made changes so that on-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.<br /> <br /> {|<br /> | [[File:shorterforms.png|thumb|Note the &quot;expand all&quot; option and condensed links]]<br /> | [[File:assignmentform.png|thumb|Assignment types are neatly summarised]]<br /> |}<br /> <br /> In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:<br /> <br /> {|<br /> | [[File:quizform1.png|thumb|Without the editing tools]]<br /> | [[File:quizform2.png|thumb|With the editing tools]]<br /> |}<br /> <br /> ===Folders can be displayed inline on a course page===<br /> <br /> You can now choose whether to have a folder show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:<br /> <br /> {|<br /> | [[File:folder1.png|thumb|Typical folder display before 2.5]]<br /> | [[File:folder2.png|thumb|Folder displayed inline]]<br /> | [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]<br /> |}<br /> <br /> ===Badges===<br /> It's now possible for teachers to award course badges based on chosen criteria. These badges may also connect with [http://openbadges.org/ Mozilla Open Badges]<br /> <br /> {|<br /> | [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]<br /> | [[File:studentbadgeview.png|thumb|Student view of allocated badges]]<br /> | [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]<br /> |}<br /> <br /> ===Word count in forum posts===<br /> A new setting in forums will display the number of words in a post:<br /> <br /> {|<br /> | [[File:bonding.png|thumb|Note word count bottom left]]<br /> |<br /> |}<br /> <br /> ===Templates for Essay question types===<br /> When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:<br /> <br /> {|<br /> | [[File:templatebox.png|thumb|Response template in question set up screen]]<br /> | [[File:quiztemplate.png|thumb|What the student sees]]<br /> |<br /> |}<br /> <br /> ===Glossary block enhancements===<br /> <br /> You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:<br /> {|<br /> | [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]<br /> |}<br /> <br /> ==For administrators:==<br /> <br /> ===A new theme suited to all screen sizes===<br /> &quot;Bootstrap&quot; is a theme which changes according to the screensize of the device used - on smaller screens for example, blocks move to the bottom, freeing up space for the main content at the top:<br /> <br /> {|<br /> | [[File:Bootrap2.png|thumb|Bootstrap theme on standard screen]]<br /> | [[File:Bootstrap1.png|thumb|Bootstrap theme on smaller screen; note position of Navigation block]]<br /> |}<br /> <br /> ===Install add-ons from inside Moodle===<br /> It's now possible to install add-ons from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the Moodle plugins directory:<br /> <br /> {|<br /> | [[File:Selection_011.png|thumb|Add-on install tool]]<br /> | [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Main_page&diff=103912 2013-04-09T07:14:16Z

<p>Dougiamas: </p> <hr /> <div>&lt;div class=&quot;navtrail&quot;&gt;&lt;/div&gt;<br /> &lt;div class=&quot;frontpagetotal&quot;&gt;&lt;p class=&quot;note&quot;&gt;'''''Welcome to the Moodle 2.5 documentation''' including details of [[:Category:New features|new features in Moodle 2.5]]!''&lt;/p&gt;<br /> <br /> <br /> Documentation for older versions of Moodle is also available:<br /> <br /> * '''[https://docs.moodle.org/24/en Moodle 2.4 documentation]'''<br /> * '''[https://docs.moodle.org/23/en Moodle 2.3 documentation]'''<br /> * '''[https://docs.moodle.org/22/en Moodle 2.2 documentation]'''<br /> <br /> ===See also===<br /> <br /> *'''[https://docs.moodle.org/overview/ Documentation overview]''' - list of all documentation in different languages <br /> *'''[https://docs.moodle.org/dev/Main_Page Moodle developer documentation]'''<br /> <br /> &lt;div class=&quot;frontpageblock&quot;&gt;<br /> &lt;h2&gt;[[About Moodle]]&lt;/h2&gt;<br /> *[[Philosophy]]<br /> *[[Pedagogy]]<br /> *[[Usage]]<br /> *[[Moodle site - basic structure]]<br /> *[[Moodle key terms]]<br /> *[[About Moodle FAQ]]<br /> <br /> &lt;h2&gt;[[Installation]]&lt;/h2&gt;<br /> *[[Installing Moodle]]<br /> *[[Installation Quickstart]]<br /> *[[Cron]]<br /> *[[Installing plugins]]<br /> *[[Installation FAQ]]<br /> *[[Upgrading]]<br /> *[[Upgrade overview]]<br /> *[[Automatic updates deployment]]<br /> *[[Git for Administrators|Git guide]]<br /> *[[Administration via command line]]<br /> *[[Upgrading FAQ]]<br /> *[[Moodle migration]]<br /> <br /> &lt;/div&gt;<br /> &lt;div class=&quot;frontpageblock&quot;&gt;<br /> &lt;h2&gt;[[Managing a Moodle site]]&lt;/h2&gt;<br /> *[[Authentication]]<br /> *[[Managing accounts]]<br /> *[[Enrolments]]<br /> *[[Roles and permissions]]<br /> *[[Security]]<br /> *[[Performance]]<br /> *[[Backup]]<br /> *[[Site appearance]]<br /> *[[Language]]<br /> *[[Server settings]]<br /> *[[Site-wide reports]]<br /> *[[Admin tools]]<br /> *[[Developer tools]]<br /> *[[Web services]]<br /> *[[Moodle for mobile]]<br /> *[[Community hubs]]<br /> *[[More features]]<br /> &lt;/div&gt;<br /> &lt;div class=&quot;frontpageblock&quot;&gt;<br /> &lt;h2&gt;[[Managing a Moodle course]]&lt;/h2&gt;<br /> * [[Courses]]<br /> * [[Editing text]]<br /> * [[Activities]]<br /> * [[Resources]]<br /> * [[Blocks]]<br /> * [[Questions]]<br /> * [[Course enrolment]]<br /> * [[Grouping users]]<br /> * [[Tracking progress]]<br /> * [[Reusing activities]]<br /> &lt;/div&gt;<br /> &lt;div class=&quot;frontpageblock&quot;&gt;<br /> &lt;h2&gt;[[Managing content]]&lt;/h2&gt;<br /> * [[Working with files]]<br /> * [[Repositories]]<br /> * [[Portfolios]]<br /> * [[Working with media]]<br /> * [[Filters]]<br /> * [[Licences]]<br /> * [[Plagiarism prevention]]<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> __NOTOC__<br /> See the full '''[[Table of Contents]]''' for more detail.<br /> <br /> <br /> ''If you can't find the documentation you're looking for, please let us know by posting in the [http://moodle.org/mod/forum/view.php?id=7135 Moodle community sites forum].''<br /> <br /> [[de:Hauptseite]]<br /> [[es:Página Principal]]<br /> [[eu:Azala]]<br /> [[fr:Accueil]]<br /> [[hr:Glavna stranica]]<br /> [[ja:メインページ]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Mobile_app&diff=103897 2013-04-08T09:41:53Z

<p>Dougiamas: /* How to report a bug */</p> <hr /> <div>{{Mobile}}<br /> &lt;p class=&quot;note&quot;&gt;'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.&lt;/p&gt;<br /> <br /> == Features ==<br /> * upload a picture into your private file area<br /> * record an audio file and upload it into your private file area<br /> * send a private message to a course participant (can be done offline)<br /> * take a personal note about a course participant (can be done offline)<br /> * add a course participant to your phone contact<br /> * call a course participant touching the phone number<br /> * locate a course participant address on Google map<br /> * download and view some resources<br /> * quick access to your course contents<br /> <br /> ==Moodle sites must be enabled for the app to access them==<br /> <br /> The administrator of your Moodle site (which must be version 2.4 or later) must enable mobile access as follows:<br /> <br /> * In ''Site administration &gt; Plugins &gt; Web services &gt; Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes.<br /> <br /> ==Installing the mobile app==<br /> <br /> Android: https://play.google.com/store/apps/details?id=com.moodle.moodlemobile<br /> <br /> iOS: Coming soon<br /> <br /> ==Testing the app on a demo site==<br /> <br /> In the login screen, type &quot;teacher&quot; or &quot;student&quot; in the Username field and click the Add button. You will be logged automatically to a Moodle demo site for testing the app.<br /> <br /> == Cache ==<br /> If you connect to your Moodle site and update/create/delete anything, and then go to your mobile app, the content will not be displayed. You will have to wait a couple of minutes. The cache time for the app is currently 5 minutes.<br /> <br /> ==How to report a bug==<br /> <br /> # Log in to the Moodle Mobile tracker [https://tracker.moodle.org/browse/MOBILE https://tracker.moodle.org/browse/MOBILE] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)<br /> # ''Check whether the issue has already been reported by [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE searching all the issues]''<br /> # If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle Mobile' as the project<br /> # Add a detailed description then click the Create button<br /> # Attach the following files to the issue by selecting 'Attach Files' in the 'More actions' dropdown menu:<br /> #* 'Device information' - this can be found in the app (Settings -&gt; Development -&gt; Device info, you can send yourself this information by email using the e-mail button at the bottom)<br /> #* App Log (''Settings -&gt; Development -&gt; Show Log'', again you can send yourself this information by email)<br /> <br /> === Report a bug by email ===<br /> You can send us the same report by email using ''Settings -&gt; Report a bug''. As the report is sent by email to mobile@moodle.com, the report will take more time to be filed in the tracker.<br /> <br /> == See also ==<br /> <br /> * [[:dev:Moodle Mobile|Moodle Mobile developer docs]]<br /> * [[Mobile web services]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Mobile_app&diff=103680 2013-03-20T03:45:53Z

<p>Dougiamas: </p> <hr /> <div>{{Mobile}}<br /> &lt;p class=&quot;note&quot;&gt;'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.&lt;/p&gt;<br /> <br /> ==Moodle sites must be enabled for the app to access them==<br /> <br /> The administrator of your Moodle site (which must be version 2.4 or later) must enable mobile access as follows:<br /> <br /> # In ''Settings &gt; Site administration &gt; Advanced features'' tick the 'Enable web services' checkbox, then click the button to save changes<br /> # In ''Site administration &gt; Plugins &gt; Web services &gt; Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes. (Ticking the 'Enable web services' checkbox should enable this also, but doesn't always.)<br /> <br /> ==Installing the mobile app==<br /> <br /> Android: https://play.google.com/store/apps/details?id=com.moodle.moodlemobile<br /> <br /> iOS: Coming soon<br /> <br /> ==Connecting to your Moodle site ==<br /> <br /> <br /> <br /> ==Browsing courses==<br /> <br /> ''Information coming soon...''<br /> <br /> ==Uploading photos and audio==<br /> <br /> ''Information coming soon...''<br /> <br /> ==Managing multiple Moodle sites==<br /> <br /> ==Notifications==<br /> <br /> Currently not available<br /> <br /> <br /> <br /> <br /> ==Settings==<br /> <br /> ''Information coming soon...''<br /> <br /> ==Testing the app on a demo site==<br /> <br /> In the login screen, type &quot;teacher&quot; or &quot;student&quot; in the Username field and click the Add button. You will be logged automatically to a Moodle demo site for testing the app.<br /> <br /> ==How to report a bug==<br /> <br /> # Log in to the [http://tracker.moodle.org/ Moodle Tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)<br /> # ''Check whether the issue has already been reported by searching''<br /> # If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle Mobile' as the project<br /> # Add a detailed description then click the Create button<br /> # Attach the following files to the issue by selecting 'Attach Files' in the 'More actions' dropdown menu:<br /> #* 'Device information' - this can be found in the app (Settings -&gt; Device info, you can send yourself this information by email using the e-mail button at the bottom)<br /> #* App Log (Settings -&gt; Development -&gt; Show Log, again you can send yourself this information by email)<br /> <br /> == See also ==<br /> <br /> * [[:dev:Moodle Mobile|Moodle Mobile developer docs]]<br /> * [[Mobile web services]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=admin/mdeploy/notdownloadable&diff=102372 2012-12-12T05:51:11Z

<p>Dougiamas: </p> <hr /> <div>Your Moodle site is not able to download things securely from moodle.org or download.moodle.org.<br /> <br /> See [[Available update notifications]] for full information.<br /> <br /> The most likely solution is here [[SSL certificate for moodle.org]].<br /> <br /> <br /> [[Category:Error|Mdeploy]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=admin/mdeploy/notdownloadable&diff=102371 2012-12-12T05:50:30Z

<p>Dougiamas: </p> <hr /> <div>Your Moodle site is not able to download things securely from moodle.org or download.moodle.org.<br /> <br /> See [[Available_update_notifications]] for full information.<br /> <br /> The most likely solution is here [[SSL_certificate_for_moodle.org]].<br /> <br /> <br /> [[Category:Error|Mdeploy]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=admin/mdeploy/notdownloadable&diff=102370 2012-12-12T05:50:08Z

<p>Dougiamas: </p> <hr /> <div>Your Moodle siite is not able to download things securely from moodle.org or download.moodle.org.<br /> <br /> See [[Available_update_notifications]] for full information.<br /> <br /> The most likely solution is here [[SSL_certificate_for_moodle.org]].<br /> <br /> <br /> [[Category:Error|Mdeploy]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Caching&diff=102367 2012-12-11T09:01:17Z

<p>Dougiamas: </p> <hr /> <div>{{Performance}}{{New features}}<br /> <br /> A cache is a collection of processed data that is kept on hand and re-used in order to avoid costly repeated database queries.<br /> <br /> Moodle 2.4 saw the implementation of MUC, the Moodle Universal Cache. This new system allows certain functions of Moodle (eg string fetching) take advantage of different installed cache services (eg files, ram, memcached).<br /> <br /> In future versions of Moodle we will continue expanding the number of Moodle functions that use MUC, which will continue improving performance, but you can already start using it to improve your site.<br /> <br /> ==General approach to performance testing==<br /> <br /> Here is the general strategy you should be taking:<br /> <br /> # Build a test environment that is as close to your real production instance as possible (eg hardware, software, networking, etc)<br /> # Make sure to remove as many uncontrolled variables as you can from this environment (eg other services)<br /> # Use a tool to place a realistic, but simulated and repeatable load upon you server. (eg jmeter or selenium).<br /> # Decide on a way to measure performance of the server by capturing data (ram, load, time taken, etc)<br /> # Run your load and measure a baseline performance result.<br /> # Change one variable at a time, and re-run the load to see if performance gets better or worse. Repeat as necessary.<br /> # When you discover settings that result in a consistent performance improvement, apply to your production site.<br /> <br /> ==How to use the caching settings==<br /> <br /> (to be written)<br /> <br /> <br /> <br /> ==Other performance testing==<br /> <br /> Two links that might be useful to anyone considering testing performance on their own servers:<br /> <br /> * [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]<br /> * [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]<br /> <br /> ==See also==<br /> <br /> * Using Moodle [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] forum discussion<br /> <br /> Developer documentation:<br /> * [[:dev:The Moodle Universal Cache (MUC)]]<br /> * [[:dev:Cache API]]<br /> * [[:dev:Cache API - Quick reference]]<br /> <br /> <br /> {{stub}}<br /> [[de:Caching]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=admin/mdeploy/notdownloadable&diff=102276 2012-12-04T08:03:31Z

<p>Dougiamas: Created page with &quot;Until we have better docs, do this: Download this root certificate: https://www.digicert.com/testroot/DigiCertHighAssuranceEVRootCA.crt And put it in your moodle data directory...&quot;</p> <hr /> <div>Until we have better docs, do this:<br /> <br /> Download this root certificate: https://www.digicert.com/testroot/DigiCertHighAssuranceEVRootCA.crt<br /> <br /> And put it in your moodle data directory with this name: moodledata/moodleorgca.crt</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=admin/mdeploy/notwritable&diff=102274 2012-12-04T04:07:05Z

<p>Dougiamas: </p> <hr /> <div>For Moodle to install and manage plugins automatically, you need to make certain directories writeable by the web server process. The &quot;apache&quot; user is common on Unix-based systems using the Apache web server.<br /> <br /> The exact directories depends on the type of plugins. For a full list of directories see the Moodle path on https://docs.moodle.org/dev/Plugins <br /> <br /> For example Moodle activities are stored in the /mod directory, so you might do this from a shell prompt on your server:<br /> <br /> cd &lt;your main moodle directory&gt;<br /> chown -R apache mod<br /> chmod -R u+rw mod<br /> <br /> See also more about [[Installing plugins]].</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=admin/mdeploy/notwritable&diff=102273 2012-12-04T04:06:25Z

<p>Dougiamas: </p> <hr /> <div>For Moodle to install plugins automatically, you need to make certain directories writeable by the web server process. The &quot;apache&quot; user is common on Unix-based systems using the Apache web server.<br /> <br /> The exact directories depends on the type of plugins. For a full list of directories see the Moodle path on https://docs.moodle.org/dev/Plugins <br /> <br /> For example Moodle activities are stored in the /mod directory, so you might do this:<br /> <br /> cd &lt;your main moodle directory&gt;<br /> chown -R apache mod<br /> chmod -R u+rw mod<br /> <br /> See also more about [[Installing plugins]].</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=admin/mdeploy/notwritable&diff=102272 2012-12-04T04:04:11Z

<p>Dougiamas: Created page with &quot;For Moodle to install plugins automatically, you need to make certain directories writeable by the web server process. For example, the &quot;apache&quot; user is common on Unix-based sys...&quot;</p> <hr /> <div>For Moodle to install plugins automatically, you need to make certain directories writeable by the web server process. For example, the &quot;apache&quot; user is common on Unix-based systems using the Apache web server.<br /> <br /> The exact directories depends on the type of plugins. For example Moodle activities are stored in the /mod directory. For a full list of directories see the Moodle path on https://docs.moodle.org/dev/Plugins <br /> <br /> See also more about [[Installing plugins]].</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Site_registration&diff=101608 2012-10-30T07:40:45Z

<p>Dougiamas: </p> <hr /> <div>{{Server settings}}<br /> ==Moodle.org registration==<br /> <br /> [[Image:Registration.png|thumb|Moodle.org registration]]An administrator can register their site with moodle.org in ''Settings &gt; Site Administration &gt; Registration''.<br /> <br /> When you register your site with Moodle.org<br /> <br /> * You are added to a low-volume mailing list for important notifications such as security alerts and new releases of Moodle<br /> * Statistics about your site will be added to the statistics of the worldwide Moodle community http://moodle.org/stats/<br /> * Your site is also registered with the [http://hub.moodle.org/ moodle.org open community hub (MOOCH)], allowing users with the [[Capabilities/moodle/course:publish|publish courses capability]] (by default only managers) the option of publishing courses to MOOCH<br /> <br /> If you wish, you can choose for your site to be listed in http://moodle.org/sites/.<br /> <br /> To register your site:<br /> <br /> # Go to ''Settings &gt; Site Administration &gt; Registration''<br /> # Click the 'Register with moodle.org now' button<br /> # Review the registration information, amending as necessary<br /> # Click the 'Update registration on moodle.org' button at the bottom of the page<br /> <br /> After registering, MOOCH will be listed on ''Settings &gt; Site administration &gt; Server &gt; Hubs''.<br /> <br /> You may change the registration information at any time by updating your registration.<br /> <br /> Updated site statistics are sent to moodle.org automatically every 7 days.<br /> <br /> Note: it can sometimes take a little while (some days) for information to appear on http://moodle.org/sites<br /> <br /> Note: Only sites which are publicly available on the Internet are eligible to be registered.<br /> <br /> ==Registering with other hubs==<br /> <br /> An administrator can register their site with other community hubs in ''Settings &gt; Site administration &gt; Server &gt; Hubs''.<br /> <br /> A public hub may be selected from the list or a private hub URL and password may be entered.<br /> <br /> If you add the [[Community finder block]] to courses on your site, teachers, non-editing teachers and managers (and any other users with the capability [[Capabilities/moodle/community:add|moodle/community:add]]) will be able to access the hub and search for courses for download or to enrol in.<br /> <br /> == Unregistering from a hub==<br /> <br /> You may unregister from a hub at any time by clicking the unregister button. You will then be given the option to remove all courses currently being advertised on the hub and remove all courses that were uploaded to the hub.<br /> <br /> ==See also==<br /> *[[Usage]] for how statistics about Moodle sites are collected and maintained<br /> * [[Community hub]]<br /> * [[MOOCH FAQ]]<br /> <br /> [[Category:Hub]]<br /> <br /> [[ja: サイト登録]]<br /> [[de:Moodle-Site registrieren]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Site_registration&diff=101607 2012-10-30T07:39:29Z

<p>Dougiamas: </p> <hr /> <div>{{Server settings}}<br /> ==Moodle.org registration==<br /> <br /> [[Image:Registration.png|thumb|Moodle.org registration]]An administrator can register their site with moodle.org in ''Settings &gt; Site Administration &gt; Registration''.<br /> <br /> When you register your site with Moodle.org<br /> <br /> * You are added to a low-volume mailing list for important notifications such as security alerts and new releases of Moodle<br /> * Statistics about your site will be added to the statistics of the worldwide Moodle community http://moodle.org/stats/<br /> * Your site is also registered with the [http://hub.moodle.org/ moodle.org open community hub (MOOCH)], allowing users with the [[Capabilities/moodle/course:publish|publish courses capability]] (by default only managers) the option of publishing courses to MOOCH<br /> <br /> If you wish, you can choose for your site to be listed in http://moodle.org/sites/.<br /> <br /> To register your site:<br /> <br /> # Go to ''Settings &gt; Site Administration &gt; Registration''<br /> # Click the 'Register with moodle.org now' button<br /> # Review the registration information, amending as necessary<br /> # Click the 'Update registration on moodle.org' button at the bottom of the page<br /> <br /> After registering, MOOCH will be listed on ''Settings &gt; Site administration &gt; Server &gt; Hubs''.<br /> <br /> You may change the registration information at any time by updating your registration.<br /> <br /> Updated site statistics are sent to moodle.org automatically every 7 days.<br /> <br /> Note: Only sites which are publicly available on the Internet are eligible to be registered.<br /> <br /> ==Registering with other hubs==<br /> <br /> An administrator can register their site with other community hubs in ''Settings &gt; Site administration &gt; Server &gt; Hubs''.<br /> <br /> A public hub may be selected from the list or a private hub URL and password may be entered.<br /> <br /> If you add the [[Community finder block]] to courses on your site, teachers, non-editing teachers and managers (and any other users with the capability [[Capabilities/moodle/community:add|moodle/community:add]]) will be able to access the hub and search for courses for download or to enrol in.<br /> <br /> == Unregistering from a hub==<br /> <br /> You may unregister from a hub at any time by clicking the unregister button. You will then be given the option to remove all courses currently being advertised on the hub and remove all courses that were uploaded to the hub.<br /> <br /> ==See also==<br /> *[[Usage]] for how statistics about Moodle sites are collected and maintained<br /> * [[Community hub]]<br /> * [[MOOCH FAQ]]<br /> <br /> [[Category:Hub]]<br /> <br /> [[ja: サイト登録]]<br /> [[de:Moodle-Site registrieren]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=IMS_Common_Cartridge_import_and_export&diff=101059 2012-10-04T01:27:57Z

<p>Dougiamas: </p> <hr /> <div>{{Backup}}<br /> ==IMS Common Cartridge import==<br /> IMS Common Cartridge packages, such as a study package from [http://openlearn.open.ac.uk/ The Open University LearningSpace] can be imported into Moodle by uploading the zip file to ''Settings &gt; Course administration &gt; Restore'' then clicking the restore button (the same process as restoring a course backup).<br /> <br /> ===Troubleshooting tips===<br /> <br /> Occasionally you may have problems with packages from some other systems (Blackboard 9.1 is one example). In these cases try running the package through the [http://validator.imsglobal.org/index.jsp?validate=manifest IMS CC validator] to check it for errors. The validator can also fix some of the errors.<br /> <br /> [http://validator.imsglobal.org/index.jsp?validate=manifest http://validator.imsglobal.org/index.jsp?validate=manifest]<br /> <br /> <br /> <br /> ==IMS Common Cartridge export==<br /> <br /> {{New features}}A course can be exported as an IMS Common Cartridge as follows:<br /> <br /> # Go to ''Settings &gt; Course administration &gt; Backup''<br /> # Tick the 'IMS Common Cartridge 1.1' checkbox in the backup settings<br /> # Go through the backup steps<br /> # Complete - Click the Continue button<br /> <br /> An IMS CC (with distinctive .imscc extension to avoid confusion with .zip files) is then saved in the private user backup area.<br /> <br /> ==See also==<br /> <br /> * MDL-30265 Common Cartridge Export (take2) - Details of future improvements to CC export<br /> <br /> [[Category:Common Cartridge]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=MySQL&diff=99158 2012-07-16T03:14:18Z

<p>Dougiamas: </p> <hr /> <div>{{Installing Moodle}}<br /> MySQL is one of the supported databases that underpins a Moodle installation. <br /> <br /> == Installing MySQL ==<br /> <br /> * If you are running Linux your preference should be to install using your distributions package manager. This ensures you will get any available updates. <br /> * There are installers available for most popular operating systems at http://www.mysql.com/downloads/mysql/.<br /> * It is possible and reasonably straightforward to build mysql from source but it is not recommended (the pre-built binaries are supposedly better optimised).<br /> * Make sure you set a password for the 'root' user (see http://dev.mysql.com/doc/refman/5.0/en/default-privileges.html).<br /> * Consider installing and configuring my.cnf (the MySQL settings file) to suit your needs. The default configuration is usually very conservative in respect of memory usage versus performance.<br /> <br /> == Creating Moodle database ==<br /> <br /> These are the steps to create an empty Moodle database. Substitute your own database name, user name and password as appropriate.<br /> <br /> The instructions assume that the web server and MySQL server are on the same machine. In this case the 'dbhost' is 'localhost'. If they are on different machines substitute the name of the web server for 'localhost' in the following instructions and the 'dbhost' setting will be the name of the database server. <br /> <br /> === Command line === <br /> <br /> * To create a database using the 'mysql' command line client, first log into MySQL<br /> &lt;pre&gt;<br /> $ mysql -u root -p<br /> Enter password: <br /> &lt;/pre&gt;<br /> (Enter the password you previously set - or been given - for the MySQL 'root' user). After some pre-amble this should take you to the ''mysql&gt;'' prompt.<br /> * Create a new database (called 'moodle' - substitute your own name if required). We recommend you use '''utf8_unicode_ci''' for collation.<br /> &lt;pre&gt;<br /> mysql&gt; CREATE DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;<br /> &lt;/pre&gt;<br /> * Add a user/password with the minimum needed permissions:<br /> &lt;pre&gt;<br /> mysql&gt; GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,CREATE TEMPORARY TABLES,DROP,INDEX,ALTER ON moodle.* TO moodleuser@localhost IDENTIFIED BY 'yourpassword';<br /> &lt;/pre&gt;<br /> ...which creates a user called 'moodleuser' with a password 'yourpassword'. Make sure you invent a strong password and resist the temptation to 'GRANT ALL'.<br /> <br /> === phpMyAdmin ===<br /> <br /> [http://www.phpmyadmin.net/ phpMyAdmin] is a web based administration tool for MySQL. If this is available you can use it to create a new database. Make sure that you select 'UTF8' as the default character set.<br /> <br /> == See also ==<br /> <br /> * [http://www.mysql.com/ The MySQL homepage]<br /> * [http://moodle.org/mod/forum/view.php?id=45 Using Moodle databases forum]<br /> * [http://en.wikipedia.org/wiki/MySQL Wikipedia article about ''MySQL'']<br /> * [http://forums.mysql.com/read.php?24,92131,92131 List of articles on MySQL performance tuning]<br /> <br /> [[Category:SQL databases]]<br /> <br /> [[ja:MySQL]]<br /> [[de:MySQL]]</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99058 2012-07-09T07:15:06Z

<p>Dougiamas: /* Step 4: Perform the upgrade! */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> [[Image:Environment.png|thumb|right]]<br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared!==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your Moodle code==<br /> [[Image:Download.gif|frame|right]]<br /> <br /> At this point you can replace the Moodle code on your server with the version you downloaded. Remember to also update any plugins you added!<br /> <br /> <br /> ==Step 4: Perform the upgrade!==<br /> <br /> Trigger the upgrade by [[Upgrading#Finishing_the_upgrade|visiting the admin page]].<br /> <br /> If you have a large site this may take hours, so we recommend [[Administration_via_command_line#Upgrading_via_command_line|upgrading via command line]].<br /> <br /> ==How did you go?==<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99057 2012-07-09T07:13:57Z

<p>Dougiamas: /* Step 2: Be prepared for failure */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> [[Image:Environment.png|thumb|right]]<br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared!==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your Moodle code==<br /> [[Image:Download.gif|frame|right]]<br /> <br /> At this point you can replace the Moodle code on your server with the version you downloaded. Remember to also update any plugins you added!<br /> <br /> <br /> ==Step 4: Perform the upgrade!==<br /> <br /> Trigger the upgrade by [[Upgrading#Finishing_the_upgrade|installing the new Moodle software visiting the admin page]].<br /> <br /> If you have a large site this may take hours, so we recommend [[Administration_via_command_line#Upgrading_via_command_line|upgrading via command line]].<br /> <br /> <br /> <br /> <br /> ==How did you go?==<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99056 2012-07-09T07:13:34Z

<p>Dougiamas: /* Step 3: Replace your Moodle code and run the upgrade! */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> [[Image:Environment.png|thumb|right]]<br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your Moodle code==<br /> [[Image:Download.gif|frame|right]]<br /> <br /> At this point you can replace the Moodle code on your server with the version you downloaded. Remember to also update any plugins you added!<br /> <br /> <br /> ==Step 4: Perform the upgrade!==<br /> <br /> Trigger the upgrade by [[Upgrading#Finishing_the_upgrade|installing the new Moodle software visiting the admin page]].<br /> <br /> If you have a large site this may take hours, so we recommend [[Administration_via_command_line#Upgrading_via_command_line|upgrading via command line]].<br /> <br /> <br /> <br /> <br /> ==How did you go?==<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99055 2012-07-09T06:48:55Z

<p>Dougiamas: </p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> [[Image:Environment.png|thumb|right]]<br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your Moodle code and run the upgrade!==<br /> [[Image:Download.gif|frame|right]]<br /> ;Small site: Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> ;Large site?: Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> ===Success?===<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99054 2012-07-09T06:48:08Z

<p>Dougiamas: /* Step 1: Make sure that your server can run Moodle 2.2 */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> {|<br /> | [[File:Environment.png|thumb|Step 1: Server check]]<br /> | [[File:Site backup.png|thumb|Step 2: Backup]]<br /> | [[File:Download.gif|thumb|Step 3: Get new code]]<br /> |}<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> [[Image:Environment.png|frame|right]]<br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your Moodle code and run the upgrade!==<br /> [[Image:Download.gif|frame|right]]<br /> ;Small site: Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> ;Large site?: Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> ===Success?===<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99053 2012-07-09T06:47:53Z

<p>Dougiamas: /* Step 1: Make sure that your server can run Moodle 2.2 */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> {|<br /> | [[File:Environment.png|thumb|Step 1: Server check]]<br /> | [[File:Site backup.png|thumb|Step 2: Backup]]<br /> | [[File:Download.gif|thumb|Step 3: Get new code]]<br /> |}<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> [[Image:Environment.png|frame|right]<br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your Moodle code and run the upgrade!==<br /> [[Image:Download.gif|frame|right]]<br /> ;Small site: Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> ;Large site?: Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> ===Success?===<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99052 2012-07-09T06:46:38Z

<p>Dougiamas: /* Step 3: Replace your Moodle code and run the upgrade! */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> {|<br /> | [[File:Environment.png|thumb|Step 1: Server check]]<br /> | [[File:Site backup.png|thumb|Step 2: Backup]]<br /> | [[File:Download.gif|thumb|Step 3: Get new code]]<br /> |}<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> <br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your Moodle code and run the upgrade!==<br /> [[Image:Download.gif|frame|right]]<br /> ;Small site: Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> ;Large site?: Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> ===Success?===<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99051 2012-07-09T06:44:37Z

<p>Dougiamas: /* Step 3: Replace your old Moodle code with new Moodle 2.2 code */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> {|<br /> | [[File:Environment.png|thumb|Step 1: Server check]]<br /> | [[File:Site backup.png|thumb|Step 2: Backup]]<br /> | [[File:Download.gif|thumb|Step 3: Get new code]]<br /> |}<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> <br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your Moodle code and run the upgrade!==<br /> <br /> ;Small site: Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> ;Large site?: Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> ===Success?===<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99050 2012-07-09T06:43:00Z

<p>Dougiamas: /* Step 1: Make sure that your server can run Moodle 2.2 */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> {|<br /> | [[File:Environment.png|thumb|Step 1: Server check]]<br /> | [[File:Site backup.png|thumb|Step 2: Backup]]<br /> | [[File:Download.gif|thumb|Step 3: Get new code]]<br /> |}<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> <br /> (Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.)<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your old Moodle code with new Moodle 2.2 code==<br /> <br /> To upgrade Moodle all you need to do is replace the code and then run the upgrade scripts.<br /> <br /> ;Small site: Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> ;Large site?: Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> ===Success?===<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99049 2012-07-09T06:39:31Z

<p>Dougiamas: /* Step 3: Replace your old Moodle code with new Moodle 2.2 code */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> {|<br /> | [[File:Environment.png|thumb|Step 1: Server check]]<br /> | [[File:Site backup.png|thumb|Step 2: Backup]]<br /> | [[File:Download.gif|thumb|Step 3: Get new code]]<br /> |}<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your old Moodle code with new Moodle 2.2 code==<br /> <br /> To upgrade Moodle all you need to do is replace the code and then run the upgrade scripts.<br /> <br /> ;Small site: Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> ;Large site?: Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> ===Success?===<br /> <br /> ; Yes - it worked!: Great! Repeat the process for Moodle 2.3, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99048 2012-07-09T06:37:37Z

<p>Dougiamas: /* Step 3: Replace your old Moodle code with new Moodle 2.2 code */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> {|<br /> | [[File:Environment.png|thumb|Step 1: Server check]]<br /> | [[File:Site backup.png|thumb|Step 2: Backup]]<br /> | [[File:Download.gif|thumb|Step 3: Get new code]]<br /> |}<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your old Moodle code with new Moodle 2.2 code==<br /> <br /> To upgrade Moodle all you need to do is replace the code and then run the upgrade scripts.<br /> <br /> ;Small site: Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> ;Large site?: Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> ===Success?===<br /> <br /> ; Yes - it worked!: Great! Please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your joy with the Moodle community!<br /> ; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas https://docs.moodle.org/25/en/index.php?title=Upgrade_overview&diff=99047 2012-07-09T06:33:44Z

<p>Dougiamas: /* Step 2: Be prepared for failure */</p> <hr /> <div>&lt;span class=&quot;small-info-right&quot;&gt;''Moodle 2&lt;br /&gt;available now!''&lt;/span&gt;<br /> {|<br /> | [[File:Environment.png|thumb|Step 1: Server check]]<br /> | [[File:Site backup.png|thumb|Step 2: Backup]]<br /> | [[File:Download.gif|thumb|Step 3: Get new code]]<br /> |}<br /> <br /> There’s no need to visit a store and pay for software. You can start enjoying the cool features of Moodle 2 in three easy steps...<br /> __NOTOC__<br /> ==Step 1: Make sure that your server can run Moodle 2.2==<br /> <br /> Go to ''Settings &gt; Site administration &gt; Server &gt; Environment''<br /> <br /> Status OK for everything? Great! Go to step 2...<br /> <br /> Note: You need to upgrade to Moodle 2.2 before upgrading to 2.3.<br /> <br /> ==Step 2: Be prepared for failure==<br /> <br /> As usual with any large upgrade, you should always be prepared to &quot;roll back&quot; if there's an issue with your data or some custom code you've added.<br /> <br /> ; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.<br /> <br /> ; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].<br /> <br /> ==Step 3: Replace your old Moodle code with new Moodle 2.2 code==<br /> <br /> *Small site? Instructions here: [https://docs.moodle.org/22/en/Upgrading#Install_the_new_Moodle_software Installing the new Moodle software]<br /> *Large site? Instructions here: [https://docs.moodle.org/22/en/Administration_via_command_line#Upgrading_via_command_line Upgrading via command line]<br /> <br /> Finish by going to ''Settings &gt; Site administration &gt; Notifications'' and watching Moodle do all the rest!<br /> <br /> ===Success?===<br /> <br /> Yes - Great! Please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your joy with the Moodle community!<br /> <br /> No - Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.</div>

Dougiamas