https://docs.moodle.org/310/en/api.php?action=feedcontributions&feedformat=atom&user=StuartrmealorMoodleDocs - User contributions [en]2026-04-12T16:12:06ZUser contributionsMediaWiki 1.43.5https://docs.moodle.org/310/en/index.php?title=Custom_SQL_queries_report&diff=138664Custom SQL queries report2020-10-11T04:05:34Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{Sitewide reports}}<br />
Created by The Open University<br />
<br />
This admin report plugin allows Administrators to set up arbitrary database queries to act as ad-hoc reports. Reports can be of two types: either run on demand, or scheduled to run automatically. Other users with the right capability can go in and see a list of queries that they have access to. Results can be viewed on-screen or downloaded as CSV.<br />
<br />
==Installing this report==<br />
<br />
Follow the generic [[Installing plugins]] documentation.<br />
<br />
==Screen shots==<br />
<br />
Here are two example screen shots, showing the two main screens.<br />
<br />
[[Image:Custom_report_list.png|thumb|none|600px|The list of available reports]]<br />
[[Image:Custom_report.png|thumb|none|600px|The results of running one of the reports]]<br />
<br />
(Note, these screen shots are in the OU theme, not the standard Moodle theme, and iCMA is OU-jargon for quiz.)<br />
<br />
==Interface for normal users==<br />
<br />
===List of available queries===<br />
<br />
Users with the report/customsql:view capability can access the list of reports in the admin block. Each query is accessible only to a certain people. There are three levels of access:<br />
* Available to any one who can access the report at all (those with report/customsql:view).<br />
* Available to people who are able to see other system reports (those with moodle/site:viewreports)<br />
* Available to administrators only (those with moodle/site:config)<br />
<br />
When you go to the list, it will only show the queries you have access to. There is a note beside each query saying when it was last run, and how long it took to generate.<br />
<br />
The list shows on-demand and scheduled queries separately.<br />
<br />
===Running an on-demand query===<br />
<br />
To run an on-demand query, click on its name in the list of queries.<br />
<br />
The query will be run, and the results will be displayed as a table. Any URLs in the table will automatically be made into hyperlinks.<br />
<br />
A description of the query may appear above the table.<br />
<br />
The summary of when the query was run and how long it took is shown at the bottom, along with a link to download the CSV file (for example to get the data into Excel) and a link back to the list of all available queries.<br />
<br />
===Viewing the results of scheduled queries===<br />
<br />
Scheduled queries can work in one of two ways. Either each run of the report generates and entire table of reasults, or each run just creates one line of results, and the report builds up a row at a time.<br />
<br />
When you click the name in the list of queries, you get taken to a display of the latest results, just like in the on-demand case.<br />
<br />
However, if each scheduled run generates a complete report, then at the bottom of a page there will be a list of all the previous runs of the report, so that you can go and see how the report changed over time.<br />
<br />
==Interface for administrators==<br />
<br />
Administrators (that is, users with report/customsql:definequeries) see everything that other users see, but with some additions.<br />
<br />
===Additional controls in the staff interface===<br />
<br />
Administrators get shown who each report in the list is available to.<br />
<br />
They also get an edit and a delete icon next to each query.<br />
<br />
There is an '''Add new query button''' at the end of the list of queries.<br />
<br />
When viewing a particular query, Administrators get an edit and a delete link underneath the table of results.<br />
<br />
===Adding or editing a query===<br />
<br />
When you click the '''Add new query button''', you get taken to an editing form that lets you define the query.<br />
<br />
You must give the query a name.<br />
<br />
You can optionally enter a description that is displayed above the results table. You should use this to explain what the results of the query mean.<br />
<br />
You must enter the SQL to generate the results you want displayed. This must be an SQL select statement. You must use the prefix prefix_ for table names. It should not be possible to enter any SQL that would alter the contents of the database.<br />
<br />
You choose who you want the query to be accessible to.<br />
<br />
You choose whether the query should be run on-demand or scheduled weekly or monthly. If the report is scheduled, you can say whether the each run returns one row to be added to a single table, or whether each run generates a separate table.<br />
<br />
When you save the new query, the SQL is checked to make sure that it will execute without errors. If you have said that the report will only return a single row, this is also checked.<br />
After saving the query, if this was a manual query, you are taken to the query results page, so you can see what the results look like. If it was an automatic query or if you cancel the form, you are taken to the list of available queries.<br />
<br />
Editing an existing query uses the same form as for adding a new query, but to change the properties of an existing query.<br />
<br />
Note that at the OU, weeks start on Saturday. If you don't like that, there is a fairly obvious constant to hack at the top of locallib.php.<br />
<br />
===Deleting a query===<br />
<br />
When you click the delete icon or link for a query, you are taken to a confirmation page that shows you SQL of the query you are about to delete. The query is only deleted if you click Yes on the confirmation page.<br />
<br />
After deleting a query, you are taken back to the list of queries.<br />
<br />
==Share your interesting queries here==<br />
<br />
If you come up with any interesting SQL to custom reports, you can share it here.<br />
<br />
=== Students that are in a course where groups are turned on, but have not been assigned to a group yet ===<br />
This query was set to run daily to provide a report of students in a course that uses groups but have not yet been assigned to a group and provide a link to the view to assign them to a group. Teacher/Non-Editing teacher roles are filtered out.<br />
<br />
<code sql><br />
SELECT<br />
DISTINCT u.username, CONCAT( u.firstname, " ", u.lastname ) AS NAME,<br />
ic.shortname AS "Course Code",<br />
CONCAT("%%WWWROOT%%/enrol/users.php%%Q%%id=",ic.id, "&action=addmember&user=", u.id) AS "Link to Add to Group"<br />
FROM<br />
prefix_course ic<br />
JOIN prefix_context con ON con.instanceid = ic.id<br />
JOIN prefix_role_assignments ra ON con.id = ra.contextid AND con.contextlevel = 50<br />
JOIN prefix_role r ON ra.roleid = r.id<br />
JOIN prefix_user u ON u.id = ra.userid<br />
LEFT JOIN prefix_groups_members gm ON u.id = gm.userid<br />
WHERE<br />
ic.visible = 1<br />
AND ic.shortname NOT LIKE '%META%'<br />
AND ic.shortname NOT LIKE '%INOL%'<br />
AND u.username NOT LIKE 'email@domain.com'<br />
AND ic.groupmode <> '0'<br />
AND gm.userid IS NULL<br />
AND r.id NOT IN (3,4)<br />
ORDER BY ic.shortname<br />
</code><br />
<br />
===Quiz attempts in the last week/month===<br />
<br />
Set this up as a scheduled report:<br />
<br />
<code sql><br />
SELECT COUNT(*)<br />
FROM prefix_quiz_attempts<br />
WHERE timefinish > %%STARTTIME%%<br />
AND timefinish <= %%ENDTIME%%<br />
AND preview = 0<br />
</code><br />
<br />
This '''must''' be set up as a '''Scheduled, on the first day of each week''' or '''Scheduled, on the first day of each month''' report, or it will not work.<br />
<br />
===Usage summary===<br />
<br />
This report shows roughly the same usage statistics that are sent to moodle.org when you register your site. The ones that are aggregated at http://moodle.org/stats/. (The only difference is that the registration form does not do AND confirmed = 1 for some reason.<br />
<br />
<code sql><br />
SELECT<br />
(SELECT COUNT(id) FROM prefix_course) - 1 AS courses,<br />
(SELECT COUNT(id) FROM prefix_user WHERE deleted = 0 AND confirmed = 1) AS users,<br />
(SELECT COUNT(DISTINCT ra.userid)<br />
FROM prefix_role_capabilities rc<br />
JOIN prefix_role_assignments ra ON ra.roleid = rc.roleid<br />
WHERE rc.capability IN ('moodle/course:upd' || 'ate', 'moodle/site:doanything')) AS teachers,<br />
(SELECT COUNT(id) FROM prefix_role_assignments) AS enrolments,<br />
(SELECT COUNT(id) FROM prefix_forum_posts) AS forum_posts,<br />
(SELECT COUNT(id) FROM prefix_resource) AS resources,<br />
(SELECT COUNT(id) FROM prefix_question) AS questions<br />
</code><br />
<br />
There are two interesting queries in this blog post [http://tjhunt.blogspot.com/2010/03/when-do-students-submit-their-online.html When do students submit their online tests?].<br />
<br />
===Monthly Usage by Role===<br />
<br />
This report shows a distinct count of users by their role, accessing your site. Each instance of user and role is counted once per month, no matter how many courses they access. We use this to show the total number of students and teachers accessing our site.<br />
<br />
<code sql><br />
SELECT <br />
month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)) AS calendar_month,<br />
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)) AS calendar_year,<br />
prefix_role.name as user_role,<br />
COUNT(DISTINCT prefix_stats_user_monthly.userid) AS total_users<br />
FROM<br />
prefix_stats_user_monthly<br />
Inner Join prefix_role_assignments ON prefix_stats_user_monthly.userid = prefix_role_assignments.userid<br />
Inner Join prefix_context ON prefix_role_assignments.contextid = prefix_context.id<br />
Inner Join prefix_role ON prefix_role_assignments.roleid = prefix_role.id<br />
WHERE prefix_context.contextlevel = 50<br />
AND `prefix_stats_user_monthly`.`stattype` = 'activity'<br />
AND prefix_stats_user_monthly.courseid <>1<br />
GROUP BY month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),<br />
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),<br />
prefix_stats_user_monthly.stattype,<br />
prefix_role.name<br />
ORDER BY <br />
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)), month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),<br />
prefix_role.name<br />
</code><br />
<br />
You must have Statistics turned on to be able to generate any data with this report.<br />
<br />
PostgreSQL version of the Monthly Usage by Role query:<br />
<br />
<code sql><br />
SELECT <br />
extract(month from to_timestamp(prefix_stats_user_monthly.timeend)) AS calendar_month,<br />
extract(year from to_timestamp(prefix_stats_user_monthly.timeend)) AS calendar_year,<br />
prefix_role.name AS user_role,<br />
COUNT(DISTINCT prefix_stats_user_monthly.userid) AS total_users<br />
FROM<br />
prefix_stats_user_monthly<br />
INNER JOIN prefix_role_assignments ON prefix_stats_user_monthly.userid = prefix_role_assignments.userid<br />
INNER JOIN prefix_context ON prefix_role_assignments.contextid = prefix_context.id<br />
INNER JOIN prefix_role ON prefix_role_assignments.roleid = prefix_role.id<br />
WHERE prefix_context.contextlevel = 50<br />
AND prefix_stats_user_monthly.stattype = 'activity'<br />
AND prefix_stats_user_monthly.courseid <>1<br />
GROUP BY extract(month from to_timestamp(prefix_stats_user_monthly.timeend)),<br />
extract(year from to_timestamp(prefix_stats_user_monthly.timeend)),<br />
prefix_stats_user_monthly.stattype,<br />
prefix_role.name<br />
ORDER BY <br />
extract(year from to_timestamp(prefix_stats_user_monthly.timeend)), extract(month from to_timestamp(prefix_stats_user_monthly.timeend)),<br />
prefix_role.name<br />
</code><br />
<br />
===Show all Quiz results across a site===<br />
I'm sure someone will be able to improve upon this, but this is a query that will show Quiz results across a site. --[[User:Stuart Mealor|Stuart Mealor]] 22:07, 9 April 2010 (UTC)<br />
<br />
<code sql><br />
SELECT <br />
prefix_grade_items.itemname,<br />
prefix_grade_items.grademax,<br />
ROUND(prefix_grade_grades.finalgrade, 0) AS finalgrade,<br />
prefix_user.firstname,<br />
prefix_user.lastname,<br />
prefix_user.username<br />
FROM<br />
prefix_grade_grades<br />
INNER JOIN prefix_user ON prefix_grade_grades.userid = prefix_user.id<br />
INNER JOIN prefix_grade_items ON prefix_grade_grades.itemid = prefix_grade_items.id<br />
WHERE (prefix_grade_items.itemname IS NOT NULL)<br />
AND (prefix_grade_items.itemtype = 'mod' OR prefix_grade_items.itemtype = 'manual')<br />
AND (prefix_grade_items.itemmodule = 'quiz' OR prefix_grade_items.itemmodule IS NULL)<br />
AND (prefix_grade_grades.timemodified IS NOT NULL)<br />
AND (prefix_grade_grades.finalgrade > 0)<br />
AND (prefix_user.deleted = 0)<br />
</code><br />
<br />
==See also==<br />
<br />
* [http://moodle.org/mod/forum/discuss.php?d=136484 Custom SQL queries report] forum announcement<br />
* list of [[ad-hoc contributed reports]]<br />
* [http://moodle.org/mod/forum/discuss.php?d=153059 Forum post] with some more useful queries.<br />
* [http://moodle.org/mod/data/view.php?d=13&rid=2884 Modules and plugins database entry]<br />
* [[Configurable_reports|Configurable reports]] block<br />
* [https://www.moodlebites.com/mod/page/view.php?id=9112 Moodle SQL Reporting] online introduction course.<br />
<br />
[[Category:Contributed_code]]<br />
<br />
[[es:Reportes de consultas personalizadas SQL]]<br />
[[fr:admin/report/customsql/index]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Administration_FAQ&diff=133100Administration FAQ2019-02-05T03:23:18Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{Managing a Moodle site}}<br />
<br />
==Common questions==<br />
===How do I find the version of Moodle currently installed?===<br />
See the [[Moodle version]] information on the ''Site Administration > Notifications'' page.<br />
<br />
=== I have forgotten the admin password ===<br />
<br />
First, try using the Forgotten password link (if you have one on your site.) If you don't know the admin username, often it is simply 'admin'.<br />
<br />
It is possible to reset the admin user's password using [[Administration_via_command_line#Reset_user_password|command line tools]] provided with Moodle.<br />
<br />
Failing that, if you can access the database using an administration tool, you can modify a password there. Passwords for all users, including admin, are stored as cryptographic hashes in the table ''mdl_user''. You can manually replace the old hash with md5 value of the new password, it will be upgraded to the strong hash value after the first log-in.<br />
<br />
===How do I prevent users from logging in while I do maintenance?===<br />
<br />
Use one or the other of the two methods for [[Maintenance_mode|Maintenance mode]] to do this.<br />
<br />
===My site is stuck in maintenance mode===<br />
<br />
Sometimes Moodle gets stuck in maintenance mode and you'll see the message "This site is undergoing maintenance and is currently unavailable" despite your attempts to turn-off maintenance mode. <br />
<br />
When you put Moodle into maintenance mode it creates a file called maintenance.html in moodledata/maintenance.html (the site files folder). To fix this try the following:<br />
<br />
* Check that the web server user has write permissions to the moodledata folder.<br />
* Manually delete the maintenance.html file.<br />
<br />
===How can I change the domain name or URL of the Moodle site?===<br />
<br />
The base URL of your site is set in the config.php file setting wwwroot. All dynamic links (e.g. course and activity URLs) are built by prefixing this setting on the fly. These are known as "relative links."<br />
<br />
Your Moodle site may also contain "absolute links" to resources which point to the previous URL, if you or anyone has copy/pasted the links into activities like Pages, or other locations in Moodle. These are text strings just like any text or link to a web site. <br />
<br />
To change such absolute in bulk, Moodle contains a utility called [[Search_and_replace_tool|Search and replace]] to change all the links to the new URL. To change this login as admin and enter http://yoursite.com/admin/tool/replace/index.php in your browser address bar. Fill in your old base url and new base in the boxes and run the utility. <br />
<br />
If you change the domain name of your site, there may be work you need to do on your web server and/or DNS settings as well to configure it to understand the new domain. See [[Moodle_migration|Migration]] for more tips.<br />
<br />
[[File:searchandreplacecommandlinetool_interface_m30.png|Search and replace interface screenshot]]<br />
<br />
=== My log table has disappeared - No logs found! ===<br />
The most likely cause is that the mdl_log table has become corrupted. See the [[How to check your database for corruption]]. NOTE: A new logging system has been i place since Moodle 2.7 as an option. Be sure to check in ''Site administration > Plugins > Logging > Manage log stores'' to see whether you are still using the old style logging, Legacy log, or the Standard log.<br />
<br />
===How do I repair a corrupted Moodle database?===<br />
Typically, you might see an error message like './moodle/mdl_quiz_grades' is marked as crashed and should be repaired. See [[How to check your database for corruption]] for the solution.<br />
<br />
===How do I change spellings like 'enrol' to 'enroll'?===<br />
<br />
This is controlled by your language pack and default language. In this case, you are probably using the default Moodle language pack 'en' which is common (and sometimes specifically Austrialian) spellings. If you need American English, add the en_us language pack and set it as the default.<br />
<br />
== Site policies and settings ==<br />
<br />
=== How do the limits on uploaded files work? ===<br />
<br />
See [[File upload size]] for more information. <br />
<br />
File upload sizes are restricted in a number of ways - each one in the list restricts the following ones.<br />
<br />
1. Not very likely these days (i.e. check if the other settings don't work), there is a setting in Apache 2 which you may need to change. You can change the limit by adding or editing a line in Apache's ''/usr/local/apache2/conf/httpd.conf'' with the upload size in bytes (check your operating system's documentation for the correct location - e.g. under /etc/apache2 is a common alternative):<br />
<br />
LimitRequestBody 10485760<br />
<br />
2. PHP also has limits. If you have access to it they are set in your site-wide '''php.ini''' file. On shared hosting you may be able to set these in a ''.htaccess'' file or a ''php.ini''. You are recommended to check with your hosting company how this works on their systems.<br />
<br />
In a php.ini file the lines will look something like:<br />
<pre><br />
upload_max_filesize 64M<br />
post_max_size 64M<br />
</pre><br />
<br />
...in .htaccess the entries will look like this:<br />
<code><br />
php_value upload_max_filesize 64M<br />
php_value post_max_size 64M<br />
</code><br />
<br />
An .htaccess file usually can be placed in the root of your Moodle install and will affect the whole Moodle. A (non site-wide) php.ini file may need to be copied into all the directories it needs to affect. The following are a good start:<br />
* public_html<br />
* moodle/admin<br />
* moodle/course<br />
* moodle/files<br />
* moodle/repository<br />
* root of your moodledata directory<br />
<br />
Please note that a server re-start may be required for the above changes to take effect.<br />
<br />
3. Moodle has a site-wide limit called maxbytes that may be set in ''Site Administration > Security > Site security settings > Maximum uploaded file size''. The default here is (site limit) which it reads from the php.ini files You can set this lower if you wish for Moodle itself but don't set it lower than the largest possible file you will be uploading<br />
<br />
To find out the server limit setting in php.ini (without server access, just using the Moodle administration interface), see ''Site Administration > Server > PHP info'' (Tip: search for filesize)<br />
<br />
4. You should usually set the default for all newly created courses to something lower than the site limit. This is set in ''Site administration > Courses > Course default settings > Maximum upload size''. Inside each course, this then may be individually set or changed for that course as needed by the usual teacher role in [[course/edit|Course settings]].<br />
<br />
5. Activity modules that can be set to allow students to upload files to them, such as [[Forums]] and [[Assignments]], have their own limits which may be set when adding or editing the activity.<br />
<br />
'''See also'''<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=39625 Detailed instructions to increase the maximum allowed size for uploaded files] forum discussion<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97907 Instructions to increase maximum allowed size on hosted servers] forum discussion<br />
* [[File_upload_size|File Upload Size]] page<br />
* Instructions below on [https://docs.moodle.org/310/en/Administration_FAQ#How_to_change_the_maximum_execution_time How to change the maximum execution time]<br />
<br />
=== How to change upload file size on a Windows localhost===<br />
In a localhost (using a [[Complete install packages for Windows]] on a computer) it is easy to change the uploaded file size to something larger than the default 16M. <br />
<br />
Here is an example of how to change the upload file size to 100M.<br />
*Find ..'''/php/php.ini''' and open it with WordPad by right-clicking -> Open With -> then choose WordPad. <br />
*In this file scroll or do a search on the text "_max_" to find <code>upload_max_filesize = 16M</code> <br />
*Change that line to<br />
upload_max_filesize = 100M<br />
*In the same way, find <code>post_max_size = 16M</code> <br />
*Change that line to<br />
post_max_size = 100M<br />
*Save the file. <br />
<br />
After any changes to the php.ini file you need to restart Apache. So restart xampp and browse to localhost. You should find that the Upload file size in Configuration now reads 100M.<br />
<br />
'''See also'''<br />
<br />
* Instructions below on How to change the maximum execution time<br />
<br />
=== How to change the maximum execution time for file uploads ===<br />
<br />
A side-effect of increasing the file upload limit is that the php scripts may execute beyond the limit set by default (300 seconds/5 minutes). To change this, look for max_execution_time in php.ini and change to something like this:<br />
<br />
max_execution_time = 600<br />
<br />
If you are using Apache and have a .htaccess file to change php settings, add this line to your .htaccess file:<br />
<br />
php_value max_execution_time 600<br />
<br />
Restart your webserver for these changes to take effect, and check that the values have been changed by looking at your phpinfo output in the moodle admin -> environment page.<br />
<br />
==Logging in and out==<br />
===My site is logging users out to quickly===<br />
User login sessions are checked to see if the user is still active, and will log them out after a specific period of idleness. This is set in ''Site administration > Server > Session handling > Timeout''. The default is two hours. Increase it if you need to.<br />
<br />
===Users can not login, they need cookies and debug mentions config.php===<br />
Your site's [[Configuration file|config.php file]] probably has extra lines after '''?>'''. Solution is to delete the last '''?>'''.<br />
<br />
===After using the 'Login as' function, why am I logged out of Moodle?===<br />
This is by design. After using the 'Login as' function, for security reasons you are automatically logged out of Moodle when you return to your normal role. If you login again you will be redirected to the page that you were on previously. <br />
<br />
==Text and Appearance==<br />
===Why do I see <nowiki>[[missing strings]]</nowiki>?===<br />
Double square brackets around text indicate that language strings are missing for that function for that language. This is most common with third-party plugins or for languages that may not have all the strings translated for it yet.<br />
<br />
First update your language packs to the latest versions in ''Site administration > Language > [[Language packs]] > Update all installed language packs''. <br />
<br />
If the missing strings are for a non-standard plugin, try to update that plugin and / or check with that plugin maintainer to see if this is a reported issue. If you have access to the server code, you can check the code for this plugin; language strings are supposed to be contained in a ''lang'' folder within the module or plugin folder. <br />
<br />
Note: after changing language strings you may see a lag in the cache for these to show up. You can force this in ''Site administration > Development > Purge all caches''.<br />
<br />
===Changing text in Moodle===<br />
<br />
The language editing interface in ''Administration > Language > [[Language customisation]]'' enables you to easily change any string, any word or phrase, used on the site. <br />
<br />
The strings are stored per language pack. So if you change them for 'en' (common English), that will not change them for 'en_us' (US English) or any other language. <br />
<br />
You may need to search through several files to find the word or phrase you are looking for. The file moodle.php contains all common site-wide phrases and the admin.php contains many admin phrases. Tip: if you don't know the file the string is in, select ALL the file options to search through.<br />
<br />
Also, these customisations override but do not delete the default language strings but are stored separately in the language folders in your site's moodledata location. <br />
<br />
===My style sheet or other theme changes aren't showing up===<br />
<br />
Browsers usually cache style sheets and so a forced refresh in your browser is required before any changes show up.<br />
<br />
The Moodle server also caches all styles. You can force a refresh of the cache from disk in ''Site Administration>Appearance>Themes>Theme selector'', click "Clear theme caches".<br />
<br />
===How can I change center of the Front Page from course categories to something else?===<br />
<br />
Go to Front Page > Settings and change "Front page" to None all down. Change "Front page items when logged in" to None all down. Ensure that "Include a topic section" is checked. Save changes and return to the front page. Turn editing on, obviously, and you should now see the "Add a resource" and "Add an activity" drop down combo-boxes. Select "Add a resource" and select "Insert a label". You can then edit the label in any way you want to in the WYSYWYG editor.<br />
<br />
===How can I change the initial login screen?===<br />
<br />
Edit one of the language files. ''Site administration > Language> Language customisation'', look in the moodle.php file. Look for ''loginusing'' or ''loginsteps'' or ''loginstepsnone'' string variables.<br />
<br />
===How can I change the initial login screen help?===<br />
<br />
To change or add a help message for the login go to ''Site administration > Plugins > Authentication > Manage authentication.'' Type your help message in there in the'' Instructions'' text box.<br />
<br />
==Errors and Troubleshooting==<br />
<br />
===How do I enable/disable debugging?===<br />
If you are getting a blank or partially complete page, or receive a page that presents a short error message that is not informative enough, you can turn on debugging to learn more details.<br />
<br />
Turning on debugging will let you see what the error message is, which may help you diagnose the problem. Set this in ''Site administration > Development > Debugging'' - see [[Debugging]] for more.<br />
<br />
===Incomplete page displayed when I click "Turn Editing On"===<br />
When you see an incomplete page, it is normally a sign that an error occurred. To find out more, turn on [[Debugging]], and you should see an error message which may help you to diagnose the problem.<br />
<br />
This is usually as a result of an incompatible contributed module or block that you have installed. Follow these steps:<br />
#Follow the module removal instructions in [[Installing contributed modules or plugins]].<br />
#Re-visit your course page and try clicking on the "Turn Editing On" button again. <br />
<br />
If you find an incompatible module or block, please report the problem to the person named as the maintainer in the [https://moodle.org/plugins/ Modules and Plugins database].<br />
<br />
=== Receive error message "a required parameter (id) was missing" when uploading a file or ===<br />
<br />
This message sometimes is generated when attempting to upload a file larger than the upload limit. This can also be caused by user's having more than one login to the same site open in the same browser in different windows or tabs. <br />
<br />
===User gets 'an invalid session key' error===<br />
<br />
A number of things may caused the invalid session key error. The most common is if the person tries to login into the same Moodle site in more than one tab or window in the same browser. That will not work. The fix is to close all those tabs and windows and close and restart the browser. This is almost always a transient issue. The fix is to close and restart the browser, and log back into Moodle.<br />
<br />
If you send someone a URL to something in Moodle, like a course activity or particular page, is may be that the session id key is tacked onto the end of the URL. Simply delete that parameter from the URL.<br />
<br />
===Why is a page blank, or half missing?===<br />
<br />
A blank page, or a page that seems to have half missing, is normally a sign that an error occurred. If (as is recommended on production systems) you have display of error messages turned off, it can be very hard to understand what is going on.<br />
<br />
The solution is to [[Debugging|turn on the debugging options]] temporarily. Then, when you go back to the problem page, you should see the error message. Once you had finished solving the problem, remember to turn debugging off again.<br />
<br />
===How can I fix just one bug, without upgrading my whole site?===<br />
<br />
Suppose:<br />
* You are experiencing a particular bug.<br />
* You have searched in the [http://tracker.moodle.org/ tracker], and found that your problem is MDL-abc, and that it has been fixed in the latest version.<br />
* For some reason, you cannot upgrade your whole site, even though the latest version probably has security fixes.<br />
<br />
Then, how can you get the fix for just this one bug, without upgrading your whole site? Well, if you are prepared to manually patch the code, you can probably get this information from the tracker. Please see [[How to fix just one bug without upgrading]] guide.<br />
<br />
==See also==<br />
<br />
* [[Errors FAQ]]<br />
* [[Installation FAQ]]<br />
* [https://www.moodlebites.com/mod/page/view.php?id=3212 MoodleBites Server Administrator] - completely online course for those wanting to install, setup and maintain a Moodle server, and [https://www.moodlebites.com/mod/page/view.php?id=3209 MoodleBites for Administrators] - for those who want to really understand and manage a Moodle site day-to-day. Both courses are run by [https://www.hrdnz.com HRDNZ] (Certified Moodle Partner since 2006).<br />
<br />
==Any further questions?==<br />
<br />
Please post in the [https://moodle.org/mod/forum/view.php?id=50 General help forum] on moodle.org.<br />
<br />
[[Category:FAQ]]<br />
<br />
[[de:Administration FAQ]]<br />
[[es:FAQ Administración]]<br />
[[fr:FAQ d'administration]]<br />
[[it:FAQ Amministrazione]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Creating_mobile-friendly_courses&diff=133099Creating mobile-friendly courses2019-02-05T02:51:25Z<p>Stuartrmealor: /* Learn more */</p>
<hr />
<div>{{Mobile}}<br />
As more and more students access courses from their smartphones, tablets or other mobile devices, it is increasingly important to ensure your courses are mobile-friendly.<br />
<br />
Encouraging students to install the [https://download.moodle.org/mobile/ official Moodle mobile app] is one way to improve their learning experience. Below are some suggestions for optimising your course materials for students both using the app and accessing Moodle from mobile devices.<br />
<br />
==Setting up your course==<br />
<br />
*Topics or weekly course format is best suited to mobile devices. In topics format, the first section or the highlighted section is shown by default in the app. In weekly format, the current week is shown.<br />
*Don't use orphaned activities or direct links to activities (the links will work but is not the best experience for mobile).<br />
*Site or course blocks are not displayed in the Mobile app, so avoid putting important information in blocks.<br />
*If you have a mix of students accessing the course on mobile and desktop, consider asking your admin to install the [[Moodle Mobile availability plugin]] which restricts items to desktop or mobile users.<br />
<br />
==Course content==<br />
<br />
*Use responsive HTML in pages.<br />
*Use a [[Page resource|page resource]] or [[Book]] instead of downloadable documents where possible.<br />
*Avoid uploading many documents or having numerous, text heavy pages. Think more in terms of short "information-bytes".<br />
*If you include YouTube videos, keep them short and consider providing them for download and offline viewing in a [[Folder resource|folder]]. Not all video formats are supported so add them in different formats. (MP4 is probably the most widely accepted format.)<br />
* For YouTube or Vimeo videos, you may use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example:<br />
<pre><div class="embed-responsive"><video...</pre><br />
*Note that drag and drop questions behave differently in the app. You can't drag images, you need to tap to select and tap to drop.<br />
*Note that if you add YouTube video links or map links as URL resources, they will open automatically in the app.<br />
{|<br />
| [[File:moodlemobile_short_text_intro.png|thumb|Short text for label]]<br />
| [[File:moodlemobile_responsive_html.png|thumb|Responsive HTML]]<br />
| [[File:moodlemobile_youtube_maps_links.png|thumb|Map link]]<br />
|}<br />
* Use only plugins with mobile app support so they can be accessed via the mobile app - see [https://moodle.org/plugins/browse.php?list=award&id=6 Moodle plugins directory: Award: mobile app support].<br />
* If you want to include large audio files in your course, consider including them embedded in a label or page rather than as a file resource. The reason is that embedded files will play even if the screen is locked but files won't play with the screen locked.<br />
<br />
===Media download for offline usage===<br />
<br />
To enable media files, such as video, to be downloaded<br />
<br />
* The file must be uploaded to the course, rather than being linked to (from YouTube, Vimeo etc)<br />
* The file must be small - less than 2MB for 3G users or less than 20MB for WiFi users<br />
<br />
When a page containing the video is viewed (without playing the video), the file will then be downloaded.<br />
<br />
When using Moodle Mobile 3.1 or later with a WiFi connection, when the video is played, the file will be downloaded in the background. The next time the video is played, the downloaded file will be used.<br />
<br />
===Offline activities===<br />
<br />
All the supported activities work offline, although some require specific settings like the quiz module. See [[Moodle Mobile quiz offline attempts]] for more information.<br />
<br />
=== Things to avoid===<br />
<br />
Some activities are not yet fully supported by the mobile app, so find alternatives. See [[Moodle Mobile SCORM player]] for things to avoid in SCORM packages.<br />
<br />
You can find the list of activities supported by the app in the [[Moodle Mobile features]] page.<br />
<br />
==Use the latest stable version of Moodle==<br />
<br />
As indicated in [[Moodle Mobile features]] some features are only available in recent Moodle versions.<br />
<br />
It is recommended to use the latest stable version or, if is not possible to upgrade your site, install the [[Moodle Mobile additional features]] plugin.<br />
<br />
==Notifications and messages==<br />
<br />
Encourage your students to enable mobile notifications so they are alerted about calendar events, forum posts, messages, assignment submissions and so on. Find out more in [[Mobile app notifications]].<br />
<br />
You can also enable mobile notifications for all the users by default via the [[Messaging settings]] default message outputs. Students can disable Mobile notifications within the app.<br />
<br />
==Mobile device considerations==<br />
<br />
The app works better on devices running<br />
* Android 4.4 onwards<br />
* iOs 6 onwards<br />
<br />
In old devices you may find problems related to:<br />
* User interface<br />
* Connection problems (specifically when connecting to sites using https certificates)<br />
* Slowness <br />
<br />
The first version of the app was supported in Windows Phone and Windows 7. This version is not supported any more and it was withdrawn from the Windows Store. Its usage is not advised.<br />
<br />
==Links to open the Moodle app==<br />
<br />
If required, links which open the Moodle app may be provided in the course (for users browsing the site using a mobile device with the app installed).<br />
<br />
Links are of the form <code>moodlemobile://link=https://yourmoodlesite.org/mod/...</code><br />
<br />
For example, the link <code>moodlemobile://link=https://mysite.es/mod/choice/view.php?id=8</code> will open the mobile app and display a choice activity.<br />
<br />
==Learn more==<br />
<br />
* An online course specifically for [https://www.moodlebites.com/mod/page/view.php?id=26980 Moodle mobile design] is run by [http://www.hrdnz.com HRDNZ] (certified Moodle Partner since 2006) specifically focussing on the use of Moodle with mobile devices, and how to best design courses for these environments - including the Moodle app. <br />
* [http://es.slideshare.net/juanleyva/tips-for-creating-moodle-mobile-friendly-courses-sites-moodlemoot-spain-2014 Tips for creating Moodle Mobile friendly courses and sites - MoodleMoot Spain 2014] - Juan Leyva, Mobile app developer, presented this in 2014. While some features have now been updated, the general principles are still useful. <br />
* An open course, about "[http://tempus-efa.proj.ac.il/moodle/course/view.php?id=102 Teaching using Mobile - Best practices]"<br />
* Forum post: [https://moodle.org/mod/forum/discuss.php?d=349160 Try the Moodle Mobile app with a mobile-friendly course].<br />
* [https://docs.moodle.org/dev/Creating_mobile_question_types How to make third party question types work in Mobile] documentation for developers<br />
<br />
[[de:Moodle Mobile - Websites optimieren]]<br />
[[es:Crear sitios amistosos para Moodle Mobile]]<br />
[[fr:Créer des cours pour appareils mobiles]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Themes&diff=128149Themes2017-06-09T00:17:29Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{Site appearance}}<br />
Themes provide a "skin" to completely change the look and feel of your site (or even an individual course).<br />
<br />
*[[Theme settings]]<br />
*[[Standard themes]] including information on changing your theme<br />
*[[Installing a new theme]]<br />
<br />
==See also==<br />
<br />
* [[Themes FAQ]]<br />
* [[Theme credits]] <br />
* [[:dev:Themes]]<br />
* [http://youtu.be/K3MYE8am7M4 Install a New Theme] MoodleBites video on YouTube <br />
* [http://www.moodlebites.com/mod/page/view.php?id=3208 Theme Design online course] MoodleBites 100% online asynchronous and facilitated<br />
<br />
[[Category:Themes]]<br />
<br />
[[es:Temas]]<br />
[[eu:Itxurak]]<br />
[[de:Designs]]<br />
[[fr:Thèmes]]<br />
[[ja:テーマ]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Booking_module&diff=127383Booking module2017-04-10T01:14:52Z<p>Stuartrmealor: /* Credits */</p>
<hr />
<div>'''Booking module for managing course participants (online course or offline course)<br />
<br />
==Features==<br />
<br />
*Max participants<br />
*Waitinglist<br />
*Automatic course subscription<br />
*Confirmation mail<br />
*Download userlist as xls or ods (you can select which custom fields to export)<br />
*Cancellation system<br />
*Subscription period<br />
*Automatic add events to Moodle calendar<br />
*Tags, categories<br />
*Automatic enrol users in groups<br />
*Attachments<br />
*Sending custom message to users<br />
*etc.<br />
<br />
==How to use the booking module==<br />
#General settings:<br />
##Add an activity > Booking<br />
## Give a general name (not your EVENT name), booking text will be shown at the top of page.<br />
## Default booking limit Numbers can be defined at each event page too.<br />
##Time period is very important.<br />
## Yes to email settings<br />
## Policy page is really useful.<br />
## Save and display<br />
## Edit booking option (See No3. in step2)<br />
#Events settings<br />
## Click on the ‘Manage x responses’ link at the top-right corner<br />
## Click on the bottom/latest ‘Edit this booking option’ under ‘Mange column’<br />
##Give an Event name into ‘Booking’ field.<br />
## You can define ‘limit number’ and ‘Restrict time’ here again.<br />
## Looks like you can book for other course, but, I think we can ignore this.<br />
## Description will be shown on the booking table, very important.<br />
## Click on ‘Save and add new’<br />
#Editing<br />
## You can delete a user’s booking<br />
## You can delete an event with all bookings in it.<br />
## You can click on the button ‘Download users as .xls’ to download bookings in spreadsheet for each Event, or click on the button at the bottom of page to get a full list (Great!) <br />
#Permissions:<br />
## Click on the ‘Permissions’ under the ‘Settings’ block.<br />
## At the dropdown menu: ‘Advanced role override’ choose ‘Manager’ (or teacher, or any role)<br />
## At table: Activity: Booking, tick ‘Allow’ Permission to all five lines (or less)<br />
##Save changes<br />
#Bugs<br />
## Fixed all known bugs except:<br />
## At the ‘Edit this booking option’ page. Site admin can select one or more user names and then choose ‘Delete’ under ‘With selected’ dropdown menu. The page will be redirected to a delete page to confirm. But, this not works in IE8. Please reminder users to avoid IE for this function.<br />
#How to add a new booking option<br />
## Go to "Manage XX bookings"<br />
## Click on "Edit booking option", do not change anything and click "Save and add new"<br />
#Special user profile fields<br />
##If you want to have certain information about your users (phone numbers), you can define custom user profile fields in the Site admin settings. You have to make them "required", then users have to fill out the form with the information requested before they can proceed to book a course.<br />
<br />
==CSV import==<br />
Create booking options and add users.<br />
<br />
Fields in CSV file are (must be in this order):<br />
#name - name of booking option<br />
#startdate - start date, 0 for no date<br />
#enddate - end date, 0 for no date<br />
#institution - institution<br />
#institutionaddress - institution address<br />
#teacheremail - teacher email - to match in users table<br />
#useremail - user email to match with user in Moodle<br />
#finished - if user has completed activity<br />
#maxanswers - max. number of participants (default 0)<br />
#maxoverbooking - max. number of places on waiting list (default 0)<br />
#limitanswers - limit the number of participants Help with Limit the number of participants (1 for limiting or 0 to disable)<br />
#location - location ex. room number<br />
<br />
==CSV import - activity completion==<br />
<br />
Fields in CSV:<br />
#OptionID - Option ID <br />
#UserID - User ID<br />
#CourseCompleted - 1 - competed, 0 - not completed<br />
<br />
<br />
*Field delimiter: , (coma)<br />
*Enclosure field: " (quotation mark)<br />
*Escape character: \ (backslash)<br />
*Date parse format - format of startdate and enddate fields.<br />
<br />
==Credits==<br />
* [http://www.edulabs.org/ Edulabs.org]<br />
* [http://www.princic.net/ Andraž Prinčič]<br />
<br />
==See also==<br />
* [http://plugins.moodlebites.com Try the Booking plugin] on http://plugins.moodlebites.com</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Accessibility&diff=127377Accessibility2017-04-07T04:46:56Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{About Moodle}}<br />
<br />
Moodle's goal is to be fully accessible and usable for all users regardless of ability.<br />
<br />
This page describes the current state of accessibility in Moodle as well as our plans for the future.<br />
<br />
== Established practices ==<br />
<br />
Moodle core developers spend a lot of time making sure new developments are accessible. Part of the process when building new code in Moodle is to follow established best practices and part of the process for accepting new code into core is to test pages carefully and gather feedback from experts.<br />
<br />
== Screen-reader support ==<br />
<br />
From Moodle 2.7 onwards, [[:dev:Moodle_2.7_release_notes#Screen_reader_support|supported screen-reader/browser configurations]] are described in release notes.<br />
<br />
== Conformance to standards ==<br />
<br />
The Moodle platform is a complex system with many parts. Its code is always evolving. Modules can be enabled and disabled. The interface can be heavily customised using themes and thousands of settings. Actual content can be produced by any teacher or any student. As such it is impossible to say with 100% certainty whether Moodle or any site based on Moodle is absolutely accessible or not. Accessibility is not a state, it is a process of continuous improvement in response to our users and the wider technical environment.<br />
<br />
=== [http://www.w3.org/TR/WCAG20 WCAG 2.0] ===<br />
<br />
* When deciding how Moodle should present its content for best Web accessibility, the [http://www.w3.org/TR/WCAG20 WCAG 2.0] guidelines is followed.<br />
* We hope to have document here soon discussing how well Moodle meets WCAG 2.0 requirements.<br />
<br />
=== [http://www.w3.org/TR/ATAG20 ATAG 2.0] ===<br />
<br />
* As Moodle is a place to construct content (as well as consume content), we also refer to the [http://www.w3.org/TR/ATAG20 ATAG 2.0] guidelines.<br />
* In Moodle 2.7 a new editor Atto was added that not only helps to improve how everyone can use the editor itself, but also helps to improve the accessibility of the content produced with it.<br />
<br />
=== [http://www.w3.org/TR/wai-aria ARIA 1.0] ===<br />
<br />
* As many parts of the Moodle user interface are dynamic and interactive, we follow the [http://www.w3.org/TR/wai-aria ARIA] recommendations to inform assistive technologies, such as screen-readers.<br />
<br />
=== Section 508 (US) ===<br />
<br />
* As Moodle is used by US Government agencies, the US Section 508 amendment can be relevant to Moodle.<br />
<br />
== Discussions ==<br />
<br />
One of the main places accessibility work is being carried out right now is on the Moodle Accessibility Collaboration Group mailing list, see http://collaborate.athenpro.org/group/moodle/<br />
<br />
There are also many discussion on issues in the [https://tracker.moodle.org/browse/MDL/component/10083/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-issues-panel Moodle Tracker]<br />
<br />
== Known Bugs and issues ==<br />
<br />
This is [https://tracker.moodle.org/issues/?jql=component%20%3D%20Accessibility%20AND%20project%20%3D%20MDL%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC the main list of accessibility issues], organised by priority. This list is always changing.<br />
<br />
== Areas of ongoing development ==<br />
<br />
* [https://tracker.moodle.org/browse/MDL-39663 Filepicker]<br />
* [https://tracker.moodle.org/browse/MDL-41773 Forum]<br />
<br />
== See also ==<br />
<br />
[[dev:Accessibility|Accessibility for Moodle Developers]]<br />
* [http://plugins.moodlebites.com Try the Accessibility plugin] on http://plugins.moodlebites.com<br />
<br />
[[es:Accesibilidad]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Analytics_plugins&diff=127376Analytics plugins2017-04-07T04:44:44Z<p>Stuartrmealor: /* See also... */</p>
<hr />
<div>{{Tracking progress}}<br />
Learning Analytics are any piece of information that can help an LMS user improve learning outcomes. Users include students, teachers, administrators and decision-makers.<br />
<br />
== Moodle Plugins ==<br />
<br />
There are a number of reports, blocks and other plugins for Moodle that provide learning analytics.<br />
<br />
{| class="nicetable"<br />
|-<br />
! Plugin <br />
! Plugin type<br />
! Standard / Additional<br />
! Useful for<br />
! Description<br />
! Reported usage*<br />
|-<br />
| [[:en:Logs|Logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| Filterable log of events<br />
| style="text-align:center;" | 71.4%<br />
|-<br />
| [[:en:Activity_report|Activity]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| View count of activities in course<br />
| style="text-align:center;" | 69.1%<br />
|-<br />
| [[:en:Using_Activity_completion|Activity completion]], see also [[:en:Using_Course_completion|Course completion]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Completion matrix of students and activities<br />
| style="text-align:center;" | 66.3%<br />
|-<br />
| [[:en:Logs|Live logs]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| Automatically refreshing log of events<br />
| style="text-align:center;" | 55.2% <br />
|-<br />
| [[:en:Feedback_activity|Feedback]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| Configurable survey tool<br />
| style="text-align:center;" | 59.5% <br />
|-<br />
| [[:en:Quiz_statistics_report|(Quiz) Statistics]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Student quiz performance report<br />
| style="text-align:center;" | 53.0%<br />
|-<br />
| [[:en:Participation_report|(Course) Participation]]<br />
| Report<br />
| Standard<br />
| Teachers<br />
| Single student's participation in course<br />
| style="text-align:center;" | 49.9%<br />
|-<br />
| [[:en:Survey_module|Survey]]<br />
| Activity<br />
| Standard<br />
| Teachers, Researchers<br />
| Set of standardised educational surveys<br />
| style="text-align:center;" | 45.6%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=mod_questionnaire Questionnaire]<br />
| Activity<br />
| Additional<br />
| Teachers, Researchers<br />
| Configurable survey tool<br />
| style="text-align:center;" | 45.3%<br />
|-<br />
| [[:en:Course_overview_report|Course overview]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| Comparison of participation across multiple courses<br />
| style="text-align:center;" | 45.0%<br />
|-<br />
| [[:en:Course_completion_status_block|Course completion status]]<br />
| Block<br />
| Standard<br />
| Students<br />
| View of student's own completion of activities<br />
| style="text-align:center;" | 41.4%<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_progress Progress Bar]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Time management tool for students with overview for teachers<br />
| style="text-align:center;" | 32.0%<br />
|-<br />
| [[:en:Events_list_report|Events list]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins<br />
| Events that can be monitored/searched in logs<br />
| style="text-align:center;" | 28.6%<br />
|-<br />
| [[:en:Activity_results_block|Activity results block]]<br />
| Block<br />
| Standard<br />
| Students<br />
| Leader-board of results in single activity<br />
| style="text-align:center;" | 26.1%<br />
|-<br />
| [http://moodle.org/plugins/view.php?id=82 Configurable Reports] <br />
([https://docs.moodle.org/29/en/ad-hoc_contributed_reports A list of contributed reports])<br />
| Block ([https://github.com/nadavkav/moodle-report_configurablereports Report] [https://github.com/nadavkav/moodle-filter_crgraph Graphs filter])<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| Report generation and viewing<br />
| style="text-align:center;" | 22.7%<br />
|-<br />
| [[Overview_report|(Gradebook) Overview]]<br />
| Report<br />
| Standard<br />
| Teachers, Students<br />
| View of student grades across activites<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [[Statistics]]<br />
| Report<br />
| Standard<br />
| Admins, Decision-makers<br />
| Daily activity across site<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [[:en:Event_monitoring|Event monitor]]<br />
| Report<br />
| Standard<br />
| Teachers, Admins, Decision-makers<br />
| Proactive, focussed monitor tool<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/report_customsql Ad-hoc database queries]<br />
| Report<br />
| Additional<br />
| Teachers, Admins, Decision-makers<br />
| SQL-based report generation and viewing<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/browse.php?list=set&id=20 Engagement Analytics]<br />
| Block, Report, Activity module<br />
| Additional<br />
| Teachers<br />
| Configurable engagement measurement report and block<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_dedication Course Dedication]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Estimated time online for students<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view.php?plugin=block_graph_stats Graph Stats]<br />
| Block<br />
| Additional<br />
| Teachers, Admins<br />
| Daily visits to site or course<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_gismo GISMO]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Numerous charts of student activity participation<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/view/block_xp Level Up!]<br />
| Block<br />
| Additional<br />
| Students, Teachers<br />
| Incentive-drive participation meter<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [http://moodle.org/plugins/report_forumgraph Forum Graph]<br />
| Report<br />
| Additional<br />
| Teachers<br />
| Graph of forum interactions<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_analytics_graphs Analytics Graphs]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Visualisation of student participation<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/block_heatmap Heatmap]<br />
| Block<br />
| Additional<br />
| Teachers<br />
| Colour-coded indication of activity views on course page<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/local_analytics Analytics]<br />
| Local<br />
| Additional<br />
| Admins, Decision-makers<br />
| Enriched feed to Google Analytics and Pywick<br />
| style="text-align:center;" | N/A<br />
|-<br />
| [https://moodle.org/plugins/logstore_xapi Logstore xAPI]<br />
| Logstore<br />
| Additional<br />
| Admins, Decision-makers, Researchers<br />
| xAPI event stream output<br />
| style="text-align:center;" | N/A<br />
|}<br />
<br />
<nowiki>*</nowiki> Reported usage is drawn from the [http://research.moodle.net/71/1/Plugins%20Usage%20Survey%202015%20Report.pdf Plugins Usage Survey from 2015].<br />
<br />
== Integrations with Moodle ==<br />
<br />
A number of systems integrate with Moodle to provide learning analytics information externally.<br />
<br />
* [http://damos.world/2013/08/30/the-moodle-activity-viewer-mav-heatmaps-of-student-activity/ Moodle Activity Viewer] (MAV) ([https://github.com/damoclark/mav-enterprise Git]), consider [https://moodle.org/plugins/block_heatmap Heatmap] as an alternative<br />
* [http://www.intelliboard.net/ Intelliboard]<br />
* [http://www.lambdasolutions.net/products/lmsreporting/ Zoola (was Analytika)]<br />
* [https://learninglocker.net/ Learning Locker], can be used with [https://moodle.org/plugins/logstore_xapi Logstore xAPI]<br />
* [http://klassdata.com/smartklass-learning-analytics-plugin/learning-analytics-moodle-smartklass/ SmartKlass]<br />
* [http://www.blackboard.com/education-analytics/blackboard-predict.aspx Blackboard Predict]<br />
* [http://melbourne-cshe.unimelb.edu.au/research/edutech/completing-the-loop Completing the loop]<br />
* [https://www.iadlearning.com/ IADlearning] offers institutions and educators a rich set of analytics allowing them to understand the quality of their training content, as well as the quality of the ongoing learning processes.<br />
<br />
== Dimensions of Analytics ==<br />
<br />
Learning analytics are a concept that has been emerging under a number of different names through the past decades. Its origins lie in research in data mining and intelligent tutoring systems. LA tools can be categorised in a number of ways:<br />
<br />
* Descriptive<br />
* Predictive<br />
* Diagnostic<br />
* Prescriptive<br />
<br />
== See also... ==<br />
* [https://moodle.org/mod/forum/view.php?id=8044 Analytics and reporting forum]<br />
* [https://moodle.org/mod/forum/view.php?id=8205 Moodle Research forum]<br />
* [[:dev:Moodle_research|Moodle research page]]<br />
* [[Logging]]<br />
* [[:en:Events_list_report|Events list]]<br />
* [[:dev:Learning_Analytics_Specification|Learning Analytics API specification]]<br />
* [[:dev:Working_Groups#Assessment_Analytics|Assessment Analytics working group details and issues]]<br />
* [[:dev:Event_2|Events specification]]<br />
* [[:dev:Logging_2|Logging specification]]<br />
* [[:dev:reportbuilder/API|Report Builder API specification]]<br />
* Use [https://moodle.org/plugins/filter_generico Generico filter] to display custom DB reports with graphs [https://moodle.org/mod/forum/discuss.php?d=324771#p1334032 Demo / Forums]<br />
* [https://www.jisc.ac.uk/blog/solving-the-ethical-and-legal-issues-around-learning-analytics-a-series-of-podcasts-11-mar-2016 Solving the ethical and legal issues around learning analytics: a series of podcasts]<br />
* [http://plugin.moodlebites.com A number of free Moodle analytics plugins you can try] available on http://plugins.moodlebites.com<br />
<br />
== Presentations ==<br />
* [https://www.youtube.com/watch?v=MHv4vp1hxQc&index=5&list=TLGCVIc9g1-qUMUxOTEwMjAxNg Moodle Analytics Plans I Elizabeth Dalton at MoodleMoot Australia 2016] (video 24m)<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Análisis del aprendizaje]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Installation_FAQ&diff=127360Installation FAQ2017-04-04T01:45:15Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{Installing Moodle}}<br />
== System information needed for Installation problems forum ==<br />
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Consider providing some or all of the following:<br />
* Server Operating System name (version also if possible): <br />
* PHP version (e.g. PHP 5.4.4)<br />
* Database server type and version (e.g. MySQL 5.5.18)<br />
* Browser and version (e.g. Firefox, IE8):<br />
* Moodle version (e.g. 3.0):<br />
* Moodle install type? (New/Upgrade):<br />
* Moodle config.php attached (please remove passwords):<br />
* Phpinfo attached?:<br />
<br />
Make sure you provide a sensible description (never HELP! or URGENT!) and a full description of what you did and what happened. Copy and paste any error messages accurately in full. 'Nothing' is not a symptom, even a blank page is something!<br />
<br />
[[#top|Top]]<br />
<br />
==PHP - is it installed and what version do I have?==<br />
<br />
Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:<br />
<br />
<code php><br />
<?PHP phpinfo() ?><br />
</code><br />
<br />
If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.<br />
<br />
[[#top|Top]]<br />
<br />
<br />
==I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x==<br />
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:<br />
extension=php_intl.dll<br />
in the Dynamic Extensions section of your php.ini file.<br />
<br />
You can also set the error level using:<br />
intl.error_level = E_WARNING <br />
but this is not essential<br />
<br />
If you are using a Linux install, use your system package manager or specify compilation flag.<br />
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl <br />
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl<br />
<br />
This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.<br />
<br />
[[#top|Top]]<br />
<br />
===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===<br />
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:<br />
<br />
Resource Limits<br />
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less. <br />
<br />
Data Handling <br />
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances<br />
<br />
Paths and Directories<br />
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )<br />
and<br />
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)<br />
<br />
File Uploads<br />
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)<br />
<br />
Dynamic Extensions ('''Windows Only''')<br />
{| class="nicetable"<br />
|-<br />
! PHP 5.3.x<br />
|-<br />
|<br />
extension=php_curl.dll<br />
extension=php_gd2.dll<br />
extension=php_gettext.dll<br />
extension=php_intl.dll<br />
extension=php_imap.dll<br />
extension=php_ldap.dll<br />
extension=php_mbstring.dll<br />
extension=php_exif.dll ; Must be after mbstring as it depends on it<br />
extension=php_mysql.dll<br />
extension=php_mysqli.dll<br />
extension=php_openssl.dll<br />
extension=php_pdo_mssql.dll<br />
extension=php_pdo_mysql.dll<br />
extension=php_soap.dll<br />
extension=php_sockets.dll<br />
extension=php_sqlite.dll<br />
extension=php_xmlrpc.dll<br />
extension=php_zip.dll<br />
|}<br />
<br />
These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications. <br />
<br />
One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.<br />
<br />
[[#top|Top]]<br />
<br />
==What & where are Moodle's configuration settings stored?==<br />
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the [[Configuration file]] docs. <br />
[[#top|Top]]<br />
<br />
==Downloading previous releases of Moodle==<br />
<br />
Previous versions of Moodle that are not found on [http://download.moodle.org Moodle downloads] may be downloaded from <nowiki>http://download.moodle.org/stable[version_number]/</nowiki> where [version_number] is the number without a point. For example http://download.moodle.org/stable22/ or http://download.moodle.org/stable27/<br />
<br />
You'll see a directory tree with the files displayed. Click on the one you want and download as normal. If you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.<br />
<br />
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:<br />
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki><br />
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac packages], use either of these URLs (depending on whether you need the Intel or PPC package):<br />
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki><br />
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki><br />
<br />
For details of how to download a particular weekly version, see the post [https://moodle.org/mod/forum/discuss.php?d=346698#p1398162 Looking for VERY specific release of older Moodle].<br />
<br />
[[#top|Top]]<br />
<br />
== How to enable and check PHP error logs==<br />
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[dev:PHP error logs|PHP_error_logs]].<br />
<br />
== "Could not find a top level course" ==<br />
If this appears immediately after you have attempted to install Moodle it almost certainly means that the installation did not complete. A complete installation will ask you for the administrator profile and to name the site just before it completes. Check your logs for errors. Then drop the database and start again. If you used the web-based installer try the command line one. Does your computer definitely have sufficient resource to run Moodle?<br />
<br />
==Email copies are not being sent from my forums==<br />
<br />
You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on. Please refer to the [[Cron|cron instructions]].<br />
<br />
Tips:<br />
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...<br />
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page<br />
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.<br />
* Check your firewall or ask your network administrator. Many mail servers are heavily locked down and you may need permission to send mail through them.<br />
<br />
[[#top|Top]]<br />
<br />
==I can't log in - I just stay stuck on the login screen==<br />
<br />
This may also apply if you are seeing “Your session has timed out. Please login again” or "A server error that affects your login session was detected. Please login again or restart your browser" and cannot log in.<br />
<br />
The following are possible causes and actions you can take (in no particular order):<br />
<br />
* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.<br />
* Check that your hard disk is not full or if your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in. <br />
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory. <br />
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].<br />
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)<br />
* Try deleting cookies on your computer and/or try another browser or another client computer<br />
* In ''Settings > Site administration > Server > Session Handling'', try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser. <br />
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values. <br />
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?<br />
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations. <br />
* Check config.php - it should NOT have any spaces/new lines at the end of code.<br />
* You are using the correct username and password, yes?<br />
<br />
If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it - see [[Administration FAQ]].<br />
<br />
[[#top|Top]]<br />
<br />
==I log in but the login link doesn't change. I am logged in and can navigate freely.==<br />
<br />
Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.<br />
<br />
[[#top|Top]]<br />
==Uploaded files give "File not found"==<br />
<br />
For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.<br />
<br />
This indicates that slash arguments are not enabled on your web server. Please see [[Using slash arguments]] for details.<br />
<br />
[[#top|Top]]<br />
<br />
==Why are all my pages blank?==<br />
<br />
Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (e.g.)<br />
<br />
<code php><br />
$CFG->dirroot = "/var/www/moodle";<br />
</code><br />
<br />
Another reason might be that PHP has not been configured to support MySQL (or whatever other database you are using). This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].<br />
<br />
To determine if database support is your problem, insert this as the second line in your ''config.php'' file<br />
<br />
<code php><br />
phpinfo();<br />
</code><br />
<br />
then reload the web page. Examine the output closely to see if you chosen database is supported. If not, look for a package you are missing.<br />
<br />
[[#top|Top]]<br />
<br />
== Why is a particular page blank or incomplete? ==<br />
<br />
*'''Check your web server log files!!''' <br />
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.<br />
<br />
*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".<br />
<br />
*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.<br />
<br />
*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.<br />
<br />
'''See also''':<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion<br />
<br />
==Installation hangs when setting-up database tables==<br />
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there. <br />
<br />
See [[Unexpected installation halts]] for more about solutions that involve:<br />
*Checking for MySQL limits<br />
*Checking the .htaccess files <br />
*Code customizations issues<br />
*Checking memory limit <br />
*Upgrade incrementally<br />
*Fix fopen function<br />
<br />
[[#top|Top]]<br />
<br />
==Why can't I upload a new image into my profile?==<br />
<br />
If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:<br />
*The permissions associated with the role you are using are preventing you from changing your profile picture.<br />
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > PHP info'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.<br />
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]<br />
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.<br />
<br />
If Moodle thinks GD is not installed, then you will need to '''install the GD library'''. <br />
*On Unix you may need to re-compile PHP with arguments something like this:<br />
<br />
./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd <br />
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf <br />
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars <br />
--enable-versioning --with-zlib<br />
<br />
* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:<br />
extension=php_gd2.dll<br />
<br />
:Windows users should see the [[Installing AMP|installation instructions]] for further help. <br />
<br />
3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.<br />
<br />
'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.<br />
<br />
== Why doesn't my Moodle site display the time and date correctly? ==<br />
<br />
Please check the timezone settings in settings in ''Administration > Site administration > Location > Location settings''.<br />
<br />
== How do I uninstall Moodle?==<br />
<br />
'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:<br />
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):<br />
<pre>sql>DROP DATABASE moodle;</pre><br />
:In the above example replace 'moodle' with the name of the moodle database you created when installing.<br />
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.<br />
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.<br />
<br />
'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:<br />
*Open cmd.exe and navigate to this directory within your installation directory:<br />
<pre>server/mysql/bin</pre><br />
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):<br />
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre><br />
*Enter your database password at the prompt (the default is "" [blank]).<br />
*Enter "y" to confirm the database drop.<br />
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.<br />
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.<br />
<br />
==Migrating Moodle to a new site or server==<br />
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the [[Search and replace tool]], your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.<br />
<br />
[[#top|Top]]<br />
<br />
==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==<br />
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:<br />
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php). <br />
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.<br />
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].<br />
<br />
[[#top|Top]]<br />
==Maximum upload file size - how to change it?==<br />
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].<br />
<br />
If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server. [http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size NGINX] system administrators should also add client_max_body_size=XXX to the "http" section of their nginx main configuration file. ([https://rtcamp.com/tutorials/php/increase-file-upload-size-limit/#change-in-nginx-config see more info])<br />
<br />
For more help see:<br />
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]<br />
*[[Installing_Moodle#Recheck_PHP_settings]]<br />
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]<br />
*[[Site_policies#Maximum_uploaded_file_size]]<br />
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650<br />
<br />
[[#top|Top]]<br />
<br />
==Moodle claims PHP float handling is not compatible==<br />
<br />
The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".<br />
<br />
[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.<br />
<br />
You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.<br />
<br />
Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding <br />
ini_set('precision', 14);<br />
to your config.php file, and report your success in MDL-18253.<br />
<br />
==When upgrading Moodle claims my MySQL database is not UTF8 when I'm sure it is==<br />
<br />
The UTF-8 detection for MySQL databases was finally fixed in Moodle 2.5, some incorrectly configured databases were previously reported as compatible. <br />
<br />
Please note it is not enough to alter the charset and collation of the database, you must fix each text column in each database table!<br />
<br />
Before going any further make sure you understand the difference between character encoding (how text is stored) and collations (the rules for comparing text strings). Collation problems will never cause this error but have a bunch of problems of their own.<br />
<br />
See [[Converting your MySQL database to UTF8]]<br />
<br />
[[#top|Top]]<br />
<br />
== How do I run multiple instances of Moodle without duplicating base code? ==<br />
<br />
See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].<br />
<br />
== What is FreeTDS and how can I use it in my installation? ==<br />
[[Installing MSSQL for PHP|FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.<br />
<br />
== How do I install a plugin? ==<br />
<br />
Please see [[Installing plugins]].<br />
<br />
==I can't enable a plugin on the Plugins overview page because the icon is not clickable==<br />
The open and closed eye icon on the Plugins overview page is simply there to show whether or not a plugin is enabled. You can't edit plugins from this screen. If you wish to enable a plugin, to to the appropriate page for managing the type of plugin you need, for instance ''Settings>Site administration>Plugins>Repositories>Manage repositories'' or ''Settings>Site administration>Plugins>Activity modules>Manage activities.''<br />
<br />
== See also ==<br />
<br />
* [[Errors FAQ]]<br />
* [http://moodle.org/mod/forum/view.php?id=28 Installing and upgrading help forum] on moodle.org<br />
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]<br />
Once your site is installed use these movies to inform your initial site setup;<br />
* [https://youtu.be/6b4bPmScegw MoodleBites for Administrators - Site setup part 1] YouTube movie<br />
* [https://youtu.be/XiHWJEJG8Ow MoodleBites for Administrators - Site setup part 2] YouTube movie<br />
<br />
Installing Moodle in a shared web hosting environment:<br />
* [[Finding_and_Selecting_A_Web_Host|Finding and Selecting a web host]]<br />
<br />
[[Category:FAQ]]<br />
<br />
[[es:FAQ Instalación]]<br />
[[fr:FAQ d'installation]]<br />
[[ja:インストールFAQ]]<br />
[[de:Installation FAQ]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Adding_a_new_course&diff=127359Adding a new course2017-04-04T01:32:26Z<p>Stuartrmealor: /* Screencasts */</p>
<hr />
<div>{{Courses}}<br />
==Adding a course==<br />
<br />
By default a regular teacher can't add a new course. To add a new course to Moodle, you need to have either [[Administrator|Administrator]], [[Course creator|Course Creator]] or [[Manager|Manager]] rights.<br />
<br />
To add a course:<br />
*Go to ''Administration>Site Administration>Courses>Manage courses and categories''<br />
{|<br />
|[[File:26addcourse.png|200px|thumb|Link to add a new course]]<br />
|[[File:26addcourse1.png|200px|thumb|Click New course in the category page on the right]]<br />
|}<br />
<br />
*Click on the category where you want your course to be. For more information see [[Course categories|Course categories]]<br />
*Click the "New course" link<br />
*Enter the [[Course settings|course settings]], and then choose either to "Save and return" to go back to your course, or "Save and display" to go to the next screen.<br />
<br />
[[File:newcoursesavereturn.png]]<br />
<br />
*On the next screen,if you have chosen "Save and display", choose your students/teachers to assign to the course.<br />
<br />
==Deleting a course==<br />
<br />
Teachers cannot delete courses. Managers (i.e. users with a role for which the capability [[Capabilities/moodle/course:delete|moodle/course:delete]] is allowed) can delete courses and [[Course creator|course creators]] can delete courses they have created themselves, but only within 24 hours of creating the course. This is so that courses created by mistake may be deleted without needing to ask an administrator.<br />
<br />
Administrators can always delete courses.<br />
<br />
To delete a course (as an admin or manager):<br />
# Go to ''Administration > Site Administration > Courses > Manage courses and categories''<br />
# Click the course's category and click the course in the screen on the right.<br />
# Click the Delete link.<br />
<br />
{|<br />
|[[File:26coursedelete.png|200px|thumb|center|Deleting a course]]<br />
|}<br />
You can delete multiple courses by: <br />
*Creating a new (temporary) category. You can name it "To be deleted".<br />
*Select and '''move''' the "About to be deleted" courses to that category ("To be deleted").<br />
*Delete the category ("To be deleted") and choose "Delete ALL - cannot be undone".<br />
<br />
There is no user interface for course creators to delete courses they have created; however they can do so by editing the URL of the course from <nowiki>http://yourmoodlesite.net/course/view.php?id=N</nowiki> to <nowiki>http://yourmoodlesite.net/course/delete.php?id=N</nowiki> (replacing 'view' with 'delete').<br />
<br />
==Sorting courses==<br />
Courses may be sorted by an admin or manager from ''Administration>Site administration>Courses>Manage courses and categories.'' <br />
<br />
Courses may be sorted by ascending/descending and by time created.<br />
[[File:coursesort.png|thumb|200px|center|Sorting courses]]<br />
<br />
==Course requests==<br />
<br />
The course request feature can be enabled by an administrator in ''Administration > Site administration > Courses > Course request''.<br />
<br />
An admin can set the default category for course requests, whether users can select a category when requesting a course, and who can receive notification of course requests (from a list of users with the capability [[Capabilities/moodle/site:approvecourse|moodle/site:approvecourse]]).<br />
<br />
A 'Request a new course' button will then appear on the 'All courses' page. The All courses page can be accessed via a link in the [[Courses block]].<br />
<br />
If course requests are enabled, by default all authenticated users can make course requests. See [[Course requester role]] for details of how to restrict users who can make course requests.<br />
<br />
==Bulk course creation==<br />
<br />
For full details on how to bulk create courses and use course templates, see [[Upload courses]].<br />
<br />
# Go to ''Administration > Site Administration > Courses > Upload courses''.<br />
# Upload a CSV file either by dragging and dropping or using the button to select from the File picker.<br />
# Select your import options and click Preview. If the settings are acceptable, click Upload.<br />
<br />
==Course templates==<br />
<br />
It is possible, from ''Administration>Site Administration>Courses>Upload courses'' to specify a course and settings to use as template for future courses.<br />
<br />
Default blocks for new courses can also be configured in config.php.<br />
<br />
===Using an existing course as a template===<br />
<br />
First, create or locate on your Moodle the course you wish to use as a template and make a note of its shortname. A template course might for example have common headings or section summaries or policy agreements used throughout the site for consistency.<br />
<br />
''Note that only the content of the course will be restored; not its settings. Settings are added separately.''<br />
<br />
====Method 1====<br />
<br />
*Create your csv file. See [[Upload courses]] for accepted fields.<br />
*From ''Site administration>Administration>Courses>Upload courses'', add your file.<br />
*Preview it and scroll down to 'Course process'. In the box 'Restore from this course after upload', add the shortname of your template course.<br />
*If you are creating several courses using the same template and you wish them all to have the same settings, you can specify these in the Default course values.<br />
*Upload your csv file.<br />
<br />
{|<br />
|[[File:template1.png|thumb|400px|Adding shortname of template course]]<br />
|<br />
|[[File:26defaultcoursevalues.png|thumb|400|Default course values]]<br />
|}<br />
<br />
====Method 2====<br />
<br />
*All the settings and the chosen template course can be specified in the csv file you create. Use ''templatecourse'' as the field for your chosen template course, and use the course shortname. See [[Upload courses]] for full list of fields you can include.<br />
*Here is an example of a csv file for restoring a course to be used as a template. It specifies for example the theme, language, enrolment method and alternative names for student and teacher.<br />
<br />
<code bash><br />
shortname,fullname,category,newsitems,theme,lang,format,enrolment_1,enrolment_1_role,role_student,role_teacher,templatecourse<br />
Knit,Knitting,2,0,afterburner,fr,topics,manual,student,NewKnitter,MasterKnitter,OMT<br />
</code><br />
*Go to Administration>Site administration>Courses>Upload courses and add your csv file.<br />
<br />
===Using a backup course as a template===<br />
<br />
It is possible during the process of creating courses with a csv file in ''Site administration>Administration>Courses>Upload courses'' to specify and upload a backup file to be used as a template.<br />
<br />
*Create your csv file. See [[Upload courses]] for accepted fields.<br />
*From ''Site administration>Administration>Courses>Upload courses'', add your file.<br />
*Preview it and scroll down to 'Course process'. In the box 'Restore from this file after upload', add the backup file you wish to use as the template.<br />
*If you are creating several courses using the same template and you wish them all to have the same settings, you can specify these in the 'Default course values' section.<br />
*Alternatively, you can specify the course settings (such as format, enrolment methods, language) in the csv file. This method is useful if you wish different courses using the same template to have different settings.<br />
*Upload your csv file.<br />
{|<br />
|[[File:template2.png|thumb|400px|Uploading a template course]]<br />
|}<br />
<br />
==See also==<br />
<br />
===Screencasts===<br />
* [http://youtu.be/MzK2jb-9SwE Bulk course creation]<br />
* [http://youtu.be/19ke-cvhnug MoodleBites for Teachers - Course Settings] YouTube movie <br />
* [https://youtu.be/gpjuudeFP1o MoodleBites for Administrators - Courses] YouTube movie<br />
<br />
===Forum discussions===<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=83830 Hide Courses from some users or students] forum discussion<br />
<br />
[[de:Kurs anlegen]]<br />
[[es:Añadiendo un nuevo curso]]<br />
[[eu:Ikastaroak_%28Kudeatzaileak%29]]<br />
[[fr:Ajouter_un_cours]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Managing_accounts&diff=127358Managing accounts2017-04-04T01:28:18Z<p>Stuartrmealor: </p>
<hr />
<div>{{Managing a Moodle site}}<br />
<br />
An administrator can perform various tasks relating to user accounts in ''Administration > Site administration > Users > Accounts''. The links below provide more information:<br />
<br />
* [[Browse list of users]] - how to search for, find and edit user accounts<br />
* [[Bulk user actions]] - how to message, confirm, download or perform other actions on a large group of users globally<br />
* [[Add a new user]] - how to create one individual user account<br />
* User default preferences - for email display, format and digest type, and for forum auto-subscribe and forum tracking<br />
* [[User profile fields]] - how to create customised profile fields<br />
* [[Cohorts]] - how to create cohorts of users <br />
* [[Upload users]] - how to bulk create new user accounts<br />
* [[Upload user pictures]] - how to bulk upload profile pictures for users<br />
<br />
* [[Additional name fields]]<br />
<br />
==See also==<br />
*[[Accounts FAQ]]<br />
*[https://youtu.be/zHpSDcxM6-A MoodleBites for Administrators - Users] YouTube movie<br />
<br />
[[Category:Accounts]]<br />
<br />
[[de:Nutzerverwaltung]]<br />
[[es:Gestionando cuentas]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Grade_settings&diff=127357Grade settings2017-04-04T01:25:57Z<p>Stuartrmealor: </p>
<hr />
<div>{{Grades}}<br />
==Course grade settings==<br />
<br />
[[File:grade settings.PNG|thumb|Course grade settings]]Course grade settings determine how the gradebook appears for all participants in the course.<br />
<br />
Course grade settings are found in ''Administration > Grade administration > Course grade settings'' or via the gradebook Settings tab.<br />
<br />
The default course grade settings are set by an administrator in ''Administration > Site administration > Grades''.<br />
<br />
==Grader report preferences==<br />
<br />
[[File:Grader report preferences.png|thumb|Grader report preferences]]Teachers can set their preferences for the grader report via 'My preferences' These settings will apply to all courses for that teacher. The teacher may change them at any time. <br />
<br />
For example it's possible to set the grader report to only show active participants or all participants (including suspended users) from the ''Show only active enrolments'' setting. Users may be suspended from the course by changing their status in ''Enrolled users>Edit enrolment.'' The user's role must not be removed when suspending the user or they will not show up in the grader report even if the "Show only active enrolments" option is set to "No."<br />
<br />
The default grader report preferences are set by an administrator in ''Administration > Site administration > Grades > Report settings > Grader report''.<br />
<br />
In Moodle 2.4.2 onwards, the default number of students per page (''grade_report_studentsperpage'') can safely be increased without any loss of data when grading large numbers of students with many assignments.<br />
<br />
==Site administration settings==<br />
<br />
Default values for all grade settings can be set by an administrator. The easiest way to do so is to log in as admin then browse a course gradebook and follow the 'Change defaults' links.<br />
<br />
The following additional grade settings can be found in ''Administration > Site administration > Grades > General settings''. The settings will affect all gradebooks used by all teachers. <br />
<br />
===Graded Roles===<br />
<br />
Graded roles are the type of user that will appear in the gradebook. Most of the time "student" is the only one needed.<br />
<br />
===User profile report===<br />
<br />
The default user profile report setting has just one option, 'User report', unless a custom user report has been added to the site.<br />
<br />
Teachers can view the user reports for all or selected students in the course in ''Administration > Grades administration > User report''.<br />
<br />
===Include scales in aggregation===<br />
Scales can be included as numbers in all aggregated grades across all gradebooks in all courses. Changing this setting will force all aggregated grades to be recalculated.<br />
<br />
If this is checked (and it is by default) then all custom scales will have a corresponding value that is assigned based on the number of options in the scale (ie. three values will have values of 1,2,3) and this will be included in the grade aggregation.<br />
<br />
===Enable publishing===<br />
[[Image:gradepublishing.png|thumb|Grade publishing settings]]<br />
Grade publishing is a way of importing and exporting grades via a URL without being logged in to Moodle. Grade publishing is intended for administrators only. Security implications should be thoroughly considered before allowing non-admin users to publish grades.<br />
<br />
Grade publishing may be enabled by checking the gradepublishing box. If enabled, administrators are provided with [[Grade export|grade export]] publishing settings in each course gradebook.<br />
===Navigation method===<br />
The default gradebook navigation is tabs, which displays well with the Boost theme. However, the admin can change that to a dropdown list or have both dropdown and tabs if desired.<br />
<br />
===Recover grades default===<br />
<br />
When [[Enrolled users|manually enrolling]] a student in a course, there is an option 'Recover user's old grades if possible', however this checkbox is easy to miss. Enabling 'Recover grades default' results in 'Recover user's old grades if possible' being ticked for every course.<br />
<br />
[[File:enrol users enrolment options.png]]<br />
<br />
===Unlimited grades===<br />
Teachers can enter grades over 100% directly in the gradebook if the ''unlimitedgrades'' setting is enabled.<br />
<br />
===Grade point maximum/Grade point default===<br />
<br />
The administrator can set here the maximum point value in activities, and also the default point value which will appear when a teacher uses points for activities in their course. (Both these are set to 100 initially)<br />
<br />
[[File:gradepointmaxdefault.png]]<br />
<br />
==Grade capabilities==<br />
<br />
*[[Capabilities/moodle/grade:edit|Edit grades]]<br />
*[[Capabilities/moodle/grade:export|Export grades]]<br />
*[[Capabilities/moodle/grade:hide|Hide/unhide grades or items]]<br />
*[[Capabilities/moodle/grade:import|Import grades]]<br />
*[[Capabilities/moodle/grade:lock|Lock grades or items]]<br />
*[[Capabilities/moodle/grade:manage|Manage grade items]]<br />
*[[Capabilities/moodle/grade:managegradingforms|Manage advanced grading methods]]<br />
*[[Capabilities/moodle/grade:manageletters|Manage grade letters]]<br />
*[[Capabilities/moodle/grade:manageoutcomes|Manage grade outcomes]]<br />
*[[Capabilities/moodle/grade:unlock|Unlock grades or items]]<br />
*[[Capabilities/moodle/grade:view|View own grades]]<br />
*[[Capabilities/moodle/grade:viewall|View grades of other users]]<br />
*[[Capabilities/moodle/grade:viewhidden|View hidden grades for owner]]<br />
<br />
==See also==<br />
*[https://youtu.be/SwFVSZrbKDw MoodleBites for Administrators - Grades] YouTube movie<br />
*[https://youtu.be/lWcheVbQe2E MoodleBites for Teachers - Gradebook] YouTube movie<br />
<br />
[[de:Bewertungseinstellungen]]<br />
[[es:Configuraciones de calificación]]<br />
[[fr:Paramètres de notes]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Grade_settings&diff=127356Grade settings2017-04-04T01:24:45Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{Grades}}<br />
==Course grade settings==<br />
<br />
[[File:grade settings.PNG|thumb|Course grade settings]]Course grade settings determine how the gradebook appears for all participants in the course.<br />
<br />
Course grade settings are found in ''Administration > Grade administration > Course grade settings'' or via the gradebook Settings tab.<br />
<br />
The default course grade settings are set by an administrator in ''Administration > Site administration > Grades''.<br />
<br />
==Grader report preferences==<br />
<br />
[[File:Grader report preferences.png|thumb|Grader report preferences]]Teachers can set their preferences for the grader report via 'My preferences' These settings will apply to all courses for that teacher. The teacher may change them at any time. <br />
<br />
For example it's possible to set the grader report to only show active participants or all participants (including suspended users) from the ''Show only active enrolments'' setting. Users may be suspended from the course by changing their status in ''Enrolled users>Edit enrolment.'' The user's role must not be removed when suspending the user or they will not show up in the grader report even if the "Show only active enrolments" option is set to "No."<br />
<br />
The default grader report preferences are set by an administrator in ''Administration > Site administration > Grades > Report settings > Grader report''.<br />
<br />
In Moodle 2.4.2 onwards, the default number of students per page (''grade_report_studentsperpage'') can safely be increased without any loss of data when grading large numbers of students with many assignments.<br />
<br />
==Site administration settings==<br />
<br />
Default values for all grade settings can be set by an administrator. The easiest way to do so is to log in as admin then browse a course gradebook and follow the 'Change defaults' links.<br />
<br />
The following additional grade settings can be found in ''Administration > Site administration > Grades > General settings''. The settings will affect all gradebooks used by all teachers. <br />
<br />
===Graded Roles===<br />
<br />
Graded roles are the type of user that will appear in the gradebook. Most of the time "student" is the only one needed.<br />
<br />
===User profile report===<br />
<br />
The default user profile report setting has just one option, 'User report', unless a custom user report has been added to the site.<br />
<br />
Teachers can view the user reports for all or selected students in the course in ''Administration > Grades administration > User report''.<br />
<br />
===Include scales in aggregation===<br />
Scales can be included as numbers in all aggregated grades across all gradebooks in all courses. Changing this setting will force all aggregated grades to be recalculated.<br />
<br />
If this is checked (and it is by default) then all custom scales will have a corresponding value that is assigned based on the number of options in the scale (ie. three values will have values of 1,2,3) and this will be included in the grade aggregation.<br />
<br />
===Enable publishing===<br />
[[Image:gradepublishing.png|thumb|Grade publishing settings]]<br />
Grade publishing is a way of importing and exporting grades via a URL without being logged in to Moodle. Grade publishing is intended for administrators only. Security implications should be thoroughly considered before allowing non-admin users to publish grades.<br />
<br />
Grade publishing may be enabled by checking the gradepublishing box. If enabled, administrators are provided with [[Grade export|grade export]] publishing settings in each course gradebook.<br />
===Navigation method===<br />
The default gradebook navigation is tabs, which displays well with the Boost theme. However, the admin can change that to a dropdown list or have both dropdown and tabs if desired.<br />
<br />
===Recover grades default===<br />
<br />
When [[Enrolled users|manually enrolling]] a student in a course, there is an option 'Recover user's old grades if possible', however this checkbox is easy to miss. Enabling 'Recover grades default' results in 'Recover user's old grades if possible' being ticked for every course.<br />
<br />
[[File:enrol users enrolment options.png]]<br />
<br />
===Unlimited grades===<br />
Teachers can enter grades over 100% directly in the gradebook if the ''unlimitedgrades'' setting is enabled.<br />
<br />
===Grade point maximum/Grade point default===<br />
<br />
The administrator can set here the maximum point value in activities, and also the default point value which will appear when a teacher uses points for activities in their course. (Both these are set to 100 initially)<br />
<br />
[[File:gradepointmaxdefault.png]]<br />
<br />
==Grade capabilities==<br />
<br />
*[[Capabilities/moodle/grade:edit|Edit grades]]<br />
*[[Capabilities/moodle/grade:export|Export grades]]<br />
*[[Capabilities/moodle/grade:hide|Hide/unhide grades or items]]<br />
*[[Capabilities/moodle/grade:import|Import grades]]<br />
*[[Capabilities/moodle/grade:lock|Lock grades or items]]<br />
*[[Capabilities/moodle/grade:manage|Manage grade items]]<br />
*[[Capabilities/moodle/grade:managegradingforms|Manage advanced grading methods]]<br />
*[[Capabilities/moodle/grade:manageletters|Manage grade letters]]<br />
*[[Capabilities/moodle/grade:manageoutcomes|Manage grade outcomes]]<br />
*[[Capabilities/moodle/grade:unlock|Unlock grades or items]]<br />
*[[Capabilities/moodle/grade:view|View own grades]]<br />
*[[Capabilities/moodle/grade:viewall|View grades of other users]]<br />
*[[Capabilities/moodle/grade:viewhidden|View hidden grades for owner]]<br />
<br />
==See also==<br />
*[https://youtu.be/SwFVSZrbKDw MoodleBites for Administrators - Grades] YouTube movie<br />
*[https://youtu.be/lWcheVbQe2E The Moodle Gradebook for Teachers] MoodleBites video on YouTube <br />
<br />
[[de:Bewertungseinstellungen]]<br />
[[es:Configuraciones de calificación]]<br />
[[fr:Paramètres de notes]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Developer_tools&diff=127355Developer tools2017-04-03T23:59:50Z<p>Stuartrmealor: </p>
<hr />
<div>{{Managing a Moodle site}}<br />
Developers of Moodle code have some special tools included in the Moodle package to assist them. Most of the tools should ONLY be used on test sites (not production sites). However there are a few which may be used by a cautious administrator.<br />
<br />
==Experimental features==<br />
<br />
Moodle includes a few experimental features which a cautious administrator may consider enabling. See [[Experimental settings]] for details.<br />
<br />
==Debugging==<br />
<br />
''Administration > Site administration > Development > Debugging''<br />
<br />
At certain times a site administrator will need to see more and/or a more complete error message. The default is to show NONE. These messages can also 1) be very confusing to teachers and students when they suddenly appear and 2) can reveal things about your Moodle and web server that should not be common knowledge. Thus use with care and for short periods of time. See [[Debugging]] for details.<br />
<br />
==Web services test client==<br />
<br />
See [[Web services test client]] for details.<br />
<br />
==Purge all caches==<br />
<br />
''Administration > Site administration > Development > Purge all caches''<br />
<br />
Moodle can cache themes, language strings, filters and other bits of information that have been calculated and stored by the web browser. This link forces all user web browsers to refresh their screens of '''any''' information that Moodle has cached. Several modules that use cache have settings which will turn off caching for that module. Eliminating or purging caches slows performance.<br />
<br />
==Third party libraries==<br />
<br />
A list of all third party libraries in use together with versions and licenses is available at ''Administration > Site administration > Development > Third party libraries''.<br />
<br />
See also [[:dev:Moodle libraries credits|Moodle libraries credits]] in the dev docs.<br />
<br />
==Acceptance testing==<br />
<br />
''Administration > Site administration > Development > Acceptance testing''<br />
<br />
See [[:dev:Acceptance testing|Acceptance testing]] in the dev docs for details.<br />
<br />
==Test course generator==<br />
<br />
See [[Test course generator]] for details.<br />
<br />
==JMeter test plan generator==<br />
<br />
See [[JMeter test plan generator]] for details.<br />
<br />
==PHP Unit tests==<br />
<br />
''Administration > Site administration > Development > PHPUnit tests''<br />
<br />
See [[:dev:PHPUnit]] in the dev docs for details.<br />
<br />
==Template library==<br />
<br />
See [[Template library]] for details.<br />
<br />
==XMLDB editor==<br />
<br />
''Site administration > Development > XMLDB editor''<br />
<br />
The XMLDB editor is a tool for making the .xml files that specify how Moodle should set up its database tables. See [[:dev:XMLDB editor|XMLDB editor]] in the dev docs for details.<br />
<br />
==See also==<br />
*[https://youtu.be/KtuoOPsahZ8 MoodleBites for Administrators - Development settings] YouTube movie<br />
<br />
[[es:Herramientas para desarrolladores]]<br />
[[de:Entwicklerwerkzeuge]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Site-wide_reports&diff=127354Site-wide reports2017-04-03T23:55:44Z<p>Stuartrmealor: </p>
<hr />
<div>{{Managing a Moodle site}}<br />
==Standard Reports for Administrators==<br />
In addition to reports available at both site and course level, the following site-wide reports are available for administrators:<br />
<br />
* [[admin/comment/index#Comments_report|Comments]] - See all comments created on the site. <br />
* [[admin/report/backups/index#Backups_report|Backups]] - displays a list of all course backups made, the time taken to create them, their status, and the next scheduled automated backup execution time<br />
* [[Config changes report]] - Shows changes made by an administrator to the site configuration<br />
* [[Logs]] - Activity reports for course or site<br />
* [[admin/report/loglive/index#Live_logs_from_the_past_hour|Live Logs]] - Live logs from the past hour as a table<br />
* [[Performance_overview|Performance overview]] - overview of settings that may impact site performance such as Theme Designer Mode or Debugging<br />
* [[admin/report/questioninstances/index|Question instances]] - Reports where particular question types are used on the site<br />
* [[admin/report/security/index|Security overview]] - overview of security related settings such as Allowing EMBED and OBJECT tags or No Authentication.<br />
* [[admin/tool/spamcleaner/index#Cleaning_up_spam|Spam cleaner]] - helpful tool for rooting out spam users if you do not have [[Email-based_self-registration#Enable_reCAPTCHA_element|Captcha]] required as part of authentication.<br />
<br />
==See also==<br />
*[https://youtu.be/LW2cWQhkyQU MoodleBites for Administrators - Reports] YouTube movie<br />
*[[Browser sessions]]<br />
*[[Course overview report]]<br />
*[[Events list report]]<br />
*[[Reports FAQ]] <br />
*[[Course reports]] in Managing a Moodle course<br />
*[[Plugins_overview| Plugins overview]] for checking the status of all plugins on the site.<br />
*[[:dev:General report plugins|General report plugins]] developer documentation<br />
*[[ad-hoc contributed reports]]<br />
<br />
[[Category:Report]]<br />
<br />
[[es:Reportes del sitio]]<br />
[[de:Systemweite Berichte]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Scheduled_tasks&diff=127353Scheduled tasks2017-04-03T23:49:54Z<p>Stuartrmealor: </p>
<hr />
<div>{{Server settings}}<br />
An administrator can schedule routine tasks very precisely from ''Administration > Site administration > Server > Scheduled tasks.''<br />
<br />
Note that you still need to run the [[Cron|CRON scripts]] (\admin\cli\cron.php or http:\\yoursite\admin\cron.php) at regular intervals. The script is best run every minute.<br />
{|<br />
|-<br />
|[[File:scheduledtasks1.png|thumb|Scheduled tasks]]<br />
|[[File:scheduledtasks2.png|thumb|Editing a scheduled task]]<br />
|}<br />
<br />
Clicking the edit icon allows the administrator to specify the minute/hour/day/month or day of the week the task is to be run. It is also possible to reset the task to its default setting or disable it completely.<br />
<br />
The column 'Next run' provides information on whether a plugin or a task is disabled (as well as the date that a task will next run).<br />
<br />
==Format for scheduling tasks==<br />
<br />
When typing into the fields, the format is the same as for Unix cron. Examples are as follows and are according to which field you are editing:<br />
<br />
* is every minute, hour, day, month<br />
*/2 is every two minutes, every two hours or every second day<br />
2-10 is every minute between two and ten past the hour or every hour between 2 and 10 am <br />
0 is every Sunday<br />
1 is every Monday or every January<br />
2,5 is the second and 5th of the month, or February and May, or Tuesday and Friday.<br />
<br />
==Fail Delay==<br />
<br />
If you're trying to debug a cron task, you may notice the Fail Delay becomes populated with a number. This is the time in seconds the cron will delay running the task. To sidestep this problem for development purposes, take a look at the Scheduled Tasks section here: [[Administration_via_command_line#Scheduled_tasks]].<br />
<br />
==See Also==<br />
*[https://youtu.be/gPbNXWiA__E MoodleBites for Administrators - Server settings] YouTube movie<br />
<br />
[[es:Tareas agendadas]]<br />
[[de:Geplante Vorgänge]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Mail_configuration&diff=127352Mail configuration2017-04-03T23:46:50Z<p>Stuartrmealor: </p>
<hr />
<div>{{Server settings}}<br />
==Outgoing mail configuration==<br />
<br />
Settings related to mail sent by Moodle can be found in 'Outgoing mail configuration' in Site administration.<br />
<br />
{{New features}}The setting 'Allowed email domains' (allowedemaildomains) allows you to enter domains allowed by your mail server so that emails can be sent from users' real addresses. It accepts a wildcard for conveniently adding a lot of domains (*.example.com - tim@first.example.com), or a strict match (example.com - tim@example.com). <br />
<br />
If allowed domains are set then the user's email address will be used in the "From" and "Reply to" field only in the following situations:<br />
<br />
* The email matches the allowed domains, and the user's setting is to display their email address to everyone.<br />
* The email matches the allowed domains, and the user's setting is to display their email only to course members, and the email is to be delivered to a course member.<br />
<br />
All other situations use the no-reply address.<br />
<br />
(In Moodle 3.2 onwards, the setting ' 'Allowed email domains' replaces the setting 'Always send from no-reply address'.)<br />
<br />
{{New features}}The setting 'Email via information' (emailfromvia) adds via information in the From section of outgoing email to inform the recipient where the email came from:<br />
Name (via shortname) <noreplyaddress><br />
'shortname' is the short name for the site as set in the front page settings.<br />
<br />
==Incoming mail configuration==<br />
If incoming mail processing is enabled in 'Incoming mail configuration' in Site administration, then users are able to reply to forum posts via email and send files to their private files as email attachments.<br />
<br />
===Mailbox configuration===<br />
It is important to have a dedicated email address here. Don't use one you normally use for your personal emails. You do not need to add the @ sign. If you have set up the email mountorangeschool @ besteveremail.com then it would be entered as in the following screenshot:<br />
[[File:emailexampleincoming.png|thumb|center|400px]]<br />
<br />
===Incoming mail server settings===<br />
As an example, if you are using gmail you would use '''IMAP.gmail.com''' in the Incoming mail server (messageinbound_host) field. (If using gmail you also need to make sure that you've enabled IMAP for yor gmail account - see https://support.google.com/mail/troubleshooter/1668960?hl=en )<br />
<br />
Note1: The SMTP server hosting the mailbox you've configured above must support ''plus addressing'' i.e. any email sent to mountorangeschool+blahblahblah@besteveremail.com is still delivered to mountorangeschool@besteveremail.com.<br />
<br />
Note2 : The username and password here must relate to the settings you entered earlier in Mailbox configuration. So if your address was mountorangeschool @ besteveremail.com and your username is ''mountorangeschool'', then enter your username in this section along with the password you use to get into this email account.<br />
<br />
Note 3: You may also need to make sure that your host does not block outbound connections to the IMAP ports (some do by default).<br />
<br />
Note 4: If using gmail, you may find that IMAP does not work with Google's higher security setting. If IMAP is not working with gmail, check out https://support.google.com/accounts/answer/6010255?hl=en-GB<br />
<br />
==Message handlers==<br />
<br />
===Email to Private files===<br />
*If you enable this, then users will be able to send attachments via email directly to their private files. See [[Private files]] for details of how the feature works.<br />
*Each user will be provided with an address in their Private files to which they send the email and attached files. You can set the default expiry period for this address here.<br />
*Checking the 'Validate sender address' box will mean that if an email is sent to a user's private files from a different account from that registered with user in Moodle, then Moodle will check first before allowing the file to be stored in the user's Private files.<br />
<br />
===Invalid recipient handler===<br />
If a valid message is received but the sender cannot be authenticated, the message is stored on the email server and the user is contacted using the email address in their user profile. The user is given the chance to reply to confirm the authenticity of the original message.This handler processes those replies.<br />
<br />
It is not possible to disable sender verification of this handler because the user may reply from an incorrect email address if their email client configuration is incorrect.<br />
<br />
===Reply to forum posts===<br />
*If you enable this, then users will be able to reply to forum posts directly from their email inbox. See the section on 'Reply to posts via email' in [[Using Forum]] for details of how the feature works.<br />
*You must set ''Site administration > Plugins > Message outputs > Email'' to 'Always send email from the No reply address'; otherwise users will see the email of the forum poster instead.<br />
*Each user will be provided with reply-to address when they click to reply to a forum post via email. You can set the default expiry period for this address here.<br />
<br />
==See also==<br />
* [https://moodle.org/mod/forum/discuss.php?d=277594 Need help configuring forum's "Reply to post" feature] forum discussion<br />
* [https://youtu.be/gPbNXWiA__E MoodleBites for Administrators - Server settings] YouTube movie<br />
<br />
[[es:Configuración del correo]]<br />
[[de:Einstellungen für E-Mails]]<br />
<br />
[[Category:Forum]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Site_registration&diff=127351Site registration2017-04-03T23:44:30Z<p>Stuartrmealor: </p>
<hr />
<div><div class="navtrail">[[Main page]] ► [[Managing a Moodle site]] ► [[{{PAGENAME}}]]</div><br />
__NOTOC__<br />
[[File:Boost-Moodle-Registrations.jpg]]<br />
==Why register my site?==<br />
Registering your site gives us a better picture of how Moodle is used worldwide and helps us make decisions about new features and plugins.<br />
<br />
==4 reasons to register==<br />
# Stay up to date by email whenever there are new releases of Moodle or security alerts. <br />
# Be part of the [https://moodle.net/stats/ statistics of the worldwide community]. <br />
# List your site on our [https://moodle.net/sites/ list of registered sites in your country]. (But if you want to keep it private, that’s fine too!)<br />
# Make use of the messaging server https://messages.moodle.net/ for [[Mobile app notifications|Moodle mobile push notifications]].<br />
<br />
==How about security?==<br />
We don’t share your information with anyone. We don’t go into your site. We use the aggregated anonymous data to publish the statistics of the worldwide community and use the other data to help us in our decision making around new features and plugins.<br />
<br />
==How do I register?==<br />
Register your site by logging in as an administrator and going to ''Administration > Site administration > Registration''. If you’re not the admin, ask them nicely to check!<br />
<br />
==I don’t want my details public==<br />
Your registration is private to us unless you choose to make it public.<br />
<br />
==Do I have to register? What happens if I don’t?==<br />
Registration is optional, but we wouldn’t want you to miss out on any important security issues or upgrades and put your site at risk. <br />
<br />
The more people who register, the better a picture we get of how Moodle is used and which aspects we can improve. <br />
<br />
So registering is a win-win for you as well as for us.<br />
<br />
==I can’t register my site!==<br />
Only sites which are online can be registered. If your site is online and you have problems registering or updating your registration, please email [mailto:support@moodle.org support@moodle.org].<br />
<br />
Note that it can take a while before your site is listed on https://moodle.net/sites/ so please be patient.<br />
<br />
==See also==<br />
*[https://youtu.be/gPbNXWiA__E MoodleBites for Administrators - Server settings] YouTube movie<br />
<br />
[[Category:Site administration]]<br />
<br />
[[ja: サイト登録]]<br />
[[de:Moodle-Site registrieren]]<br />
[[es:Registro del sitio]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Environment&diff=127350Environment2017-04-03T23:43:03Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{Server settings}}<br />
An administrator can check that their site meets all system requirements for the current and future versions of Moodle in ''Administration > Site administration > Server > Environment''. It is important to check system requirements prior to [[Upgrading|upgrading]].<br />
[[File:Environment.png|thumb|center|500px|Environment]]<br />
<br />
==See also ==<br />
<br />
*[[:Category:Environment]]<br />
*[https://youtu.be/gPbNXWiA__E MoodleBites for Administrators - Server settings] YouTube movie<br />
<br />
[[Category:Environment]]<br />
<br />
[[es:Entorno]]<br />
[[eu:Ingurunea]]<br />
[[fr:Environnement]]<br />
[[ja:動作環境]]<br />
[[de:Serverkonfiguration]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Cleanup&diff=127349Cleanup2017-04-03T23:42:11Z<p>Stuartrmealor: </p>
<hr />
<div>{{Server settings}}<br />
An administrator can limit the size of certain tables in the database by setting appropriate options in ''Administration > Site administration > Server > Cleanup''.<br />
<br />
==Delete unconfirmed users after==<br />
'''Note:''' ''This feature is reported as not working. See https://tracker.moodle.org/browse/MDL-54106.''<br />
<br />
<br />
If you're using [[Email-based self-registration]] users must confirm their account (complete the email registration process) within a certain time-frame. Once the time set here has passed, any account that hasn't been confirmed will be deleted. The default is 7 days.<br />
<br />
==Delete incomplete users after==<br />
<br />
Once users have confirmed their account, they must complete their profile within the time interval set here.<br />
<br />
A ''complete profile'' is one where the following fields have been filled in (are not empty):<br />
*First name<br />
*Last name<br />
*Email address<br />
Just as a reference, given that the firstname, lastname and email are required fields of the [[Upload users]] module, any account created this way is automatically a complete account.<br />
<br />
==Disable grade history==<br />
<br />
History tracking of changes in grades-related tables may be disabled by checking the ''disablegradehistory'' box.<br />
<br />
==Grade history lifetime==<br />
<br />
The length of time that the history of changes in grade-related tables is kept may be set (from 30 days to never).<br />
<br />
<br />
Note for users who have upgraded from earlier versions: The setting 'Keep logs for' is now located in the [[Logging|log store settings]].<br />
<br />
==See also==<br />
<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=87795 How do I prune mdl_log table?] forum discussion<br />
*[https://youtu.be/gPbNXWiA__E MoodleBites for Administrators - Server settings] YouTube movie<br />
<br />
[[eu:Garbiketa]]<br />
[[fr:Nettoyage]]<br />
[[ja:クリーンアップ]]<br />
[[de:Aufräumarbeiten]]<br />
[[es:Limpieza]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Session_handling&diff=127348Session handling2017-04-03T23:41:07Z<p>Stuartrmealor: </p>
<hr />
<div>{{Server settings}}<br />
An administrator can change the following settings in ''Administration > Site administration > Server > Session Handling''.<br />
<br />
Once someone logs in to your Moodle server, the server starts a session. The session data allows the server to track users as they access different pages.<br />
<br />
==Use database for session information==<br />
<br />
Moodle needs to store the session data in some storage. By default either file or database session storage is selected, this option allows admin to change it. Large installation should use memcached driver described below.<br />
<br />
Note that this option disappears after setting the $CFG->session_handler_class in config.php file.<br />
<br />
==Timeout==<br />
<br />
If users don't load a new page during the amount of time set here, Moodle will end their session and log them out.<br />
<br />
Be sure this time frame is long enough to cover the longest test your teachers may offer. If a student is logged out while they are taking a test, their responses to the test questions may be lost.<br />
<br />
==Cookie prefix==<br />
<br />
Most of the time, you can leave this blank, unless you are running more than one Moodle site on the same server. In this case, you will want to customize the name of the cookie each Moodle site uses to track the session. This enables you to be logged into more than one Moodle site at the same time.<br />
<br />
Note: If you change "Cookie prefix" or "Cookie path" you will need to login again as the changes take effect immediately.<br />
<br />
==Cookie path==<br />
<br />
The relative path to this Moodle installation, this may be used to force sending of Moodle session cookie to parent directories. Invalid values are ignored automatically.<br />
<br />
==Cookie domain==<br />
<br />
This can be used to send session cookies to higher domains instead of just the server domain. This may be useful for some SSO solutions. Invalid values are ignored automatically.<br />
<br />
==Session drivers==<br />
User sessions may be stored in different backends. Session drivers can be configured only in config.php file - see examples in config-dist.php file.<br />
<br />
===Memcached session driver===<br />
The Memcached session driver is the fastest driver. It requires external memcached server and memcached PHP extension. Server cluster nodes must use shared session storage.<br />
<br />
Configuration options in config.php:<br />
<code php><br />
$CFG->session_handler_class = '\core\session\memcached';<br />
$CFG->session_memcached_save_path = '127.0.0.1:11211';<br />
$CFG->session_memcached_prefix = 'memc.sess.key.';<br />
$CFG->session_memcached_acquire_lock_timeout = 120;<br />
$CFG->session_memcached_lock_expire = 7200; // Ignored if memcached extension <= 2.1.0<br />
</code><br />
<br />
Notes:<br />
* Make sure the memcached server has enough memory.<br />
* Use different prefix when storing sessions from multiple Moodle sites in one server.<br />
* If PECL memcached extension version installed is less that 2.2.0, the locking works differently from other drivers - the lock is expired/released at the end of timeout - see MDL-42485.<br />
* '''Don't use the same memcached server for both sessions and MUC. Events triggering MUC caches to be purged leads to MUC purging the memcached server - thus terminating ALL sessions.'''<br />
* The <code php>$CFG->session_memcached_number_of_replicas</code> option is no longer supported.<br />
<br />
For windows users, PHP.net only supplies binaries for memcache, (and not memcached). (http://windows.php.net/downloads/pecl/releases/)<br />
<br />
(As of 2.7, two different contribs exist for memcache session handling - see MDL-42011 - it seems the OU one doesn't use prefix/lock_expire for some reason... possibly better to use the catalyst patch, where the only difference to the above config.php is the spelling of memcache(d))<br />
<br />
===File session driver===<br />
This driver is used by default in new installation.<br />
<br />
Configuration options in config.php:<br />
<code php><br />
$CFG->session_handler_class = '\core\session\file';<br />
$CFG->session_file_save_path = $CFG->dataroot.'/sessions';<br />
</code><br />
<br />
Notes:<br />
* File based sessions require file system that supports file locking.<br />
<br />
===Database session driver===<br />
This type of driver was used by default in Moodle 2.0-2.5.<br />
<br />
<code php><br />
$CFG->session_handler_class = '\core\session\database';<br />
$CFG->session_database_acquire_lock_timeout = 120;<br />
</code><br />
<br />
Notes:<br />
* DB sessions are not compatible with MyISAM database engine.<br />
* If you are using MySQL/MariaDB make sure that \'max_allowed_packet\' in my.cnf (or my.ini) is at least 4M.<br />
* The performance is relatively low, it is not recommended for large sites.<br />
<br />
===Redis session driver===<br />
<br />
The Redis session driver is available in Moodle 3.1.3 onwards (see MDL-54606). It requires a Redis server and the Redis extension.<br />
<br />
Configuration options in config.php:<br />
<code php><br />
$CFG->session_handler_class = '\core\session\redis';<br />
$CFG->session_redis_host = '127.0.0.1';<br />
$CFG->session_redis_port = 6379; // Optional.<br />
$CFG->session_redis_database = 0; // Optional, default is db 0.<br />
$CFG->session_redis_prefix = ''; // Optional, default is don't set one.<br />
$CFG->session_redis_acquire_lock_timeout = 120;<br />
$CFG->session_redis_lock_expire = 7200;<br />
</code><br />
<br />
==See also==<br />
* [[Sessions FAQ]]<br />
* [https://youtu.be/gPbNXWiA__E MoodleBites for Administrators - Server settings] YouTube movie<br />
<br />
[[cs:admin/setting/sessionhandling]]<br />
[[ja:セッションハンドリング]]<br />
[[de:Sitzungsinformationen]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=System_paths&diff=127347System paths2017-04-03T23:38:47Z<p>Stuartrmealor: </p>
<hr />
<div>{{Server settings}}<br />
An administrator can set the following system paths in ''Administration > Site administration > Server > System Paths''.<br />
<br />
'''Note''': When setting the system paths on Windows systems, use of the 8.3 notation for the path and filename is preferred. So instead of entering ''c:\program files\path to aspell\aspell.exe'', enter ''c:\progra~1\path~1\aspell.exe''. Check the exact 8.3 path using the ''dir /x'' command at the prompt.<br />
<br />
==Path to du==<br />
<br />
This binary file was used in Moodle 1.x to quickly look up the size of data directories. It is possible that some add-ons still use this functionality. In linux based servers, du is by default installed and can be located generally in /usr/bin/share<br />
<br />
If you have access to a terminal:<br />
<br />
[root@moodle ~]# which du<br />
/usr/bin/du<br />
<br />
==Path to aspell==<br />
<br />
If PSpellSpell is selected as the spell engine for TinyMCE in ''Administration > Site administration > Plugins > Text editors > TinyMCE HTML editor'' then you must specify the correct path to access the aspell binary.<br />
<br />
In addition, you MUST have aspell 0.50 or later installed on your server. On Unix/Linux systems use the which program to determine the path:<br />
<br />
[root@moodle ~]# which aspell<br />
/usr/bin/aspell<br />
<br />
In this example the path to enter is ''/usr/bin/aspell''. <br />
<br />
On a Windows system, download and install [http://aspell.net/win32 GNU aspell] together with at least one dictionary and then use the search facility in Explorer to find the aspell.exe file. The path should look like:<br />
<br />
c:\program files\aspell\bin\aspell.exe<br />
<br />
It can be best to install aspell in c:\aspell or use the 8.3 notation if you are installing in ''c:\program files'' so that the path looks like <br />
<br />
c:\progra~1\aspell\bin\aspell.exe<br />
<br />
==Path to dot==<br />
<br />
Path to dot is for enabling image generation in profiling. The generated graphs are really useful to see what each request does. To have profiling visible (and working), the xhprof extension must be installed in PHP.<br />
<br />
==External links==<br />
<br />
*[http://aspell.sourceforge.net/ GNU Aspell]<br />
*[http://aspell.net/win32/ GNU Aspell (Win32 version)]<br />
<br />
==See also==<br />
<br />
* [http://moodle.org/mod/forum/discuss.php?d=125912 HowTo: Installing aspell in Ubuntu (with dictionary)] forum discussion<br />
* [https://youtu.be/gPbNXWiA__E MoodleBites for Administrators - Server settings] YouTube movie<br />
<br />
[[cs:admin/setting/systempaths]]<br />
[[de:Systempfade]]<br />
[[es:Rutas del sistema]]<br />
[[hu:Rendszerútvonalak]]<br />
[[ja:システムパス]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Server_settings&diff=127346Server settings2017-04-03T23:33:31Z<p>Stuartrmealor: </p>
<hr />
<div>{{Managing a Moodle site}}<br />
*[[System paths]]<br />
*[[Session handling]]<br />
*[[HTTP]]<br />
*[[Maintenance mode]]<br />
*[[Cleanup]]<br />
*[[Environment]]<br />
*[[Site registration]]<br />
*[[Mail configuration]]<br />
*[[Scheduled tasks]]<br />
<br />
===See also===<br />
* [https://youtu.be/gPbNXWiA__E MoodleBites for Administrators YouTube movie - Server settings]<br />
<br />
[[de:Servereinstellungen]]<br />
[[es:Configuraciones del servidor]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Customising_appearance&diff=127345Customising appearance2017-04-03T23:19:58Z<p>Stuartrmealor: </p>
<hr />
<div>There are many ways to customize the way Moodle appears. <br />
*[[Themes]] - are a set of instructions that determine the colors, line widths, block heading formats and CSS on your Moodle site. A site can have more than 1 theme. They can be selected for:<br />
**Course Category <br />
**Course<br />
**Activity<br />
**My Moodle <br />
**Site <br />
* [[Blocks]] can add many visual elements, as well as activities in the course. The list is long but includes:<br />
**Calendar<br />
**HTML(basically a blank block to put text, images or some custome html code<br />
**RSS keep your course fresh with RSS feeds from your favorite source<br />
**Glossary - put entries from a glossary<br />
*[[Language]] - you can force or allow different languages by defining them in a [[Context]]<br />
*[[Front Page]] - The Home page of the site can have it's own look.<br />
*Site settings - The default theme, establish sticky blocks and defaults for the entire site<br />
<br />
Appearance means different things to many people. Just remember that Moodle is modular, contextual and open source. Thus if the interface can not alter the appearance of something, it probably is possible to do it by altering the code.<br />
<br />
==See also==<br />
* [https://youtu.be/hRmaZnuJnuA MoodleBites for Administrators YouTube movie - Appearance]<br />
* [https://youtu.be/FU4RT2Yhld0 MoodleBites for Administrators YouTube movie - Appearance (Themes)]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Site_appearance&diff=127344Site appearance2017-04-03T23:19:36Z<p>Stuartrmealor: </p>
<hr />
<div>{{Managing a Moodle site}}<br />
<br />
There are many ways to customise the appearance of your Moodle site so that it blends in with, for example, your college site or your company's corporate brand. The links below provide more information on personalising the appearance of Moodle:<br />
*[[Front page]] - how best to display the entry page to your Moodle. Here you can decide how to display announcements and courses (if you want to) and how to add attractive images and descriptive text to promote your organisation.<br />
*[[Theme settings]] - how to add custom dropdown menus and (if you wish) personalise the user menu top right.<br />
*[[Header and footer]] - how to display useful information at the top and bottom of your course and link to Google Analytics.<br />
*[[Themes]] - general information on changing the "skin" of your Moodle for the whole site or just sections. Look at [[Standard themes]] for examples of how to easily customise Moodle's 'More' theme.<br />
*[[Dashboard]] - a personalised page for each user. Find out how to set the default dashboard and how to allow users to select their own home page.<br />
*[[User profiles]]<br />
*[[Navigation]] - control how users find their way around Moodle<br />
*[[Course list]] - control who appears in the list of courses<br />
<br />
==See also==<br />
* [https://youtu.be/hRmaZnuJnuA MoodleBites for Administrators YouTube movie - Appearance]<br />
* [https://youtu.be/FU4RT2Yhld0 MoodleBites for Administrators YouTube movie - Appearance (Themes)]<br />
*Change the language or default wording on your site - [[Language|Language]]<br />
* [https://moodle.org/mod/forum/discuss.php?d=314373 Beautiful Moodle site] forum thread<br />
<br />
[[de:Darstellung]]<br />
[[es:Apariencia del sitio]]<br />
[[fr:Apparence du site]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Customising_appearance&diff=127343Customising appearance2017-04-03T23:18:19Z<p>Stuartrmealor: </p>
<hr />
<div>There are many ways to customize the way Moodle appears. <br />
*[[Themes]] - are a set of instructions that determine the colors, line widths, block heading formats and CSS on your Moodle site. A site can have more than 1 theme. They can be selected for:<br />
**Course Category <br />
**Course<br />
**Activity<br />
**My Moodle <br />
**Site <br />
* [[Blocks]] can add many visual elements, as well as activities in the course. The list is long but includes:<br />
**Calendar<br />
**HTML(basically a blank block to put text, images or some custome html code<br />
**RSS keep your course fresh with RSS feeds from your favorite source<br />
**Glossary - put entries from a glossary<br />
*[[Language]] - you can force or allow different languages by defining them in a [[Context]]<br />
*[[Front Page]] - The Home page of the site can have it's own look.<br />
*Site settings - The default theme, establish sticky blocks and defaults for the entire site<br />
<br />
Appearance means different things to many people. Just remember that Moodle is modular, contextual and open source. Thus if the interface can not alter the appearance of something, it probably is possible to do it by altering the code.<br />
<br />
See also<br />
<br />
* [https://youtu.be/hRmaZnuJnuA MoodleBites for Administrators YouTube movie - Appearance]<br />
* [https://youtu.be/FU4RT2Yhld0 MoodleBites for Administrators YouTube movie - Appearance (Themes)]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Installing_plugins&diff=127342Installing plugins2017-04-03T22:44:49Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{Installing Moodle}}<br />
==Why install additional plugins?==<br />
<br />
Plugins enable you to add additional features and functionality to Moodle, such as new activities, new quiz question types, new reports, integrations with other systems and many more. <br />
<br />
Note: Certain hosting solutions, such as [https://moodle.com/cloud/ MoodleCloud], prevent plugins being installed from within Moodle.<br />
<br />
==Choosing the best plugins for your site==<br />
<br />
Note: It is recommended that you proceed with caution and always try installing these plugins in a local experimental server before installing them in a production server.<br />
<br />
* Moodle has a [https://moodle.org/plugins/report/index.php?report=favourites&p=0&l=50&s=favourited&d=DESC list of the most favourite plugins], which might be worth considering for adding to your site :)<br />
* You can find the plugins with the largest number of downloads in the last three months at [https://moodle.org/plugins/stats.php https://moodle.org/plugins/stats.php]. These are the plugins most likely to be most useful for most sites. It would probably be a good idea to consider them first.<br />
* You can test and try more than 50 of the most popular Moodle plugins at [http://plugins.moodlebites.com plugins.moodlebites.com]<br />
* See the [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick<br />
* Moodle has a list of plugins that have received the [https://moodle.org/plugins/browse.php?list=award&id=1 Reviewers' choice award]. These are given by the plugins guardians and reviewers for particularly useful, well coded or otherwise interesting plugins. <br />
* Special cases:<br />
** All plugins with ''mobile'' in their name, are related to [https://docs.moodle.org/310/en/Moodle_Mobile mobile devices].<br />
<br />
===Elementary school teaching===<br />
You might consider some plugins for [[Gamification|gamification]], such as the [https://moodle.org/plugins/mod_quizgame Quizventure].<br />
<br />
===Plugins for K-12 teaching===<br />
For [https://en.wikipedia.org/wiki/K%E2%80%9312 K-12] teaching and learning environments, please consider installing the plugins that are included in the [https://moodle.com/cloud/school/?utm_source=Sendy&utm_medium=Email&utm_campaign=Newsletter_July2016 Moodle for School at MoodleCloud]: <br />
* [https://moodle.org/plugins/mod_attendance Attendance]<br />
* [http://bigbluebutton.org/ BigBlueButton]<br />
* [https://moodle.org/plugins/mod_checklist Checklist]<br />
* [https://moodle.org/plugins/atto_chemistry Chemistry editor]<br />
* [https://moodle.org/plugins/mod_choicegroup Group choice]<br />
* [https://moodle.org/plugins/block_xp Level up!]<br />
* [https://moodle.org/plugins/mod_quizgame Quizventure]<br />
* [https://moodle.org/plugins/tinymce_wordcount Word count]<br />
<br />
===Plugins for University teaching===<br />
For universities, there is a [https://docs.moodle.org/310/en/Tertiary_education#Moodle_plugins_by.2Ffor_Universities list of plugins by/for Universities], and a [https://docs.moodle.org/310/en/Tertiary_education#Discipline-specific_plugins link to discipline-specific plugins], which might be worth considering.<br />
<br />
== Considerations for production sites (skip if you're just moodling) ==<br />
<br />
'''VERY IMPORTANT''' Warning: Please be aware that some plugins have not been reviewed, and the quality and/or suitability for your Moodle site has not been checked. Please be careful. It may not do what you expect, it may have serious security issues or it may even not work at all. This is however improving over time with the evolving new plugins directory system.<br />
<br />
* If you have a large site for production purposes consider if you '''really''' need the plugin? More functionality means more things to support, more things to (potentially) go wrong and more things to worry about at upgrade time. <br />
* Is the plugin supported and maintained? If something goes wrong can you get support? Will bugs be fixed?<br />
* If the plugin does not work in a future version of Moodle, what will you do about it?<br />
* Beware of ''patches'' ([https://moodle.org/plugins/browse.php?list=category&id=38 Moodle Plugins Directory Other category]) ! If a plugin modifies or replaces core files then be very careful. It can only be guaranteed to work with the exact build (version) of Moodle it was created for and is highly unlikely to survive a Moodle upgrade.<br />
* Look at [https://moodle.org/mod/forum/discuss.php?d=340821#p1373707 this] and [https://moodle.org/mod/forum/discuss.php?d=346296 also this] forum threads of users worried about installing a plugin.<br />
<br />
==Installing a plugin==<br />
<br />
To install a plugin, its source code must be put (deployed) into the appropriate location inside the Moodle installation directory and the main administration page ''Administration > Site administration > Notifications'' must be visited. There are three ways how the plugin code can be deployed into Moodle.<br />
<br />
Plugin code may be deployed from within Moodle, either directly from the Moodle plugins directory or by uploading a ZIP file. The web server process has to have write access to the plugin type folder where the new plugin is to be installed in order to use either of these methods.<br />
<br />
Alternatively, a plugin may be deployed manually at the server.<br />
<br />
===Installing directly from the Moodle plugins directory===<br />
<br />
# Login as an admin and go to ''Site administration > Plugins > Install plugins''. (If you can't find this location, then plugin installation is prevented on your site.)<br />
# Click the button 'Install plugins from Moodle plugins directory'.<br />
# Search for a plugin with an Install button, click the Install button then click Continue.<br />
# Confirm the installation request<br />
# Check the plugin validation report<br />
<br />
===Installing via uploaded ZIP file===<br />
<br />
# Go to the [https://moodle.org/plugins Moodle plugins directory], select your current Moodle version, then choose a plugin with a Download button and download the ZIP file.<br />
# Login to your Moodle site as an admin and go to ''Administration > Site administration > Plugins > Install plugins''.<br />
# Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if your plugin is not automatically detected.<br />
# If your target directory is not writeable, you will see a warning message.<br />
# Check the plugin validation report<br />
<br />
{|<br />
| [[File:plugin1.png|thumb|Install plugins]]<br />
| [[File:add-on package validation.png|thumb|Plugin package validation]]<br />
|}<br />
<br />
===Installing manually at the server===<br />
<br />
If you can't deploy the plugin code via the administration web interface, you have to copy it to the server file system manually (e.g. if the web server process does not have write access to the Moodle installation tree to do this for you).<br />
<br />
First, establish the correct place in the Moodle code tree for the plugin type. Common locations are:<br />
<br />
* /path/to/moodle/theme/ - themes<br />
* /path/to/moodle/mod/ - activity modules and resources<br />
* /path/to/moodle/blocks/ - sidebar blocks<br />
* /path/to/moodle/question/type/ - question types<br />
* /path/to/moodle/course/format/ - course formats<br />
* /path/to/moodle/admin/report/ - admin reports<br />
<br />
See [[:dev:Plugins]] for the full list of all plugin types and their locations within the Moodle tree.<br />
<br />
# Go to the [https://moodle.org/plugins Moodle plugins directory]; select your current Moodle version, then choose a plugin with a Download button and download the ZIP file.<br />
# Upload or copy it to your Moodle server.<br />
# Unzip it in the right place for the plugin type (or follow the plugin instructions). <br />
# In your Moodle site (as admin) go to ''Settings > Site administration > Notifications'' (you should, for most plugin types, get a message saying the plugin is installed).<br />
<br />
Note: The plugin may contain language files. They'll be found by your Moodle automatically. These language strings can be customized using the standard ''Settings > Site administration > Language'' editing interface. If you get a "Database error" when you try to edit your language files, there is a strong chance that the language files included within the downloaded ZIP file of this plugin have a coding problem. If you delete the ''plugin_name/lang/other_language_different_to_English/'' folder with the new language strings and the database error disappears, this is indeed the case. Please notify the plugin maintainer, so that it can be fixed in future releases.<br />
<br />
==Troubleshooting==<br />
<br />
===Errors===<br />
<br />
If you obtain an error, please [[Debugging|turn debugging on]] to obtain additional information about the cause of the error.<br />
<br />
;Database error while doing a language customization : May not be related to the [[Language_customisation#Database_error|Language customization]], but rather a problem with a recently installed plugin.<br />
<br />
;tool_installaddon/err_curl_exec - cURL error 60 : This suggests problems with the validation of the SSL certificate of the remote (moodle.org) site. This is also a known problem in Moodle Windows 7 servers running the Moodle package for Windows. See [[SSL certificate for moodle.org]] for more info and possible solutions.<br />
<br />
===A file permissions error has occurred===<br />
<br />
On certain 3.0.x versions, when installing plugins via the administration interface, the Moodle uses the configuration settings <tt>$CFG->directorypermissions</tt> and <tt>$CFG->filepermissions</tt>. If these are not defined explicitly in your config.php, the default value is set automatically to 777 (rwxrwxrwx) for directories and 666 (rw-rw-rw-) for files (see lib/setup.php).<br />
<br />
If this default behaviour does not fit your needs and hosting environment, you may wish to specify more strict setting such as<br />
<br />
$CFG->directorypermissions = 02750;<br />
<br />
A common error after installing plugins is that when you create an instance of the module and then save and display it, it reports the error, "A file permissions error has occurred. Please check the permissions on the script and the directory it is in and try again." If you get this, the file permissions of the package are mostl likely set to 711 preventing them from running correctly. With your preferred FTP client or via your web hosts control panel, set the file permissions of all the files and directories in the installed module, e.g. /moodle/mod/[myplugin]/ to 755 and then see if you can successfully view the module instance.<br />
<br />
===Default exception handler: Error writing to database Debug: Duplicate entry 'en_us-...===<br />
* These errors are usually caused by a third party plugin. <br />
* To find the involved plugin, go to [http://lang.moodle.org http://lang.moodle.org] and use the AMOS tool to find all the strings with the given string identifier.<br />
* Remove the suspected plugin and check if the error has disappeared. If so, please contact the plugin maintainer and report this issue.<br />
* Please see [https://moodle.org/mod/forum/discuss.php?d=219504 this forum thread] for known causes and fixes.<br />
<br />
===When installing manually===<br />
<br />
* Check the file permissions. The web server needs to be able to read the plugin files. If the the rest of Moodle works then try to make the plugin permissions and ownership match. <br />
* Did you '''definitely''' unzip or install the plugin in the correct place?<br />
* Because Moodle scans plugin folders for new plugins you cannot have any other files or folders there. Make sure you deleted the zip file and don't try to rename (for example) an old version of the plugin to some other name - it will break.<br />
* Make sure the directory name for the plugin is correct. All the names '''have''' to match. If you change the name, then it won't work.<br />
<br />
===Obtaining help===<br />
<br />
Ask in a forum in [http://moodle.org/course/view.php?id=5 Moodle in English]. Make sure you describe your system (including versions of MySQL, PHP etc.), what you tried and what happened. Copy and paste error messages exactly. Provide the link to the version of the plugin you downloaded (some have very similar names).<br />
<br />
==Uninstalling a plugin==<br />
<br />
To uninstall a plugin<br />
# Go to ''Administration> Site Administration > Plugins > Plugins overview'' and click the Uninstall link opposite the plugin you wish to remove<br />
# Use a file manager to remove/delete the actual plugin directory as instructed, otherwise Moodle will reinstall it next time you access the site administration<br />
<br />
==Plugins overview==<br />
<br />
[[File:plugins overview.png|thumb|center|400px|Plugins overview highlighting available check button]]<br />
<br />
The Plugins overview page in ''Administration > Site Administration > Plugins > Plugins overview'' lists all installed plugins, together with the version number,release, availability (enabled or disabled) and settings link (if applicable).<br />
<br />
A 'Check for available updates' button enables admins to quickly check for any updates available for plugins installed on the site (from the [http://moodle.org/plugins plugins directory]). Any updates available are highlighted, with further information and a download link in the notes column opposite the plugin.<br />
<br />
===Plugin updating from within Moodle===<br />
<br />
An administrator can enable updates deployment in ''Administration > Site Administration > Server > Update notifications''. Then when updates are available, 'Install this update' buttons are shown on the Plugins overview page. See [[Automatic updates deployment]] for more details.<br />
<br />
==Preventing installing plugins from within Moodle==<br />
<br />
If required, installing and updating from within Moodle can be prevented by copying the following lines of code from config-dist.php and pasting them in config.php.<br />
<br />
<code php><br />
// Use the following flag to completely disable the installation of plugins<br />
// (new plugins, available updates and missing dependencies) and related<br />
// features (such as cancelling the plugin installation or upgrade) via the<br />
// server administration web interface.<br />
$CFG->disableupdateautodeploy = true;<br />
</code><br />
<br />
==See also==<br />
* [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick<br />
* [[Notifications]] for further details of update notifications<br />
* [[Plugin Review Criteria]]<br />
* [[Plugins FAQ]]<br />
* Moodle in English [http://moodle.org/mod/forum/view.php?id=44 General plugins forum]<br />
* [[Installing Moodle from Git repository#Installing a contributed extension from its Git repository|Installing a contributed extension from its Git repository]]<br />
* [https://youtu.be/uP_rUGZR0aw Moodle Plugins Administration] MoodleBites video on YouTube <br />
* [https://youtu.be/FU4RT2Yhld0 Install a new Theme] MoodleBites video on YouTube <br />
<br />
For developers:<br />
<br />
*[[:dev:Category:Plugins|Plugins developer documentation]]<br />
*[[:dev:Plugin validation]]<br />
*[[:dev:On-click add-on installation]]<br />
<br />
[[Category:Contributed code]]<br />
<br />
[[de:Plugins installieren]]<br />
[[es:Instalar complementos]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Installing_plugins&diff=127341Installing plugins2017-04-03T22:43:20Z<p>Stuartrmealor: /* See also */</p>
<hr />
<div>{{Installing Moodle}}<br />
==Why install additional plugins?==<br />
<br />
Plugins enable you to add additional features and functionality to Moodle, such as new activities, new quiz question types, new reports, integrations with other systems and many more. <br />
<br />
Note: Certain hosting solutions, such as [https://moodle.com/cloud/ MoodleCloud], prevent plugins being installed from within Moodle.<br />
<br />
==Choosing the best plugins for your site==<br />
<br />
Note: It is recommended that you proceed with caution and always try installing these plugins in a local experimental server before installing them in a production server.<br />
<br />
* Moodle has a [https://moodle.org/plugins/report/index.php?report=favourites&p=0&l=50&s=favourited&d=DESC list of the most favourite plugins], which might be worth considering for adding to your site :)<br />
* You can find the plugins with the largest number of downloads in the last three months at [https://moodle.org/plugins/stats.php https://moodle.org/plugins/stats.php]. These are the plugins most likely to be most useful for most sites. It would probably be a good idea to consider them first.<br />
* You can test and try more than 50 of the most popular Moodle plugins at [http://plugins.moodlebites.com plugins.moodlebites.com]<br />
* See the [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick<br />
* Moodle has a list of plugins that have received the [https://moodle.org/plugins/browse.php?list=award&id=1 Reviewers' choice award]. These are given by the plugins guardians and reviewers for particularly useful, well coded or otherwise interesting plugins. <br />
* Special cases:<br />
** All plugins with ''mobile'' in their name, are related to [https://docs.moodle.org/310/en/Moodle_Mobile mobile devices].<br />
<br />
===Elementary school teaching===<br />
You might consider some plugins for [[Gamification|gamification]], such as the [https://moodle.org/plugins/mod_quizgame Quizventure].<br />
<br />
===Plugins for K-12 teaching===<br />
For [https://en.wikipedia.org/wiki/K%E2%80%9312 K-12] teaching and learning environments, please consider installing the plugins that are included in the [https://moodle.com/cloud/school/?utm_source=Sendy&utm_medium=Email&utm_campaign=Newsletter_July2016 Moodle for School at MoodleCloud]: <br />
* [https://moodle.org/plugins/mod_attendance Attendance]<br />
* [http://bigbluebutton.org/ BigBlueButton]<br />
* [https://moodle.org/plugins/mod_checklist Checklist]<br />
* [https://moodle.org/plugins/atto_chemistry Chemistry editor]<br />
* [https://moodle.org/plugins/mod_choicegroup Group choice]<br />
* [https://moodle.org/plugins/block_xp Level up!]<br />
* [https://moodle.org/plugins/mod_quizgame Quizventure]<br />
* [https://moodle.org/plugins/tinymce_wordcount Word count]<br />
<br />
===Plugins for University teaching===<br />
For universities, there is a [https://docs.moodle.org/310/en/Tertiary_education#Moodle_plugins_by.2Ffor_Universities list of plugins by/for Universities], and a [https://docs.moodle.org/310/en/Tertiary_education#Discipline-specific_plugins link to discipline-specific plugins], which might be worth considering.<br />
<br />
== Considerations for production sites (skip if you're just moodling) ==<br />
<br />
'''VERY IMPORTANT''' Warning: Please be aware that some plugins have not been reviewed, and the quality and/or suitability for your Moodle site has not been checked. Please be careful. It may not do what you expect, it may have serious security issues or it may even not work at all. This is however improving over time with the evolving new plugins directory system.<br />
<br />
* If you have a large site for production purposes consider if you '''really''' need the plugin? More functionality means more things to support, more things to (potentially) go wrong and more things to worry about at upgrade time. <br />
* Is the plugin supported and maintained? If something goes wrong can you get support? Will bugs be fixed?<br />
* If the plugin does not work in a future version of Moodle, what will you do about it?<br />
* Beware of ''patches'' ([https://moodle.org/plugins/browse.php?list=category&id=38 Moodle Plugins Directory Other category]) ! If a plugin modifies or replaces core files then be very careful. It can only be guaranteed to work with the exact build (version) of Moodle it was created for and is highly unlikely to survive a Moodle upgrade.<br />
* Look at [https://moodle.org/mod/forum/discuss.php?d=340821#p1373707 this] and [https://moodle.org/mod/forum/discuss.php?d=346296 also this] forum threads of users worried about installing a plugin.<br />
<br />
==Installing a plugin==<br />
<br />
To install a plugin, its source code must be put (deployed) into the appropriate location inside the Moodle installation directory and the main administration page ''Administration > Site administration > Notifications'' must be visited. There are three ways how the plugin code can be deployed into Moodle.<br />
<br />
Plugin code may be deployed from within Moodle, either directly from the Moodle plugins directory or by uploading a ZIP file. The web server process has to have write access to the plugin type folder where the new plugin is to be installed in order to use either of these methods.<br />
<br />
Alternatively, a plugin may be deployed manually at the server.<br />
<br />
===Installing directly from the Moodle plugins directory===<br />
<br />
# Login as an admin and go to ''Site administration > Plugins > Install plugins''. (If you can't find this location, then plugin installation is prevented on your site.)<br />
# Click the button 'Install plugins from Moodle plugins directory'.<br />
# Search for a plugin with an Install button, click the Install button then click Continue.<br />
# Confirm the installation request<br />
# Check the plugin validation report<br />
<br />
===Installing via uploaded ZIP file===<br />
<br />
# Go to the [https://moodle.org/plugins Moodle plugins directory], select your current Moodle version, then choose a plugin with a Download button and download the ZIP file.<br />
# Login to your Moodle site as an admin and go to ''Administration > Site administration > Plugins > Install plugins''.<br />
# Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if your plugin is not automatically detected.<br />
# If your target directory is not writeable, you will see a warning message.<br />
# Check the plugin validation report<br />
<br />
{|<br />
| [[File:plugin1.png|thumb|Install plugins]]<br />
| [[File:add-on package validation.png|thumb|Plugin package validation]]<br />
|}<br />
<br />
===Installing manually at the server===<br />
<br />
If you can't deploy the plugin code via the administration web interface, you have to copy it to the server file system manually (e.g. if the web server process does not have write access to the Moodle installation tree to do this for you).<br />
<br />
First, establish the correct place in the Moodle code tree for the plugin type. Common locations are:<br />
<br />
* /path/to/moodle/theme/ - themes<br />
* /path/to/moodle/mod/ - activity modules and resources<br />
* /path/to/moodle/blocks/ - sidebar blocks<br />
* /path/to/moodle/question/type/ - question types<br />
* /path/to/moodle/course/format/ - course formats<br />
* /path/to/moodle/admin/report/ - admin reports<br />
<br />
See [[:dev:Plugins]] for the full list of all plugin types and their locations within the Moodle tree.<br />
<br />
# Go to the [https://moodle.org/plugins Moodle plugins directory]; select your current Moodle version, then choose a plugin with a Download button and download the ZIP file.<br />
# Upload or copy it to your Moodle server.<br />
# Unzip it in the right place for the plugin type (or follow the plugin instructions). <br />
# In your Moodle site (as admin) go to ''Settings > Site administration > Notifications'' (you should, for most plugin types, get a message saying the plugin is installed).<br />
<br />
Note: The plugin may contain language files. They'll be found by your Moodle automatically. These language strings can be customized using the standard ''Settings > Site administration > Language'' editing interface. If you get a "Database error" when you try to edit your language files, there is a strong chance that the language files included within the downloaded ZIP file of this plugin have a coding problem. If you delete the ''plugin_name/lang/other_language_different_to_English/'' folder with the new language strings and the database error disappears, this is indeed the case. Please notify the plugin maintainer, so that it can be fixed in future releases.<br />
<br />
==Troubleshooting==<br />
<br />
===Errors===<br />
<br />
If you obtain an error, please [[Debugging|turn debugging on]] to obtain additional information about the cause of the error.<br />
<br />
;Database error while doing a language customization : May not be related to the [[Language_customisation#Database_error|Language customization]], but rather a problem with a recently installed plugin.<br />
<br />
;tool_installaddon/err_curl_exec - cURL error 60 : This suggests problems with the validation of the SSL certificate of the remote (moodle.org) site. This is also a known problem in Moodle Windows 7 servers running the Moodle package for Windows. See [[SSL certificate for moodle.org]] for more info and possible solutions.<br />
<br />
===A file permissions error has occurred===<br />
<br />
On certain 3.0.x versions, when installing plugins via the administration interface, the Moodle uses the configuration settings <tt>$CFG->directorypermissions</tt> and <tt>$CFG->filepermissions</tt>. If these are not defined explicitly in your config.php, the default value is set automatically to 777 (rwxrwxrwx) for directories and 666 (rw-rw-rw-) for files (see lib/setup.php).<br />
<br />
If this default behaviour does not fit your needs and hosting environment, you may wish to specify more strict setting such as<br />
<br />
$CFG->directorypermissions = 02750;<br />
<br />
A common error after installing plugins is that when you create an instance of the module and then save and display it, it reports the error, "A file permissions error has occurred. Please check the permissions on the script and the directory it is in and try again." If you get this, the file permissions of the package are mostl likely set to 711 preventing them from running correctly. With your preferred FTP client or via your web hosts control panel, set the file permissions of all the files and directories in the installed module, e.g. /moodle/mod/[myplugin]/ to 755 and then see if you can successfully view the module instance.<br />
<br />
===Default exception handler: Error writing to database Debug: Duplicate entry 'en_us-...===<br />
* These errors are usually caused by a third party plugin. <br />
* To find the involved plugin, go to [http://lang.moodle.org http://lang.moodle.org] and use the AMOS tool to find all the strings with the given string identifier.<br />
* Remove the suspected plugin and check if the error has disappeared. If so, please contact the plugin maintainer and report this issue.<br />
* Please see [https://moodle.org/mod/forum/discuss.php?d=219504 this forum thread] for known causes and fixes.<br />
<br />
===When installing manually===<br />
<br />
* Check the file permissions. The web server needs to be able to read the plugin files. If the the rest of Moodle works then try to make the plugin permissions and ownership match. <br />
* Did you '''definitely''' unzip or install the plugin in the correct place?<br />
* Because Moodle scans plugin folders for new plugins you cannot have any other files or folders there. Make sure you deleted the zip file and don't try to rename (for example) an old version of the plugin to some other name - it will break.<br />
* Make sure the directory name for the plugin is correct. All the names '''have''' to match. If you change the name, then it won't work.<br />
<br />
===Obtaining help===<br />
<br />
Ask in a forum in [http://moodle.org/course/view.php?id=5 Moodle in English]. Make sure you describe your system (including versions of MySQL, PHP etc.), what you tried and what happened. Copy and paste error messages exactly. Provide the link to the version of the plugin you downloaded (some have very similar names).<br />
<br />
==Uninstalling a plugin==<br />
<br />
To uninstall a plugin<br />
# Go to ''Administration> Site Administration > Plugins > Plugins overview'' and click the Uninstall link opposite the plugin you wish to remove<br />
# Use a file manager to remove/delete the actual plugin directory as instructed, otherwise Moodle will reinstall it next time you access the site administration<br />
<br />
==Plugins overview==<br />
<br />
[[File:plugins overview.png|thumb|center|400px|Plugins overview highlighting available check button]]<br />
<br />
The Plugins overview page in ''Administration > Site Administration > Plugins > Plugins overview'' lists all installed plugins, together with the version number,release, availability (enabled or disabled) and settings link (if applicable).<br />
<br />
A 'Check for available updates' button enables admins to quickly check for any updates available for plugins installed on the site (from the [http://moodle.org/plugins plugins directory]). Any updates available are highlighted, with further information and a download link in the notes column opposite the plugin.<br />
<br />
===Plugin updating from within Moodle===<br />
<br />
An administrator can enable updates deployment in ''Administration > Site Administration > Server > Update notifications''. Then when updates are available, 'Install this update' buttons are shown on the Plugins overview page. See [[Automatic updates deployment]] for more details.<br />
<br />
==Preventing installing plugins from within Moodle==<br />
<br />
If required, installing and updating from within Moodle can be prevented by copying the following lines of code from config-dist.php and pasting them in config.php.<br />
<br />
<code php><br />
// Use the following flag to completely disable the installation of plugins<br />
// (new plugins, available updates and missing dependencies) and related<br />
// features (such as cancelling the plugin installation or upgrade) via the<br />
// server administration web interface.<br />
$CFG->disableupdateautodeploy = true;<br />
</code><br />
<br />
==See also==<br />
* [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick<br />
* [[Notifications]] for further details of update notifications<br />
* [[Plugin Review Criteria]]<br />
* [[Plugins FAQ]]<br />
* Moodle in English [http://moodle.org/mod/forum/view.php?id=44 General plugins forum]<br />
* [[Installing Moodle from Git repository#Installing a contributed extension from its Git repository|Installing a contributed extension from its Git repository]]<br />
* [http://www.somerandomthoughts.com/blog/2013/05/07/managing-add-ons-in-moodle-2-5/ Managing add-ons in Moodle 2.5] blog post by Gavin Henrick<br />
* [https://youtu.be/uP_rUGZR0aw Moodle Plugins Administration] MoodleBites video on YouTube <br />
* [https://youtu.be/FU4RT2Yhld0 Install a new Theme] MoodleBites video on YouTube <br />
<br />
For developers:<br />
<br />
*[[:dev:Category:Plugins|Plugins developer documentation]]<br />
*[[:dev:Plugin validation]]<br />
*[[:dev:On-click add-on installation]]<br />
<br />
[[Category:Contributed code]]<br />
<br />
[[de:Plugins installieren]]<br />
[[es:Instalar complementos]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Installing_plugins&diff=127340Installing plugins2017-04-03T22:37:40Z<p>Stuartrmealor: /* Choosing the best plugins for your site */</p>
<hr />
<div>{{Installing Moodle}}<br />
==Why install additional plugins?==<br />
<br />
Plugins enable you to add additional features and functionality to Moodle, such as new activities, new quiz question types, new reports, integrations with other systems and many more. <br />
<br />
Note: Certain hosting solutions, such as [https://moodle.com/cloud/ MoodleCloud], prevent plugins being installed from within Moodle.<br />
<br />
==Choosing the best plugins for your site==<br />
<br />
Note: It is recommended that you proceed with caution and always try installing these plugins in a local experimental server before installing them in a production server.<br />
<br />
* Moodle has a [https://moodle.org/plugins/report/index.php?report=favourites&p=0&l=50&s=favourited&d=DESC list of the most favourite plugins], which might be worth considering for adding to your site :)<br />
* You can find the plugins with the largest number of downloads in the last three months at [https://moodle.org/plugins/stats.php https://moodle.org/plugins/stats.php]. These are the plugins most likely to be most useful for most sites. It would probably be a good idea to consider them first.<br />
* You can test and try more than 50 of the most popular Moodle plugins at [http://plugins.moodlebites.com plugins.moodlebites.com]<br />
* See the [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick<br />
* Moodle has a list of plugins that have received the [https://moodle.org/plugins/browse.php?list=award&id=1 Reviewers' choice award]. These are given by the plugins guardians and reviewers for particularly useful, well coded or otherwise interesting plugins. <br />
* Special cases:<br />
** All plugins with ''mobile'' in their name, are related to [https://docs.moodle.org/310/en/Moodle_Mobile mobile devices].<br />
<br />
===Elementary school teaching===<br />
You might consider some plugins for [[Gamification|gamification]], such as the [https://moodle.org/plugins/mod_quizgame Quizventure].<br />
<br />
===Plugins for K-12 teaching===<br />
For [https://en.wikipedia.org/wiki/K%E2%80%9312 K-12] teaching and learning environments, please consider installing the plugins that are included in the [https://moodle.com/cloud/school/?utm_source=Sendy&utm_medium=Email&utm_campaign=Newsletter_July2016 Moodle for School at MoodleCloud]: <br />
* [https://moodle.org/plugins/mod_attendance Attendance]<br />
* [http://bigbluebutton.org/ BigBlueButton]<br />
* [https://moodle.org/plugins/mod_checklist Checklist]<br />
* [https://moodle.org/plugins/atto_chemistry Chemistry editor]<br />
* [https://moodle.org/plugins/mod_choicegroup Group choice]<br />
* [https://moodle.org/plugins/block_xp Level up!]<br />
* [https://moodle.org/plugins/mod_quizgame Quizventure]<br />
* [https://moodle.org/plugins/tinymce_wordcount Word count]<br />
<br />
===Plugins for University teaching===<br />
For universities, there is a [https://docs.moodle.org/310/en/Tertiary_education#Moodle_plugins_by.2Ffor_Universities list of plugins by/for Universities], and a [https://docs.moodle.org/310/en/Tertiary_education#Discipline-specific_plugins link to discipline-specific plugins], which might be worth considering.<br />
<br />
== Considerations for production sites (skip if you're just moodling) ==<br />
<br />
'''VERY IMPORTANT''' Warning: Please be aware that some plugins have not been reviewed, and the quality and/or suitability for your Moodle site has not been checked. Please be careful. It may not do what you expect, it may have serious security issues or it may even not work at all. This is however improving over time with the evolving new plugins directory system.<br />
<br />
* If you have a large site for production purposes consider if you '''really''' need the plugin? More functionality means more things to support, more things to (potentially) go wrong and more things to worry about at upgrade time. <br />
* Is the plugin supported and maintained? If something goes wrong can you get support? Will bugs be fixed?<br />
* If the plugin does not work in a future version of Moodle, what will you do about it?<br />
* Beware of ''patches'' ([https://moodle.org/plugins/browse.php?list=category&id=38 Moodle Plugins Directory Other category]) ! If a plugin modifies or replaces core files then be very careful. It can only be guaranteed to work with the exact build (version) of Moodle it was created for and is highly unlikely to survive a Moodle upgrade.<br />
* Look at [https://moodle.org/mod/forum/discuss.php?d=340821#p1373707 this] and [https://moodle.org/mod/forum/discuss.php?d=346296 also this] forum threads of users worried about installing a plugin.<br />
<br />
==Installing a plugin==<br />
<br />
To install a plugin, its source code must be put (deployed) into the appropriate location inside the Moodle installation directory and the main administration page ''Administration > Site administration > Notifications'' must be visited. There are three ways how the plugin code can be deployed into Moodle.<br />
<br />
Plugin code may be deployed from within Moodle, either directly from the Moodle plugins directory or by uploading a ZIP file. The web server process has to have write access to the plugin type folder where the new plugin is to be installed in order to use either of these methods.<br />
<br />
Alternatively, a plugin may be deployed manually at the server.<br />
<br />
===Installing directly from the Moodle plugins directory===<br />
<br />
# Login as an admin and go to ''Site administration > Plugins > Install plugins''. (If you can't find this location, then plugin installation is prevented on your site.)<br />
# Click the button 'Install plugins from Moodle plugins directory'.<br />
# Search for a plugin with an Install button, click the Install button then click Continue.<br />
# Confirm the installation request<br />
# Check the plugin validation report<br />
<br />
===Installing via uploaded ZIP file===<br />
<br />
# Go to the [https://moodle.org/plugins Moodle plugins directory], select your current Moodle version, then choose a plugin with a Download button and download the ZIP file.<br />
# Login to your Moodle site as an admin and go to ''Administration > Site administration > Plugins > Install plugins''.<br />
# Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if your plugin is not automatically detected.<br />
# If your target directory is not writeable, you will see a warning message.<br />
# Check the plugin validation report<br />
<br />
{|<br />
| [[File:plugin1.png|thumb|Install plugins]]<br />
| [[File:add-on package validation.png|thumb|Plugin package validation]]<br />
|}<br />
<br />
===Installing manually at the server===<br />
<br />
If you can't deploy the plugin code via the administration web interface, you have to copy it to the server file system manually (e.g. if the web server process does not have write access to the Moodle installation tree to do this for you).<br />
<br />
First, establish the correct place in the Moodle code tree for the plugin type. Common locations are:<br />
<br />
* /path/to/moodle/theme/ - themes<br />
* /path/to/moodle/mod/ - activity modules and resources<br />
* /path/to/moodle/blocks/ - sidebar blocks<br />
* /path/to/moodle/question/type/ - question types<br />
* /path/to/moodle/course/format/ - course formats<br />
* /path/to/moodle/admin/report/ - admin reports<br />
<br />
See [[:dev:Plugins]] for the full list of all plugin types and their locations within the Moodle tree.<br />
<br />
# Go to the [https://moodle.org/plugins Moodle plugins directory]; select your current Moodle version, then choose a plugin with a Download button and download the ZIP file.<br />
# Upload or copy it to your Moodle server.<br />
# Unzip it in the right place for the plugin type (or follow the plugin instructions). <br />
# In your Moodle site (as admin) go to ''Settings > Site administration > Notifications'' (you should, for most plugin types, get a message saying the plugin is installed).<br />
<br />
Note: The plugin may contain language files. They'll be found by your Moodle automatically. These language strings can be customized using the standard ''Settings > Site administration > Language'' editing interface. If you get a "Database error" when you try to edit your language files, there is a strong chance that the language files included within the downloaded ZIP file of this plugin have a coding problem. If you delete the ''plugin_name/lang/other_language_different_to_English/'' folder with the new language strings and the database error disappears, this is indeed the case. Please notify the plugin maintainer, so that it can be fixed in future releases.<br />
<br />
==Troubleshooting==<br />
<br />
===Errors===<br />
<br />
If you obtain an error, please [[Debugging|turn debugging on]] to obtain additional information about the cause of the error.<br />
<br />
;Database error while doing a language customization : May not be related to the [[Language_customisation#Database_error|Language customization]], but rather a problem with a recently installed plugin.<br />
<br />
;tool_installaddon/err_curl_exec - cURL error 60 : This suggests problems with the validation of the SSL certificate of the remote (moodle.org) site. This is also a known problem in Moodle Windows 7 servers running the Moodle package for Windows. See [[SSL certificate for moodle.org]] for more info and possible solutions.<br />
<br />
===A file permissions error has occurred===<br />
<br />
On certain 3.0.x versions, when installing plugins via the administration interface, the Moodle uses the configuration settings <tt>$CFG->directorypermissions</tt> and <tt>$CFG->filepermissions</tt>. If these are not defined explicitly in your config.php, the default value is set automatically to 777 (rwxrwxrwx) for directories and 666 (rw-rw-rw-) for files (see lib/setup.php).<br />
<br />
If this default behaviour does not fit your needs and hosting environment, you may wish to specify more strict setting such as<br />
<br />
$CFG->directorypermissions = 02750;<br />
<br />
A common error after installing plugins is that when you create an instance of the module and then save and display it, it reports the error, "A file permissions error has occurred. Please check the permissions on the script and the directory it is in and try again." If you get this, the file permissions of the package are mostl likely set to 711 preventing them from running correctly. With your preferred FTP client or via your web hosts control panel, set the file permissions of all the files and directories in the installed module, e.g. /moodle/mod/[myplugin]/ to 755 and then see if you can successfully view the module instance.<br />
<br />
===Default exception handler: Error writing to database Debug: Duplicate entry 'en_us-...===<br />
* These errors are usually caused by a third party plugin. <br />
* To find the involved plugin, go to [http://lang.moodle.org http://lang.moodle.org] and use the AMOS tool to find all the strings with the given string identifier.<br />
* Remove the suspected plugin and check if the error has disappeared. If so, please contact the plugin maintainer and report this issue.<br />
* Please see [https://moodle.org/mod/forum/discuss.php?d=219504 this forum thread] for known causes and fixes.<br />
<br />
===When installing manually===<br />
<br />
* Check the file permissions. The web server needs to be able to read the plugin files. If the the rest of Moodle works then try to make the plugin permissions and ownership match. <br />
* Did you '''definitely''' unzip or install the plugin in the correct place?<br />
* Because Moodle scans plugin folders for new plugins you cannot have any other files or folders there. Make sure you deleted the zip file and don't try to rename (for example) an old version of the plugin to some other name - it will break.<br />
* Make sure the directory name for the plugin is correct. All the names '''have''' to match. If you change the name, then it won't work.<br />
<br />
===Obtaining help===<br />
<br />
Ask in a forum in [http://moodle.org/course/view.php?id=5 Moodle in English]. Make sure you describe your system (including versions of MySQL, PHP etc.), what you tried and what happened. Copy and paste error messages exactly. Provide the link to the version of the plugin you downloaded (some have very similar names).<br />
<br />
==Uninstalling a plugin==<br />
<br />
To uninstall a plugin<br />
# Go to ''Administration> Site Administration > Plugins > Plugins overview'' and click the Uninstall link opposite the plugin you wish to remove<br />
# Use a file manager to remove/delete the actual plugin directory as instructed, otherwise Moodle will reinstall it next time you access the site administration<br />
<br />
==Plugins overview==<br />
<br />
[[File:plugins overview.png|thumb|center|400px|Plugins overview highlighting available check button]]<br />
<br />
The Plugins overview page in ''Administration > Site Administration > Plugins > Plugins overview'' lists all installed plugins, together with the version number,release, availability (enabled or disabled) and settings link (if applicable).<br />
<br />
A 'Check for available updates' button enables admins to quickly check for any updates available for plugins installed on the site (from the [http://moodle.org/plugins plugins directory]). Any updates available are highlighted, with further information and a download link in the notes column opposite the plugin.<br />
<br />
===Plugin updating from within Moodle===<br />
<br />
An administrator can enable updates deployment in ''Administration > Site Administration > Server > Update notifications''. Then when updates are available, 'Install this update' buttons are shown on the Plugins overview page. See [[Automatic updates deployment]] for more details.<br />
<br />
==Preventing installing plugins from within Moodle==<br />
<br />
If required, installing and updating from within Moodle can be prevented by copying the following lines of code from config-dist.php and pasting them in config.php.<br />
<br />
<code php><br />
// Use the following flag to completely disable the installation of plugins<br />
// (new plugins, available updates and missing dependencies) and related<br />
// features (such as cancelling the plugin installation or upgrade) via the<br />
// server administration web interface.<br />
$CFG->disableupdateautodeploy = true;<br />
</code><br />
<br />
==See also==<br />
* [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick<br />
* [[Notifications]] for further details of update notifications<br />
* [[Plugin Review Criteria]]<br />
* [[Plugins FAQ]]<br />
* Moodle in English [http://moodle.org/mod/forum/view.php?id=44 General plugins forum]<br />
* [[Installing Moodle from Git repository#Installing a contributed extension from its Git repository|Installing a contributed extension from its Git repository]]<br />
* [http://www.somerandomthoughts.com/blog/2013/05/07/managing-add-ons-in-moodle-2-5/ Managing add-ons in Moodle 2.5] blog post by Gavin Henrick<br />
*[http://youtu.be/RxlmVzIllVk Moodle 2 Plugins Administration] MoodleBites video on YouTube <br />
* [http://youtu.be/K3MYE8am7M4 Install a New Theme] MoodleBites video on YouTube <br />
<br />
For developers:<br />
<br />
*[[:dev:Category:Plugins|Plugins developer documentation]]<br />
*[[:dev:Plugin validation]]<br />
*[[:dev:On-click add-on installation]]<br />
<br />
[[Category:Contributed code]]<br />
<br />
[[de:Plugins installieren]]<br />
[[es:Instalar complementos]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Installing_plugins&diff=127339Installing plugins2017-04-03T22:26:35Z<p>Stuartrmealor: /* Choosing the best plugins for your site */</p>
<hr />
<div>{{Installing Moodle}}<br />
==Why install additional plugins?==<br />
<br />
Plugins enable you to add additional features and functionality to Moodle, such as new activities, new quiz question types, new reports, integrations with other systems and many more. <br />
<br />
Note: Certain hosting solutions, such as [https://moodle.com/cloud/ MoodleCloud], prevent plugins being installed from within Moodle.<br />
<br />
==Choosing the best plugins for your site==<br />
<br />
Note: It is recommended that you proceed with caution and always try installing these plugins in a local experimental server before installing them in a production server.<br />
<br />
* Moodle has a [https://moodle.org/plugins/report/index.php?report=favourites&p=0&l=50&s=favourited&d=DESC list of the most favourite plugins], which might be worth considering for adding to your site :)<br />
* You can find the plugins with the largest number of downloads in the last three months at [https://moodle.org/plugins/stats.php https://moodle.org/plugins/stats.php]. These are the plugins most likely to be most useful for most sites. It would probably be a good idea to consider them first.<br />
* You can see and try 50 of the most popular Moodle plugins at [http://plugins.moodlebites.com]<br />
* See the [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick<br />
* Moodle has a list of plugins that have received the [https://moodle.org/plugins/browse.php?list=award&id=1 Reviewers' choice award]. These are given by the plugins guardians and reviewers for particularly useful, well coded or otherwise interesting plugins. <br />
* Special cases:<br />
** All plugins with ''mobile'' in their name, are related to [https://docs.moodle.org/310/en/Moodle_Mobile mobile devices].<br />
<br />
===Elementary school teaching===<br />
You might consider some plugins for [[Gamification|gamification]], such as the [https://moodle.org/plugins/mod_quizgame Quizventure].<br />
<br />
===Plugins for K-12 teaching===<br />
For [https://en.wikipedia.org/wiki/K%E2%80%9312 K-12] teaching and learning environments, please consider installing the plugins that are included in the [https://moodle.com/cloud/school/?utm_source=Sendy&utm_medium=Email&utm_campaign=Newsletter_July2016 Moodle for School at MoodleCloud]: <br />
* [https://moodle.org/plugins/mod_attendance Attendance]<br />
* [http://bigbluebutton.org/ BigBlueButton]<br />
* [https://moodle.org/plugins/mod_checklist Checklist]<br />
* [https://moodle.org/plugins/atto_chemistry Chemistry editor]<br />
* [https://moodle.org/plugins/mod_choicegroup Group choice]<br />
* [https://moodle.org/plugins/block_xp Level up!]<br />
* [https://moodle.org/plugins/mod_quizgame Quizventure]<br />
* [https://moodle.org/plugins/tinymce_wordcount Word count]<br />
<br />
===Plugins for University teaching===<br />
For universities, there is a [https://docs.moodle.org/310/en/Tertiary_education#Moodle_plugins_by.2Ffor_Universities list of plugins by/for Universities], and a [https://docs.moodle.org/310/en/Tertiary_education#Discipline-specific_plugins link to discipline-specific plugins], which might be worth considering.<br />
<br />
== Considerations for production sites (skip if you're just moodling) ==<br />
<br />
'''VERY IMPORTANT''' Warning: Please be aware that some plugins have not been reviewed, and the quality and/or suitability for your Moodle site has not been checked. Please be careful. It may not do what you expect, it may have serious security issues or it may even not work at all. This is however improving over time with the evolving new plugins directory system.<br />
<br />
* If you have a large site for production purposes consider if you '''really''' need the plugin? More functionality means more things to support, more things to (potentially) go wrong and more things to worry about at upgrade time. <br />
* Is the plugin supported and maintained? If something goes wrong can you get support? Will bugs be fixed?<br />
* If the plugin does not work in a future version of Moodle, what will you do about it?<br />
* Beware of ''patches'' ([https://moodle.org/plugins/browse.php?list=category&id=38 Moodle Plugins Directory Other category]) ! If a plugin modifies or replaces core files then be very careful. It can only be guaranteed to work with the exact build (version) of Moodle it was created for and is highly unlikely to survive a Moodle upgrade.<br />
* Look at [https://moodle.org/mod/forum/discuss.php?d=340821#p1373707 this] and [https://moodle.org/mod/forum/discuss.php?d=346296 also this] forum threads of users worried about installing a plugin.<br />
<br />
==Installing a plugin==<br />
<br />
To install a plugin, its source code must be put (deployed) into the appropriate location inside the Moodle installation directory and the main administration page ''Administration > Site administration > Notifications'' must be visited. There are three ways how the plugin code can be deployed into Moodle.<br />
<br />
Plugin code may be deployed from within Moodle, either directly from the Moodle plugins directory or by uploading a ZIP file. The web server process has to have write access to the plugin type folder where the new plugin is to be installed in order to use either of these methods.<br />
<br />
Alternatively, a plugin may be deployed manually at the server.<br />
<br />
===Installing directly from the Moodle plugins directory===<br />
<br />
# Login as an admin and go to ''Site administration > Plugins > Install plugins''. (If you can't find this location, then plugin installation is prevented on your site.)<br />
# Click the button 'Install plugins from Moodle plugins directory'.<br />
# Search for a plugin with an Install button, click the Install button then click Continue.<br />
# Confirm the installation request<br />
# Check the plugin validation report<br />
<br />
===Installing via uploaded ZIP file===<br />
<br />
# Go to the [https://moodle.org/plugins Moodle plugins directory], select your current Moodle version, then choose a plugin with a Download button and download the ZIP file.<br />
# Login to your Moodle site as an admin and go to ''Administration > Site administration > Plugins > Install plugins''.<br />
# Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if your plugin is not automatically detected.<br />
# If your target directory is not writeable, you will see a warning message.<br />
# Check the plugin validation report<br />
<br />
{|<br />
| [[File:plugin1.png|thumb|Install plugins]]<br />
| [[File:add-on package validation.png|thumb|Plugin package validation]]<br />
|}<br />
<br />
===Installing manually at the server===<br />
<br />
If you can't deploy the plugin code via the administration web interface, you have to copy it to the server file system manually (e.g. if the web server process does not have write access to the Moodle installation tree to do this for you).<br />
<br />
First, establish the correct place in the Moodle code tree for the plugin type. Common locations are:<br />
<br />
* /path/to/moodle/theme/ - themes<br />
* /path/to/moodle/mod/ - activity modules and resources<br />
* /path/to/moodle/blocks/ - sidebar blocks<br />
* /path/to/moodle/question/type/ - question types<br />
* /path/to/moodle/course/format/ - course formats<br />
* /path/to/moodle/admin/report/ - admin reports<br />
<br />
See [[:dev:Plugins]] for the full list of all plugin types and their locations within the Moodle tree.<br />
<br />
# Go to the [https://moodle.org/plugins Moodle plugins directory]; select your current Moodle version, then choose a plugin with a Download button and download the ZIP file.<br />
# Upload or copy it to your Moodle server.<br />
# Unzip it in the right place for the plugin type (or follow the plugin instructions). <br />
# In your Moodle site (as admin) go to ''Settings > Site administration > Notifications'' (you should, for most plugin types, get a message saying the plugin is installed).<br />
<br />
Note: The plugin may contain language files. They'll be found by your Moodle automatically. These language strings can be customized using the standard ''Settings > Site administration > Language'' editing interface. If you get a "Database error" when you try to edit your language files, there is a strong chance that the language files included within the downloaded ZIP file of this plugin have a coding problem. If you delete the ''plugin_name/lang/other_language_different_to_English/'' folder with the new language strings and the database error disappears, this is indeed the case. Please notify the plugin maintainer, so that it can be fixed in future releases.<br />
<br />
==Troubleshooting==<br />
<br />
===Errors===<br />
<br />
If you obtain an error, please [[Debugging|turn debugging on]] to obtain additional information about the cause of the error.<br />
<br />
;Database error while doing a language customization : May not be related to the [[Language_customisation#Database_error|Language customization]], but rather a problem with a recently installed plugin.<br />
<br />
;tool_installaddon/err_curl_exec - cURL error 60 : This suggests problems with the validation of the SSL certificate of the remote (moodle.org) site. This is also a known problem in Moodle Windows 7 servers running the Moodle package for Windows. See [[SSL certificate for moodle.org]] for more info and possible solutions.<br />
<br />
===A file permissions error has occurred===<br />
<br />
On certain 3.0.x versions, when installing plugins via the administration interface, the Moodle uses the configuration settings <tt>$CFG->directorypermissions</tt> and <tt>$CFG->filepermissions</tt>. If these are not defined explicitly in your config.php, the default value is set automatically to 777 (rwxrwxrwx) for directories and 666 (rw-rw-rw-) for files (see lib/setup.php).<br />
<br />
If this default behaviour does not fit your needs and hosting environment, you may wish to specify more strict setting such as<br />
<br />
$CFG->directorypermissions = 02750;<br />
<br />
A common error after installing plugins is that when you create an instance of the module and then save and display it, it reports the error, "A file permissions error has occurred. Please check the permissions on the script and the directory it is in and try again." If you get this, the file permissions of the package are mostl likely set to 711 preventing them from running correctly. With your preferred FTP client or via your web hosts control panel, set the file permissions of all the files and directories in the installed module, e.g. /moodle/mod/[myplugin]/ to 755 and then see if you can successfully view the module instance.<br />
<br />
===Default exception handler: Error writing to database Debug: Duplicate entry 'en_us-...===<br />
* These errors are usually caused by a third party plugin. <br />
* To find the involved plugin, go to [http://lang.moodle.org http://lang.moodle.org] and use the AMOS tool to find all the strings with the given string identifier.<br />
* Remove the suspected plugin and check if the error has disappeared. If so, please contact the plugin maintainer and report this issue.<br />
* Please see [https://moodle.org/mod/forum/discuss.php?d=219504 this forum thread] for known causes and fixes.<br />
<br />
===When installing manually===<br />
<br />
* Check the file permissions. The web server needs to be able to read the plugin files. If the the rest of Moodle works then try to make the plugin permissions and ownership match. <br />
* Did you '''definitely''' unzip or install the plugin in the correct place?<br />
* Because Moodle scans plugin folders for new plugins you cannot have any other files or folders there. Make sure you deleted the zip file and don't try to rename (for example) an old version of the plugin to some other name - it will break.<br />
* Make sure the directory name for the plugin is correct. All the names '''have''' to match. If you change the name, then it won't work.<br />
<br />
===Obtaining help===<br />
<br />
Ask in a forum in [http://moodle.org/course/view.php?id=5 Moodle in English]. Make sure you describe your system (including versions of MySQL, PHP etc.), what you tried and what happened. Copy and paste error messages exactly. Provide the link to the version of the plugin you downloaded (some have very similar names).<br />
<br />
==Uninstalling a plugin==<br />
<br />
To uninstall a plugin<br />
# Go to ''Administration> Site Administration > Plugins > Plugins overview'' and click the Uninstall link opposite the plugin you wish to remove<br />
# Use a file manager to remove/delete the actual plugin directory as instructed, otherwise Moodle will reinstall it next time you access the site administration<br />
<br />
==Plugins overview==<br />
<br />
[[File:plugins overview.png|thumb|center|400px|Plugins overview highlighting available check button]]<br />
<br />
The Plugins overview page in ''Administration > Site Administration > Plugins > Plugins overview'' lists all installed plugins, together with the version number,release, availability (enabled or disabled) and settings link (if applicable).<br />
<br />
A 'Check for available updates' button enables admins to quickly check for any updates available for plugins installed on the site (from the [http://moodle.org/plugins plugins directory]). Any updates available are highlighted, with further information and a download link in the notes column opposite the plugin.<br />
<br />
===Plugin updating from within Moodle===<br />
<br />
An administrator can enable updates deployment in ''Administration > Site Administration > Server > Update notifications''. Then when updates are available, 'Install this update' buttons are shown on the Plugins overview page. See [[Automatic updates deployment]] for more details.<br />
<br />
==Preventing installing plugins from within Moodle==<br />
<br />
If required, installing and updating from within Moodle can be prevented by copying the following lines of code from config-dist.php and pasting them in config.php.<br />
<br />
<code php><br />
// Use the following flag to completely disable the installation of plugins<br />
// (new plugins, available updates and missing dependencies) and related<br />
// features (such as cancelling the plugin installation or upgrade) via the<br />
// server administration web interface.<br />
$CFG->disableupdateautodeploy = true;<br />
</code><br />
<br />
==See also==<br />
* [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick<br />
* [[Notifications]] for further details of update notifications<br />
* [[Plugin Review Criteria]]<br />
* [[Plugins FAQ]]<br />
* Moodle in English [http://moodle.org/mod/forum/view.php?id=44 General plugins forum]<br />
* [[Installing Moodle from Git repository#Installing a contributed extension from its Git repository|Installing a contributed extension from its Git repository]]<br />
* [http://www.somerandomthoughts.com/blog/2013/05/07/managing-add-ons-in-moodle-2-5/ Managing add-ons in Moodle 2.5] blog post by Gavin Henrick<br />
*[http://youtu.be/RxlmVzIllVk Moodle 2 Plugins Administration] MoodleBites video on YouTube <br />
* [http://youtu.be/K3MYE8am7M4 Install a New Theme] MoodleBites video on YouTube <br />
<br />
For developers:<br />
<br />
*[[:dev:Category:Plugins|Plugins developer documentation]]<br />
*[[:dev:Plugin validation]]<br />
*[[:dev:On-click add-on installation]]<br />
<br />
[[Category:Contributed code]]<br />
<br />
[[de:Plugins installieren]]<br />
[[es:Instalar complementos]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Creating_mobile-friendly_courses&diff=123997Creating mobile-friendly courses2016-06-01T07:35:43Z<p>Stuartrmealor: /* Learn more */</p>
<hr />
<div>{{Mobile}}<br />
As more and more students access courses from their smartphones, tablets or other mobile devices, it is increasingly important to ensure your courses are mobile-friendly.<br />
<br />
Encouraging students to install the [https://download.moodle.org/mobile/ official Moodle mobile app] is one way to improve their learning experience. Below are some suggestions for optimising your course materials for students both using the app and accessing Moodle from mobile devices.<br />
<br />
==Use a mobile-friendly theme==<br />
<br />
Recent versions of Moodle allow for responsive themes, which adapt to the browser screen size. Make sure your course uses such a theme and check its contents yourself before your students start the course.<br />
<br />
==Notifications and messages==<br />
<br />
Encourage your students to enable mobile notifications so they are alerted about calendar events, forum posts, messages, assignment submissions and so on. Find out more in [[Mobile app notifications]].<br />
<br />
==Provide a 'how to' guide to Moodle on the mobile==<br />
<br />
Consider offering your students a guide (as a PDF or a page resource) on how to access your course on the app, what they can do and not (yet) do from the app. Read up on the [[Moodle Mobile features]] and what's [[New for mobile]].<br />
<br />
==Setting up your course==<br />
<br />
*Topics or weekly course format is best suited to mobile devices.<br />
*Don't use orphaned activities or direct links to activities.<br />
*If you have a mix of students accessing the course on mobile and desktop, consider asking your admin to install the [[Moodle Mobile availability plugin]] which restricts items to desktop or mobile users.<br />
<br />
==Course content==<br />
<br />
*Labels are initially collapsed, so include a short text introduction of what is inside any label.<br />
*Use responsive HTML in pages or mini-sites.<br />
*Try to use a [[Page resource|page resource]] instead of downloadable documents where possible.<br />
*Avoid uploading many documents or having numerous, text heavy pages. Think more in terms of short "information-bytes".<br />
*If you include YouTube videos, provide them also for download and offline viewing in a [[Folder resource|folder]]. Not all video formats are supported so add them in different formats. (MP4 is probably the most widely accepted format.)<br />
*Note that if you add YouTube video links or map links as URL resources, they will open automatically in the app.<br />
<br />
{|<br />
| [[File:moodlemobile_short_text_intro.png|thumb|Short text for label]]<br />
| [[File:moodlemobile_responsive_html.png|thumb|Responsive HTML]]<br />
| [[File:moodlemobile_youtube_maps_links.png|thumb|Map link]]<br />
|}<br />
<br />
===Media download for offline usage===<br />
<br />
To enable media files, such as video, to be downloaded<br />
<br />
* The file must be uploaded to the course, rather than being linked to (from YouTube, Vimeo etc)<br />
* The file must be small - less than 2MB for 3G users or less than 20MB for WiFi users<br />
<br />
When a page containing the video is viewed (without playing the video), the file will then be downloaded.<br />
<br />
When using Moodle Mobile 3.1 with a WiFi connection, when the video is played, the file will be downloaded in the background. The next time the video is played, the downloaded file will be used.<br />
<br />
=== Things to avoid===<br />
<br />
Some activities are not yet fully supported by the mobile app, so find alternatives. See [[Moodle Mobile SCORM player]] for things to avoid in SCORM packages.<br />
<br />
==Links to open the Moodle Mobile app==<br />
<br />
If required, links which open the Moodle Mobile app may be provided in the course (for users browsing the site using a mobile device with the app installed).<br />
<br />
Links are of the form <code>moodlemobile://link=https://yourmoodlesite.org/mod/...</code><br />
<br />
For example, the link <code>moodlemobile://link=https://mysite.es/mod/choice/view.php?id=8</code> will open the mobile app and display a choice activity.<br />
<br />
==Learn more==<br />
<br />
* A "[http://mobile.moodlebites.com free Moodle Mobile MOOC]" run by [http://www.hrdnz.com HRDNZ] (Moodle Partner) twice a year, specifically focussing on the use of Moodle with mobile devices, and how to best design courses for these environments - including the Moodle Mobile App. <br />
* [http://es.slideshare.net/juanleyva/tips-for-creating-moodle-mobile-friendly-courses-sites-moodlemoot-spain-2014 Tips for creating Moodle Mobile friendly courses and sites - MoodleMoot Spain 2014] - Juan Leyva, Mobile app developer, presented this in 2014. While some features have now been updated, the general principles are still useful. <br />
* An open course, about "[http://tempus-efa.proj.ac.il/moodle/course/view.php?id=102 Teaching using Mobile - Best practices]"<br />
<br />
[[es:Crear sitios amistosos para Moodle Mobile]]<br />
[[fr:Créer des cours pour appareils mobiles]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Step-by-step_Installation_Guide_for_Ubuntu&diff=106734Step-by-step Installation Guide for Ubuntu2013-09-30T22:03:08Z<p>Stuartrmealor: /* Step 4: Download Moodle */</p>
<hr />
<div>== Step 1: Install Ubuntu 10.04 ==<br />
<br />
http://www.ubuntu.com/download<br />
<br />
== Step 2: Install LAMP stack ==<br />
Open the Terminal and install tasksel<br />
<br />
<pre>sudo apt-get install tasksel</pre><br />
<br />
and then the LAMP stack:<br />
<br />
<pre>sudo tasksel install lamp-server</pre><br />
<br />
<br />
This will run a gui install of the lamp stack. <br />
<br />
''''It will prompt you to set the root password for mysql - take note of it, you will need it in step 5.'''<br />
<br />
== Step 3: Install the additional PHP extensions ==<br />
<br />
<pre>sudo apt-get install php5-curl php5-gd php5-intl php5-xmlrpc</pre><br />
<br />
restart apache for the installation to complete<br />
<br />
<pre>sudo service apache2 restart</pre><br />
<br />
== Step 4: Download Moodle ==<br />
<br />
<pre>cd /var/www<br />
<br />
sudo wget http://download.moodle.org/stable25/moodle-latest-25.tgz<br />
<br />
sudo tar -zxf moodle-latest-25.tgz<br />
<br />
sudo mkdir /var/moodledata<br />
<br />
sudo chmod 777 /var/moodledata<br />
<br />
sudo chmod 777 /var/www/moodle</pre><br />
<br />
== Step 5: Create Moodle database ==<br />
<pre>mysql -u root -p</pre><br />
<br />
You will be prompted for the mysql root password you have created in step 2<br />
<br />
<pre>create database moodledb charset=utf8;<br />
<br />
create user 'mdluser'@'localhost' identified by 'password';<br />
<br />
grant all privileges on moodledb.* to 'mdluser'@'localhost';<br />
<br />
\q</pre><br />
<br />
== Step 6: Setup Moodle server ==<br />
<br />
Open your browser and go to http://localhost/moodle <br />
<br />
Follow the prompts selecting:<br />
<br />
===database type===<br />
<br />
Choose: mysqli<br />
<br />
=== database settings ===<br />
<br />
Host server: localhost<br />
<br />
Database: moodledb<br />
<br />
User: mdluser<br />
<br />
Password: password<br />
<br />
Tables Prefix: mdl_<br />
<br />
=== environment checks ===<br />
<br />
This will indicate if any elements required to run moodle haven't been installed.<br />
<br />
=== next next next... ===<br />
follow prompts and confirm installation<br />
<br />
===create a site administrator account ===<br />
Create your moodle user account which will have site administrator permissions.<br />
<br />
The password you select has to meet certain security requirements.<br />
<br />
===Installation Complete ===<br />
Bravo! You can now start playing with moodle!</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Mobile_web_services&diff=89446Mobile web services2011-09-11T00:38:52Z<p>Stuartrmealor: Fixed typo</p>
<hr />
<div>Moodle 2.1 comes with a built-in web service designed for mobile applications. It is required to run the official [https://docs.moodle.org/en/Development:Mobile_app Moodle app]. Enable it only if you want people to use the official app or if third party app explicitly requires it.<br />
<br />
== Enable the mobile web services ==<br />
Go to ''Administration block > Plugins > Web services > External services.''<br />
Check ''Enable mobile web services'' and ''Save''.<br />
<br />
'''That's it! No other steps required.''' <br />
<br />
The rest of this document explains "behind the scenes" for any further mobile service customisation.<br />
<br />
Enabling the mobile web services will automatically:<br />
* enable the web services system (''Administration block > Advanced features'')<br />
* enable the built-in external service called 'Mobile web services' - you should see this new mobile service listed as enabled.<br />
* enable the xml-rpc protocol<br />
* allow the 'webservice/xmlrpc:use' capability for authenticated user role<br />
<br />
It is not possible to edit this mobile service.<br />
<br />
== Disable the mobile web services ==<br />
When you uncheck 'Enable mobile web services', it will automatically:<br />
* disable the external service called 'Mobile web services'.<br />
*if 'Mobile web services' was the only external service enabled:<br />
** disable the web services system<br />
** disable the xml-rpc protocol<br />
** disallow the 'webservice/xmlrpc:use' capability for authenticated user role<br />
<br />
[[Category:Web Services]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Manager_role&diff=82020Manager role2011-03-17T10:45:11Z<p>Stuartrmealor: Edited a useful description provided by Tim Hunt in a Moodle.org Forum</p>
<hr />
<div>{{stub}}{{Moodle 2.0}}<br />
<br />
The default manager role, in Moodle 2.0 onwards, enables users assigned the role to access courses and modify them.<br />
<br />
The Manager role is a 'real role', ''similar'' to Administrator (but much safer to use).<br />
<br />
The way permission checks work in the Moodle code is that there is a function called has_capability. For admins, has_capability will '''always''' return true, no matter how the roles are set up.<br />
<br />
However, the Manager role is a normal role, like Course Creator, or Teacher. By default the Manager role has almost every capability but, because it is a normal role, you can edit that role if you choose (there is no way to edit what permissions an Administrator has).<br />
Best-practice might suggest that Admins should normally use a Manager role, and not use an Administrator account.<br />
<br />
This is similar to the way you are recommended not to log into Linux as root.<br />
<br />
The Manager role therefore allows a site Administrator to give very powerful roles to others who are assigned a Manager role, but without having to give them a full Administrator role.<br />
<br />
==See also==<br />
<br />
* [[Site administrators]]<br />
<br />
[[Category:Roles]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Custom_SQL_queries_report&diff=70881Custom SQL queries report2010-04-09T22:07:01Z<p>Stuartrmealor: /* Monthly Usage by Role */</p>
<hr />
<div>Created by The Open University<br />
<br />
This admin report plugin allows Administrators to set up arbitrary database queries to act as ad-hoc reports. Reports can be of two types: either run on demand, or scheduled to run automatically. Other users with the right capability can go in and see a list of queries that they have access to. Results can be viewed on-screen or downloaded as CSV.<br />
<br />
==Installing this report==<br />
<br />
Follow the generic [[Installing contributed modules or plugins]] documentation.<br />
<br />
<br />
==Screen shots==<br />
<br />
Here are two example screen shots, showing the two main screens.<br />
<br />
[[Image:Custom_report_list.png|thumb|none|600px|The list of available reports]]<br />
[[Image:Custom_report.png|thumb|none|600px|The results of running one of the reports]]<br />
<br />
(Note, these screen shots are in the OU theme, not the standard Moodle theme, and iCMA is OU-jargon for quiz.)<br />
<br />
==Interface for normal users==<br />
<br />
===List of available queries===<br />
<br />
Users with the report/customsql:view capability can access the list of reports in the admin block. Each query is accessible only to a certain people. There are three levels of access:<br />
* Available to any one who can access the report at all (those with report/customsql:view).<br />
* Available to people who are able to see other system reports (those with moodle/site:viewreports)<br />
* Available to administrators only (those with moodle/site:config)<br />
<br />
When you go to the list, it will only show the queries you have access to. There is a note beside each query saying when it was last run, and how long it took to generate.<br />
<br />
The list shows on-demand and scheduled queries separately.<br />
<br />
<br />
===Running an on-demand query===<br />
<br />
To run an on-demand query, click on its name in the list of queries.<br />
<br />
The query will be run, and the results will be displayed as a table. Any URLs in the table will automatically be made into hyperlinks.<br />
<br />
A description of the query may appear above the table.<br />
<br />
The summary of when the query was run and how long it took is shown at the bottom, along with a link to download the CSV file (for example to get the data into Excel) and a link back to the list of all available queries.<br />
<br />
<br />
===Viewing the results of scheduled queries===<br />
<br />
Scheduled queries can work in one of two ways. Either each run of the report generates and entire table of reasults, or each run just creates one line of results, and the report builds up a row at a time.<br />
<br />
When you click the name in the list of queries, you get taken to a display of the latest results, just like in the on-demand case.<br />
<br />
However, if each scheduled run generates a complete report, then at the bottom of a page there will be a list of all the previous runs of the report, so that you can go and see how the report changed over time.<br />
<br />
<br />
==Interface for administrators==<br />
<br />
Administrators (that is, users with report/customsql:definequeries) see everything that other users see, but with some additions.<br />
<br />
<br />
===Additional controls in the staff interface===<br />
<br />
Administrators get shown who each report in the list is available to.<br />
<br />
They also get an edit and a delete icon next to each query.<br />
<br />
There is an '''Add new query button''' at the end of the list of queries.<br />
<br />
When viewing a particular query, Administrators get an edit and a delete link underneath the table of results.<br />
<br />
<br />
===Adding or editing a query===<br />
<br />
When you click the '''Add new query button''', you get taken to an editing form that lets you define the query.<br />
<br />
You must give the query a name.<br />
<br />
You can optionally enter a description that is displayed above the results table. You should use this to explain what the results of the query mean.<br />
<br />
You must enter the SQL to generate the results you want displayed. This must be an SQL select statement. You must use the prefix prefix_ for table names. It should not be possible to enter any SQL that would alter the contents of the database.<br />
<br />
You choose who you want the query to be accessible to.<br />
<br />
You choose whether the query should be run on-demand or scheduled weekly or monthly. If the report is scheduled, you can say whether the each run returns one row to be added to a single table, or whether each run generates a separate table.<br />
<br />
When you save the new query, the SQL is checked to make sure that it will execute without errors. If you have said that the report will only return a single row, this is also checked.<br />
After saving the query, if this was a manual query, you are taken to the query results page, so you can see what the results look like. If it was an automatic query or if you cancel the form, you are taken to the list of available queries.<br />
<br />
Editing an existing query uses the same form as for adding a new query, but to change the properties of an existing query.<br />
<br />
Note that at the OU, weeks start on Saturday. If you don't like that, there is a fairly obvious constant to hack at the top of locallib.php.<br />
<br />
===Deleting a query===<br />
<br />
When you click the delete icon or link for a query, you are taken to a confirmation page that shows you SQL of the query you are about to delete. The query is only deleted if you click Yes on the confirmation page.<br />
<br />
After deleting a query, you are taken back to the list of queries.<br />
<br />
==Share your interesting queries here==<br />
<br />
If you come up with any interesting SQL to custom reports, you can share it here.<br />
<br />
===Quiz attempts in the last week/month===<br />
<br />
Set this up as a scheduled report:<br />
<br />
<code sql><br />
SELECT COUNT(*)<br />
FROM prefix_quiz_attempts<br />
WHERE timefinish > %%STARTTIME%%<br />
AND timefinish <= %%ENDTIME%%<br />
AND preview = 0<br />
</code><br />
<br />
This '''must''' be set up as a '''Scheduled, on the first day of each week''' or '''Scheduled, on the first day of each month''' report, or it will not work.<br />
<br />
===Usage summary===<br />
<br />
This report shows roughly the same usage statistics that are sent to moodle.org when you register your site. The ones that are aggregated at http://moodle.org/stats/. (The only difference is that the registration form does not do AND confirmed = 1 for some reason.<br />
<br />
<code sql><br />
SELECT<br />
(SELECT COUNT(id) FROM prefix_course) - 1 AS courses,<br />
(SELECT COUNT(id) FROM prefix_user WHERE deleted = 0 AND confirmed = 1) AS users,<br />
(SELECT COUNT(DISTINCT ra.userid)<br />
FROM prefix_role_capabilities rc<br />
JOIN prefix_role_assignments ra ON ra.roleid = rc.roleid<br />
WHERE rc.capability IN ('moodle/course:upd' || 'ate', 'moodle/site:doanything')) AS teachers,<br />
(SELECT COUNT(id) FROM prefix_role_assignments) AS enrolments,<br />
(SELECT COUNT(id) FROM prefix_forum_posts) AS forum_posts,<br />
(SELECT COUNT(id) FROM prefix_resource) AS resources,<br />
(SELECT COUNT(id) FROM prefix_question) AS questions<br />
</code><br />
<br />
There are two interesting queries in this blog post [http://tjhunt.blogspot.com/2010/03/when-do-students-submit-their-online.html When do students submit their online tests?].<br />
<br />
===Monthly Usage by Role===<br />
<br />
This report shows a distinct count of users by their role, accessing your site. Each instance of user and role is counted once per month, no matter how many courses they access. We use this to show the total number of students and teachers accessing our site.<br />
<br />
<code sql><br />
SELECT <br />
month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)) AS calendar_month,<br />
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)) AS calendar_year,<br />
prefix_role.name as user_role,<br />
COUNT(DISTINCT prefix_stats_user_monthly.userid) AS total_users<br />
FROM<br />
prefix_stats_user_monthly<br />
Inner Join prefix_role_assignments ON prefix_stats_user_monthly.userid = prefix_role_assignments.userid<br />
Inner Join prefix_context ON prefix_role_assignments.contextid = prefix_context.id<br />
Inner Join prefix_role ON prefix_role_assignments.roleid = prefix_role.id<br />
WHERE prefix_context.contextlevel = 50<br />
AND `prefix_stats_user_monthly`.`stattype` = 'activity'<br />
AND prefix_stats_user_monthly.courseid <>1<br />
GROUP BY month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),<br />
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),<br />
prefix_stats_user_monthly.stattype,<br />
prefix_role.name<br />
ORDER BY <br />
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)), month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),<br />
prefix_role.name<br />
</code><br />
<br />
You must have Statistics turned on to be able to generate any data with this report.<br />
<br />
===Show all Quiz results across a site===<br />
I'm sure someone will be able to improve upon this, but this is a query that will show Quiz results across a site. --[[User:Stuart Mealor|Stuart Mealor]] 22:07, 9 April 2010 (UTC)<br />
<br />
<code sql><br />
SELECT <br />
prefix_grade_items.itemname,<br />
prefix_grade_items.grademax,<br />
ROUND(prefix_grade_grades.finalgrade, 0) AS finalgrade,<br />
prefix_user.firstname,<br />
prefix_user.lastname,<br />
prefix_user.username<br />
FROM<br />
prefix_grade_grades<br />
INNER JOIN prefix_user ON prefix_grade_grades.userid = prefix_user.id<br />
INNER JOIN prefix_grade_items ON prefix_grade_grades.itemid = prefix_grade_items.id<br />
WHERE (prefix_grade_items.itemname IS NOT NULL)<br />
AND (prefix_grade_items.itemtype = 'mod' OR prefix_grade_items.itemtype = 'manual')<br />
AND (prefix_grade_items.itemmodule = 'quiz' OR prefix_grade_items.itemmodule IS NULL)<br />
AND (prefix_grade_grades.timemodified IS NOT NULL)<br />
AND (prefix_grade_grades.finalgrade > 0)<br />
AND (prefix_user.deleted = 0)<br />
</code><br />
<br />
==See also==<br />
<br />
* [[Reports_(administrator)]] for other admin reports<br />
* [[Installing contributed modules or plugins]]<br />
* [http://moodle.org/mod/forum/discuss.php?d=136484 Custom SQL queries report] forum announcement<br />
<br />
[[Category: Administrator]]<br />
[[Category:Report]]<br />
[[Category:Contributed_code]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Blog_settings&diff=62882Blog settings2009-09-10T21:06:08Z<p>Stuartrmealor: Added Permalink</p>
<hr />
<div>{{Template:Blogs}}<br />
[[Image:Blog_newentry.gif|thumb|Add a new blog entry in Moodle 1.6]]<br />
==Adding a blog entry==<br />
<br />
#Click on the Blog tab in your profile page.<br />
#Click on the "Add a new entry" link.<br />
#Write your entry and give it a title.<br />
#If you want to attach a file (in Moodle 1.8 onwards), click the Browse button, find the file on your computer, and click Open. Be sure your document is smaller than the maximum attachment size.<br />
#Choose who you wish to publish the entry to i.e. who may see the entry. There are three options:<br />
#*Yourself i.e. your blog entry is a draft<br />
#*Anyone on your site<br />
#*Anyone in the world<br />
#Select appropriate official tags for your entry and/or add one or more user defined tags. If you add more then one, they should be comma separated.<br />
#Click on the "Save changes" button.<br />
==Editing a blog entry==<br />
You may edit your blog entry at any time, perhaps changing the publish option from yourself to anyone on your site, via the edit link at the bottom of the entry. You may also delete the blog entry if you wish.<br />
==Permalink==<br />
Clicking Permalink on a blog entry gives you a direct link to that particular blog posting (in the address bar). This is so you can send a link to this ''specific'' post to someone else.<br />
[[eu:Sarrera_gehitu_blogean]]<br />
[[de:Blog-Eintrag anlegen]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=User:Stuart_Mealor&diff=62153User:Stuart Mealor2009-08-27T05:23:32Z<p>Stuartrmealor: </p>
<hr />
<div>Hi :-)<br />
* I'm Managing Director of ''[http://www.hrdnz.com HRDNZ]'', Moodle Partner in New Zealand.<br />
We run the ''[http://www.moodlemoot.co.nz Moodle Moot]'' in NZ each year <br />
* I'm Moodle Certification Manager - which is currently the Moodle Course Creator Certificate (MCCC) ''[http://moodle.org/course/view.php?id=48 Moodle Certification]''.<br />
* I'm also joint facilitator of the ''[http://moodle.org/course/view.php?id=32 Moodle Business Uses]'' area (Also run the ''[http://www.linkedin.com/groups?gid=128299 Linkedin MoodleUsers Group]''<br />
* I've presented at Moodle Moots meeting fantastic people along the way(!) in:<br />
** Australia (Sydney and Brisbane)<br />
** Muscat (Oman)<br />
** Rome (Italy)<br />
** Barcelona (Spain)<br />
** San Francisco twice and Oklahoma (USA)<br />
** 5(!) Moots in New Zealand.<br />
** Also you might have met me at LearnX, E-Fest, ULearn, or Ascilite conferences.<br />
<br />
Please say hello on my [[User talk:Stuart Mealor|talk page]] :-)</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=User:Stuart_Mealor&diff=62152User:Stuart Mealor2009-08-27T05:19:37Z<p>Stuartrmealor: </p>
<hr />
<div>Hi :-)<br />
* I'm Managing Director of ''[http://www.hrdnz.com HRDNZ]'', Moodle Partner in New Zealand.<br />
We run the ''[http://www.moodlemoot.co.nz Moodle Moot]'' in NZ each year <br />
* I'm Moodle Certification Manager - which is currently the Moodle Course Creator Certificate (MCCC) ''[http://moodle.org/course/view.php?id=48 Moodle Certification]''.<br />
* I'm also joint facilitator of the ''[http://moodle.org/course/view.php?id=32 Moodle Business Uses]'' area <br />
* I've presented at Moodle Moots meeting fantastic people along the way(!) in:<br />
** Australia (Sydney and Brisbane)<br />
** Muscat (Oman)<br />
** Rome (Italy)<br />
** Barcelona (Spain)<br />
** San Francisco twice and Oklahoma (USA)<br />
** 5(!) Moots in New Zealand.<br />
** Also you might have met me at LearnX, E-Fest, ULearn, or Ascilite conferences.<br />
<br />
Please say hello on my [[User talk:Stuart Mealor|talk page]] :-)</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=User:Stuart_Mealor&diff=62151User:Stuart Mealor2009-08-27T05:09:18Z<p>Stuartrmealor: </p>
<hr />
<div>Hi :-)<br />
* I'm Managing Director of HRDNZ, Moodle Partner in New Zealand.<br />
We run the ''[http://www.moodlemoot.co.nz Moodle Moot]'' in NZ each year <br />
* I'm Moodle Certification Manager - which is currently the Moodle Course Creator Certificate (MCCC) ''[http://moodle.org/course/view.php?id=48 Moodle Certification]''.<br />
* I'm also joint facilitator of the ''[http://moodle.org/course/view.php?id=32 Moodle Business Uses]'' area <br />
* I've presented at Moodle Moots in:<br />
** Australia (Sydney and Brisbane)<br />
** Muscat (Oman)<br />
** Rome (Italy)<br />
** Barcelona (Spain)<br />
** San Francisco x2 and Oklahoma (USA)<br />
** 5(!) Moots in New Zealand.<br />
** Also you might have met me at LearnX, E-Fest, ULearn, or Ascilite conferences.<br />
<br />
Please say hello on my [[User talk:Stuart Mealor|talk page]] :-)</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=User:Stuart_Mealor&diff=62150User:Stuart Mealor2009-08-27T05:07:41Z<p>Stuartrmealor: </p>
<hr />
<div>Hi :-)<br />
* I'm Managing Director of HRDNZ, Moodle Partner in New Zealand.<br />
We run the ''[http://www.moodlemoot.co.nz Moodle Moot]'' in NZ each year <br />
* I'm Moodle Certification Manager - which is currently the Moodle Course Creator Certificate (MCCC) ''[http://moodle.org/course/view.php?id=48 Moodle Certification]''.<br />
* I'm also joint facilitator of the Moodle Business Uses area ''[http://moodle.org/course/view.php?id=32 Moodle Business Uses]''<br />
* I've presented at Moodle Moots in<br />
** Australia (Sydney and Brisbane)<br />
** Muscat (Oman)<br />
** Rome (Italy)<br />
** Barcelona (Spain)<br />
** San Francisco x2 and Oklahoma (USA)<br />
** 5 Moots in New Zealand.<br />
** Also you might have met me at LearnX, E-Fest, ULearn, or Ascilite conferences.<br />
<br />
Please say hello on my [[User talk:Stuart Mealor|talk page]] :-)</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=User:Stuart_Mealor&diff=62149User:Stuart Mealor2009-08-27T04:55:30Z<p>Stuartrmealor: New page: Hi :-) * I'm Managing Director of HRDNZ, Moodle Partner in New Zealand. We run the ''[http://moodle.org/course/view.php?id=32 Moodle Moot]'' in NZ each year * I'm Moodle Certification Man...</p>
<hr />
<div>Hi :-)<br />
* I'm Managing Director of HRDNZ, Moodle Partner in New Zealand.<br />
We run the ''[http://moodle.org/course/view.php?id=32 Moodle Moot]'' in NZ each year <br />
* I'm Moodle Certification Manager - which is currently the Moodle Course Creator Certificate (MCCC) ''[http://moodle.org/course/view.php?id=48 Moodle Certification]''.<br />
* I'm also joint facilitator of the Moodle Business Uses area ''[http://moodle.org/course/view.php?id=32 Moodle Business Uses]''<br />
* I've presented at Moodle Moots in Australia (Sydney and Brisbane), Muscat (Oman), Rome (Italy), Barcelona (Spain), San Francisco x2 and Oklahoma (USA), as well as 5 Moots in New Zealand. Also you might have met me at LearnX, E-Fest, ULearn, or Ascilite conferences.<br />
<br />
Please say hello on my [[User talk:Stuart Mealor|talk page]] :-)</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=report/security/report_security_check_displayerrors&diff=62148report/security/report security check displayerrors2009-08-27T04:42:45Z<p>Stuartrmealor: </p>
<hr />
<div>If PHP is set to display errors, then anyone can enter a faulty URL causing PHP to give up valuable information about directory structures and so on. <br />
<br />
(Can someone add instructions on where to turn this off please).<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7301 Security and Privacy forum]<br />
* Using [http://moodle.org/mod/forum/discuss.php?d=101761 upgrade to 1.9.2 has PHP setting display_errors message] Moodle forum discussion<br />
<br />
[[Category:Security]]<br />
<br />
[[eu:report/security/report_security_check_displayerrors]]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Standard_Moodle_tags&diff=62100Standard Moodle tags2009-08-26T08:55:25Z<p>Stuartrmealor: /* Tags in use */</p>
<hr />
<div>Tags are useful for connecting different bits of information together.<br />
<br />
Obviously it's important to use the same tags everywhere.<br />
<br />
This page describes standard Moodle tags that you should use when describing Moodle events on the internet (Flickr, Twitter, Facebook, del.icio.us etc)<br />
<br />
==General Moodle stuff==<br />
<br />
For general discussion of Moodle, use the tag "moodle".<br />
<br />
Twitter example:<br />
I just installed #moodle on a computer I bought ten years ago!<br />
<br />
==Moodle Moots==<br />
<br />
For Moodle conferences (Moots) use mootCCYY where:<br />
* CC is a country ISO code or state abbreviation, and<br />
* YY is a year.<br />
<br />
mootAU09<br />
<br />
Capitalisation doesn't matter and just helps readability.<br />
<br />
The two letter code would usually be a country, but for somewhere like the US where there are different moots they might choose to use "us" or a state like "sf" or "ok". It really doesn't matter if two moots both used mootus09 for example, because they would be separated in time.<br />
<br />
==Tags in use==<br />
<br />
* #mooteu09 MoodleMoot Euskadi<br />
* #mootNL09 Amsterdam Moodlemoot<br />
* #mootUS09ok Moodlemoot Oklahoma (or #mootok09)<br />
* #mootUS09SF Moodlemoot San Francisco (or #mootsf09)<br />
* #mootin09 Goshen Midwest MoodleMoot<br />
* #mootus09ny MoodleMoot Delhi (or #mootny09) <br />
* #mootar09 MoodleMoot Argentina<br />
* #mootat09 MoodleMoot Austria <br />
* #mootDE09 Moodlemoot Germany 2009 in Elmshorn 18. September 2009<br />
* #moodle #OE09 Moodle at Online Educa 2009 in Berlin (December)<br />
* #mootDE10b Moodlemoot Germany 2010 in Berlin March<br />
* #mootDE10e Moodlemoot Germany 2010 in Essen September<br />
* #mootJP10hk Moodlemoot Japan in Hakodate, February 2010<br />
* #mootNZ10 Moodle Moot New Zealand (Christchurch), 13th-15th April 2010<br />
<br />
==See also==<br />
<br />
* Lounge discussion [http://moodle.org/mod/forum/discuss.php?d=121619 A standard naming scheme for Moodle hashtags]</div>Stuartrmealorhttps://docs.moodle.org/310/en/index.php?title=Moodle_manuals&diff=42393Moodle manuals2008-08-20T23:00:46Z<p>Stuartrmealor: /* English */</p>
<hr />
<div>__NOTOC__<br />
This page contains some links to manuals, tutorials and other multimedia documentation produced by moodlers all over the world. Please feel free to submit your contribution by adding a link to this page or sending the file to [mailto:docs@moodle.org docs@moodle.org].<br />
<br />
<br />
==Teacher manuals==<br />
<br />
===English===<br />
*[http://download.moodle.org/download.php/docs/en/moodle_1.4.3_for_teachers_and_trainers.pdf Moodle 1.4.3 For Teachers and Trainers] - by '''Bryan Williams''' (PDF, 2.4MB)<br />
*[http://download.moodle.org/download.php/docs/en/using-your-moodle.pdf Using Your Moodle (1.4.3)] by [[User:Darren_Smith Darren Smith]] (PDF, 2MB, Published Jan 2005)<br />
*[http://download.moodle.org/download.php/docs/en/teacher-manual.pdf Moodle 1.4 Teacher Manual] - by '''Matt Riordan''' (PDF, 3.5MB)<br />
*[http://www.staff.sbc.edu/tmarcais/classfiles/moodle/Moodle1.5.3.pdf Moodle 1.5.3 Teacher Manual] - Original Documentation by '''Matt Riordan''', updated to version 1.5.3 by '''Tom Marcais''' (PDF, 9.1MB)<br />
*[http://www.packtpub.com/moodle/book Moodle E-Learning Course Development] - by William Rice, [http://www.packtpub.com/ Packt Publishing], May 2006, 250 pages, €33.29/$35.99<br />
*[http://moodle.fct.unl.pt/mod/resource/view.php?id=24107 A Visual Introduction to Moodle - for teachers and page creators] - by '''João Fernandes''' (PDF, 4MB), 43 pages, [http://creativecommons.org/licenses/by-nc-sa/2.5/ Creative Commons Non-Comercial Share Alike 2.5 License]<br />
*[http://moodle.tokem.fi/mod/book/index.php?id=1 Illustrated on-line Beginner, Student and Teacher manuals for Moodle 1.5.4, 1.6.4 and 1.8.3] (including some third-party tools and Flash demos as well as a concise Hot Potatoes manual) by '''Paul Nijbakker''', eLearning Centre of Kemi-Tornio University of Applied Sciences.<br />
*[http://moodle.sbc.edu/mod/resource/view.php?id=8088 Moodle Upgrading from 1.5.3 to 1.8, Changes for Teachers] - by '''Tom Marcais''' (PDF, 3.5MB)<br />
*[http://moodle.sbc.edu/mod/resource/view.php?id=8087 Moodle 1.8 Teacher Manual] - by '''Tom Marcais''' (based in part on documentation by '''Matt Riordan''') (PDF, 10.6MB)<br />
*[http://moodle.de/mod/resource/view.php?id=2092 Moodle Teacher Handbook (Moodle 1.9)] - by '''Renate Jirmann and Ralf Hilgenstock''', 163 pages, 30,- € plus mailing expenses, customized versions and online licence available<br />
*[http://www.oreilly.com/catalog/9780596529185/ Using Moodle, Second Edition] - by '''Jason Cole''' and '''Helen Foster''', 282 pages, $27,99 for the PDF version, each chapter available as a PDF for $3,99 a piece<br />
*[http://www.schoolanywhere.co.uk/moodle_book.php Teacher's Beginners Guide to Using Moodle] - by '''SchoolAnywhere''' , 24 pages, FREE for the PDF version<br />
*[http://www.howtomoodle.com/index.php/moodle-manuals Course Creator Reference Manual 1.8] - by '''Ray Lawrence''' Print 191 pages £15<br />
*[http://www.howtomoodle.com/index.php/moodle-manuals Administrator Reference Manual 1.8] - by '''Ray Lawrence''' Print 69 pages £12<br />
*[http://www.elearning.org.nz MoodleBites online training] - by '''HRDNZ''' 8 week teachers course NZ$199 (free introduction to Moodle available)<br />
<br />
===Other Languages===<br />
*[http://www.lakapps.lk/websvn/filedetails.php?repname=Lakapps&path=%2FMoodle%2FTamil%2FMoodle_Teacher_Manual_TA.pdf Moodle 1.8+ Teacher Manual (Tamil - Sri Lanka)] - by '''Kengatharaiyer Sarveswaran''' ,LAKapps project, University of Moratuwa, Sri Lanka. (PDF, 1.54MB)<br />
*[http://www.lakapps.lk/websvn/filedetails.php?repname=Lakapps&path=%2FMoodle%2FSinhala%2FMoodle_Teacher_Manual_SI.pdf Moodle 1.8+ Teacher Manual (Sinhala)] - by '''Sulochana Sooriyaarachchi''' ,LAKapps project, University of Moratuwa, Sri Lanka. (PDF, 2.79MB)<br />
*[http://download.moodle.org/download.php/docs/nl/teacher-manual-1.5-nl.pdf Moodle 1.5 Teacher Manual (Dutch)] - (PDF, 3MB)<br />
*[http://download.moodle.org/download.php/docs/it/teacher-manual-it.pdf Moodle 1.3 Teacher Manual (Italian)] - (PDF, 3.1MB)<br />
*[http://download.moodle.org/download.php/docs/fr/teacher-manual-fr.pdf Moodle 1.3 Teacher Manual (French)] - (PDF, 5MB)<br />
*[http://download.moodle.org/download.php/docs/es/teacher-manual-es.pdf Moodle Teacher Manual (Spanish)] - by '''Enrique Castro Lopez''' (PDF, 5.4MB)<br />
*[http://www.lasalle.es/descargas/ManualMoodle2006.zip Moodle 1.5 Teacher Manual (Spanish)] - by '''Jesús Martín''' (PDF, 5.2MB)<br />
*[http://moodle.de/file.php/1/Moodle_Trainer_18_public.pdf Moodle 1.8 Trainerhandbuch (German) Inhaltsverzeichnis/Content] - von Renate Jirmann und Ralf Hilgenstock 30,- € (gedruckt 155 Seiten)<br />
*[http://moodle.de//mod/resource/view.php?id=1294 moodle @ work (German) Praxisberichte /Use Cases Inhaltsverzeichnis/Content] 12,50 €(gedruckt 150 Seiten)<br />
*[http://moodle.de/mod/resource/view.php?id=1645 moodle- Praxisbuch (German) Info] - von Fredi Gertsch, Addison&Wesley 540 pages, 44,95 €<br />
*[http://file024r.mylivepage.com/chunk24/390895/255/Arb_MOODLE.pdf Moodle Teacher Manual (Arabic)] - by '''Jamil Itmazi''' (PDF, 6.4MB) استعمال موودل للمعلمين باللغة العربية من إعداد: د.جميل إطميزي<br />
*[http://moodle.fct.unl.pt/mod/resource/view.php?id=24107 Uma introdução visual ao Moodle - pa] - by '''João Fernandes''' ra professores e criadores de páginas (PDF, 4MB), 43 pages, [http://creativecommons.org/licenses/by-nc-sa/2.5/ Creative Commons Non-Comercial Share Alike 2.5 License]<br />
*[http://www.open.hr/request.php?5 Moodle 1.6 Teacher Manual (Croatian)] - by '''Ivana Bosnić''' (PDF, 3MB)<br />
*[http://www.moodle.si/moodle/mod/wiki/view.php?id=22 Moodle 1.6 Teacher Manual (Slovenian)] - by '''Alja Sulčič''' and '''Viktorija Sulčič''', Center for e-learning, Faculty of management Koper, Slovenia (Wiki version, requires free site registration)<br />
*[http://195.148.254.152/moodle/mod/book/index.php?id=1 Moodle opiskelijan ja opettajan opas 1.5.4 ja 1.6.4] '''Sanna Saukkoriipi''', Kemi-Tornion ammattikorkeakoulun eOppimiskeskus.<br />
*[http://moodle.de German DVD] 8 Stunden Anleitungsvideos- von '''Ralf Hilgenstock'''<br />
*[http://aulavirtual2.educa.madrid.org/mod/resource/view.php?inpopup=true&id=5659 Moodle versión 1.8 Manual de consulta para el profesorado (Spanish)] - '''Jesús Baños Sancho''' (16.5MB)<br />
<br />
==Administration manuals==<br />
*[http://www.howtomoodle.com/index.php/moodle-manuals Administrator Reference Manual 1.8] - by '''Ray Lawrence''' Print 69 pages £12<br />
*[http://moodle.de//mod/resource/view.php?id=1191 Handbuch Installation und Administration (German) Inhaltsverzeichnis/Content] - von André Krüger, Urs Hunkler, Ralf Hilgenstock 30,- € (gedruckt 110 Seiten)<br />
*[http://moodle.org/file.php/16/moddata/forum/160/234243/Install_Moodle.pdf Moodle Administrator Manual (Arabic)] - by '''Jamil Itmazi''' (PDF, 0.3MB) تنزيل موودل باللغة العربية من إعداد: د.جميل إطميزي<br />
<br />
==Student manuals==<br />
*[http://www.lakapps.lk/websvn/filedetails.php?repname=Lakapps&path=%2FMoodle%2FTamil%2FMoodle_Student_Manual_TA.pdf Moodle 1.8+ Student Manual (Tamil - Sri Lanka)] - by '''Kengatharaiyer Sarveswaran ,LAKapps project, University of Moratuwa, Sri Lanka.''' (PDF, 700KB)<br />
*[http://www.lakapps.lk/websvn/filedetails.php?repname=Lakapps&path=%2FMoodle%2FSinhala%2FMoodle_Student_Manual_SI.pdf Moodle 1.8+ Student Manual (Sinhala)] - by '''Sulochana Sooriyaarachchi ,LAKapps project, University of Moratuwa, Sri Lanka.''' (PDF, 2 MB)<br />
*[http://download.moodle.org/download.php/docs/es/user_manual_es.pdf Moodle User Manual (Spanish)] - by '''Enrique Castro''' (PDF, 3.1MB)<br />
*[http://moodle.de//file.php?file=/1/Bestellblatt.pdf Teilnehmerhandbuch (German) Info und Bestellformular] - von Ralf Hilgenstock und Renate Jirmann (gedruckt 63 Seiten)<br />
*[http://jamildepalestina.mylivepage.com/file/?fileid=882 Moodle Student Manual (Arabic)] - by '''Jamil Itmazi''' (PDF, 3 MB) استعمال موودل للطلاب باللغة العربية من إعداد: د.جميل إطميزي<br />
*[http://moodle.tokem.fi/mod/book/index.php?id=1 Illustrated on-line Beginner, Student and Teacher manuals for Moodle 1.5.4, 1.6.4 and 1.8.2] (including descriptions of some contrib tools) in English and Finnish by '''Paul Nijbakker''' and '''Sanna Saukkoriipi''', eLearning Centre of Kemi-Tornio University of Applied Sciences.<br />
<br />
==See also==<br />
*[[Moodle presentations]]<br />
[[Category:Teacher]]<br />
<br />
[[es:Manuales de Moodle]]</div>Stuartrmealor