https://docs.moodle.org/24/en/api.php?action=feedcontributions&feedformat=atom&user=DougiamasMoodleDocs - User contributions [en]2026-05-11T16:45:57ZUser contributionsMediaWiki 1.43.5https://docs.moodle.org/24/en/index.php?title=Mobile_app&diff=103897Mobile app2013-04-08T09:41:53Z<p>Dougiamas: /* How to report a bug */</p>
<hr />
<div>{{Mobile}}<br />
<p class="note">'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.</p><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 > Plugins > Web services > 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 "teacher" or "student" 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 -> Development -> Device info, you can send yourself this information by email using the e-mail button at the bottom)<br />
#* App Log (''Settings -> Development -> 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 -> 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Mobile_app&diff=103680Mobile app2013-03-20T03:45:53Z<p>Dougiamas: </p>
<hr />
<div>{{Mobile}}<br />
<p class="note">'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.</p><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 > Site administration > Advanced features'' tick the 'Enable web services' checkbox, then click the button to save changes<br />
# In ''Site administration > Plugins > Web services > 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 "teacher" or "student" 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 -> Device info, you can send yourself this information by email using the e-mail button at the bottom)<br />
#* App Log (Settings -> Development -> 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/mdeploy/notdownloadable&diff=102372admin/mdeploy/notdownloadable2012-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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/mdeploy/notdownloadable&diff=102371admin/mdeploy/notdownloadable2012-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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/mdeploy/notdownloadable&diff=102370admin/mdeploy/notdownloadable2012-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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Caching&diff=102367Caching2012-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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/mdeploy/notdownloadable&diff=102276admin/mdeploy/notdownloadable2012-12-04T08:03:31Z<p>Dougiamas: Created page with "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..."</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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/mdeploy/notwritable&diff=102274admin/mdeploy/notwritable2012-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 "apache" 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 <your main moodle directory><br />
chown -R apache mod<br />
chmod -R u+rw mod<br />
<br />
See also more about [[Installing plugins]].</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/mdeploy/notwritable&diff=102273admin/mdeploy/notwritable2012-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 "apache" 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 <your main moodle directory><br />
chown -R apache mod<br />
chmod -R u+rw mod<br />
<br />
See also more about [[Installing plugins]].</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/mdeploy/notwritable&diff=102272admin/mdeploy/notwritable2012-12-04T04:04:11Z<p>Dougiamas: Created page with "For Moodle to install plugins automatically, you need to make certain directories writeable by the web server process. For example, the "apache" user is common on Unix-based sys..."</p>
<hr />
<div>For Moodle to install plugins automatically, you need to make certain directories writeable by the web server process. For example, the "apache" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Site_registration&diff=101608Site registration2012-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 > Site Administration > 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 > Site Administration > 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 > Site administration > Server > 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 > Site administration > Server > 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Site_registration&diff=101607Site registration2012-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 > Site Administration > 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 > Site Administration > 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 > Site administration > Server > 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 > Site administration > Server > 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=IMS_Common_Cartridge_import_and_export&diff=101059IMS Common Cartridge import and export2012-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 > Course administration > 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 > Course administration > 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=MySQL&diff=99158MySQL2012-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 />
<pre><br />
$ mysql -u root -p<br />
Enter password: <br />
</pre><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>'' prompt.<br />
* Create a new database (called 'moodle' - substitute your own name if required). We recommend you use '''utf8_unicode_ci''' for collation.<br />
<pre><br />
mysql> CREATE DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;<br />
</pre><br />
* Add a user/password with the minimum needed permissions:<br />
<pre><br />
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,CREATE TEMPORARY TABLES,DROP,INDEX,ALTER ON moodle.* TO moodleuser@localhost IDENTIFIED BY 'yourpassword';<br />
</pre><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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99058Upgrade overview2012-07-09T07:15:06Z<p>Dougiamas: /* Step 4: Perform the upgrade! */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99057Upgrade overview2012-07-09T07:13:57Z<p>Dougiamas: /* Step 2: Be prepared for failure */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99056Upgrade overview2012-07-09T07:13:34Z<p>Dougiamas: /* Step 3: Replace your Moodle code and run the upgrade! */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99055Upgrade overview2012-07-09T06:48:55Z<p>Dougiamas: </p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99054Upgrade overview2012-07-09T06:48:08Z<p>Dougiamas: /* Step 1: Make sure that your server can run Moodle 2.2 */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99053Upgrade overview2012-07-09T06:47:53Z<p>Dougiamas: /* Step 1: Make sure that your server can run Moodle 2.2 */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99052Upgrade overview2012-07-09T06:46:38Z<p>Dougiamas: /* Step 3: Replace your Moodle code and run the upgrade! */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99051Upgrade overview2012-07-09T06:44:37Z<p>Dougiamas: /* Step 3: Replace your old Moodle code with new Moodle 2.2 code */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99050Upgrade overview2012-07-09T06:43:00Z<p>Dougiamas: /* Step 1: Make sure that your server can run Moodle 2.2 */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99049Upgrade overview2012-07-09T06:39:31Z<p>Dougiamas: /* Step 3: Replace your old Moodle code with new Moodle 2.2 code */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99048Upgrade overview2012-07-09T06:37:37Z<p>Dougiamas: /* Step 3: Replace your old Moodle code with new Moodle 2.2 code */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99047Upgrade overview2012-07-09T06:33:44Z<p>Dougiamas: /* Step 2: Be prepared for failure */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" 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 > Site administration > 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99046Upgrade overview2012-07-09T06:30:01Z<p>Dougiamas: /* Step 2: Be prepared for failure */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" if there's an issue with your data or some custom code you've added.<br />
<br />
===A test install===<br />
<br />
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===<br />
<br />
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 > Site administration > 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrade_overview&diff=99045Upgrade overview2012-07-09T06:28:32Z<p>Dougiamas: /* Step 2: Backup everything */</p>
<hr />
<div><span class="small-info-right">''Moodle 2<br />available now!''</span><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 > Site administration > Server > 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 "roll back" if there's an issue.<br />
<br />
===A test install===<br />
<br />
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===<br />
<br />
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 > Site administration > 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>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Chat_settings&diff=98610Chat settings2012-06-20T03:41:00Z<p>Dougiamas: /* Chat server daemon */</p>
<hr />
<div>{{Chat}}<br />
<br />
==Chat administration==<br />
===Adding a Chat to your course===<br />
<br />
*With the editing turned on,in the section you wish to add your chat, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu )and choose ''Chat''<br />
<br />
==Course settings==<br />
[[File:Chatsetup.png]]<br />
<br />
<br />
===Name of this chat room===<br />
*Whatever you type here will form the link learners click on to enter the chat so it is helpful to give it a name that suggests its purpose - for example "Student council discussion" or "Field trip planning meeting". <br />
===Introduction text===<br />
<br />
Type the description of the chat here. Include precise instructions for students regarding the subject of the chat. There is also an option to display the chat description on the course page below the link to the activity.<br />
<br />
===Next chat time===<br />
<br />
*The day and hour of the next chat session. This will appear in the calendar so students know the schedule but it doesn't stop them accessing the chatroom at any other time.<br />
*If you don't want them in the chatroom at other times, then hide it (with the eye icon) or use [[Conditional activities]] to restrict access.<br />
*If you don't wish to schedule chat times then ignore this and choose from the next settings.<br />
<br />
'''Note:'''For courses involving users across different time zones, it is useful to know that the time you set here will be adjusted to match the time zone of the user viewing it.<br />
<br />
===Repeat sessions===<br />
<br />
*There are four options for scheduling future chat sessions: <br />
<br />
# '''Don't publish any chat times'''- there are no set times and students are welcome to chat at any time. <br />
# '''No repeats - publish the specified time only'''- only the Next chat time will be published. This could be used to schedule special events or meetings or simply to help learners identify a common time in which they can expect to find other learners in the chat room.<br />
# '''At the same time every day'''- Daily chats are useful for scheduling daily office hours or work sessions with learners.<br />
# '''At the same time every week'''--This setting will schedule a chat for the same day and time every week, which could be useful for instance for meeting and reviewing key ideas and questions related to the week’s content/assessment. <br />
<br />
===Save past sessions===<br />
<br />
*Choose from the dropdown how many days to save - or save everything by selecting ''Never delete messages''<br />
*If you have any concerns about discussions that might take place in your chat room, you may want to keep transcripts te check the suitablility of what is discussed. If your learners are using the chatroom to collaborate on a group project you won't want to delete the messages until the project is complete.<br />
<br />
===Everyone can view past sessions===<br />
<br />
*Decide here whether or not allow everyone to view past chat sessions. (Teachers can always view past sessions)<br />
<br />
===Other settings===<br />
There are the usual [[Common module settings]] and - if admin has enabled them - the Restrict access settings [[Conditional activities]].<br />
<br />
<br />
===Locally assigned roles===<br />
<br />
*In ''Settings > Chat administration > Locally assigned roles'' selected users can be given additional roles in the activity, such as the capability to delete chat logs.<br />
<br />
*Role permissions for the activity can be changed in ''Settings > Chat administration > Permissions''.<br />
<br />
==Site administration settings==<br />
<br />
The chat module has additional settings which may be changed by an administrator in ''Settings > Site administration > Plugins > Activity modules > Chat''. They depend on the chat method which has been selected:<br />
<br />
[[File:Chatmethod.png]]<br />
<br />
===Ajax===<br />
*This is the default method. It works everywhere but if many people are chatting it can put a large load on the server. Its particular settings are: <br />
**'''Refresh user list''' - choose the number of seconds after which the user list is refreshed<br />
**'''Disconnect timeout''' - choose the number of seconds after which we detect a user has disconnected.<br />
<br />
===Normal method===<br />
*The particular settings for this method are:<br />
**'''Refresh room''' - choose the number of seconds after which the room is refreshed<br />
**'''Update method''' - choose how to update the chatroom - "Keep alive" or "Stream" strategy. Stream works better but your sever might not support it.<br />
<br />
===Chat server daemon===<br />
*A daemon is a program that runs all the time in the background. In this case it's a PHP script, listening to a particular port on your server, accepting and giving out chat information.If you intend to use the chat activity a lot, then you should consider using a chat server daemon to reduce server load.Its particular settings are:<br />
**Server name<br />
**Server IP address<br />
**Server port<br />
**Max users<br />
<br />
Then you need to start the chat daemon script from the command line:<br />
<br />
cd moodle/mod/chat<br />
php chatd.php --start &<br />
<br />
==Chat capabilities==<br />
<br />
*[[Capabilities/mod/chat:chat|Access a chat room]]<br />
*[[Capabilities/mod/chat:deletelog|Delete chat logs]]<br />
*[[Capabilities/mod/chat:exportparticipatedsession|Export chat session which you took part in]]<br />
*[[Capabilities/mod/chat:exportsession|Export any chat session]]<br />
*[[Capabilities/mod/chat:readlog|Read chat logs]]<br />
*[[Capabilities/mod/chat:addinstance|Add a new chat]]<br />
<br />
[[de:Chat konfigurieren]]<br />
[[fr:Ajouter/modifier un chat]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Template:Repositories&diff=98174Template:Repositories2012-06-04T07:26:39Z<p>Dougiamas: </p>
<hr />
<div><div class="navtrail">[[Main page]] ► [[Managing content]] ► [[Repositories]] ► [[{{PAGENAME}}]]</div><br />
<div class="sideblock right" style="width: 12em;"> <br />
<div class="header">[[Repositories]]</div> <br />
<div class="content"><br />
* [[Managing repositories]]<br />
* [[Upload a file repository|Upload a file]]<br />
* [[Server files repository|Server files]]<br />
* [[Recent files repository|Recent files]]<br />
* [[Private files]]<br />
* [[Google Docs repository|Google Docs]]<br />
* [[Youtube videos repository|Youtube videos]]<br />
* [[Flickr public repository|Flickr public]]<br />
* [[Flickr repository|Flickr]]<br />
* [[Picasa web album repository|Picasa web album]]<br />
* [[URL downloader repository|URL downloader]]<br />
* [[Wikimedia repository|Wikimedia]]<br />
* [[Alfresco repository|Alfresco]]<br />
* [[Amazon S3 repository|Amazon S3]]<br />
* [[Box.net_repository|Box.net]]<br />
* [[Dropbox repository|Dropbox]]<br />
* [[File_system_repository|File system]]<br />
* [[Legacy course files]]<br />
* [[Merlot.org repository|Merlot.org]]<br />
* [[EQUELLA repository|EQUELLA]]<br />
* [[WebDAV repository|WebDAV]]<br />
* [[Repositories FAQ]]<br />
</div><br />
</div><br />
<br />
<includeonly>[[Category:Repositories]]<br />
[[Category:Site administration]]</includeonly><br />
<noinclude>This template will categorize articles that include it into [[:Category:Repositories]] and [[:Category:Site administration]].</noinclude></div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Repositories&diff=98173Repositories2012-06-04T07:25:07Z<p>Dougiamas: /* Additional repositories may be enabled by a site administrator */</p>
<hr />
<div>{{Managing content}}<br />
Repositories in Moodle enable users to upload files, access previously uploaded files and to easily bring content into Moodle from external repositories, such as Flickr or Google Docs. Enabled repositories are available in the [[File picker]].<br />
<br />
==Standard repositories==<br />
<br />
===Repositories enabled by default===<br />
<br />
* [[Upload a file repository|Upload a file]] - you use this for browsing for and uploading a file from your computer or USB.<br />
* [[Server files repository|Server files]] - this give access to files elsewhere on Moodle according to your permissions.<br />
* [[Recent files repository|Recent files]] - the last 50 files you have uploaded, according to the context.<br />
* [[Private files]] - your own personal storage area for files.<br />
* [[Youtube videos repository|Youtube videos]] - search for and display Youtube videos<br />
* [[URL downloader repository|URL downloader]] - download files, images from a particular URL<br />
* [[Wikimedia repository|Wikimedia]] - search for and display media from Wikimedia<br />
<br />
===Additional repositories may be enabled by a site administrator===<br />
<br />
* [[Google Docs repository|Google Docs]] - bring files from your Google docs account<br />
* [[Flickr public repository|Flickr public]] - search for and display images from Flickr<br />
* [[Flickr repository|Flickr]] - search for and display images from your personal Flickr account<br />
* [[Picasa web album repository|Picasa web album]] - search for and display images from your Picasa account<br />
* [[Alfresco repository|Alfresco]] - link to or copy files from Alfresco into Moodle<br />
* [[Amazon S3 repository|Amazon S3]]<br />
* [[Box.net_repository|Box.net]] - bring files in from your Box.net account<br />
* [[Dropbox repository|Dropbox]] - bring files in from Dropbox<br />
* [[File_system_repository|File system]] - access files uploaded to a folder on your server (by, eg FTP)<br />
* [[Legacy course files]] - use the old system from 1.9 of "course files"<br />
* [[Merlot.org repository|Merlot.org]] - bring resources in from Merlot.org<br />
* [[WebDAV repository|WebDAV]] -bring in files using webdav<br />
* [[EQUELLA repository|EQUELLA]] - link to files in an EQUELLA installation<br />
<br />
<br />
Repositories in Moodle 2.0 video:<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=zdrdyev82bU</mediaplayer><br />
<br />
==See also==<br />
<br />
* [[Managing repositories]]<br />
* [[Repositories FAQ]]<br />
* [http://www.somerandomthoughts.com/blog/whitepaper-moodle-2-repositories/ Whitepaper – Moodle 2 Repositories] by ghenrick<br />
* [[:dev:Repository plugins]] developer documentation<br />
<br />
[[Category:Repositories]]<br />
<br />
[[eu:Biltegiak]]<br />
[[de:Repositories]]<br />
[[fr:Dépôts]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=EQUELLA_repository&diff=98172EQUELLA repository2012-06-04T07:20:51Z<p>Dougiamas: Created page with "{{Repositories}} The EQUELLA repository enables users to make aliases (shortcuts) to EQUELLA files. Updating the files in EQUELLA will automatically cause them to update in Mo..."</p>
<hr />
<div>{{Repositories}}<br />
<br />
The EQUELLA repository enables users to make aliases (shortcuts) to EQUELLA files. Updating the files in EQUELLA will automatically cause them to update in Moodle.<br />
<br />
==Capabilities==<br />
<br />
<br />
==See also==<br />
<br />
<br />
{{stub}}</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/repository/equella&diff=98171admin/repository/equella2012-06-04T07:18:23Z<p>Dougiamas: Redirected page to EQUELLA repository</p>
<hr />
<div>#REDIRECT [[EQUELLA repository]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Repositories&diff=98170Repositories2012-06-04T07:18:02Z<p>Dougiamas: /* Additional repositories may be enabled by a site administrator */</p>
<hr />
<div>{{Managing content}}<br />
Repositories in Moodle enable users to upload files, access previously uploaded files and to easily bring content into Moodle from external repositories, such as Flickr or Google Docs. Enabled repositories are available in the [[File picker]].<br />
<br />
==Standard repositories==<br />
<br />
===Repositories enabled by default===<br />
<br />
* [[Upload a file repository|Upload a file]] - you use this for browsing for and uploading a file from your computer or USB.<br />
* [[Server files repository|Server files]] - this give access to files elsewhere on Moodle according to your permissions.<br />
* [[Recent files repository|Recent files]] - the last 50 files you have uploaded, according to the context.<br />
* [[Private files]] - your own personal storage area for files.<br />
* [[Youtube videos repository|Youtube videos]] - search for and display Youtube videos<br />
* [[URL downloader repository|URL downloader]] - download files, images from a particular URL<br />
* [[Wikimedia repository|Wikimedia]] - search for and display media from Wikimedia<br />
<br />
===Additional repositories may be enabled by a site administrator===<br />
<br />
* [[Google Docs repository|Google Docs]] - bring files from your Google docs account<br />
* [[Flickr public repository|Flickr public]] - search for and display images from Flickr<br />
* [[Flickr repository|Flickr]] - search for and display images from your personal Flickr account<br />
* [[Picasa web album repository|Picasa web album]] - search for and display images from your Picasa account<br />
* [[Alfresco repository|Alfresco]] - link to or copy files from Alfresco into Moodle<br />
* [[Amazon S3 repository|Amazon S3]]<br />
* [[Box.net_repository|Box.net]] - bring files in from your Box.net account<br />
* [[Dropbox repository|Dropbox]] - bring files in from Dropbox<br />
* [[File_system_repository|File system]] - access files uploaded to a folder on your server (by, eg FTP)<br />
* [[Legacy course files]] - use the old system from 1.9 of "course files"<br />
* [[Merlot.org repository|Merlot.org]] - bring resources in from Merlot.org<br />
* [[WebDAV repository|WebDAV]] -bring in files using webdav<br />
* [[EQUELLA repository|EQUELLA]]<br />
<br />
<br />
Repositories in Moodle 2.0 video:<br />
<br />
<mediaplayer>http://www.youtube.com/watch?v=zdrdyev82bU</mediaplayer><br />
<br />
==See also==<br />
<br />
* [[Managing repositories]]<br />
* [[Repositories FAQ]]<br />
* [http://www.somerandomthoughts.com/blog/whitepaper-moodle-2-repositories/ Whitepaper – Moodle 2 Repositories] by ghenrick<br />
* [[:dev:Repository plugins]] developer documentation<br />
<br />
[[Category:Repositories]]<br />
<br />
[[eu:Biltegiak]]<br />
[[de:Repositories]]<br />
[[fr:Dépôts]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=admin/repository/equella&diff=98169admin/repository/equella2012-06-04T07:16:54Z<p>Dougiamas: Redirected page to Equella repository</p>
<hr />
<div>#REDIRECT [[Equella repository]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=URL_resource_settings&diff=96807URL resource settings2012-04-09T07:25:27Z<p>Dougiamas: /* Parameters */</p>
<hr />
<div>{{URL}}<br />
==Adding a new URL to your course==<br />
<br />
*You can add link to a website or online file by choosing [[URL]] from the "Add a resource" drop down menu in your course.<br />
*The "Adding a new URL" screen will ask for a link name and a description (which may be required or optional according to the admin settings)<br />
*In the "Content" box you type or paste a copied external weblink. The "Choose a link" button takes them to the file picker where they can choose URLs from online areas such as youtube, Box.net, Picasa, Merlot etc, depending on what admin has allowed.<br />
<br />
[[File:Url.png]]<br />
<br />
==Course administration settings==<br />
===Display options===<br />
<br />
* ''Automatic'' - Make the best guess at what should happen (probably what is wanted 99% of the time).<br />
* ''Embed'' - Show the Moodle page with heading, blocks and footer. Show the title/description of the item and display the file directly in the page as well<br />
* ''Open'' - No Moodle heading, blocks, footer or description - just show the file in the web browser (e.g. shows image, PDF, flash animation, taking up the whole browser window)<br />
* ''In pop-up'' - Same as 'Open', but opens a new browser window to show this file (without the Moodle heading, blocks, etc) - this browser window also does not have all the menus and address bar in it.<br />
<br />
*There are additional options if you enable them via ''Site administration > Plugins > Activity modules > URL'':<br />
<br />
===Advanced Settings===<br />
====Parameters====<br />
<br />
The parameters section allows you to pass internal information as part of the URL.<br />
<br />
This is useful if the URL is actually an interactive web page that takes parameters, and you want to pass something like the name of the current user, for example.<br />
<br />
===Other settings===<br />
There are the usual [[Common module settings]] and the Restrict access settings [[Conditional activities]].<br />
<br />
{{New features}}There is also an option to display the URL description on the course page below the link to the URL. See the screencast [http://www.screencast.com/t/ieLFs7To0e Moodle 2.2 - Show descriptions] for a demonstration by developer Sam Marshall.<br />
<br />
==URL module capabilities==<br />
<br />
There is just one capability - [[Capabilities/mod/url:view|View URL]].<br />
<br />
==Site administration settings==<br />
<br />
The URL module has additional settings which may be changed by an administrator in ''Settings > Site administration > Plugins > Activity modules > URL''.<br />
<br />
===Frame height===<br />
<br />
Here you can specify the height of the top frame (containing the navigation) if you choose the "in frame" display option. Note:If your theme has a large header then the height should be increased to prevent horizontal and vertical scrollbars.<br />
<br />
===Require activity description===<br />
<br />
This setting allows you to turn off the requirement for users to type something into the description box.<br />
<br />
===Password===<br />
<br />
Here you can add a password that will connect your users to a secure site. [http://moodle.org/mod/forum/discuss.php?d=189842#p826416 See this forum post] for more details.<br />
<br />
===Include role names in parameters===<br />
<br />
===Available display options===<br />
<br />
This setting allows you to add different ways the resource may be displayed on the course page. There are a number of defaults but you can add or change them here. Other display options are;<br />
* ''In frame'' - show the Moodle heading and the file description, with the file displayed in a resizable area below <br />
* ''New window'' - very much like 'in pop-up', but the new window is a full browser window, with menus and address bar, etc.<br />
[[File:Display.gif]]<br />
<br />
===Default values for activity settings===<br />
<br />
Here you can set the defaults for this resource. You can also choose which setting(s) to class as "Advanced". These settings will only then appear if the user clicks "Show advanced" in the settings.</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Main_page&diff=94525Main page2011-12-13T04:48:40Z<p>Dougiamas: </p>
<hr />
<div><div class="navtrail"></div><br />
<div class="frontpagetotal"><p class="note">'''''Welcome to the Moodle 2.2 documentation''' including details of [[:Category:New features|new features in Moodle 2.2]]!''</p><br />
<br /><br />
Note: This wiki is using a new theme designed to help users with smaller screen sizes. Blocks previously in the left column can now be found at the bottom of each page. Feedback on this new layout is welcome - please join the discussion [http://moodle.org/mod/forum/discuss.php?d=191693 Moodle 2.2 documentation and new Moodle Docs theme].<br />
<div class="frontpageblock"><br />
<h2>[[About Moodle]]</h2><br />
*[[Philosophy]]<br />
*[[Pedagogy]]<br />
*[[Moodle site - basic structure]]<br />
*[[Moodle key terms]]<br />
*[[About Moodle FAQ]]<br />
<br />
<h2>[[Installation]]</h2><br />
*[[Installing Moodle]]<br />
*[[Installation Quickstart]]<br />
*[[Upgrading]]<br />
*[[Upgrading to Moodle 2.2]]<br />
*[[Installing plugins]]<br />
*[[Installation FAQ]]<br />
*[[Upgrading FAQ]]<br />
<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing a Moodle site]]</h2><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 />
*[[Developer tools]]<br />
*[[Web services]]<br />
*[[Moodle for mobile]]<br />
*[[Community hubs]]<br />
*[[More features]]<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing a Moodle course]]</h2><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 />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing content]]</h2><br />
* [[Working with files]]<br />
* [[Repositories]]<br />
* [[Portfolios]]<br />
* [[Working with media]]<br />
* [[Filters]]<br />
* [[Licences]]<br />
* [[Plagiarism prevention]]<br />
</div><br />
</div><br />
__NOTOC__<br />
<br />
See the full [[Table of Contents]] for more detail.<br />
<br />
For help with Moodle documentation features see [[Help:Contents]].</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Main_page&diff=94524Main page2011-12-13T04:46:41Z<p>Dougiamas: </p>
<hr />
<div><div class="navtrail">Click on the 2.2 logo at any time to return to this page</div><br />
<div class="frontpagetotal"><p class="note">'''''Welcome to the Moodle 2.2 documentation''' including details of [[:Category:New features|new features in Moodle 2.2]]!''</p><br />
<br /><br />
Note: This wiki is using a new theme designed to help users with smaller screen sizes. Blocks previously in the left column can now be found at the bottom of each page. Feedback on this new layout is welcome - please join the discussion [http://moodle.org/mod/forum/discuss.php?d=191693 Moodle 2.2 documentation and new Moodle Docs theme].<br />
<div class="frontpageblock"><br />
<h2>[[About Moodle]]</h2><br />
*[[Philosophy]]<br />
*[[Pedagogy]]<br />
*[[Moodle site - basic structure]]<br />
*[[Moodle key terms]]<br />
*[[About Moodle FAQ]]<br />
<br />
<h2>[[Installation]]</h2><br />
*[[Installing Moodle]]<br />
*[[Installation Quickstart]]<br />
*[[Upgrading]]<br />
*[[Upgrading to Moodle 2.2]]<br />
*[[Installing plugins]]<br />
*[[Installation FAQ]]<br />
*[[Upgrading FAQ]]<br />
<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing a Moodle site]]</h2><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 />
*[[Developer tools]]<br />
*[[Web services]]<br />
*[[Moodle for mobile]]<br />
*[[Community hubs]]<br />
*[[More features]]<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing a Moodle course]]</h2><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 />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing content]]</h2><br />
* [[Working with files]]<br />
* [[Repositories]]<br />
* [[Portfolios]]<br />
* [[Working with media]]<br />
* [[Filters]]<br />
* [[Licences]]<br />
* [[Plagiarism prevention]]<br />
</div><br />
</div><br />
__NOTOC__<br />
<br />
See the full [[Table of Contents]] for more detail.<br />
<br />
For help with Moodle documentation features see [[Help:Contents]].</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=MediaWiki:Sidebar&diff=94445MediaWiki:Sidebar2011-12-09T04:57:23Z<p>Dougiamas: </p>
<hr />
<div>* Navigation<br />
** mainpage|mainpage<br />
** Table_of_Contents|Table of contents<br />
** recentchanges-url|recentchanges<br />
** Special:Search|Search<br />
<br />
* More docs<br />
** https://docs.moodle.org/21/en|Moodle Docs 2.1<br />
** https://docs.moodle.org/20/en|Moodle Docs 2.0<br />
** https://docs.moodle.org/19/en|Moodle Docs 1.9<br />
** https://docs.moodle.org/dev/Main_Page|Developer Docs<br />
** https://docs.moodle.org/overview/|Other languages<br />
<br />
SEARCH</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Upgrading_to_Moodle_2.2&diff=94059Upgrading to Moodle 2.22011-11-24T08:32:19Z<p>Dougiamas: /* Before upgrading please... */</p>
<hr />
<div>{{Installing Moodle}}<br />
{{Moodle 2.2}}You can upgrade to Moodle 2.2 from Moodle 2.1, 2.0 or 1.9. If you are upgrading from 1.9, please read the [https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to Moodle 2.0] page too. If you are using an earlier version of Moodle, you must upgrade to the latest Moodle 1.9.x first.<br />
<br />
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''<br />
<br />
==System requirements==<br />
<br />
* PHP must be '''5.3.2''' or later<br />
** Required PHP extensions: iconv, curl, ctype, zip, simplexml, spl, pcre, dom, xml, json<br />
** Required PHP memory_limit at least 40MB (64MB or more recommended if you have a choice)<br />
* Databases should be one of the following:<br />
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)<br />
** PostgreSQL 8.3 or later<br />
** Oracle 10.2 or later<br />
** MS SQL 2005 or later<br />
* Any standards-supporting browser from the past few years, for example:<br />
** Firefox 3 or later <br />
** Safari 3 or later <br />
** Google Chrome 4 or later<br />
** Opera 9 or later<br />
** MS Internet Explorer 7 or later<br />
<br />
Note: The above system requirements are unchanged from Moodle 2.1.<br />
<br />
==Before upgrading please... ==<br />
<br />
'''NOTE''': The upgrade process will irreversibly modify the contents of your database '''and''' your moodledata file storage area. If something goes wrong you '''cannot''' go back. It is vital that you take good backups of both moodledata and the database in case you have problems with the upgrade. If you are not sure how see [[Site backup]] or ask in the moodle.org forums (explaining what your operating system is). <br />
<br />
* Read the [[:dev:Moodle 2.2 release notes]]<br />
* Always check your site to make sure it meets all system requirements for 2.2 in ''Settings > Site administration > Server > [[Environment]]''<br />
* '''Do a full database backup!'''<br />
* '''Do a full moodledata backup'''<br />
* '''Check your backups carefully'''<br />
* Remember to purge PHP cache if using any PHP accelerator<br />
<br />
<br />
==Possible issues that may affect you==<br />
<br />
* If you have custom reports, there have been changes that may require (simple) changes to be made to their code.<br />
* Global search has been removed from core as it was broken. A new global search is being written for 2.3.<br />
* Some web service functions have been deprecated. They still work, but check any web service connections you may have to your Moodle for the future.<br />
<br />
==Checking database schema - old sites==<br />
<br />
If your Moodle site has been upgraded through many prior versions it is possible that there will be some problems with the database schema (compared to a fresh 2.0 installation). This may cause the upgrade to fail. If your site started life prior to Moodle 2.0 it is a very good idea to check and correct the database schema before upgrading. See [[Verify Database Schema]]. You should also run the database integrity checks in the XMLDB editor, see the 'See also' for a link to extra scripts to check for other discrepancies.<br />
<br />
==Now upgrade==<br />
<br />
Once you have satisfied the requirements for Moodle 2.2, follow the instructions on the [[Upgrading|upgrading]] page.<br />
<br />
On Linux servers, Moodle 2.2 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.<br />
<br />
==After upgrade==<br />
<br />
The config.php file from your 2.0 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.0 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.2 config-dist.php.<br />
<br />
==See also==<br />
<br />
* [[dev:Moodle 2.2 release notes]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=grade/grading/form/rubric/edit&diff=93896grade/grading/form/rubric/edit2011-11-18T02:29:41Z<p>Dougiamas: Redirected page to Rubrics</p>
<hr />
<div>#REDIRECT [[Rubrics]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Activities&diff=93600Activities2011-11-10T09:32:55Z<p>Dougiamas: Descriptive lists better?</p>
<hr />
<div>{{Managing a Moodle course}}<br />
An activity is a general name for a group of features in a Moodle course. Usually an activity is something that a student will do that interacts with other students and or the teacher. <br />
<br />
There are 13 different types of activities in the standard Moodle that can be found on the "add an activity" drop down menu. <br />
;[[Assignment module|Assignments]]: Enable teachers to grade and give comments on uploaded files and assignments created on and off line<br />
;[[Chat module|Chat]]: Allows participants to have a real-time synchronous discussion<br />
;[[Choice module|Choice]]: A teacher asks a question and specifies a choice of multiple responses<br />
;[[Database activity module|Database]]: Enables participants to create, maintain and search a bank of record entries<br />
;[[Feedback module|Feedback]]: For creating and conducting surveys to collect feedback<br />
;[[Forum module|Forum]]: Allows participants to have asynchronous discussions<br />
;[[Glossary module|Glossary]]: Enables participants to create and maintain a list of definitions, like a dictionary<br />
;[[Lesson module|Lesson]]: For delivering content in flexible ways<br />
;[[Quiz module|Quiz]]: Allows the teacher to design and set quiz tests, which may be automatically marked and feedback and/or to correct answers shown<br />
;[[SCORM module|SCORM]]: Enables SCORM packages to be included as course content<br />
;[[Survey module|Survey]]: For gathering data from students to help teachers learn about their class and reflect on their own teaching<br />
;[[Wiki module|Wiki]]: A collection of web pages that anyone can add to or edit<br />
;[[Workshop module|Workshop]]: Enables peer assessment<br />
<br />
A site may add other activities which have been developed as [[:Category:Contributed code|contributed code]] and found in Moodle.org's [http://moodle.org/plugins Modules and Plugins] database for adding to a site. <br />
<br />
==See also==<br />
<br />
* [[Activities block]] - lists all the activities in a course<br />
* [[Managing activities]] - for administrators</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Main_page&diff=93013Main page2011-10-31T05:31:06Z<p>Dougiamas: </p>
<hr />
<div><div class="frontpagetotal"><p class="note">Welcome to the Moodle 2.0 documentation! ('''[[MoodleDocs:News|STILL NEW AND UNDER CONSTRUCTION]]'''...) </p><br />
<div class="frontpageblock"><br />
<h2>[[About Moodle]]</h2><br />
*[[Philosophy]]<br />
*[[Pedagogy]]<br />
*[[Moodle site - basic structure]]<br />
*[[Moodle key terms]]<br />
*[[About Moodle FAQ]]<br />
<br />
<br />
<br />
<h2>[[Installing Moodle]]</h2><br />
*[[Upgrading]]<br />
*[[Installing plugins]]<br />
*[[Installation FAQ]]<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing a Moodle site]]</h2><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 />
*[[Developer tools]]<br />
*[[More features]]<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing a Moodle course]]</h2><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 />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing content]]</h2><br />
* [[Working with files]]<br />
* [[Repositories]]<br />
* [[Portfolios]]<br />
* [[Working with media]]<br />
* [[Filters]]<br />
* [[Licences]]<br />
* [[Plagiarism prevention]]<br />
</div><br />
</div><br />
__NOTOC__<br />
<br />
'''See the full [[Table of Contents]] for more detail'''<br />
<br />
''' For help with Moodle documentation features see [[Help:Contents]].'''<br />
<br />
'''Join a [http://moodle.org/mod/forum/view.php?id=5838 community discussion] about Moodle documentation'''</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=CVS_for_Administrators&diff=92141CVS for Administrators2011-10-18T07:25:43Z<p>Dougiamas: </p>
<hr />
<div>{{Note|<br />
Note that Moodle development now takes place using the [[Git]] version control system. You may find it better to read [[Git for Administrators]] than this page if you want to use Git. However, CVS is still the easiest way to do it on many servers, and we will continue providing CVS mirrors of the Moodle code for the foreseeable future.<br />
}}<br />
<br />
The [http://cvs.moodle.org/ CVS archive] contains all the source code for Moodle. You can use a CVS program to extract versions ranging from the most stable release to the most cutting-edge development version. CVS can be an extremely convenient way of maintaining a Moodle server.<br />
<br />
[[Image:Cvstree.png|CVS tree]]<br />
<br />
Developers may have selective write access to the Moodle CVS archive (see [[CVS for Developers]] for details about how to do this). However, most people only need read-only access, so they can just connect to one of the mirrors using '''anonymous CVS''' as described below. There can however currently be a delay of up to 1 hour between the time a developer commits changes to developer CVS and the time it becomes available on anonymous CVS. <br />
<br />
==CVS Servers==<br />
<br />
Please choose the closest CVS mirror server to you from this list:<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
|'''Country'''<br />
|'''Server'''<br />
|'''Provided by'''<br />
|-<br />
|EU<br />
|'''eu.cvs.moodle.org'''<br />
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]<br />
|-<br />
|ES<br />
|'''es.cvs.moodle.org'''<br />
|[http://www.mondragon.edu/ Mondragon Unibertsitatea] In case of trouble, contact [mailto:iarenuno@eteo.mondragon.edu iarenuno@eteo.mondragon.edu] or [mailto:iarenaza@escomposlinux.org iarenaza@escomposlinux.org]<br />
|-<br />
|UK<br />
|'''uk.cvs.moodle.org'''<br />
|[http://www.open.ac.uk/ The Open University] In case of trouble, contact [mailto:r.t.c.norfor@open.ac.uk Rod Norfor] or [mailto:d.a.woolhead@open.ac.uk Derek Woolhead]<br />
|-<br />
|US<br />
|'''us.cvs.moodle.org'''<br />
|San Francisco State University, Academic Technology ([http://www.sfsu.edu/ SFSU]). In case of trouble, contact [mailto:ilearn@sfsu.edu iLearn support]<br />
|-<br />
|US<br />
|'''us2.cvs.moodle.org'''<br />
|[http://www.contractorsinstitute.com The Contractors Institute] pserver and viewvc. In case of trouble contact [mailto:cvs@contractorsinstitute.com network support].<br />
|}<br />
<br />
Replace the SERVER.cvs.moodle.org in the instructions below with the server you chose above!<br />
<br />
For up-to-date alerts about planned or unplanned outages on any of these servers subscribe to the [http://lists.moodle.org/info/outages Moodle Outage mailing list]. See [http://moodle.org/stats/network.php moodle.org/stats/network.php] for server availability.<br />
<br />
(If you would like to contribute to the project by running a mirror, please see [[How to set up a CVS mirror]])<br />
<br />
==Moodle versions and CVS branches==<br />
<br />
CVS stores every version of Moodle there has ever been. Versions are organised into branches as in the diagram at the top of this page. There is one branch for each series of stable releases, so the 1.9.x releases all come from the MOODLE_19_STABLE branch.<br />
<br />
Along that branch, each actual release is marked with a tag. For example the Moodle 1.9 release is tagged MOODLE_19, and the 1.9.1 release is MOODLE_191. The latest 1.9.x+ weekly build is always tagged MOODLE_19_WEEKLY.<br />
<br />
If you want Moodle 2.0, check out MOODLE_20_WEEKLY.<br />
<br />
The latest development version is what all the stable branches branch away from. It is sometimes called HEAD or TRUNK. Use with caution.<br />
<br />
As explained below you when you do a CVS checkout, you choose which version you want.<br />
<br />
==Installing and maintaining Moodle via CVS==<br />
<br />
===From a Unix computer===<br />
<br />
To connect and login for the first time to the CVS server, you can use this command (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):<br />
<br />
cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login<br />
<br />
There is no password - when asked for one, just hit Enter.<br />
<br />
To checkout (download) the entire Moodle code for the first time, use this command to get the latest WEEKLY version (generally the latest, most bug free version):<br />
<br />
cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P -r MOODLE_19_WEEKLY moodle<br />
<br />
Or the latest development version - sometimes called HEAD - (not for production use):<br />
<br />
cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P moodle<br />
<br />
Or the modules in Contrib<br />
<br />
cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co contrib<br />
<br />
Later, to update your local copy of Moodle to the current version in CVS you just need to go into your local Moodle directory and type:<br />
<br />
cvs update -dP<br />
<br />
To update your local copy of Moodle to a new version (e.g. from 1.8+ to 1.9), go into your local Moodle directory and type:<br />
<br />
cvs update -dP -r MOODLE_19_STABLE<br />
<br />
To update your local copy of Moodle to a version from a specific date (e.g. 4th February 2009), go into your local Moodle directory and type:<br />
<br />
cvs -q update -dP -r MOODLE_19_STABLE -D "4 Feb 2009"<br />
<br />
To update your local copy and to save the log of the process, use the following command instead the previous one:<br />
<br />
cvs update -dP -r MOODLE_19_STABLE | tee upgrade.log<br />
<br />
Then look at the upgrade.log, notably look for lines starting with "C" (conflict):<br />
<br />
grep '^C' upgrade.log<br />
<br />
Conflicts may appear in case you have manually modified your source files. You have to resolve conflicts before using the site. See [[CVS for Developers]] for more details.<br />
<br />
===Changing the directory name===<br />
<br />
By default, the CVS checkout creates a directory on your webserver called 'moodle'. If you want your Moodle installation in a different directory, you can change the name of the directory that it will checkout the files to, by typing the following. This would download the MOODLE_19_STABLE branch into a directory called "mydirectory" (-d mydirectory).<br />
<br />
cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d mydirectory''' -r MOODLE_19_STABLE moodle<br />
<br />
Or the latest development version to a directory called 'moodle-dev':<br />
<br />
cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -P '''-d moodle-dev''' moodle<br />
<br />
You can also change the name of the directory after the files are downloaded, and before you go through the Moodle install process. If you change the name of the directory before install, it will not affect anything during the install or during a CVS update. If you change the name of the directory after an install, you will need to change the config.php to reflect the name change ([[Moodle_migration#Migrating_a_complete_Moodle_site|guidance here]]). It won't affect the CVS update though.<br />
<br />
===Change directory owner===<br />
<br />
Depending on your webserver setup, you may well need to change the owner of the directory to the webserver user. Follow this step if you get permissions error when you try to access the page. For apache:<br />
<br />
chown -R www-data:www-data moodle<br />
<br />
===From a Windows computer===<br />
<br />
To get started with a fresh copy of Moodle, follow the following steps (remember to replace '''SERVER.cvs.moodle.org''' in the instructions below with the mirror server you chose above):[[Image:CVS moodle settings for tortoise CVS.jpg|thumb|Tortoise CVS Screen capture]]<br />
[[Image:Ecran cvs.jpg|thumb|Tortoise CVS (real name) Screen capture]]<br />
# Get TortoiseCVS from [http://www.tortoisecvs.org/ tortoisecvs.org] and install it, then reboot.<br />
# Find or create a new folder somewhere where you want Moodle to be downloaded to.<br />
# Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box. <br />
# Copy this text into the CVSROOT field: <code>:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle</code><br />
#* NOTE - replace "SERVER" with "eu", "es", "uk" or "us" depending on your location.<br />
# Under the "Module" field, type "moodle" to get moodle. (Other options here include"contrib" to get the contrib directory of hacks and addons, or "mysql" to get the optional MySQL Admin module).<br />
#* For the latest STABLE version, click on the "Revision" tab and then check the radio button labelled "Choose branch or tag". From the drop-down menu select MOODLE_18_STABLE.<br />
#* If you don't see the very latest version in the long drop-down list under Branch or tag name, click the Update List button next to it and wait for the list to be updated.<br />
#* For the latest UNSTABLE development version, the radio-button "Use HEAD branch" in the Revision tab should be checked.<br />
# Press the button: "OK" and everything should be downloaded. <br />
<br />
Later, to update your local copy of Moodle to the current version in CVS, just right-mouse-click the folder and choose "CVS Update".<br />
<br />
Note that the enclosing moodle folder is self-contained - you can move it anywhere you like or even rename it.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''NOTE.-''' Admins with a developer account on cvs.moodle.org can connect with their account name, see attached screen shot.<br />
<br />
===From a Mac OS X computer===<br />
You will find useful informations about CVS and Mac OS X in the documentation for the complete installation package Moodle4Mac and for the Mac OS X Server installation. <br />
<br />
Please read [[Complete_Install_Packages_for_Mac_OS_X#How_To_Update_Your_Moodle4Mac | How to update your Moodle4Mac]] or [[Step_by_Step_Installation_on_a_Mac_OS_X_Server#How_to_install_and_update_Moodle_via_CVS | How to install and to update Moodle via CVS]]. It works fine with the Moodle CVS servers.<br />
<br />
===Troubleshooting===<br />
<br />
If you see something like this, make sure that there is not some firewall blocking the port (it's 2401):<br />
<br />
$ cvs -d:pserver:anonymous@us.cvs.moodle.org:/cvsroot/moodle login<br />
Logging in to :pserver:anonymous@us.cvs.moodle.org:2401/cvsroot/moodle<br />
CVS password:<br />
cvs [login aborted]: connect to us.cvs.moodle.org(130.212.64.111):2401 failed: Connection timed out<br />
<br />
<br />
==Switching to a new CVS server==<br />
<br />
If you were ''already'' using CVS and want to switch to a different server, you'll probably need to make a small change so that the control files in your working copy will point to the new mirrors. <br />
<br />
===Switching to a new server on Unix===<br />
<br />
Use a shell command like this to change existing installations to point to the new mirror (UK mirror used in this example):<br />
<br />
'''find . -type f -name Root -print0 | xargs -0 perl -pi -e 's/\@moodle\.cvs\.sourceforge\.net/\@uk\.cvs\.moodle\.org/''''<br />
<br />
It can be run from /home, say, to fix multiple sites at once.<br />
<br />
===Switching to a new server with TortoiseCVS===<br />
<br />
If you were ''already'' using Tortoise CVS on Windows it's tricky, because Tortoise doesn't have any interface for changing the server. http://www.tortoisecvs.org/faq.html#changecvsroot explains it. But basically, <br />
<br />
1) Install WinCVS and launch it. <br />
2) Navigate to and select your Moodle folder. <br />
3) Choose 'Macros'->CVS->Change Root from the menu. <br />
4) Accept (or change) the default for the 'old' server. <br />
5) Type the new server name. OK! <br />
<br />
It takes a few seconds to go through all of the '''cvs''' folders and update the '''root''' files.<br />
<br />
By the way, if you don't want to install WinCVS, another way of doing this is to uninstall your TortoiseCVS client on Windows, then do a regedit to clean up all the tortoisecvs related entries (might not be necessary), then reinstall TortoiseCVS client again (a good reason to upgrade to the most recent version of TortoiseCVS!). I have tested this and it cleared up the original setting of the original anonymous CVS server setting.<br />
<br />
<br />
==See also==<br />
<br />
*[[Git for Administrators]]<br />
*[[Talk:CVS for Administrators]]<br />
*[[Development:CVS_for_developers|CVS for developers]]<br />
*[[Development:Setting up Eclipse]] for step by step instructions for setting up the [http://www.eclipse.org/ Eclipse IDE] for Moodle development, which including how to do the necessary CVS operations<br />
*[[Development:Setting up Netbeans]] step by step instructions for those who prefer the [http://netbeans.org/ NetBeans IDE]. NetBeans comes with integrated CVS support.<br />
* [[Development:Tracking Moodle CVS with git]]<br />
Using Moodle forum discussions:<br />
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]<br />
*[http://moodle.org/mod/forum/discuss.php?d=91891 CVS Updating of 3rd-Party Plug-ins in the Moodle folder itself]<br />
*[http://moodle.org/mod/forum/discuss.php?d=108196 simple question for cvs]<br />
<br />
[[Category:Administrator]]<br />
<br />
[[de:CVS für Administratoren]]<br />
[[fr:CVS pour administrateurs]]<br />
[[ja:管理者用CVS]]<br />
[[ru:CVS для администраторов]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Main_page&diff=92066Main page2011-10-17T04:41:31Z<p>Dougiamas: </p>
<hr />
<div><div class="frontpagetotal"><p class="note">Welcome to the Moodle 2.0 documentation! ('''[[MoodleDocs:News|STILL NEW AND UNDER CONSTRUCTION]]'''...) </p><br />
<div class="frontpageblock"><br />
<h2>[[About Moodle]]</h2><br />
* [[Philosophy]]<br />
* [[Try Moodle]]<br />
* [[Moodle manuals]]<br />
<br />
<br />
<h2>[[Installing Moodle]]</h2><br />
*[[Upgrading]]<br />
*[[Installing plugins]]<br />
*[[Installation FAQ]]<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing a Moodle site]]</h2><br />
* [[Moodle site - basic structure]]<br />
* [[Managing site users]]<br />
* [[Customising appearance]]<br />
* [[Security]]<br />
* [[Site backup & restore]]<br />
* [[Site-wide communication tools]]<br />
* [[Server settings]]<br />
* [[Networking]]<br />
* [[Sitewide reports]]<br />
* [[Web Services|Web services]]<br />
* [[Extending standard Moodle]]<br />
* [[Developer tools]]<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing a Moodle course]]</h2><br />
* [[Creating a course]]<br />
* [[Editing text]]<br />
* [[Activities]]<br />
* [[Resources]]<br />
* [[Blocks]]<br />
* [[Questions]]<br />
* [[Course enrolment]]<br />
* [[Grouping users]]<br />
* [[Tracking progress]]<br />
* [[Reusing activities]]<br />
</div><br />
<div class="frontpageblock"><br />
<h2>[[Managing content]]</h2><br />
* [[Working with files]]<br />
* [[Repositories]]<br />
* [[Portfolios]]<br />
* [[Working with media]]<br />
* [[Filters]]<br />
* [[Licences]]<br />
* [[Plagiarism prevention]]<br />
</div><br />
</div><br />
__NOTOC__<br />
<br />
'''See the full [[Table of Contents]] for more detail'''<br />
<br />
''' For help with Moodle documentation features see [[Help:Contents]].'''<br />
<br />
'''Join a [http://moodle.org/mod/forum/view.php?id=5838 community discussion] about Moodle documentation'''</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Mobile_app&diff=89643Mobile app2011-09-16T06:10:19Z<p>Dougiamas: </p>
<hr />
<div>{{Moodle 2.1}}The official Moodle mobile app for iPhone, developed and maintained by Moodle HQ, is now available for download (free!) from the Apple Online Store:<br />
<br />
http://itunes.apple.com/app/my-moodle/id461289000<br />
<br />
==Requirements==<br />
<br />
* This app only works with Moodle 2.1 or later<br />
* [[Enable mobile web services|Mobile web services must also be enabled]] on the Moodle site.<br />
<br />
This app is not a replacement for the Moodle interface, it just provides you with some useful additional tools.<br />
<br />
<br />
==Adding your Moodle site==<br />
<br />
After downloading the app you are prompted to enter the address of your Moodle site and your username and password.<br />
<br />
[[File:Mobile app add a site.jpg]]<br />
<br />
==Dashboard==<br />
<br />
Functionalities (tasks) are displayed with icons on the home page of the app. <br />
<br />
[[File:Mobile app.jpg]]<br />
<br />
==Upload==<br />
<br />
This functionality allows you to select or capture an image, sound recording or video from your mobile device and quickly post it directly to your "Private files" area in Moodle. If you are offline, the file is saved and can be uploaded later when you are online.<br />
<br />
Once the files are on Moodle, they are then easily accessible whenever you need to insert an image into a forum post, post an assignment or anything else that uses files. <br />
<br />
[[File:Mobile app upload.jpg]]<br />
[[File:Mobile app record audio.jpg]]<br />
<br />
==Participants==<br />
<br />
This feature allows you to see all the courses you are enrolled in, and to browse the contact information for all the users in those courses.<br />
<br />
# You can see photos and descriptions of all people (according to your capabilities and privacy settings etc)<br />
# If they have phone numbers defined, you can call them or send an SMS with a single click.<br />
# If they have email addresses you can send them an email.<br />
# If Moodle messaging is enabled you can also send a private message. <br />
# If notes are enabled and you have the appropriate capability you can add a private note about someone<br />
<br />
==Web==<br />
<br />
The web icon enables you to access the web version of your Moodle site.<br />
<br />
==Help==<br />
<br />
The help icon provides access to the Moodle documentation.<br />
<br />
[[File:Mobile app viewing docs.jpg]]<br />
<br />
==Licensing==<br />
<br />
The Moodle mobile app for iPhone is available for download for free from the iTunes app store (with FULL functionality). However the source code is owned by Moodle Pty Ltd and will not be initially distributed under the GPL. <br />
<br />
On the Moodle mobile app roadmap is an app for Android. This will definitely be GPL and free for download and modification by other developers. This is in keeping with the philosophy of the Android platform and will allow the community to innovate on that platform.<br />
<br />
==See also==<br />
<br />
* [[Mobile Moodle FAQ]]<br />
* [[Enable mobile web services]]<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum]<br />
* Tracker area [http://tracker.moodle.org/browse/MOBILE Moodle for Mobiles]<br />
* Blog post [http://www.somerandomthoughts.com/blog/2011/09/09/official-moodle-mobile-app-for-iphone-released Official Moodle Mobile App for iPhone – Released!]<br />
* [[:dev:Mobile app|Mobile app developer notes]] including the Mobile app roadmap<br />
<br />
[[Category:Mobile]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Community_credits&diff=88889Community credits2011-08-30T07:22:11Z<p>Dougiamas: /* Registered Moodle sites list maintainers */</p>
<hr />
<div>==Particularly Helpful Moodlers==<br />
<br />
Particularly Helpful Moodlers are great examples of what it takes to drive a community like Moodle.<br />
<br />
Not only do they know a lot about using Moodle, and often contribute their time and expertise to the development project itself, but they are also write a lot of useful posts in the moodle.org forums, as determined by the Moodle community when they rate posts.<br />
<br />
===Particularly Helpful Moodlers in Using Moodle===<br />
<br />
Steven A, Ann Adamcik, Ludo (Marc Alier), Gary Anderson, John Andrewartha, Iñaki Arenaza, James Ballard, Gareth Barnard, Gordon Bateson, Miles Berry, Andrea Bicciolo, Steve Bilton, Stan Bogdanov, Jon Bolton, Anthony Borrow, Bernard Boucher, Adriane Boyd, Robert Brenstein, Deb Burdick-Hinton, Bill Burgos, Matt Bury, Chardelle Busch, Matt Campbell, Hubert Chathi, Derek Chirnside, Wen Hao Chuang, Mike Churchward, Scarlet Clark, Paula Clough, Chris Collman, Nicolas Connault, Mary Cooch, E. L. Cooper, Daniele Cordella, Shaun Daubney, Dale Davies, Manuel de la Torre, Gustav W Delius, Luis de Vasconcelos, Hans de Zwart, Emanuel Delgado, David Delgado, Deborah Delin, Martin Dougiamas, Mark Drechsler, Nicolas Dunand, Larry Elchuck, Scott Elliott, Shane Elliott, Richard Enison, Mary Evans, Zbigniew Fiedorowicz, Jeff Forssell, Helen Foster, Colin Fraser, Valery Fremaux, Raymond Fürst, Paul Ganderton, Wade Gemmell, Teresa Gibbison, Matt Gibson, Sharon Goodson, Andreas Grabs, Jenny Gray, Marcus Green, Marc Grober, Amy Groshek, Eric Hagley, Glenys Hanson, Ralf Hilgenstock, Don Hinkelman, Paul Holden, Jason Hollowell, Dan Humpherson, Urs Hunkler, Tim Hunt, Tony Hursh, John Isner, Elena Ivanova, Mark Johnson, Rob Johnson, Ruslan Kabalin, Petr Kalis, Samuli Karevaara, Nadav Kavalerchik, Sean Keogh, Toshihiro Kita, Mauno Korpelainen, Art Lader, Eloy Lafuente (stronk7), Chris Lamb, Martín Langhoff, Ray Lawrence, Penny Leach, Juan Leyva, Chris M, Guillermo M, Patrick Malley, Dan Marsden, Sam Marshall, Nicolas Martignoni, Colin Matheson, Daniel McCloy, Stuart Mealor, Maryel Mendiola, Ron Meske, Janne Mikkonen, Howard Miller, Jonathan Moore, Michelle Moore, Jerome Mouneyrac, David Mudrak, Tom Murdock, Paul Nicholls, Paul Nijbakker, Richard Oelmann, Bente Olsen, Barry Oosthuizen, Randy Orwin, Chad Outten, Michael Penney, Pierre Pichet, Roberto Pinna, Patrick Pollet, Dan Poltawski, Jamie Pratt, Clarence Prudhoe, Bob Puffer, Jonathan R, Frank Ralf, Visvanath Ratnaweera, Ben Reynolds, Joseph Rézeau, Julian Ridden, Thomas Robb, Jonathan Robson, John Rodgers, Koen Roggemans, Geoffrey Rowland, Hartmut Scherer, David Scotson, Peter Seaman, Jeff Sherk, Petr Škoda (škoďák), Darren Smith, Davo Smith, Harry Smith, Lesli Smith, John St, Przemyslaw Stencel, Teemu Sumi, Olumuyiwa Taiwo, Timothy Takemoto, Séverin Terrier, Itamar Tzadok, Jean-Michel Vedrine, Joachim Vogelgesang, Andrew Walker, Jeffery Watkins, John White, Bryan Williams, Ken Wilson, Jon Witts, Jeff Wood, Mike Worth, A. T. Wyatt, Mitsuhiro Yoshida, Lei Zhang<br />
<br />
(List updated 17:45, 10 August 2011 (WST))<br />
<br />
===Moodlers de gran ayuda in Moodle en Español===<br />
<br />
Iñaki Arenaza, Benito Arias, Carlos Bravo Reyes, José de Jesús Elizarrarás Quiroz, Wenceslao Fernandez, Juan Raul Garcia Canet, David Hernandez, Jorge Malaga, Jose Luis Martin Jimenez, Edwin Mudarra, Xavier Paz, Antonio Piedras, Enrique Robredo<br />
<br />
===Moodleurs particulièrement utiles in Moodle en français===<br />
<br />
Dominique Bouillet, Pascal Boulerie, Emilie Bouvrand, Éric Bugnet, Paula Caterino, Mary Cooch, Jérôme Demiaux, Valery Fremaux, Jean Fruitet, Glenys Hanson, Patrice Jan, Laurent Le Cathare, Nicolas Martignoni, Daniel Methot, Julien Morice, Patrick Pollet, Rudy Potdevin, Fred Quay, Joseph Rézeau, Étienne Rozé, Alexandre Scherbyna, Séverin Terrier, Christian Theou<br />
<br />
(Lists updated 20:10, 20 January 2011 (UTC))<br />
<br />
==Moodle.org course facilitators==<br />
<br />
Community discussion in English:<br />
<br />
* [http://moodle.org/course/view.php?id=5 Using Moodle] - Martin Dougiamas, Helen Foster, Eloy Lafuente (stronk7)<br />
* [http://moodle.org/course/view.php?id=55 Moodle Lounge] - Frances Bell, Mary Cooch<br />
* [http://moodle.org/course/view.php?id=33 Moodle Conferences] - Sean Keogh<br />
* [http://moodle.org/course/view.php?id=15 Moodle Exchange] - Paula Clough, Dan Marsden, Maryel Mendiola<br />
* [http://moodle.org/course/view.php?id=32 Moodle for Business Uses] - Ralf Hilgenstock, Stuart Mealor, (previously Chardelle Busch, Bryan Williams)<br />
* [http://moodle.org/course/view.php?id=31 Moodle for Language Teaching] - Anders Berggren, Bob Gettings, Glenys Hanson, Don Hinkelman, Thomas Robb, Mark Stevens, (previously Timothy Takemoto, Matthew Whelpton)<br />
* [http://moodle.org/course/view.php?id=48 Moodle Certification] - Haidee Foxwell, Ralf Hilgenstock, Stuart Mealor<br />
* [http://moodle.org/course/view.php?id=44 Technology and Pedagogy Study Group] - Anders Berggren<br />
* [http://moodle.org/course/view.php?id=17223 Teaching and Learning with Moodle] - Tomaz Lasic and Mary Cooch<br />
<br />
Community discussion in other languages:<br />
<br />
* [http://moodle.org/course/view.php?id=1005 Bangla Moodle] - Biplab Mazumder, Razib Mustafiz, Mashiur Rahman<br />
* [http://moodle.org/course/view.php?id=43 Bulgarian Moodle] - Daniel Denev (previously Snezhina Gileva, Milena Leneva)<br />
* [http://moodle.org/course/view.php?id=46 Dansk Moodle] - Jens Gammelgaard<br />
* [http://moodle.org/course/view.php?id=18 Deutschsprachiges Moodle] - Ralf Hilgenstock, André Krüger, Peter Sereinigg<br />
* [http://moodle.org/course/view.php?id=1008 Farsi Moodle] - Shamim Rezaie<br />
* [http://moodle.org/course/view.php?id=19 Finnish Moodle] - Petri Asikainen, Samuli Karevaara<br />
* [http://moodle.org/course/view.php?id=17219 Hebrew Moodle] - Yaniv Cohen, Nadav Kavalerchik, Roy Yarkoni<br />
* [http://moodle.org/course/view.php?id=997 Icelandic Moodle] - Sigurdur Jonsson<br />
* [http://moodle.org/course/view.php?id=14 Japanese Moodle] - Toshihiro KITA, Haruhiko Okumura, Tatsuya Shirai, Mitsuhiro Yoshida<br />
* [http://moodle.org/course/view.php?id=35 Moodle Brasileiro] - Gilvan Marques, Giovanni Farias (previously Paula de Waal)<br />
* [http://moodle.org/course/view.php?id=24 Moodle em Português] - Jaime Villate<br />
* [http://moodle.org/course/view.php?id=39 Moodle en Català] - Carles Bellver, Joan Queralt<br />
* [http://moodle.org/course/view.php?id=11 Moodle en Español] - Iñaki Arenaza, Benito Arias, Franklin Calle Zapata, Fermin Cueva, Eloy Lafuente (stronk7), Antonio Vicent<br />
* [http://moodle.org/course/view.php?id=20 Moodle en français] - Jérôme Demiaux, Nicolas Martignoni, Séverin Terrier<br />
* [http://moodle.org/course/view.php?id=42 Moodle Euskaraz] - Santurtziko Udal Euskaltegia<br />
* [http://moodle.org/course/view.php?id=17221 Moodle in Cambodia] - Dr.Wim Singhanart<br />
* [http://moodle.org/course/view.php?id=17222 Moodle in Estonian] - Nils Austa, Tõnis Tartes<br />
* [http://moodle.org/course/view.php?id=1009 Moodle in Galician] - Xosé Calvo<br />
* [http://moodle.org/course/view.php?id=49 Moodle in Greece] - Aggelos Panagiotakis<br />
* [http://moodle.org/course/view.php?id=23 Moodle in Italiano] - Andrea Bicciolo, Roberto Pinna<br />
* [http://moodle.org/course/view.php?id=36 Moodle in Thailand] - Dr.Wim<br />
* [http://moodle.org/course/view.php?id=51 Moodle sa Pilipinas] - Roel Cantada<br />
* [http://moodle.org/course/view.php?id=13 Nederlandstalig] - Hans de Zwart, Koen Roggemans<br />
* [http://moodle.org/course/view.php?id=54 Norsk Moodle] - John Harald Gartland<br />
* [http://moodle.org/course/view.php?id=22 Polski Moodle] - Adam Pawelczak<br />
* [http://moodle.org/course/view.php?id=25 Russian Moodle] - Alex Djachenko, Dmitry Pupinin<br />
* [http://moodle.org/course/view.php?id=53 Serbian Moodle] - Bojan Milosavljević<br />
* [http://moodle.org/course/view.php?id=56 Sinhala Moodle] - Rashan Anushka, Harsha Balasooriya<br />
* [http://moodle.org/course/view.php?id=1001 Slovenian Moodle] - Mitja Podreka<br />
* [http://moodle.org/course/view.php?id=26 Svenska Moodle] - Anders Berggren<br />
* [http://moodle.org/course/view.php?id=17 Türkçe Moodle] - Kemal Can, Orçun Madran (previously Ethem Evlice)<br />
* [http://moodle.org/course/view.php?id=45 Vietnamese Moodle] - Dinh Lu Giang (previously Vu Hung)<br />
* [http://moodle.org/course/view.php?id=16 Arabic Moodle] - Dr. Ali Abureesh<br />
* [http://moodle.org/course/view.php?id=1004 தமிழ் (இலங்கை) (ta-LK)] - Sarveswaran Kengatharaiyer<br />
* [http://moodle.org/course/view.php?id=999 தமிழ் Moodle (Tamil)] - Sarveswaran Kengatharaiyer, Nagarajan Vadivel<br />
* [http://moodle.org/course/view.php?id=27 简体中文 Moodle (Chinese)] - Dongsheng Cai<br />
* [http://moodle.org/course/view.php?id=21 한글무들(Korean Moodle)] - Jong-Dae Park<br />
<br />
==Moodle.org moderators==<br />
<br />
Gordon Bateson, Chris Collman, Mary Cooch, Jason Hardin, Don Hinkelman, Tim Hunt, Mauno Korpelainen, Patrick Malley, Dan Marsden, Sam Marshall, Howard Miller, David Mudrák, Dan Poltawski, Joseph Rezeau, Julian Ridden, Petr Škoda (skodak), Ken Wilson, A. T. Wyatt<br />
<br />
(List created 15:07, 1 February 2010 (UTC))<br />
<br />
Note: The above list of moderators may not be complete. Please contact Helen Foster if you know of anyone missing from the list.<br />
<br />
==Credits from the beginning of the project==<br />
<br />
Some names from the beginning of the project include (in the order they were added):<br />
<br />
Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John "Captain" Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker, Antonio Vicent, Ethem Evlice, Chardelle Busch, Miles Berry, Steve Hyndman, Julian Ridden, Ray Lawrence, Jeffery Watkins, Teemu Sumi, Tony Hursh, Andrea Bicciolo, Ralf Hilgenstock, Stuart Mealor, Dan Stowell, Iñaki Arenaza, Bill Burgos, Jonathon Moore, Daryl Hawes, Richard Wyles<br />
<br />
Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please make your suggestions on the [[Talk:Community credits|Community credits page comments]].<br />
<br />
[[Category:Credits]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Usage&diff=88224Usage2011-08-22T04:46:16Z<p>Dougiamas: We no longer manually check the sites.</p>
<hr />
<div>{{About Moodle}}<br />
==Who uses Moodle?==<br />
<br />
Moodle is used by a variety of institutions and individuals, including:<br />
* Universities <br />
* High schools <br />
* Primary schools<br />
* Government departments <br />
* Healthcare organisations <br />
* Military organistions<br />
* Airlines<br />
* Oil companies <br />
* Homeschoolers<br />
* Independent educators<br />
* special educators<br />
<br />
==How many Moodle sites are there==<br />
There are tens of thousands of registered Moodle sites in the sites list that we maintain, however it is impossible to know exactly how many Moodle sites exist because Moodle is open source, free to download and distribute, and doesn't force registration on its users. Very often we find people will not inform us about their sites.<br />
<br />
For up-to-date summary statistics about registered sites browse the [http://moodle.org/stats/ Moodle Statistics] page. Statistics shown on this page are updated daily to provide an accurate summary of collected information.<br />
You can also browse the [http://moodle.org/sites/ Moodle Sites] page, which provides a useful list of registered sites grouped by country for all sites that have chosen to make their information public.<br />
<br />
==How statistics are collected and maintained==<br />
===Registration===<br />
All information collected by moodle.org is from site administrators that have registered their sites with us. For security and privacy reasons registration has been made a manual process that only a site administrator can undertake.<br />
Registration can be undertaken by clicking on the Registration button shown in the site administration block under Notification, and filling out the simple form that then gets sent back to us.<br />
<br />
Sites can update the registration information we hold about them at any time them by repeating the manual process.<br />
It is important to note that because of the manual process information that is collected by moodle.org may be out of date.<br />
<br />
Moodle since version 1.0 has allowed users to register their sites with us, registration being something that we encourage all publicly available sites to do.<br />
You can read more about registration, the registration process and what is collected on the [[Moodle registration|Moodle Registration]] page.<br />
<br />
===Moderation===<br />
To ensure that the statistics that we collect are as accurate as possible there are certain conditions that a registered site has to meet in order to be included into both the statistics and sites pages.<br />
<br />
When a site first registers we check the information about the site to ensure that the URL they have provided is valid and that the email address for the site administrator is a valid email address.<br />
We also at this point sanity check the information being collected to remove obvious test sites.<br />
<br />
===Maintenance===<br />
Like most of the web many sites come and go. Since we strive to maintain accurate statistics we need to check registered sites on a regular basis and clean out old data.<br />
A sophisticated, automated site check process is used to undertake the task of checking every registered site on a weekly basis.<br />
<br />
In checking registered sites every sites is visited by our site check program that then evaluates and scores each site individually based on a collection of 21 defined rules that we have set to identify each and every Moodle release. The score that a site receives determines whether the site remains in the list , is flagged for manual inspection, or marked as invalid.<br />
Any site that fails the evaluation two weeks in a row is then removed from the sites list, and not included in any statistics.<br />
<br />
===Ensuring your site passes the weekly evaluation===<br />
To ensure that your site passes the weekly evaluation check that your site meets the following three criteria.<br />
* Check the URL you registered is the URL of your Moodle registration. We check only the page returned from the URL you registered, we don't dig down into your site, or search any alternatives.<br />
* Check the site is publicly available on the Internet. We can't check your site if it is only available locally, or has been wrapped in any means of authentication.<br />
* Ensure you have content when you register your site. If you don't have any content when you register it is likely we will dismiss your site as a test site. Ensure that you have created at least one course, and three users within your installation before registering.<br />
<br />
If you manage a valid Moodle site that does not meet the above criteria but want to register then please email our volunteer group who are responsible for managing our registration list with your information and information about your site and why you can't register.<br />
Should they choose they can mark your site to be manually checked rather than by the site check program.<br />
<br />
If you want to find out when we last came through you can check your personal site statistics or web server logs and look for page requests on your registered URL that have the following user agent<br />
''moodle.org Link Checker (http://moodle.org/sites/)''<br />
<br />
==See also==<br />
<br />
*[[:Category:Installations|Moodle installation listings]]</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=error/moodle/invalidrecord&diff=86865error/moodle/invalidrecord2011-08-04T09:58:12Z<p>Dougiamas: Created page with "Probably some record was deleted from the database."</p>
<hr />
<div>Probably some record was deleted from the database.</div>Dougiamashttps://docs.moodle.org/24/en/index.php?title=Moodle.org_FAQ&diff=86755Moodle.org FAQ2011-08-02T07:31:11Z<p>Dougiamas: </p>
<hr />
<div>==I tried to make an account on moodle.org but I didn't get an email to confirm my address. Why?!==<br />
<br />
Check your spam folder in your email account.<br />
<br />
==How do I stop getting email from the forums on moodle.org?==<br />
<br />
Visit the Messaging page (look in the settings block under your profile) and disable email<br />
<br />
==What is the best way to ensure my question is answered?==<br />
<br />
See [[Moodle.org forums help]] for advice.<br />
<br />
==Is it OK to post my question in more than one forum?==<br />
<br />
Please choose only the most appropriate forum to post in. Posting the same question in multiple forums is of no benefit. It only fragments the support you receive and makes it more difficult for other users to find the correct information in the future when they do a search. (Source: [[Moodle.org forums Code of Conduct]])<br />
<br />
==I have an idea for a new feature in Moodle. What do I do?==<br />
<br />
See [[Development:New feature ideas]].<br />
<br />
==Where can I report any spam I come across on moodle.org?==<br />
<br />
To report spam found anywhere on moodle.org, such as in the [http://tracker.moodle.org/ tracker] or inappropriate use of Moodle messaging, please use the [http://moodle.org/contact/ moodle.org contact form].<br />
<br />
==How are icons added next to certain users' forum posts?==<br />
<br />
The icons for [http://moodle.org/user/index.php?id=5&group=1 Particularly helpful Moodlers], [http://moodle.org/user/index.php?id=5&group=172 Core Developers] etc. are pictures indicating group membership. Group pictures may be added when [[Create group|creating or updating a group]].<br />
<br />
==What advertising is allowed on moodle.org?==<br />
<br />
See our [[Policy on Advertising]].<br />
<br />
==How can I link automatically to a tracker issue from a forum post?==<br />
<br />
Simply type the issue number e.g. MDL-1234.<br />
<br />
==How can I link automatically to a page in the documentation wiki from a forum post?==<br />
<br />
Type the title of the page in double square brackets. To use words other than the page title as the text of the link, add the pipe "|" divider followed by the alternative text. <br />
<br />
For example, to link to https://docs.moodle.org/en/Upgrading_to_Moodle_1.9 type<br />
<nowiki>[[Upgrading to Moodle 1.9]]</nowiki><br />
or<br />
<nowiki>[[Upgrading to Moodle 1.9|Documentation on upgrading to 1.9]]</nowiki><br />
<br />
To link to a page in a documentation wiki in another language, add an extra pipe "|" divider followed by the language code.<br />
<br />
For example, to link to https://docs.moodle.org/fr/Notes type<br />
<nowiki>[[Notes||fr]]</nowiki><br />
or<br />
<nowiki>[[Notes|Notes documentation in French|fr]]</nowiki><br />
<br />
==What filters are used on moodle.org?==<br />
<br />
See [[Filters used on the Moodle.org forums]] for the full list of standard and contributed filters.<br />
<br />
==Where can I post a Moodle-related job advert?==<br />
<br />
Moodle-related job adverts may be posted in the [http://moodle.org/mod/data/view.php?id=7232 Moodle Jobs database].<br />
<br />
==How do I contact moodle.org?==<br />
<br />
See [http://moodle.org/contact/ Moodle.org Contact] for a list of contact options.<br />
<br />
==Why does Moodle Docs use MediaWiki rather than the Moodle wiki module?==<br />
<br />
MediaWiki was chosen for our documentation wiki because it is designed to be used by thousands of people collaboratively editing a large numbers of pages. It has lots of features, such as inter-language linking, [[MoodleDocs:Templates|templates]], [[Special:Categories|categories]], namespaces and page redirects, which are put to good use in Moodle Docs.<br />
<br />
The [[Wiki module|wiki module]] is designed to be used within a Moodle course. Its features include nine different group options and the option to amend [[Wiki permissions|wiki permissions]] at course or activity level. It has far fewer tools than MediaWiki for handling large numbers of pages.<br />
<br />
==Where can I find the Moodle logo for use in my article?==<br />
<br />
http://moodle.org/logo<br />
<br />
A hi-res photoshop file with layers is available for download from http://moodle.org/images/moodle-logo.psd.zip<br />
<br />
==Where can I post details of the Moodle conference I am organising?==<br />
<br />
Announcements about upcoming Moodle conferences may be posted in the [http://moodle.org/mod/forum/view.php?id=2147 Conference News and Announcements Forum]. It is recommended that you specify a [[Standard_Moodle_tags|standard Moodle tag]] for your event.<br />
<br />
==How do I ask for my account on moodle.org to be deleted?==<br />
<br />
Please complete the [http://moodle.org/contact/ moodle.org contact form].<br />
<br />
==See also==<br />
<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=117601 Clarification on how moodle.org is itself constructed] forum discussion<br />
<br />
[[Category:FAQ]]<br />
[[Category:Moodle.org]]<br />
<br />
[[ja:Moodle.org FAQ]]</div>Dougiamas