https://docs.moodle.org/37/en/api.php?action=feedcontributions&user=Mits&feedformat=atomMoodleDocs - User contributions [en]2024-03-28T11:46:25ZUser contributionsMediaWiki 1.39.6https://docs.moodle.org/37/en/index.php?title=Recycle_bin&diff=132070Recycle bin2018-10-16T15:03:34Z<p>Mits: ja link</p>
<hr />
<div>{{More features}}<br />
==What is the recycle bin?==<br />
*The recycle bin allows teachers to retrieve course elements they have mistakenly deleted. It also allows those with relevant category permissions to restore deleted courses.<br />
*If deleted items are not needed, they are automatically permanently deleted after seven days (or a time specified by the admin.)<br />
*The recycle bin was the first project funded by the [https://moodleassociation.org/ Moodle Users Association]. <br />
<br />
<br />
{{MediaPlayer | url = https://www.youtube.com/watch?v=Wzieh7BYwfE | desc = Recycle bin in Moodle 3.1}}<br />
<br />
==How does it work?==<br />
===Deleted activities===<br />
<br />
1. Before a course teacher deletes an item, a reminder message appears:<br />
<br />
[[File:confirmdeletion.png]]<br />
<br />
2. If you mistakenly click 'yes', all is not lost. After a short while, a 'Recycle bin' link will appear either via the gear menu or in the Administration block (depending upon your theme). (The delay in the 'Recycle bin' link appearing is because it requires the [[Cron|cron]] to run and the page to be refreshed.)<br />
<br />
[[File:courseadminrecylebinlink.png]]<br />
<br />
3. Click the link and then click the 'restore' icon to retrieve the assignment or other item you accidentally deleted.<br />
<br />
[[File:recycle bin.png]]<br />
<br />
===Deleted courses===<br />
1. Access the category that the course was in before you accidentally deleted it.<br />
2. From the category administration block, click 'Recycle bin'.<br />
<br />
[[File:recyclebinrestorecourse1.png]]<br />
<br />
3.Click 'Restore' to restore the deleted course:<br />
<br />
[[File:recyclebinrestorecourse2.png]]<br />
<br />
==Activity deletion in progress==<br />
<br />
A message 'Activity deletion in progress...' is displayed whilst an activity is being deleted.<br />
<br />
Note: The [[Cron|cron]] should run every minute to ensure that activities are deleted promptly.<br />
<br />
==How is it set up?==<br />
*The recycle bin is available by default in all courses and categories, but the link in the administration block is only visible once something has been deleted. <br />
*Administrators can modify the settings from "Recycle bin'' in the Site administration, and can decide how long an item or a course will remain available until it is permanently deleted, and make the recycle bin visible in the administration block even when empty. If preferred, the recycle bin can be disabled.<br />
<br />
==See also==<br />
<br />
* [https://moodle.org/mod/forum/discuss.php?d=364368 Can't remove Deletion in progress activities Moodle 3.4] forum discussion <br />
<br />
[[es:Papelera de reciclaje]]<br />
[[de:Papierkorb]]<br />
[[ja:ゴミ箱]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Installation_quick_guide&diff=131892Installation quick guide2018-09-09T15:17:02Z<p>Mits: ja link</p>
<hr />
<div>{{Installing Moodle}}<br />
''This page is intended for administrators who are experienced with installing web server applications and are in a hurry to get up and running. Otherwise please see [[Installing Moodle]]''.<br />
<br />
==Basic Requirements==<br />
<br />
* You will need a working web server (e.g. [[Apache]]), a database (e.g. [[MySQL]], [[MariaDB]] or [[PostgreSQL]]) and have [[PHP]] configured. See the [{{Release notes}} release notes] in the dev docs for software requirements.<br />
* Moodle requires a number of [[PHP]] extensions. However, Moodle checks early in the installation process and you can fix the problem and re-start the install script if any are missing.<br />
* If you want Moodle to send email (you probably do) you need a working Sendmail (Unix/Linux) on your server or access to an SMTP mail server.<br />
<br />
==Getting Moodle==<br />
<br />
You have two basic options:<br />
* Download your required version from http://moodle.org/downloads ... OR<br />
* Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):<br />
<pre><br />
git clone -b MOODLE_35_STABLE git://git.moodle.org/moodle.git <br />
</pre><br />
...this fetches a complete copy of the Moodle repository and then switches to the {{Version}} Stable branch. <br />
<br />
See [[Git_for_Administrators|Git for Administrators ]] for details on using Git to install Moodle code.<br />
<br />
Note: Only download Moodle from one of the moodle.org sources. Other versions (e.g. control panel based installers, Linux distribution repositories, other "one click" installers) cannot be guaranteed to work properly, be upgradable or be supportable.<br />
<br />
==Create a database==<br />
<br />
* Using your chosen database server, create a new empty database. The default encoding must be UTF8. For example, using MySQL:<br />
<pre><br />
CREATE DATABASE moodle DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;<br />
</pre><br />
* Create a user/password combination with appropriate permissions for the database. For example (MySQL again):<br />
<pre><br />
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,CREATE TEMPORARY TABLES,DROP,INDEX,ALTER ON moodle.* TO 'moodleuser'@'localhost' IDENTIFIED BY 'yourpassword';<br />
</pre><br />
<br />
Notes: It is important to GRANT ON moodle.* as the database name including the '.*' and not just the bare database name. Save this password you use for the Moodle user, since you will need it later in the install.<br />
<br />
==Create data directory==<br />
<br />
* Create an empty directory to hold Moodle files. It '''must not''' be in the area served by the web server and must have permissions so that the web server user can write to it. Other than that it can be located anywhere. Typically, either make it owned by the web server user or give it write permissions for 'everyone'. If it is on a shared/NFS drive then read [[Caching]] - Moodle caches to this disk area by default and a slow share will mean terrible performance.<br />
<br />
==Install Moodle code==<br />
<br />
* If you downloaded the zip or tgz file earlier, then unzip / untar / move / copy the Moodle code (obtained above) so that it will be served by your web server (e.g. on Debian based Linux, move to /var/www/html/moodle)<br />
* Check the permissions and make sure that the web server does '''not''' have permissions to write to any of the files in the Moodle code directories (a very common root cause of sites being hacked).<br />
* If you need to, configure your web server to serve the Moodle site with your chosen URL.<br />
<br />
==Configure Moodle==<br />
<br />
* In the Moodle code directory, find the file ''config-dist.php'' and copy it to a new file called ''config.php'' (but read next step, 'Install Moodle', first).<br />
* Edit config.php with your favourite editor and change the appropriate settings to point to your site, directories and database. ''Note: the Moodle install script will create config.php for you if it does not exist but make sure you (re-)set permissions appropriately afterwards''<br />
<br />
==Install Moodle==<br />
<br />
* Go to the URL for your moodle site in a browser (installation will complete automatically) or run the command line version at (requires cli version of PHP):<br />
<pre><br />
/usr/bin/php /path/to/moodle/admin/cli/install.php<br />
</pre><br />
The CLI creates the config.php for you and will not run if you created one in the previous step.<br />
* After completing the install make sure your file permissions are ok for the Moodle program files (not writeable by web server) and the Moodle data files (writeable by web server).<br />
<br />
==Set up cron==<br />
<br />
You will need a cron job to run periodically. It is recommended that ''the cron is run every minute'', as required for asynchronous activity deletion when using the [[Recycle bin|recycle bin]]. A typical Unix cron entry will be as follows:<br />
<pre><br />
* * * * * /usr/bin/php /path/to/moodle/admin/cli/cron.php >/dev/null<br />
</pre><br />
Your site '''will not work properly''' unless cron is running regularly. It is very important you do not skip this step.<br />
<br />
See [[Cron]] for details.<br />
<br />
==Congratulations!==<br />
<br />
You are now ready to use your Moodle site.<br />
<br />
If you run into problems, check the [[Installation FAQ]] and visit the [http://moodle.org/mod/forum/view.php?id=28 Installation help forum].<br />
<br />
[[Category:Quick guide]]<br />
<br />
[[de:Installation in Kürze]]<br />
[[fr:Installation_rapide]]<br />
[[es:Inicio_Rápido_de_Instalación]]<br />
[[ja:インストレーションクイックガイド]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=MariaDB&diff=131669MariaDB2018-08-10T13:26:19Z<p>Mits: ja link</p>
<hr />
<div>MariaDB is a MySQL fork that is developed and maintained by original MySQL developers organised under MariaDB Foundation. It is considered to be more open and is being distributed as default MySQL compatible database by majority of modern linux distributions.<br />
<br />
MariaDB is a drop-in replacement for Oracle MySQL, you can use it with any stable supported Moodle version using standard mysqli drivers.<br />
<br />
==MariaDB driver==<br />
<br />
<br />
There is a dedicated driver for MariaDB. It is recommended to explicitly specify mariadb Moodle driver in config.php:<br />
<br />
<code php><br />
$CFG->dbtype = 'mariadb'; <br />
$CFG->dblibrary = 'native';<br />
</code><br />
<br />
At the moment the driver is similar to MySQL but in the future the implementations may diverge significantly. Moodle MariaDB driver is not compatible with MyISAM database engine.<br />
<br />
See [[MySQL]] for more information, the setup procedure is nearly identical.<br />
<br />
==FAQ==<br />
It fails during installation due to binlog_format configuration:<br />
In my.cnf file set binlog_format = ROW under [mysqld] and restart mysql service<br />
<br />
==See also==<br />
* [https://mariadb.org MariaDB.org]<br />
<br />
[[ja:MariaDB]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Installation_quick_guide&diff=131490Installation quick guide2018-07-13T13:04:14Z<p>Mits: </p>
<hr />
<div>{{Installing Moodle}}<br />
''This page is intended for administrators who are experienced with installing web server applications and are in a hurry to get up and running. Otherwise please see [[Installing Moodle]]''.<br />
<br />
==Basic Requirements==<br />
<br />
* You will need a working web server (e.g. [[Apache]]), a database (e.g. [[MySQL]], [[MariaDB]] or [[PostgreSQL]]) and have [[PHP]] configured. See the [{{Release notes}} release notes] in the dev docs for software requirements.<br />
* Moodle requires a number of [[PHP]] extensions. However, Moodle checks early in the installation process and you can fix the problem and re-start the install script if any are missing.<br />
* If you want Moodle to send email (you probably do) you need a working Sendmail (Unix/Linux) on your server or access to an SMTP mail server.<br />
<br />
==Getting Moodle==<br />
<br />
You have two basic options:<br />
* Download your required version from http://moodle.org/downloads ... OR<br />
* Pull the code from the Git repository (recommended for developers and also makes upgrading very simple):<br />
<pre><br />
git clone -b MOODLE_34_STABLE git://git.moodle.org/moodle.git <br />
</pre><br />
...this fetches a complete copy of the Moodle repository and then switches to the {{Version}} Stable branch. <br />
<br />
See [[Git_for_Administrators|Git for Administrators ]] for details on using Git to install Moodle code.<br />
<br />
Note: Only download Moodle from one of the moodle.org sources. Other versions (e.g. control panel based installers, Linux distribution repositories) cannot be guaranteed to work properly, be upgradable or be supportable.<br />
<br />
==Create a database==<br />
<br />
* Using your chosen database server, create a new empty database. The default encoding must be UTF8. For example, using MySQL:<br />
<pre><br />
CREATE DATABASE moodle DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;<br />
</pre><br />
* Create a user/password combination with appropriate permissions for the database. For example (MySQL again):<br />
<pre><br />
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,CREATE TEMPORARY TABLES,DROP,INDEX,ALTER ON moodle.* TO 'moodleuser'@'localhost' IDENTIFIED BY 'yourpassword';<br />
</pre><br />
<br />
Notes: It is important to GRANT ON moodle.* as the database name including the '.*' and not just the bare database name. Save this password you use for the Moodle user, since you will need it later in the install.<br />
<br />
==Create data directory==<br />
<br />
* Create an empty directory to hold Moodle files. It '''must not''' be in the area served by the web server and must have permissions so that the web server user can write to it. Other than that it can be located anywhere. Typically, either make it owned by the web server user or give it write permissions for 'everyone'. If it is on a shared/NFS drive then read [[Caching]] - Moodle caches to this disk area by default and a slow share will mean terrible performance.<br />
<br />
==Install Moodle code==<br />
<br />
* If you downloaded the zip or tgz file earlier, then unzip / untar / move / copy the Moodle code (obtained above) so that it will be served by your web server (e.g. on Debian based Linux, move to /var/www/html/moodle)<br />
* Check the permissions and make sure that the web server does '''not''' have permissions to write to any of the files in the Moodle code directories (a very common root cause of sites being hacked).<br />
* If you need to, configure your web server to serve the Moodle site with your chosen URL.<br />
<br />
==Configure Moodle==<br />
<br />
* In the Moodle code directory, find the file ''config-dist.php'' and copy it to a new file called ''config.php'' (but read next step, 'Install Moodle', first).<br />
* Edit config.php with your favourite editor and change the appropriate settings to point to your site, directories and database. ''Note: the Moodle install script will create config.php for you if it does not exist but make sure you (re-)set permissions appropriately afterwards''<br />
<br />
==Install Moodle==<br />
<br />
* Go to the URL for your moodle site in a browser (installation will complete automatically) or run the command line version at (requires cli version of PHP):<br />
<pre><br />
/usr/bin/php /path/to/moodle/admin/cli/install.php<br />
</pre><br />
The CLI creates the config.php for you and will not run if you created one in the previous step.<br />
* After completing the install make sure your file permissions are ok for the Moodle program files (not writeable by web server) and the Moodle data files (writeable by web server).<br />
<br />
==Set up cron==<br />
<br />
You will need a cron job to run periodically. It is recommended that ''the cron is run every minute'', as required for asynchronous activity deletion when using the [[Recycle bin|recycle bin]]. A typical Unix cron entry will be as follows:<br />
<pre><br />
* * * * * /usr/bin/php /path/to/moodle/admin/cli/cron.php >/dev/null<br />
</pre><br />
Your site '''will not work properly''' unless cron is running regularly. It is very important you do not skip this step.<br />
<br />
See [[Cron]] for details.<br />
<br />
==Congratulations!==<br />
<br />
You are now ready to use your Moodle site.<br />
<br />
If you run into problems, check the [[Installation FAQ]] and visit the [http://moodle.org/mod/forum/view.php?id=28 Installation help forum].<br />
<br />
[[Category:Quick guide]]<br />
<br />
[[de:Installation in Kürze]]<br />
[[fr:Installation_rapide]]<br />
[[es:Inicio_Rápido_de_Instalación]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Privacy_officer_role&diff=131422Privacy officer role2018-07-06T15:06:43Z<p>Mits: Changed the page name based on en change.</p>
<hr />
<div>{{Privacy}}<br />
A Privacy officer can respond to data requests and manage the data registry.<br />
<br />
==Role set-up==<br />
<br />
# Go to 'Define roles' in the Site administration.<br />
# Click the button "Add a new role".<br />
# Set the role archetype to Guest.<br />
# Give the role a name such as 'Privacy officer', short name and description.<br />
# For context types where this role may be assigned, tick system.<br />
# Enter dataprivacy in the filter box, then allow the capabilities tool/dataprivacy:managedataregistry and tool/dataprivacy:managedatarequests, and if necessary tool/dataprivacy:makedatarequestsforchildren.<br />
# Allow more capabilities as follows: moodle/site:configview, moodle/category:viewhiddencategories, moodle/course:viewhiddencourses, moodle/course:view, moodle/course:viewhiddenactivities.<br />
# Click the button "Create this role".<br />
<br />
Next<br />
<br />
# Go to 'Privacy settings' in the Site administration.<br />
# Click to select the Privacy officer in the Privacy officer role mapping setting.<br />
# Save changes.<br />
<br />
==Role assignment==<br />
<br />
# Go to 'Assign system roles' in the Site administration.<br />
# Choose the Privacy officer role to assign.<br />
# Select the user in the Potential users list, and use the left-facing arrow button to add them to the Existing users list. <br />
<br />
[[Category: Privacy]]<br />
[[Category:Roles]]<br />
<br />
<br />
[[es:Rol de Oficial de Protección de Datos]]<br />
[[de:Datenschutzbeauftragter-Rolle]]<br />
[[ja:プライバシー責任者ロール]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Privacy_officer_role&diff=131318Privacy officer role2018-06-29T14:06:30Z<p>Mits: ja link</p>
<hr />
<div>A Privacy officer can respond to data requests and manage the data registry.<br />
<br />
==Role set-up==<br />
<br />
# Go to 'Define roles' in the Site administration.<br />
# Click the button "Add a new role".<br />
# Set the role archetype to Guest.<br />
# Give the role a name such as 'Privacy officer', short name and description.<br />
# For context types where this role may be assigned, tick system.<br />
# Enter dataprivacy in the filter box, then allow the capabilities tool/dataprivacy:managedataregistry and tool/dataprivacy:managedatarequests, and if necessary tool/dataprivacy:makedatarequestsforchildren.<br />
# Allow more capabilities as follows: moodle/site:configview, moodle/category:viewhiddencategories, moodle/course:viewhiddencourses, moodle/course:view, moodle/course:viewhiddenactivities.<br />
# Click the button "Create this role".<br />
<br />
Next<br />
<br />
# Go to 'Privacy settings' in the Site administration.<br />
# Click to select the Privacy officer in the Privacy officer role mapping setting.<br />
# Save changes.<br />
<br />
==Role assignment==<br />
<br />
# Go to 'Assign system roles' in the Site administration.<br />
# Choose the Privacy officer role to assign.<br />
# Select the user in the Potential users list, and use the left-facing arrow button to add them to the Existing users list. <br />
<br />
[[Category: Privacy]]<br />
[[Category:Roles]]<br />
<br />
<br />
[[es:Rol de Oficial de Protección de Datos]]<br />
[[de:Datenschutzbeauftragter-Rolle]]<br />
[[ja:プライバシー管理責任者ロール]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Adding_a_new_course&diff=131160Adding a new course2018-06-06T13:23:55Z<p>Mits: ja link</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.To add a course:<br />
*From the Site administration link, click Courses>Manage courses and categories''<br />
<br />
[[File:26addcourse1.png|400px|thumb|center|Click New course in the category page on the right]]<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 />
# From the Site administration link, click 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 the Site administration link, click Courses>Upload courses and 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 />
===Using the course templates plugin===<br />
With emeneo's course templates plugin you can very easily create template based courses. More information and the plugin package you can find here: [https://moodle.org/plugins/local_course_templates https://moodle.org/plugins/local_course_templates]<br />
<br />
==See also==<br />
<br />
===Screencasts===<br />
* [http://youtu.be/MzK2jb-9SwE Bulk course creation]<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]]<br />
[[ja:新しいコースを追加する]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/course:delete&diff=131088Capabilities/moodle/course:delete2018-05-21T20:19:37Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to delete a course within 24 hours of creating it<br />
*This capability is allowed for the default role of manager only<br />
<br />
==See also==<br />
<br />
* [[Adding a new course]]<br />
<br />
[[Category:Capabilities|Course]]<br />
[[Category:Course]]<br />
<br />
[[eu:Capabilities/moodle/course:delete]]<br />
[[fr:Capabilities/moodle/course:delete]]<br />
[[es:Capabilities/moodle/course:delete]]<br />
[[ja:ケイパビリティ/moodle/course:delete]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/course:request&diff=130268Capabilities/moodle/course:request2018-03-09T15:01:55Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
*This capability allows a user to [[Adding a new course|request a course]] (which needs to be approved by a user with the [[Capabilities/moodle/site:approvecourse|capability to approve course requests]]).<br />
*The default [[Authenticated user]] role has this capability set to allow.<br />
<br />
==See also==<br />
<br />
* [[Course requester role]] for restricting users who can make course requests<br />
<br />
[[Category:Capabilities|Course]]<br />
[[Category:Course]]<br />
<br />
[[eu:Capabilities/moodle/course:request]]<br />
[[ja:ケイパビリティ/moodle/course:request]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Course_requester_role&diff=130265Course requester role2018-03-08T15:03:00Z<p>Mits: ja link</p>
<hr />
<div>{{Roles}}The role of Course requester may be used to restrict users who can make [[Course request|course requests]], perhaps to teachers only.<br />
<br />
==Removing the capability to make course requests==<br />
<br />
By default, all authenticated users can make course requests. To change this:<br />
<br />
#Access ''Administration > Users > Permissions > Define roles''.<br />
#Edit the authenticated user role and change the capability [[Capabilities/moodle/course:request|moodle/course:request]] from allow to not set.<br />
#Scroll to the bottom (or top) of the page and click the 'Save changes' button.<br />
<br />
==Role set-up==<br />
<br />
#Access ''Administration > Users > Permissions > Define roles''.<br />
#Click the button "Add a new role"<br />
#Give the role a name e.g. Course requester, short name and description.<br />
#Under "Context types where this role may be assigned", click on the "System" tick box turning it on.<br />
#Change the capability moodle/course:request to allow.<br />
#Click the button "Create this role".<br />
<br />
''Note'': It is necessary to create a new role, rather than simply changing the capability for the teacher role, because it needs to be assigned as a system role. (The role of teacher is generally assigned in the course or course category context.)<br />
<br />
==Role assignment==<br />
<br />
#Access ''Administration > Users > Permissions > Assign system roles''.<br />
#Choose the course requester role to assign.<br />
#Select one or more users in the Potential users list, and use the left-facing arrow button to add it to the Existing users list. If you want all your institution's teachers to be able to make course requests, you need to select and add all their names to the Existing users list.<br />
<br />
==Add a Course Request block==<br />
<br />
Now, this will work fine for those users who already have a Teacher role in at least ONE course on your Moodle site. When they log in, they will see the list of course(s) that they are enrolled in as Teacher(s) plus an All courses button. Clicking on that '''All courses''' button will show the complete list of courses on the site, plus a '''Request a course''' button, which they will be able to click to request a course.<br />
<br />
However, those Moodle site users whom we have assigned to the Course requester role in System ''and who do not yet have a Teacher role in at least ONE course on your Moodle site will not see that '''All courses''' button'', since by default all the available courses will be displayed. And consequently, the '''Request a course''' button will not appear to them. To solve this, a further step is required, viz. creating an HTML block on the front page with a direct link to /course/request.php! And of course that block will have to be made invisible to students etc.<br />
<br />
# On the front page add a block: HTML: title: ''Course request'' contents: ''Click here to request a course'' with a link to <yourmoodlesite>/course/request.php<br />
# Click the 'Assign roles' link and then in the administration block click the permissions link and edit the permissions so that only users with a Course requester or Teacher role will be able to view that block; students etc. won't see it.<br />
<br />
Now Course requesters who are not yet enrolled as Teachers in Courses will be able to see that HTML block, click on the link and request a course. Of course, this block is redundant for those Course requesters who are also Teachers, but it is needed for Teachers requesting the creation of ''their very first course'' on the Moodle site.<br />
<br />
==See also==<br />
<br />
* [http://moodle.org/mod/forum/discuss.php?d=195211 Only teachers can request courses - how to do that?] forum discussion<br />
<br />
[[es:Rol de solicitante de curso]]<br />
[[ja:コースリクエストロール]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Course_categories&diff=129853Course categories2018-01-14T15:02:46Z<p>Mits: </p>
<hr />
<div>{{Courses}}<br />
Course categories organize courses for all Moodle site participants. The default course category on a new Moodle site is "Miscellaneous" (although this can be renamed) A [[Course creator|Course creator]], [[Administrator|Administrator]] or [[Manager|Manager]] can put all courses in the Miscellaneous category. However, teachers and students will find it easier to find their classes if they are organized in descriptive categories.<br />
<br />
The list of courses within a category by default shows the teachers and the summary of each course. If the number of courses within a category exceeds 9 (10 or more), then a short list without teachers and summary is shown.<br />
<br />
==Adding a category==<br />
Most people organize their courses by department and college or by topic. Be sure to test the organizational scheme with a few users before entering a large number of courses, to save time in moving them later.<br />
<br />
Adding categories is very simple:<br />
<br />
*Go to ''Administration > Site administration > Courses > Add a category'' <br />
*Complete the details required and click 'Create category.'<br />
*Alternatively, you can go to ''Administration>Site administration>Courses>Manage courses and categories'' and click the link 'Create new category'.<br />
*If you are on the category page (or you only have Manager rights at a Course Category level), click the 'Manage courses' button at the top-right of the page and then click the link 'Create new category'.<br />
<br />
[[File:Addcategory.png]]<br />
<br />
If the category is visible, the course category description will be displayed to users when they enter the category, above the list of courses.<br />
<br />
==Editing or moving a category==<br />
*You can edit the details of a course category by clicking the actions icon next to its name in ''Administration>Site administration>Courses>Manage courses and categories.'' and selecting 'Edit'.<br />
*You can move categories up or down by clicking the up/down arrow next to the category you wish to move. You can bulk move categories by checking the box to the left of their name and then by selecting from the dropdown 'Move selected categories to'<br />
<br />
[[File:Editmovecategories.png]]<br />
<br />
==Adding sub-categories==<br />
*Sometimes it might be useful to have a sub-category of a course. For example, you might have a category "Science" and wish to have sub-categories "Biology", "Chemistry" and "Physics".<br />
<br />
*You can make one category a subcategory of another by checking the box to the left of its name and then by selecting from the drop down menu 'Move selected categories to' You can create a new, empty sub-category by clicking the actions icon next to its name in ''Administration>Site administration>Courses>Manage courses and categories.'' and selecting 'Create new subcategory.'<br />
<br />
==Hiding categories==<br />
*Categories may be easily hidden or shown via ''Administration>Site administration>Courses>Manage courses and categories'' and clicking the 'eye' icon of the category you wish to hide. Hidden categories are only visible to site administrators or those with the capability to "view hidden courses".<br />
<br />
==Sorting categories==<br />
Categories may be sorted by ascending/descending names or ID numbers from ''Administration>Site administration>Courses>Manage courses and categories'' <br />
<br />
[[File:categorysort.png|thumb|200px|center|Sorting categories]]<br />
<br />
Courses within categories may also be sorted. See [[Adding a new course]]<br />
<br />
==Setting category depth==<br />
<br />
You can limit the number of categories that are displayed in the front page 'List of Categories' or 'Combo List' from ''Administration>Site administration>Front page>Front page settings'' Deeper level categories will appear as links and the user can expand them.<br />
<br />
<br />
==Assigning users a role in a course category==<br />
<br />
To assign a Manager at the Category level, see [[Manager_role#Assigning_the_role_of_Manager_at_the_Category_level | Assign Manager role at category level]].<br />
<br />
To enrol teacher or students roles category wide, see [[Category enrolments]].<br />
<br />
==See also==<br />
===Screencasts===<br />
[http://youtu.be/1N5Vs_OfVlA Course and category management]]<br />
<br />
Using Moodle forum discussions:<br />
* [http://moodle.org/mod/forum/discuss.php?d=47954 Course Summary Sometimes Not Appearing]<br />
* [http://moodle.org/mod/forum/discuss.php?d=102803 Allowing teachers to put courses in categories]<br />
<br />
[[fr:Ajouter une catégorie de cours]]<br />
[[es:Categorías de curso]]<br />
[[de:Kursbereiche]]<br />
[[ja:コースカテゴリ]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=MNet&diff=127947MNet2017-05-17T14:42:45Z<p>Mits: Updated ja link</p>
<hr />
<div>{{Authentication}}<br />
The Moodle network feature allows a Moodle administrator to establish a link with another Moodle or a Mahara site and to share some resources with the users of that Moodle. Users go from the first Moodle to the linked site via the [[Network servers block]].<br />
<br />
[[File:Networkserversexample.png]]<br />
<br />
<br />
==Overview==<br />
The initial release of MNet is bundled with a Authentication Plugin, which makes single-sign-on between Moodles possible. A user with the username <em>jody</em> logs in to her Moodle server as normal, and clicks on a link that takes her to a page on another Moodle server. Normally, she would have only the privileges of a guest on the remote Moodle, but behind the scenes, single-sign-on has established a fully authenticated session for Jody on the remote site.<br />
<br />
'''WARNING:''' MNet requires the use of '''xmlrpc'''. Please go to your phpinfo page if you are interested in using this and search for --with-xmlrpc. If your php has not been compiled with xmlrpc then you need to address that first! At present it appears that PEAR xmlrpc will not work.<br />
[[Image:Administration Block Users Authentication MoodleNetwork.jpg|thumb|MNet setting in ''Admin > User > Authentication > Moodle Network]]<br />
<br />
==Security==<br />
The MNet feature requires that your server has the '''Curl''' and '''OpenSSL''' extensions installed. Your system will generate a OpenSSL certificate for encrypted communication with other Moodles, and will rotate encryption keys on a monthly basis (approx).<br />
<br />
Communication takes place over an XML-RPC transport, and the XML-RPC documents are wrapped first in an XMLDSIG (XML digital signature) envelope, and then in an XMLENC (XML encryption) envelope. The encryption all happens within PHP, and does not require an https (Apache SSL) server.<br />
<br />
References:<br />
*[http://www.w3.org/TR/xmldsig-core/ XML Digital Signatures]<br />
*[http://www.w3.org/TR/xmlenc-core/ XML Encryption]<br />
<br />
A special mode can be enabled which would allow a machine with a specified IP address to make calls to the XML-RPC layer without using either encryption or signature envelopes. This mode is provided to enable Moodle to communicate with other software systems in which the integration of signatures and encryption might be prohibitively difficult. It is not envisioned that unencrypted inter-Moodle networking will ever be enabled.<br />
<br />
==Peer to Peer Network==<br />
<br />
This is the basic layout of the system. It can be very useful to run one Moodle per faculty or departments, each with its own user management, and yet permit users to roam across the Moodle installs... subject to permissions of course. <br />
<br />
===Setup===<br />
<br />
The instructions will cover 2 Moodle installations: MoodleA and MoodleB. Both are installed correctly and have never had a Moodle Network configuration.<br />
<br />
Note: If you experience problems, ensure debugging is turned on in ''Administration > Site administration > Server > Debugging''. Extra diagnostic messages may be displayed.<br />
<br />
You need to first enable Networking in ''Administration > Site administration > Advanced Features''. This will add the "Networking" menu to the Site Administration menu.<br />
<br />
# Get them to talk to each other<br />
## Ensure ''Administration > Site administration > Server > Environment'' indicates you have curl installed<br />
## If MoodleA and MoodleB are hosted in the same domain, ensure they have a different cookie prefix. Note that changing the cookie prefix will log you out! You can change the cookie prefix via ''Admin > Server > Session Handling''.<br />
## On both, go to ''Administration > Site administration > Advanced Features'' and turn Networking ON.<br />
## On MoodleA go to ''Administration > Site administration > Network > Manage peers'' - put the URL of MoodleB under "Add New Host" and click Add. The URL should include the directory where your Moodle code is located and may include the protocol as well, for example ''https://www.mymoodle.org/moodle''.<br />
## Do the equivalent on MoodleB.<br />
# Get user roaming going<br />
[http://moodle.org/mod/forum/discuss.php?d=141491] ). On both servers: <br />
### Go to ''Administration > Site administration > Plugins > Authentication > Manage authentication''. Enable ''MNet Authentication'' by clicking the 'enable' icon.<br />
## On MoodleA go to ''Administration > Site administration > Networking > (Manage) Peers'', click on 'MoodleB', and click on the 'Services' tab. Enable SSO-IDP (SSO Identity Provider) publish and subscribe, and SSO-SP (SSO Service Provider) publish and subscribe.<br />
## Do the equivalent on MoodleB. (By both publishing and subscribing you allow users to move freely between the two servers. By only publishing or subscribing between servers you create a one way traversal)<br />
## On both, go to ''Administration > Site administration > Users > Permissions > Define Roles'', only roles that have "Roam to a remote Moodle moodle/site:mnetlogintoremote" will be allowed to roam. Grant the privilege as appropriate.<br />
### eg. enabling for ''Authenticated user'' allows any authenticated user to roam between servers.<br />
## On both servers, go to the homepage, and add the 'Network Servers' block.<br />
## To test, it is recommended to use a different browser (even on a different machine) that is logged in to neither. Login to MoodleA with a non-administrator account that has the permissions to roam. You should see the Network Servers block, and clicking on it you should go to MoodleB with a newly autocreated account. <br />
# Get remote enrolments going -- this is optional. It allows an administrator of MoodleB to enrol users that are "native" to MoodleB in remote courses in MoodleA, and viceversa.<br />
## On both, go to ''Site administration > Plugins > Enrolments > Manage enrol plugins'' and enable the Mnet remote enrolments plugin (click Save). Click on 'Edit' and enable 'allow_allcourses' or select some courses or categories to be remotely enrolled.<br />
## On the server you want to receive enrolments:<br />
### Go to ''Site administration > Plugins > Enrolments > Manage enrol plugins''. Enable ''MNet remote enrolments'' by clicking the 'enable' icon. (For ''MNet remote enrolments'' settings info see [[MNet_remote_enrolments|MNet remote enrolments]])<br />
## On MoodleA go to ''Admin > Networking > Peers'', click on 'MoodleB', and click on the 'Services' tab. Enable Enrolment publish and/or subscribe.<br />
## Do the equivalent on MoodleB.<br />
## On every course you want to allow enrolments into:<br />
### Enter course and go to ''Administration > Course administration > Users > Enrolment methods''<br />
### From ''Add method'' drop-down select ''MNet remote enrolments''<br />
### On the new screen select the ''Remote host'' you want to allow enrolments from, the Role for the enrolled users, and click save. (Note: you can only add a single ''MNet remote enrolments'' method per course.)<br />
<br />
===Using it===<br />
<br />
# In MoodleA go to ''Admin > Networking > Remote enrolments client''. You will see MoodleB listed. Click on ''Edit enrolments'' button beside MoodleB and you will see a list of courses that MoodleB offers for remote enrolment. Click ''Edit enrolments'', select the users you want to enroll, and then click Add to enroll them in the course.<br />
<br />
==Connecting to a Mnet hub==<br />
A Mnet hub (do not confuse it with the [[Community hub]]) is a Moodle server that is configured to accept connections from other Moodle servers, and to provide a set of services to users of these other servers. This guideline will direct you to connect to a Mnet hub, assess the services it has to offer, and enable those services for your users.<br />
<br />
===Setup===<br />
# Get talking to the Hub<br />
## Ensure that the ''Admin > Server > Environment'' page indicates you have curl and openssl installed<br />
## Go to ''Admin > Advanced Features'' and turn Networking on<br />
## Go to ''Admin > Network > Peers'' and enter the URL of Mnet Hub under "Add New Host". Click <em>Add</em><br />
## The host details for the Mnet Hub should appear with the Site Name field already populated. Click <em>Save changes</em><br />
## The details will be written to your database and two new tabs will appear in this window: 'Services' and 'Logs'. Click <em>Services</em><br />
##A list of services will appear, each with a checkbox for 'publish' and 'subscribe'. Check the checkboxes for any services you want to publish or subscribe to<br />
<br />
===Using it===<br />
If the Mnet Hub has already enabled a service for you, there will be a tick alongside the appropriate checkbox, for example: if the Hub is <em>publishing</em> Moodle Networked Enrolment, then a tick will appear alongside the <em>subscribe</em> checkbox for this service. Note that in order to enable some functionality, prominently <em>single-sign-on</em>, you may have to <em>publish</em> a service, e.g. the <em>Identity Provider</em> service. The Mnet Hub will access this service on your Moodle, asking it to authenticate your users.<br />
# Enable Roaming<br />
## Subscribe to <em>SSO (Service Provider)</em> by checking the box<br />
## Publish <em>SSO (Identity Provider)</em> by checking the box<br />
## Click <em>Save changes</em><br />
## Go to ''Admin > Users > Permissions > Define Roles'', and grant the capability <em>Roam to a remote Moodle moodle/site:mnetlogintoremote</em> to an appropriate role<br />
## Go to ''Administration > Plugins > Authentication > Manage authentication'' and enable the <em>Moodle Network authentication</em> plugin<br />
## Go to your homepage, turn on editing, and add the 'Network Servers' block<br />
## Using a different web-browser, log on as a non-admin user who inhabits the role you granted the roaming capability to<br />
## Note that the Mnet Hub is listed in the Network Servers block on the homepage. Click on the link to that server<br />
## Some of your user details will be transferred to the Mnet Hub server, and a browsing session will be started for you as if you had logged on there directly<br />
# Enable Networked Enrolment<br />
## Return to the web browser you've been using as the site administrator<br />
## Go to ''Admin > Network > Peers'' and click on the entry for the Mnet Hub.<br />
## Click on the Services tab<br />
## Subscribe to <em>Moodle Networked Enrolment</em><br />
## Go to ''Site administration > Plugins > Enrolments > Manage enrol plugins'' and enable the <em>Mnet remote enrolment </em> plugin. Click <em>Save changes</em><br />
## Click on <em>edit</em> to view the details for networked enrolments.<br />
## Go to ''Admin > Networking > Enrolments'' to see a list of Moodle servers that offer this service to you<br />
## Click on a server name to view a list of courses that the server offers to your users<br />
## Click on a course name, to view a list users that you can enrol in this course<br />
## Enrol users<br />
## Profit!<br />
<br />
==Running a Mnet hub==<br />
A Mnet hub is a regular Moodle site that runs in a special mode. As a Moodle Administrator, when you add another Moodle site to your list of network peers, your Moodle will contact that site to find out what it is called, and to request its public key for encrypted communication. Normally, the remote server will simply provide this information without making any record of the transaction.<br />
<br />
A Mnet hub is different. As soon as you add an entry for a Mnet hub to your system, the Mnet hub will create an entry for your server in its list of hosts, and may immediately begin to offer services to the users of your site.<br />
<br />
This section will guide you to set up a Mnet hub, and select services to offer to all comers.<br />
<br />
===Setup===<br />
Enable Networking<br />
# Ensure that the ''Settings > Site administration > Server > Environment'' page indicates you have curl and openssl installed<br />
# Go to ''Settings > Site administration > Advanced Features'' and turn Networking on <br />
# Go to ''Settings > Site administration > Network > Peers'' and tick the checkbox for <em>Register all hosts</em>. Click on <em>Save Changes</em><br />
# On the same page, the first entry in your list of hosts should be <em>All hosts</em>. Click this link<br />
# Click on <em>Services</em> and enable any services you want to offer to all comers<br />
<br />
==Assigning the role of admin==<br />
<br />
For security reasons, users cannot be assigned the role of admin via the Moodle interface. Instead, admin user IDs must be listed in config.php e.g. <code>$CFG->siteadmins = '2,45,67';</code><br />
<br />
Note: This applies to local admins as well as remote admins, as this overrides any local DB stored settings that assign administrative permissions.<br />
<br />
==See also==<br />
<br />
* [[Moodle Network FAQ]]<br />
* [[Upload users]] for csv upload using the ''mnethostid'' field.<br />
* [[Development:Moodle Network|Moodle Network development notes]]<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=6976 MNet forum]<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=92749 Examples of how people are using Moodle networks] forum discussion<br />
<br />
[[Category:Enrolment]]<br />
[[Category:MNet]]<br />
<br />
[[fr:Réseau Moodle]]<br />
[[ja:MNet]]<br />
[[es:Red Moodle]]<br />
[[cs:Síťové služby]]<br />
[[de:Moodle-Netzwerk]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Additional_name_fields&diff=125727Additional name fields2016-10-27T15:01:57Z<p>Mits: ja link</p>
<hr />
<div>{{Accounts}}<br />
As well as first name and surname, the following additional name fields may be used:<br />
<br />
* First name - phonetic<br />
* Surname - phonetic<br />
* Middle name<br />
* Alternate name<br />
<br />
==Administration settings==<br />
<br />
===Full name format===<br />
[[File:participants-after.png|thumb|List of users with full names displayed]]<br />
An administrator can set how names are displayed across the site via the setting 'Full name format' (fullnamedisplay) in ''Administration > Site administration > Users > Permissions > User policies''. The default setting is ''language'', which means that names are displayed according to information from the language pack used on the site. Alternatively, the following placeholders may be used:<br />
<br />
* firstname<br />
* lastname<br />
* firstnamephonetic<br />
* lastnamephonetic<br />
* middlename<br />
* alternatename<br />
<br />
For example, a user with first name John, surname Doe, middle name James, first name phonetic Jon, and surname phonetic Dough will have his name displayed as<br />
<br />
*John James Doe when 'Full name format' is set to ''firstname middlename lastname'' and<br />
*Doe John (Dough Jon) when 'Full name format' is set to ''lastname firstname (lastnamephonetic firstnamephonetic)''<br />
<br />
Users with the [[Capabilities/moodle/site:viewfullnames|view full names capability]] (by default users with the role of manager, teacher or non-editing teacher) can always see first and last names, regardless of the "Full name format" setting.<br />
<br />
Note for sites upgrading from an earlier version: The 'Full name format' setting was previously in ''Site policies''.<br />
<br />
===Alternative full name format===<br />
<br />
The alternative full name format setting may be used to define how names are shown to users with the [[Capabilities/moodle/site:viewfullnames|view full names capability]]. For example, it may be set to ''lastname firstname (lastnamephonetic firstnamephonetic)'' so that phonetic names are also displayed.<br />
<br />
==User profile settings==<br />
<br />
Users can enter additional names by editing their profile in ''Administration > My profile settings > Edit profile''.<br />
<br />
First name, surname and any additional names specified by an administrator in 'Full name format' are listed in the General section. Additional names not specified in 'Full name format' are listed in an "Additional names' section.<br />
<br />
{|<br />
| [[File:name fields in general section.png|thumb|Name fields as specified in 'Full name format']]<br />
| [[File:additional name fields.png|thumb|Additional name fields]]<br />
|}<br />
<br />
[[es:Campos de nombre adicionales]]<br />
[[de:Zusätzliche Namen]]<br />
[[ja:追加氏名フィールド]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Metacourse_examples_of_use&diff=125723Metacourse examples of use2016-10-25T15:09:29Z<p>Mits: ja link</p>
<hr />
<div>{{Enrolment}}<br />
[[Metacourse]]s can be used in many ways to fill some special needs around student enrolment. Here are some examples scenarios that may help you to understand how they work. <br />
<br />
==Yearly intake ==<br />
This example uses LDAP to enrol each year's intake of students onto that year's 'Course Noticeboard'. Then by making each of the Modules meta courses, and assigning their 'child' as that year's 'Course Noticeboard', the learners are automatically enrolled on all of the necessary module<br />
<br />
Foundation Degree (2009 intake) [course category]<br />
Course 2009 Noticeboard (uses LDAP to enrol 2009 students)<br />
Year 1 [course category]<br />
:Module 1 (Metacourse linked to 2009 Noticeboard_<br />
:Module 2 (Metacourse linked to 2009 Noticeboard_<br />
:Module 3 (Metacourse linked to 2009 Noticeboard_<br />
:etc.<br />
<br />
Foundation Degree (2010 intake) [course category]<br />
Course 2010 Noticeboard (uses LDAP to enrol 2010 students)<br />
Year 1 [course category]<br />
Module 1 (Metacourse linked to 2010 Noticeboard_<br />
Module 2 (Metacourse linked to 2010 Noticeboard_<br />
Module 3 (Metacourse linked to 2010 Noticeboard_<br />
<br />
Jerome Di Pietro in [http://moodle.org/mod/forum/discuss.php?d=39438 Teaching Strategies forum]<br />
<br />
==1 course that sends its enrolments to 4 other courses ==<br />
Meta courses 1-4 each have created a "child" link to Y which is a normal course. Students enrolling on Course Y are automatically enrolled in Meta courses 1-4. <br />
<br />
[[Image:Metacourses2_en.jpg|Upsidedown Meta course Usage|center]]<br />
<br />
For example: this would be used, when all five courses are intended to have exactly the same students.<br />
<br />
==1 course that gets its enrolment from 4 other courses==<br />
X is a meta course and Courses 1, 2, 3, 4 can be normal courses with standard student enrolments. These courses can contain resources, and activities that are specific to those courses, but they may also only contain enrolments. Students enrolling in Courses 1 or 2, or 3 or 4, are automatically enrolled onto Meta course X when the course is associated as a child course to Meta course X. The meta course is dependent upon its enrolments from each of the non-meta courses, the child courses. <br />
<br />
[[Image:Metacourses1_en.jpg|Standard Meta course usage|center]]<br />
<br />
For example, a math teacher has 2 algebra and 2 geometry courses and wants a "home room" to place things of interest for all of their students. The teacher creates a meta course called "Teacher's home room" and links the algebra and geometry courses as the "child" courses.<br />
<br />
=="Merged course" / 1 course that consolidates enrollment from multiple other courses==<br />
For a course with multiple sections - that is, a course where the same material is taught to students enrolled in several separate sections/courses - it is sometimes desirable to create a "merged course" that is used by students across all sections. This assumes that there is no section-specific information.<br />
<br />
To create a "merged course," select one existing course/section that will become the merged metacourse. In that course:<br />
<br />
#In the Settings module, navigate to Course administration -> Users -> Enrollment methods.<br />
#Use the Add method drop-down menu to select Course meta link.<br />
#Use the Link course drop-down menu to choose one of the other sections/courses you wish to merge into the metacourse.<br />
#Repeat the preceding steps as necessary for additional sections/courses.<br />
<br />
To make it clear which course is the merged metacourse, go to that course and:<br />
<br />
#In the Settings module, navigate to Course administration -> Edit settings.<br />
#Change the Course full name appropriately (consider "[Course Number] - [Course Name] - [Course Date]" e.g. "CSSE101 - Introduction to Computer Science - 201210")<br />
#Click Save changes.<br />
<br />
To hide the unused sections/courses, go to each course and:<br />
<br />
#In the Settings module, navigate to Course administration -> Edit settings.<br />
#Use the Availability drop-down menu to select This course is not available for students.<br />
#Click Save changes.<br />
<br />
==Meta course(s) used as libraries==<br />
One or more meta courses are used as a library of resources and activities. <br />
<br />
For example, the English department has collected material useful in writing papers, these are set up as meta courses, with links to their regular courses. Teachers can direct or embed a link to a specific reference about citations, or how to select a topic for a paper or suggested reading compiled by students. Thus an English 101 course should be one of the links in the "Writing Papers" meta course. This Meta course holds a resource called "Citations made easy", a Lesson "Select a topic" and a Wiki or database called "Suggested readings from classmates".<br />
<br />
==Expanding the library concept==<br />
I teach 4 sections of the same course and use a metacourse as the repository for materials used in the 4 sections. What I did was create the resource in the metacourse and then link that resource to the sections. For instance, I created a web page in the metacourse that included course notes. These course notes are in the form of 17 pdf files. The web page has links to the 17 files that were uploaded to the metacourse. Thus, the files and the web page that students will use to get to the files all exist in the metacourse.<br />
<br />
Next I created a link to the web page in my normal courses. To do this I had to execute the web page in the metacourse and copy the address from my browser into the link I created in the normal course.<br />
<br />
When the student is in the normal section course, they simply click on the link and the web page in the metacourse appears. The only minor problem is that the student navigation might leave them in the metacourse instead of the normal section course. To lessen this effect, I always launch links to the metacourse in a new window. Normally students understand that they need to close the popup window when they are finished with it.<br />
<br />
There are several advantages to using metacourses in this way. First, it saves having to upload the same materials more than once. I can change a file in the metacourse and know that it is changed in all section courses. Second, it saves storage space. Third, it provides the possibility of developing learning objects or mini courses that can be quickly linked to create a new course. Finally, it would allows several teachers to pick and choose what materials to include in their section courses.<br />
<br />
One hint, I put all activities (assignments, forums, journals, etc) in the child course, not in the metacourse. This keeps grading segregated and allows me to adjust assignments for a particular section (child).<br />
<br />
Harold Kime [http://moodle.org/mod/forum/discuss.php?d=39438 Teaching strategies forum thread].<br />
<br />
== Common department area==<br />
Here is how we use metacourses for our district. Lets take a math teacher for example who teaches algebra 1, algebra 2 and geometry. This teacher wants a space (Moodle course) for each of their main subject areas. But they also want a generic space where they can post things for all of the students in all of their classes. This is where a meta course comes into play. <br />
<br />
We create a Moodle course for algebra 1, another course for algebra 2 and a 3rd course for geometry. Now we enroll all of the appropriate students into each of these courses. Next we create a meta course and to the meta course we assign the first three courses created. Now by default, all of the students in the first three courses are automatically enrolled in the meta course. Now anything posted in the metacourse is available to all the students in the other three courses. <br />
<br />
Randy Orwin [http://moodle.org/mod/forum/discuss.php?d=39438 Teaching strategies forum thread].<br />
<br />
==A Diploma course sends its enrolment to meta courses==<br />
A Diploma program involves courses D1, D2, D3, and D4. In this case, you would create a "Diploma" course as a normal course (non-meta course). You would then designate programs D1 through D4 as meta courses and each would show the Diploma course as the "child" course. When a student enrolls in "Diploma", he or she will be automatically enrolled in courses D1 through D4.<br />
<br />
==Core subjects with fees based upon course groupings==<br />
You have 3 course subjects and want to offer them for sale in different packages. The meta courses will contain your subjects. A normal (non-Meta course) course will be the gateways to the meta course(s). Course 1 is your gold package. Meta course A, Meta course B and Meta course C all link to Course 1. The silver package is Course 2. Meta courses A and B link to Course 2. You have also set up individual courses that have a link from a specific Meta Course to them. Thus you can offer and charge for each meta course separately or in some combination.<br />
<br />
==One course, different student fees==<br />
You have one "Wizbang" course but want to charge a different rate based upon the type of user. The "Wizbang" meta course is the one that holds the content. You create a courses for "Wizbang for Large Corporation users" and "Wizbang for Small Business users". The Wizbang meta course is linked to "Introduction to Wizbang for Large Corporation users" and "Introduction to Wizbang for Small Business users" courses. You can charge a different fee for the non-meta courses, maybe brand or put some unique material in each "Introduction" course but the students will be able to take the same "Wizbang" course.<br />
==Two courses, combined teaching space==<br />
We have automatic enrolment into Moodle using a custom enrolment plugin. We often have two or more courses that are taught together by the same teacher, in the same classroom with the same lectures. We create a metacourse for both courses and add the two individual courses as child courses. <br />
==Student Support Space for degree programme==<br />
We have a programme which is fully online. We have created a metacourse as a support space which includes information for the programme, specific forums for groups of students (using groups & groupings) and Social Forums to allow students to interact with each other.<br />
<br />
[[Category:Examples of use]]<br />
<br />
[[ja:メタコース使用例]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/user:viewlastip&diff=124869Capabilities/moodle/user:viewlastip2016-08-11T15:05:02Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
*This capability allows a user to view the last IP field in [[User profiles|user profiles]].<br />
*It is set to 'Allow' for the default role of manager only and is not set for other roles.<br />
<br />
[[Category:Capabilities|User]]<br />
[[Category:Site administration]]<br />
<br />
[[es:Capabilities/moodle/user:viewlastip]]<br />
[[de:Capabilities/moodle/user:viewlastip]]<br />
[[ja:ケイパビリティ/moodle/user:viewlastip]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=View_profile&diff=124834View profile2016-08-10T15:03:39Z<p>Mits: ja link</p>
<hr />
<div>{{Accounts}}<br />
*A user may view their own full profile from the user menu top right. They may then personalise the display by clicking the "customise this page" button at the top right of the screen.<br />
*A student or course teacher may see the course profiles of users by clicking their names in ''Navigation>My courses (name of course)>Participants'' Teachers can then access the full profile by clicking the link "full profile" at the bottom of the course profile (if allowed. See 'Viewing full profiles' below).<br />
*An administrator may additionally access and view full profiles via ''Administration>Site administration>Users>Accounts>Browse list of users''. <br />
<br />
==Full (site) profile==<br />
<br />
Depending on what the user has added to their profile, this gives information such as first and last access, general interests and links to individual course profiles. Users may be messaged from the button at the top of their profile.<br />
<br />
A manager or anyone with the capability [[Capabilities/moodle/user:viewlastip]] will also see a link to the IP address from which the user last accessed Moodle.<br />
<br />
==Course profile==<br />
A shorter version of users' profiles is available in the course and includes their role(s) and groups in the course and a link to message them. Those with the relevant permissions are also able to access the full profile from here:<br />
<br />
==Viewing full profiles==<br />
<br />
By default, only admins and managers can view full profiles.<br />
<br />
To allow everyone i.e. all authenticated users to view full profiles:<br />
<br />
# Go to ''Administration > Site administration > Users > Permissions > Define roles''<br />
# Click the edit icon for authenticated user<br />
# Enter moodle/user:viewdetails in the filter box, then tick the checkbox to allow this capability<br />
# Click the 'Save changes' button<br />
<br />
To allow teachers to view full profiles:<br />
<br />
# Go to ''Administration > Site administration > Users > Permissions > Define roles'' and click the 'Add a new role' button<br />
# Give the role a name, such as 'Full profile viewer' and tick System as the context type where the role may be assigned<br />
# Copy and paste ''moodle/user:viewdetails'' into the filter box then tick the box to allow the capability<br />
# Click the 'Create this role' button<br />
# Go to ''Administration > Site administration > Users > Permissions > Assign system roles'' and click 'Full profile viewer'<br />
# Assign teachers the role of 'Full profile viewer' by selecting them in the list of potential users on the right and then adding them to the list on the left<br />
<br />
==Site administration settings==<br />
<br />
An administrator can set the defaults for certain user profile fields from ''Site administration>Users>Accounts>User default preferences''.<br />
<br />
These are:<br />
:Email display<br />
:Email format<br />
:Email digest type<br />
:Forum auto-subscribe<br />
:Forum tracking<br />
<br />
==See also==<br />
*[[User profiles]]<br />
* [[Edit profile]]<br />
*The capability [[Capabilities/moodle/user:viewdetails|moodle/user:viewdetails]]<br />
<br />
[[cs:Profil uživatele]]<br />
[[de:Nutzerprofil ansehen]]<br />
[[eu:Informazio_pertsonala]]<br />
[[fr:Voir le profil]]<br />
[[es:Ver perfil]]<br />
[[ja:ユーザプロファイル]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Roles_and_permissions&diff=124077Roles and permissions2016-06-13T15:06:32Z<p>Mits: Updated ja link</p>
<hr />
<div>{{Managing a Moodle site}}<br />
A role is a collection of permissions defined for the whole system that you can assign to specific users in specific contexts. The combination of roles and context define a specific user's ability to do something on any page. The most common examples are the roles of student and teacher in the context of a course. <br />
<br />
*[[Managing roles]]<br />
*[[Assign roles]]<br />
*[[User policies]]<br />
*[[Using roles]]<br />
*[[Standard roles]]<br />
*[[Creating custom roles]]<br />
*[[Role export and import]]<br />
*[[Permissions]]<br />
*[[Override permissions]]<br />
<br />
==See also==<br />
<br />
*[[Roles FAQ]]<br />
<br />
[[Category:Roles]]<br />
<br />
[[es:Roles y permisos]]<br />
[[eu:Rolak]]<br />
[[fr:Rôles et permissions]]<br />
[[ja:ロールおよびパーミッション]]<br />
[[de:Rollen und Rechte]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Creating_custom_roles&diff=123042Creating custom roles2016-04-26T15:44:05Z<p>Mits: </p>
<hr />
<div>{{Roles}}<br />
==Creating a new role==<br />
<br />
To create a custom role:<br />
#Go to ''Administration > Site administration > Users > Permissions > Define roles''. <br />
#Click the "Add a new role" button.<br />
#Select template for the new role or upload a preset<br />
#Give the role a Short name e.g. 'Parent'.The short name is necessary for other plugins in Moodle that may need to refer to the role (e.g. when uploading users from a file or setting enrolments via an enrolment plugin).<br />
#You must provide a full name for all custom roles. If you need to name the role for multiple languages you can use [[Multi language content|multi-lang syntax]] if you wish.<br />
#Give the role a description (optional).<br />
#Select an appropriate role archetype (see below for further information).<br />
#Select the contexts where the role may be assigned e.g. 'User' for Parent role.<br />
#Set permissions as required.<br />
#Scroll to the top or bottom of the page and click the "Create this role" button.<br />
<br />
<br />
<br />
{|<br />
|-<br />
| [[Image:addinganewrole26.png|thumb|Adding a new role and setting context types]]<br />
| [[Image:permissions125.png|thumb|Choose "Allow" where required]]<br />
| [[Image:permissions225.png|thumb|Extra options with "Show advanced" enabled]]<br />
|-<br />
|}<br />
<br />
==Role archetypes==<br />
<br />
A role archetype<br />
<br />
* Is a hard-coded template for a role<br />
* Is used during upgrades when adding defaults for new capabilities - no archetype = no new capabilities during upgrade<br />
* Is used during when resetting a role to determine the defaults - no archetype = reset removes all capabilities<br />
<br />
There is no need to set a role archetype for custom roles used for overrides or if the site admin wants to specify new capabilities manually after upgrading.<br />
<br />
The archetypes (which relate directly to the built-in roles) are:<br />
* manager<br />
* coursecreator<br />
* editingteacher<br />
* teacher<br />
* guest<br />
* user<br />
* frontpage<br />
<br />
==Creating a duplicate role==<br />
<br />
To create a duplicate role:<br />
#Go to ''Administration > Site administration > Users > Permissions > Define roles''. <br />
#Click the "Add a new role" button.<br />
#Select existing role as a template<br />
#Give a name and set permissions for your new role; scroll down and click "Create this role".<br />
<br />
==New role considerations==<br />
<br />
A new role is not automatically listed in course descriptions even if was created by copying a role that is listed, such as Teacher. If you want the new role to appear in the course listing, you must set it explicitly via ''Administration > Site administration > Appearance > Courses>Course Contacts"<br />
<br />
==Testing a new role==<br />
''Administration > Switch role to''<br />
Use the "Switch role to" link to see what another role will see in that context. <br />
<br />
Since switching roles confines you to those roles you can assign in a course context, this method is only useful for testing course-scoped capabilities (i.e. it will not be useful for testing permissions that apply outside the course context, like moodle/user:edit).<br />
<br />
''Tip:'' You can always create test user and assign the new role to them. Then logout as admin and login as the test user. This is really the best way to test a new role.<br />
<br />
==Example custom roles==<br />
<br />
*[[Parent role|Parent]] - for providing parents/mentors/tutors with permission to view certain information about their children/mentees/tutees<br />
*[[Demo teacher role|Demo teacher]] - for providing a demonstration teacher account with a password which can't be changed<br />
*[[Forum moderator role|Forum moderator]] - for providing a user with permission in a particular forum to edit or delete forum posts, split discussions and move discussions to other forums<br />
*[[Forum poster role]] - a highly restricted custom role which may be given to a visitor account to enable them to post in forums in a guest access course.<br />
*[[Calendar editor role|Calendar editor]] - for enabling a user to add site or course events to the calendar<br />
*[[Blogger role|Blogger]] - for limiting blogging to specific users only<br />
*[[Quiz user with unlimited time role|Quiz user with unlimited time]] - for allowing a user unlimited time to attempt a quiz which has a time limit set<br />
*[[Question creator role|Question creator]] - for enabling students to create questions for use in quizzes<br />
*[[Question sharer]] - for allowing teachers to share questions between courses<br />
*[[Course requester role]] - for restricting users who can make course requests<br />
*[[Feedback template creator]] - for allowing teachers to save as "Public" a Feedback template.<br />
*[[Grading forms publisher]] for allowing teachers to share Advanced grading forms with others<br />
*[[Grading forms manager]] for allowing teachers to share Advanced grading forms with others and to delete templates others have created.<br />
*[[Grade viewer]] for allowing users to view but not edit grades.<br />
*[[Gallery owner role]] - may be used to provide editing capabilities (add and edit gallery images) to users on individual Lightbox Galleries.<br />
*[[Course tagger]] - for allowing users other than managers and editing teachers to tag courses.<br />
<br />
==Uploading users to a system role==<br />
<br />
Where certain custom roles are applied in the system context, it is possible to upload users to that role in bulk by adding the field ''sysrole1'' (etc) to the CSV file<br />
<br />
==See also==<br />
<br />
Using Moodle forum discussions:<br />
* [http://moodle.org/mod/forum/discuss.php?d=66782 What happens if a user has multiple roles in a course?]<br />
* [http://moodle.org/mod/forum/discuss.php?d=90140 logged in: what role am I?]<br />
* For more information, Ask questions and get answers on the [http://moodle.org/mod/forum/view.php?id=6826 "Roles and Permissions"] forum.<br />
<br />
[[Category:Site administration]]<br />
<br />
[[de:Neue Rollen anlegen]]<br />
[[es:Crear roles personalizados]]<br />
[[fr:Création_de_rôles_personnalisés]]<br />
[[ja:カスタムロールの作成]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Course_meta_link&diff=122940Course meta link2016-04-16T15:08:07Z<p>Mits: ja link</p>
<hr />
<div>{{Enrolment}}<br />
The Course meta link plugin makes it possible for one course, called a metacourse, to bring in enrolments from other courses. The Course meta link plugin needs to be enabled both on the site level by the site admin and has to be enabled within the course. <br />
<br />
==Course settings for Course meta link==<br />
<br />
*In a course, go to ''Administration > Course administration > Users > Enrolment methods''.<br />
*Click the dropdown menu under the enrolment methods and select 'Course meta link'.<br />
''<br />
[[File:enrolmentmethods29c.png|thumb|center|300px]]<br />
*In the screen that comes up next, select from the dropdown box the course you wish to bring enrolments from and then click 'Add method'.<br />
[[File:newmetalink.png|thumb|center|400px]]<br />
<br />
*If several courses need to be added to the course, a button "Add method and create another" allows the teacher or course manager to quickly repeat the process without having to return to the main screen and start again.<br />
*For each linked course, the users may be added to an existing group in the new course, or a new group may be created for them. (Groups from the linked courses are not synced to groups in the new courses. All users will be added to one group when the link is made.)<br />
<br />
:Note: ''A teacher in a course will only be able to choose from courses they are teachers in elsewhere.''<br />
<br />
*The users from the source (child) course will now be enrolled in the current course - see the numbers in the screenshot below:<br />
<br />
[[File:Addedmetacourse.png]]<br />
<br />
*When new users are enrolled to the source (child) course, they will be automatically brought into the current target (meta)course.<br />
<br />
==Site settings for Course meta link==<br />
<br />
The Course meta link plugin may be enabled or disabled throughout the site in ''Administration > Site administration > Plugins > Enrolments > Manage enrol plugins''.<br />
<br />
The page ''Administration > Site administration > Plugins > Enrolments > Course meta link'' contains options for defaults that admin can set. (It can be also be accessed by clicking the ''Settings'' link on on the course meta link section of ''Administration > Site administration > Plugins > Enrolments > Manage enrol plugins'')<br />
<br />
By default all role assignments from child courses are synchronised to meta courses. However, the "Roles that are not synchronised to metacourses" setting enables administrators to exclude particular roles.<br />
<br />
==Course meta link capabilities==<br />
<br />
*[[Capabilities/enrol/meta:config|Configure meta enrol instances]]<br />
*[[Capabilities/enrol/meta:selectaslinked|Select course as meta linked]]<br />
<br />
==Enabling teachers to add meta links==<br />
<br />
An administrator can enable teachers to add course meta links as follows:<br />
<br />
* Go to ''Site Administration > Users > Permissions > Define Roles''<br />
* Select the Teacher Role and click on the Edit button<br />
* Scroll down to Course Meta Link as shown in the images below:<br />
{| class="nicetable" <br />
|-<br />
|[[Image:metacoursepermissionset00.png|Permission block for allowing Teachers to link Meta courses.]] <br />
|-<br />
| style="text-align: center;"| The default setting is "Not Set"<br />
|-<br />
|[[Image:metacoursepermissionset01.png|Permission changes for editing.]] <br />
|-<br />
| style="text-align: center;"| When the Edit button is clicked, the panel changes to "Allow" and a checkbox<br />
|- <br />
|[[Image:metacoursepermissionset02.png|Setting permission to allow Teachers to link Meta courses.]]<br />
|-<br />
| style="text-align: center;"| Change to "Allow" by a click on the checkbox. <br />
|}<br />
* Scroll to the bottom of the page to save your changes.<br />
<br />
==Examples of meta-linked courses==<br />
<br />
{| class="nicetable"<br />
|-<br />
![[Image:simplemetacourse0.png|thumb|left|200px|Created - a child course and a meta course.]] <br />
![[Image:simplemetacourse1.png|thumb|left|200px|Associating one child course and one meta course.]]<br />
|}<br />
<br />
Examples: one "child" course (a course linked to a meta course) can be associated with many meta courses. Or one meta course can have many child courses associated with it. Both the child courses (non-meta courses) and the meta courses are independent and can be recycled many times, that is, each can be associated with many of the other. <br />
<br />
{| class="nicetable" <br />
|-<br />
![[Image:simplemetacourse2.png|thumb|left|200px|2 child courses and a meta course.]] <br />
![[Image:simplemetacourse3.png|thumb|left|200px|1 child course and 2 meta courses.]]<br />
![[Image:simplemetacourse4a.png|thumb|left|200px|3 child courses and 2 meta courses.]]<br />
|}<br />
<br />
There is one limitation: you cannot 'nest' metacourses. In other words, if you have child course A linked to meta course B, and you then link B as a child course to meta course C, a student enrolled in A will be added to B, but not to C. In this situation, you would need to add a meta link directly between A and C instead of trying to nest them. (Another option might be to use [[Cohorts]].)<br />
<br />
<br />
==See also==<br />
<br />
Some known issues:<br />
<br />
* MDL-34938 - Important Open Issue: Enrolment expiration date settings in child course do not properly unenrol students from the Meta-course<br />
* MDL-27628 - A workaround in the tracker for adding more than one course at a time<br />
<br />
How to use:<br />
* [https://moodle.org/mod/forum/discuss.php?d=316161#p1266891 Re: Help setting up meta link metacourses with parent child courses] forum post<br />
* [http://www.youtube.com/watch?v=hA5QcTb13no&feature=player_embedded Screencast showing how to use the Course meta link plugin to make a Metacourse]<br />
*[[Metacourse examples of use]]<br />
<br />
[[de:Meta-Einschreibung]]<br />
[[es:Enlace a metacurso]]<br />
[[ja:コースメタリンク]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Managing_repositories&diff=122893Managing repositories2016-04-10T14:02:33Z<p>Mits: ja link</p>
<hr />
<div>{{Repositories}}<br />
==Enabling repositories==<br />
<br />
Repositories can be enabled by an administrator in ''Site administration > Plugins > Repositories > Manage repositories''.<br />
<br />
A repository plugin may be set to one of three possible statuses:<br />
<br />
* "Enabled and visible" means available for use in the [[File picker]]<br />
* "Enabled and hidden" means not available in the [[File picker]] <br />
* "Disabled" means not available for use and if content has been added to your site you will be given the following message:<br />
<pre><br />
Are you sure you want to remove this repository plugin, its options and all of its instances - [Repository Name here]? If you choose "Continue and download", file references to external contents will be downloaded to Moodle. This could take a long time to process.<br />
</pre><br />
With options to Continue, Continue and download, or Cancel.<br />
<br />
The order in which repositories are shown in the [[File picker|file picker]] may be set using the up and down arrows.<br />
<br />
==Vocabulary==<br />
'''Repository plugin''': it is also called a repository type. It can be named Box, Flickr, Mahara, Youtube... Adding a plugin allow users to create instances of this plugin. Only instances are displayed into the file picker. Type only exist in order to let a Moodle administrator to deactivate/delete all instances of a type in one click.<br />
<br />
'''Repository instance''': An instance is displayed into the file picker and it is the access point to an external repository. An instance can have specific settings (for example be linked to a personal account).<br />
<br />
*First case: when you add the plugin, an instance is automatically created and can not be edited. The Moodle administrator cannot change the instance name. The instance name displayed into the file picker will be exactly the same as the plugin name. For example Youtube, Box...<br />
*Second case: the plugin allow the Moodle administrator to add multiple instances. An instance has a name for example Flickr Public access to Martin account, Martin's Mahara... <br/>For this second case it is important to identify two different kind of instances:<br />
#Common instances: The instances set by Moodle administrator in these same administration pages will be available into any file picker.<br />
#Private instance: A teacher can set some instances available only for a course, and an user can set some instances only available for himself. In order to set instances for a course the teacher will go to the course page, and in order to set instances for a personal use, a user will go on his profile page. An administrator cannot add/edit private instances from the administration pages.<br />
<br />
==Common repository settings==<br />
<br />
Common repository settings can be set by an administrator in ''Site administration > Plugins > Repositories > Common Repository settings'':<br />
<br />
===Cache expire===<br />
You can specify how long in seconds file listings are cached locally when browsing external repositories.<br />
<br />
===Timeout settings===<br />
<br />
If users are reporting timeouts when using repositories, an admin can increase the timeout for downloading or synchronising files.<br />
<br />
====Get file timeout====<br />
Timeout in seconds for downloading an external file into Moodle. Defaults to 30.<br />
====Sync file timeout====<br />
Timeout in seconds for syncronising the external file size. Defaults to 1.<br />
====Sync image timeout====<br />
Timeout in seconds for downloading an image file from external repository during syncronisation. Defaults to 3.<br />
<br />
===Allow external links===<br />
<br />
With some repositories such as Flickr and Wikimedia, users can have the choice whether to copy the media into Moodle (the preferred solution) or to make a link to it instead.<br />
<br />
Defaults to Yes.<br />
<br />
===Legacy course files in new courses===<br />
<br />
This repository is not normally available in new courses as it is designed for upgraded 1.9 courses. However, if it is checked here then it will appear when new courses are created - but certain backup and restore features won't work with it. <br />
<br />
See [[Legacy course files]] for more details. This should not be enabled in sites not originally upgraded from Moodle 1.9.<br />
<br />
Defaults to No.<br />
<br />
===Allow adding to legacy course files===<br />
<br />
When 'Legacy course files' is available in a course, this setting controls if users are able to add new files to it. When enabled, users will be able to add files and directories, as well as delete. When disabled, users will not be able to add files and directories.<br />
<br />
==Repository capabilities==<br />
<br />
Authenticated user role:<br />
<br />
*[[Capabilities/repository/alfresco:view|View Alfresco repository]]<br />
*[[Capabilities/repository/areafiles:view|View Embedded files]]<br />
*[[Capabilities/repository/boxnet:view|View Box repository]]<br />
*[[Capabilities/repository/dropbox:view|View a Dropbox folder]]<br />
*[[Capabilities/repository/flickr:view|View Flickr repository]]<br />
*[[Capabilities/repository/flickr public:view|Use Flickr public repository in file picker]]<br />
*[[Capabilities/repository/googledocs:view|View Google Drive repository]]<br />
*[[Capabilities/repository/merlot:view|View the Merlot repository]]<br />
*[[Capabilities/repository/picasa:view|View Picasa repository]]<br />
*[[Capabilities/repository/recent:view|View Recent files]]<br />
*[[Capabilities/repository/s3:view|View Amazon s3 repository]]<br />
*[[Capabilities/repository/skydrive:view|View Microsoft OneDrive repository]]<br />
*[[Capabilities/repository/upload:view|Use uploading in file picker]]<br />
*[[Capabilities/repository/url:view|Use URL downloader in file picker]]<br />
*[[Capabilities/repository/user:view|View use Private files]]<br />
*[[Capabilities/repository/wikimedia:view|View Wikimedia repository]]<br />
*[[Capabilities/repository/youtube:view|Use YouTube in file picker]]<br />
<br />
Manager, Course creator, Teacher, Non-editing teacher Roles:<br />
<br />
*[[Capabilities/repository/coursefiles:view|Use Legacy course files repository]]<br />
*[[Capabilities/repository/filesystem:view|View File system repository]]<br />
*[[Capabilities/repository/local:view|View Server repository]]<br />
*[[Capabilities/repository/webdav:view|View WebDav repository]]<br />
<br />
<br />
[[de:Repositories verwalten]]<br />
[[es:Gestionando repositorios]]<br />
[[ja:リポジトリ管理]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Repositories_FAQ&diff=122143Repositories FAQ2016-01-30T15:38:39Z<p>Mits: ja link</p>
<hr />
<div>{{Repositories}}<br />
==What is a repository?==<br />
A repository can be thought of as a storage area from which users can retrieve files to add to their course. There are several repositories enabled by default, such as [[Server files]] which contains files from other courses a user has access to, or [[Upload a file repository| Upload a file]] which allows the user to search their computer or USB drive for a file to upload. Other repositories include [[Google Docs repository|Google Drive]],or [[Flickr repository|Flickr]]. See [[Repositories]] for more information.<br />
<br />
==How can I enable repositories in Moodle?==<br />
<br />
Repositories can be enabled by a site administrator in ''Administration > Site administration > Plugins > Repositories > Manage repositories''. <br />
<br />
All enabled and visible repositories will appear in the file picker.<br />
<br />
==How can I delete an embedded file previously added using the file picker?==<br />
<br />
There is no need to do anything, as any unused files are detected and then deleted automatically after a period of time. Users cannot delete files manually, since they may be used elsewhere.<br />
<br />
When an activity or resource which uses a file is deleted, the file is moved immediately to trash. The frequency with which trash is emptied i.e. files are deleted depends on the settings in ''Site administration > Server > Scheduled tasks'' (\core\task\file_trash_cleanup_task)<br />
<br />
See also the forum thread [https://moodle.org/mod/forum/discuss.php?d=317135#p1271171 Deleting uploaded files].<br />
<br />
==If I add a file (File resources) to a page, then delete the File resource, will the file I added remain in my Recent files list?==<br />
<br />
No. The file will not be available.<br />
<br />
==How do I create a new repository on my site?==<br />
You can create a new repository that will show up on the file picker. See [[File system repository]].<br />
<br />
==How can I prevent students from accessing the private files repository?==<br />
If you want to prevent students from accessing it but still wish other users to access it, follow these steps:<br />
#In ''Administration>Site administration>Users>Permissions>Define Roles'' create a new role (such as "no private files") and assign it in the system context. (See [[Creating custom roles]] for help creating a new role)<br />
#Search for and set the capabilities ''moodle/user:manageownfiles'' and ''repository/user:view'' to '''prohibit.'''<br />
#In ''Administration>Site administration>Users>Permissions>Assign system roles'', give this role to the student(s) you do not wish to access private files. <br />
#They may be enrolled as normal students in courses, but will not be able to use their private files.<br />
<br />
An alternative, but more dramatic, because it involves modifying standard roles, is to edit both the authenticated user role AND the student role to prevent the capabilities "moodle/user:manageownfiles" and "repository/user:view" - and then edit the teacher role (and any others) to allow them. You have to do it to the authenticated user role as well, as all users are authenticated users in the system as well as teachers or students.<br />
<br />
==What happens if a teacher adds a file from their Private files to the course and they later leave and their account is closed?==<br />
As long as a file is used in a context, such as a course, the file should remains available in that context.<br />
<br />
That holds true when a teacher copies a file in a course from his My private files area and also when a teacher creates an alias/shortcut: in the latter case if a teacher deletes his files from My private files area that are used as alias/shortcut in some courses, Moodle will convert existing alias/shortcuts into file copies, so your course file links won't break. ''(copied from [https://moodle.org/mod/forum/discuss.php?d=2287 forum thread thanks to Andrea Bicciolo]''<br />
<br />
==I cannot access a student's repositories when logged in as that student==<br />
This is intentional, as there is a security and privacy risk involved in an administrator being able to log in as a student and then explore and use the student's Google Drive, Dropbox and other similar repositories.<br />
<br />
==See also==<br />
<br />
* [[File picker FAQ]]<br />
* [[File system repository FAQ]]<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=1807 Repositories forum]<br />
<br />
[[Category:FAQ]]<br />
<br />
[[de:Repositories FAQ]]<br />
[[es:Repositorios FAQ]]<br />
[[ja:リポジトリFAQ]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Repositories&diff=121759Repositories2015-12-08T15:03:08Z<p>Mits: </p>
<hr />
<div>{{Managing content}}<br />
Repositories in Moodle enable users to add files to a course and other locations in Moodle. Repositories provide access to specific types of file sources. They can also allow, where appropriate, users to upload files, access previously uploaded files, and to easily bring content into Moodle from external sources, such as Flickr or Google Docs. <br />
<br />
See [[Managing repositories]] for more on configuring and managing them.<br />
<br />
==Standard repositories==<br />
<br />
Repositories are managed in ''Site administration > Plugins > Repositories > Manage repositories''. Standard repositories come with default Moodle. It is also possible to add additional repositories via Moodle plugins. <br />
<br />
===Repositories enabled by default===<br />
<br />
* [[Embedded files repository|Embedded files]] - Allows linking to files and images available to the user that have been added/embedded in their course activities<br />
* [[Server files repository|Server files]] - Gives access to files elsewhere on the Moodle site (limited by a user's permissions)<br />
* [[Recent files repository|Recent files]] - Shows the last 50 files you have uploaded, according to the context<br />
* [[Upload a file repository|Upload a file]] - Enables the "Upload a file" option in the site File picker to allow users to browse for and upload files<br />
* [[Private files]] - Enables access to a personal storage area for every user<br />
* [[URL downloader repository|URL downloader]] - Allows downloading of files and images from a particular URL<br />
* [[Wikimedia repository|Wikimedia]] - Let's users search for and insert media (images) from Wikipedia<br />
<br />
===Additional standard repositories disabled by default===<br />
These may be enabled and set to visible or hidden by a site administrator.<br />
<br />
* [[Alfresco repository|Alfresco]] - link to or copy files from Alfresco into Moodle<br />
* [[Box repository|Box]] - bring files in from your Box account<br />
* [[Legacy course files]] - use the old system from 1.9 of "course files" (pertains to sites upgraded to 1.9)<br />
* [[Dropbox repository|Dropbox]] - link to or copy files from Dropbox<br />
* [[EQUELLA repository|EQUELLA]] - link to files in an EQUELLA installation<br />
* [[File_system_repository|File system]] - access files uploaded to a folder on your server (by, eg FTP)<br />
* [[Flickr repository|Flickr]] - search for and display images from your personal Flickr account<br />
* [[Flickr public repository|Flickr public]] - search for and display images publicly available from Flickr<br />
* [[Google Drive repository|Google Drive]] - bring files from your Google Drive account<br />
* [[Merlot.org repository|Merlot.org]] - bring resources in from Merlot.org<br />
* [[Picasa web album repository|Picasa web album]] - search for and display images from your Picasa account<br />
* [[Amazon S3 repository|Amazon S3]] - enables users to copy files from Amazon S3 storage instances<br />
* [[Skydrive repository|OneDrive]] bring in files from your Microsoft OneDrive<br />
* [[WebDAV repository|WebDAV]] -bring in files from external sources using WebDAV protocol <br />
* [[Youtube videos repository|Youtube videos]] - search for and display Youtube videos<br />
<br />
==See also==<br />
<br />
* [[Managing repositories]]<br />
* [[Repositories FAQ]]<br />
* [http://www.youtube.com/watch?v=zdrdyev82bU Repositories in Moodle 2.0 video]<br />
* [http://www.somerandomthoughts.com/blog/whitepaper-moodle-2-repositories/ Whitepaper – Moodle 2 Repositories] by Gavin Henrick<br />
* [http://www.moodlerooms.com/resources/blog/five-tips-using-new-file-repository-system-moodle Five Tips for Using the New File Repository System in Moodle] by Marcelo Mendes<br />
* [[:dev:Repository plugins]] developer documentation<br />
* [http://moodle.org/plugins/browse.php?list=category&id=25 Moodle Repository Plugins database]<br />
* [http://moodle.org/mod/forum/view.php?id=1807 Moodle Repositories discussion forum]<br />
<br />
[[Category:Repositories]]<br />
<br />
[[es:Repositorios]]<br />
[[eu:Biltegiak]]<br />
[[de:Repositories]]<br />
[[fr:Dépôts]]<br />
[[ja:リポジトリ]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Unenrolment&diff=121647Unenrolment2015-11-30T04:22:21Z<p>Mits: ja link</p>
<hr />
<div>{{Course enrolment}}<br />
Unenrolment is the process of removing users from a course. It is controlled by one or more of the following:<br />
<br />
* The enrolment duration, which suspends students after the specified time has elapsed. Some plugins include the option to unenrol users after enrolment expiration<br />
* For self enrolment, the 'Unenrol inactive after' setting in ''Administration > Course administration > Users > Enrolment methods > Self enrolment'' can be set to specify a time after which a student is automatically unenrolled from a course if they haven't accessed it in that time<br />
* An [[Enrolment plugins|enrolment plugin]] may decide that the enrolment has expired, for example, if a user for a course is not present in an LDAP database, or if a Flat file is processed by Cron.<br />
<br />
In addition, users with the appropriate permission can unenrol themself from a course. <br />
<br />
==Enrolment duration==<br />
<br />
The default enrolment duration for manual enrolment can be set in ''Administration > Course administration > Users > Enrolment methods > Manual enrolment''. It can be amended from the default value when enrolling users manually in ''Administration > Course administration > Users > Enrolled users''.<br />
<br />
The enrolment duration for self enrolment can be set in ''Administration > Course administration > Users > Enrolment methods > Self enrolment''.<br />
<br />
==Bulk unenrolment==<br />
<br />
Users who were previously manually enrolled may be unenrolled in bulk via ''Administration > Course administraton > Users > Enrolment methods'' then clicking on the 'Enrol' users icon.<br />
<br />
==Unenrolment and grade history==<br />
<br />
When a user is unenrolled, their grade history is not deleted. If a user is unenrolled accidentally, their grades can be restored by going to ''Administration > Course administration > Users > Enrolled users'', clicking 'Enrol users' and making sure that the 'Recover user's old grades if possible' checkbox is ticked in the enrolment options before re-enrolling the user.<br />
<br />
Users enrolled with methods other than manual will have their grades restored depending on the value of "recovergradesdefault" in ''Administration > Site administration > Grades > General settings''.<br />
<br />
==Suspended or Unenrolled?==<br />
<br />
'''Suspended users''' are not longer able to access any of their courses on Moodle but their data is preserved, so it is possible for them to return to their course at a later time. This might be useful for example, for keeping safe the work of students who have left the establishment but whose data might be needed for inspection in future years. Suspended users currently still appear in the gradebook but a teacher can select in their Grader report preferences to show only active users or all users (including suspended users). See [[Grade settings]] for more details.<br />
<br />
''Note:'' A single user may be suspended by an admin user or manager by editing the user's profile and selecting "Suspended account". Groups of users may be suspended from "Users > Enrolled users". With the manual enrolments selected, choose "Edit user enrolments" and "Alter status > Suspended"''.<br />
<br />
It is also possible to suspend users from courses via csv/text file from ''Site administration > Users > Accounts > Upload users'' using the enrolstatus field, where 1 against a user means they are suspended (and leaving blank means they are still enrolled.)<br />
<br />
'''Unenrolled users''' do not normally retain any data and will not appear in the gradebook. However, see [[#Unenrolment and grade history]] Unenrolment is typically more final than suspension.<br />
<br />
==See also==<br />
[http://www.screencast.com/t/XtPhA6w2SM Screencast: how to bulk unenrol students from a course.]<br />
<br />
[[Category:Site administration]]<br />
<br />
[[eu:Desmatrikulatzea]]<br />
[[fr:Désinscription]]<br />
[[de:Abmelden aus einem Kurs]]<br />
[[es:Des-inscripción]]<br />
[[ja:登録解除]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Import_course_data&diff=119706Import course data2015-09-01T15:02:59Z<p>Mits: ja link</p>
<hr />
<div>{{Reusing activities}}<br />
Course activities and resources may be imported from any other course that the teacher has editing permissions in. This will allow teachers to re-use instead of re-creating one or more [[Activities|activities]] or [[Resources|resources]]. <br />
<br />
Import course data is similar to a backup and restore process and does not include any user data.<br />
<br />
==How to import activities or resources==<br />
<br />
*In ''Administration > Course Administration'', click on the ''Import'' link:<br />
<br />
[[File:Importactivities.png]]<br />
<br />
*Select the course you wish to import from and click ''Continue''.<br />
*You will be presented with the "backup settings" page. Use the check boxes for import activities, blocks and or filters as types of items which will show on the next screen. <br />
<br />
[[File:Importsettings.png]]<br />
<br />
*Select the elements you want to include in the import in the Schema settings step.<br />
<br />
[[File:Includeforimport.png]]<br />
<br />
*Review and click ''Perform import'' or click the cancel or previous buttons. The confirmation page will place green check marks and red marks next to the backup settings and include item list for you to review.<br />
<br />
[[File:Includeforimportconfirm.png]]<br />
<br />
*You should see the "Import complete. Click continue to return to the course." message, or an error message indicating that the import process did not take place.<br />
<br />
==Examples and tips==<br />
<br />
*Importing a quiz from course A to course B, will also add the questions to the question bank so you can use them in new quizzes. <br />
*''Tip:'' Groups can also be imported as a batch from a file.<br />
* ''Tip:'' It may be necessary to check all Activities (Forums, Assignments, etc.) to assure they are now using HTML format. Due to the change in the HTML editor from 1.9 to 2.2, editing of Activities comes up as "Moodle Auto-format" which displays the HTML version of the Description. Once the "Moodle Auto-format" has been changed to "HTML format" the new HTML editor is available by default when editing.<br />
<br />
<br />
==Import course capabilities==<br />
<br />
* [[Capabilities/moodle/backup:backuptargetimport|Backup for import]] - allows a user to backup a course ready for importing into another course <br />
* [[Capabilities/moodle/restore:restoretargetimport|Restore from files targeted as import]] - allows a user to import activities or resources from another course<br />
<br />
==See also==<br />
*[[Course backup]] & [[Course restore]] - for a similar process<br />
<br />
<br />
[[fr:Importation]]<br />
[[de:Kursdaten importieren]]<br />
[[es:Importar datos de curso]]<br />
[[ja:コースデータをインポートする]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/restore:restoretargetimport&diff=119695Capabilities/moodle/restore:restoretargetimport2015-08-31T15:03:18Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to [[Import course data|import activities or resources from another course]]<br />
*Together with the capability [[Capabilities/moodle/backup:backuptargetimport|moodle/backup:backuptargetimport]], this allows a user to duplicate an activity or resource using the x2 icon on the course page (when editing is turned on)<br />
*This capability is allowed for the default roles of manager and teacher <br />
<br />
==See also==<br />
<br />
* [[Reusing activities]]<br />
<br />
[[Category:Capabilities|Backup]]<br />
[[Category:Backup]]<br />
<br />
[[es:Capabilities/moodle/restore:restoretargetimport]]<br />
[[ja:ケイパビリティ/moodle/restore:restoretargetimport]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/backup:backuptargetimport&diff=119636Capabilities/moodle/backup:backuptargetimport2015-08-24T15:32:35Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to backup a course ready for importing into another course<br />
*Together with the capability [[Capabilities/moodle/restore:restoretargetimport|moodle/restore:restoretargetimport]], this allows a user to duplicate an activity or resource using the x2 icon on the course page (when editing is turned on)<br />
*This capability is allowed for the default roles of manager and teacher<br />
<br />
==See also==<br />
<br />
* [[Reusing activities]]<br />
* [[Import course data]]<br />
<br />
[[Category:Capabilities|Backup]]<br />
[[Category:Backup]]<br />
<br />
[[ja:ケイパビリティ/moodle/backup:backuptargetimport]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=SSL_certificate_for_moodle.org&diff=118779SSL certificate for moodle.org2015-06-08T15:25:35Z<p>Mits: ja link</p>
<hr />
<div>{{Security}}<br />
== Synopsis ==<br />
<br />
'''NOTE: This has been updated as of 04/11/2013 - Moodle has moved to the GeoTrust Certificate Authority'''<br />
<br />
When you, as an administrator, [[Notifications|check for available updates]] or [[Automatic updates deployment|install an update]], your Moodle site needs to communicate with moodle.org. This communication is done via the secure HTTPS protocol. Your Moodle site validates the SSL certificate of moodle.org (such as the [https://moodle.org/plugins Moodle plugins directory]) and verifies its identity. To pass this verification, there must be a certificate (in the PEM format) of the [http://en.wikipedia.org/wiki/Certificate_authority certificate authority (CA)] that issued the certificate for moodle.org installed on your server. <br />
<br />
The SSL certificate for moodle.org has been issued by the [http://www.geotrust.com/resources/root-certificates/ GeoTrust Certificate Authority].<br />
<br />
== Problem ==<br />
<br />
If this CA certificate is missing, the remote site (moodle.org) can not be verified and so your Moodle site will refuse to fetch the data (to protect you against so called man-in-the-middle attack). The exact location of the certificate on your server depends on the OS type and other settings. On Linux servers it may be typically found at ''/usr/share/ca-certificates/mozilla/GeoTrust_Primary_Certification_Authority.crt'' for example.<br />
<br />
A missing CA certificate results in an error when checking for available updates and attempting to install them.<br />
<br />
== Solutions ==<br />
<br />
=== Update your operating system (recommended) ===<br />
<br />
The recommended way to fix this problem is to update your server's operating system so that it contains recent SSL certificates from common certificate authorities. This does not seem to help for Windows servers though. At Windows, the cURL library bundled with PHP does not use the CA certificates installed in the OS and you will have to use the alternative solution described below.<br />
<br />
For Debian and RedHat based distributions, CA certificates are distributed in the ''ca-certificates'' package. Gentoo servers provide them via the ''app-misc/ca-certificates'' ebuild. It's also a good idea to make sure that the OpenSSL libraries (libssl) and cURL libraries (libcurl) are up-to-date on your server.<br />
<br />
=== Provide the CA certificate manually ===<br />
<br />
If updating the operating system is not an option for you, or the administrator of the server refuses to update the CA certificates on the server (despite there being no good reason for not doing so), or updating the CA installed in the OS did not help (such as in case of Windows servers), a possible workaround is to download the bundle of required certificates from the [http://curl.haxx.se/ca/ cURL] site. You need to download the file [http://curl.haxx.se/ca/cacert.pem cacert.pem] from there and put it into your ''moodledata/moodleorgca.crt'' file (i.e. download the cacert.pem file, rename it to moodleorgca.crt and upload it into your mooodledata). If this file is found in moodledata, Moodle will use it instead of relying on certificates provided by the operating system.<br />
<br />
It must be highlighted that having the CA certificate on your server's operating system as described above is really the recommended solution. The solution based on moodleorgca.crt should only be considered as a temporary fix (although it seems to be the only way to make it work at Windows servers).<br />
<br />
Alternatively, the direct root certificate can be found here, which you may download and install on your system.<br />
[http://www.geotrust.com/resources/root_certificates/certificates/GeoTrust_Primary_CA.pem GeoTrust Primary CA]<br />
<br />
[[es:SSL certificate for moodle.org]]<br />
[[ja:moodle.orgのSSL証明書]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=History&diff=117834History2015-04-09T17:47:01Z<p>Mits: ja link</p>
<hr />
<div>{{About Moodle}}<br />
Growing up in the Australian outback in the late 1970s, Moodle's Founder and Lead Developer Martin Dougiamas took lessons from the School of the Air, giving him from a young age an insight into distance learning.<br />
<br />
As an adult, he worked and later studied at Curtin University, where his experience with WebCT prompted him to investigate an alternative method of online teaching. In 1999 he started trialling early prototypes of a new LMS, the experiences of which formed the basis for his paper [https://otl.curtin.edu.au/professional_development/conferences/tlf/tlf2000/dougiamas.html Improving the Effectiveness of online Learning]. He registered the word 'Moodle' as a [https://docs.moodle.org/dev/License trademark of Moodle Pty Ltd] and explained his choice of name in a [https://moodle.org/mod/forum/discuss.php?d=27533&parent=129848 forum post] some years later.<br />
<br />
Research continued: the first ever Moodle site was Peter Taylor's http://smec2001.moodle.com/ at Curtin University , with Martin making the [https://moodle.org/mod/forum/discuss.php?d=1 first post] on his own Moodle.com site in November 2001. The pair published [http://dougiamas.com/writing/herdsa2002/ An Interpretive analysis of an internet based course constructed using a new courseware tool called Moodle.]<br />
<br />
By the end of 2001, Moodle could be downloaded via CVS (Git arrived in 2010 and replaced CVS in 2013) and basic installation documentation was available. It was still very much one man's vision, with Martin setting up the [https://tracker.moodle.org/secure/Dashboard.jspa tracker in May 2002] "so you can see what I am working on."<br />
<br />
[https://moodle.org/mod/forum/discuss.php?d=31 Moodle 1.0] was released in August 2002. Users were discussing Moodle on a new forum, translating Moodle into different languages and creating themes. A year later, the first contributed module (workshop) was released and [https://moodle.org/ Moodle.org] became the community arm of Moodle, with [https://moodle.com Moodle.com] representing the commercial aspect.<br />
<br />
Moodle grew quickly: the first ever Moodle Moot was held in Oxford in 2004 and companies started applying to become [http://moodle.com/partners/ Moodle partners.] 2005 marked the move to [https://moodle.org/mod/forum/discuss.php?d=32727 dedicated premises] with Martin and 4 others; [http://moodle.com/contact/ the current HQ] at Richardson St West Perth, houses 16 with 11 working remotely. At the Spanish Moodle Moot 2005 in Las Palmas de Gran Canaria, the mojito established itself as the unofficial - and then subsequently official - Moodle Moot drink. (See blog post: [http://www.moodleblog.net/2014/03/07/the-history-of-moodle-mojitos/ Moodle Mojitos History])<br />
<br />
With improved documentation and new certification , Moodle had established itself by 2007 as a leading and [https://moodle.org/mod/forum/discuss.php?d=68408 award-winning open source LMS]. From 1000 registered sites in 2004, it had gone to half a million users in 2008 and over a million users in 2010, with over 50 Moodle partners. Its translation repository [[:dev:AMOS_manual|AMOS]] held over 100 languages. The long awaited [https://moodle.org/mod/forum/discuss.php?d=162906 Moodle 2.0] came out in November 2010 and now, regular releases bring enhanced features every six months. The current focus is on mobile technology: an [https://moodle.org/mod/forum/discuss.php?d=227988 official HTML5 app] was released in 2013 and the latest version of Moodle includes a customisable theme suitable for all screen sizes.<br />
<br />
The inauguration of the [http://research.moodle.net/ Moodle Research conference] in 2012 served as a reminder that, however advanced the technology, Moodle design and development is guided by [[Philosophy| social constructionist pedagogy]]. During September 2013, the official Moodle MOOC, [http://learn.moodle.net Learn Moodle], introduced over 9000 participants to Moodle's basic features. Educators everywhere are encouraged to share their experiences, just as did Martin over a decade previously. The MOOC was repeated in January 2015 and will be run on a regular, six monthly basis.<br />
<br />
[[es:Historia]]<br />
[[de:Historie]]<br />
[[ja:歴史]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Amazon_EC2_Cloud_Services_Installation&diff=116633Amazon EC2 Cloud Services Installation2015-01-02T15:48:47Z<p>Mits: ja link</p>
<hr />
<div>This is essentially a linux box in the cloud but at the time of writing I did not like to add it to the Linux category, it seems more general than that somehow. If this install lacks detail or doesn't work then see comments attached to this page. I start this off with some assumptions and then go though a full install using the cli. <br />
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.<br />
<br />
= Install all the requirements =<br />
From the cli as root or sudo<br />
<br />
yum install httpd<br />
yum install mysql-server <br />
yum install git<br />
yum install php<br />
yum install php-gd <br />
yum install php-pear<br />
yum install php-mbstring<br />
yum install memcached <br />
yum install php-mcrypt <br />
yum install php-xmlrpc <br />
yum install php-soap <br />
yum install php-intl <br />
yum install php-zip <br />
yum install php-zts<br />
yum install php-xml<br />
<br />
Or save some typing and copy and paste this into the terminal. It will install everything one should need for a Moodle installation:<br />
<br />
sudo yum -y install aspell aspell-en aspell-fr aspell-es cvs git httpd memcached mysql mysql-server php php-cli php-gd php-intl php-mbstring php-mcrypt php-mysql php-pdo php-pear php-pecl-zip php-pspell php-soap php-xml php-xmlrpc php-zip php-zts unzip zip zip.so<br />
<br />
= To ensure that mysql and httpd come up on boot. =<br />
<br />
<br />
chkconfig mysqld on <br />
chkconfig httpd on<br />
<br />
= To ensure that utf8 is used by mysql = <br />
<br />
edit /etc/my.cnf to read as follows (I have found that the precise lines required seem to vary as time goes on)<br />
Back up my.cnf first with <br />
cp /etc/my.cnf /etc/mycnf.original<br />
<br />
Then edit to read<br />
<br />
[mysqld]<br />
default-character-set=utf8<br />
default-collation=utf8_unicode_ci<br />
character-set-server=utf8<br />
collation-server=utf8_unicode_ci<br />
datadir=/var/lib/mysql<br />
socket=/var/lib/mysql/mysql.sock<br />
user=mysql<br />
# Disabling symbolic-links is recommended to prevent assorted security risks<br />
symbolic-links=0<br />
[mysqld_safe]<br />
log-error=/var/log/mysqld.log<br />
pid-file=/var/run/mysqld/mysqld.pid<br />
[client]<br />
default-character-set=utf8<br />
<br />
Check that mysql restarts with <br />
service mysqld restart<br />
<br />
NB edit. Later with FC16 I found that I needed to make my.cnf read<br />
<br />
[mysqld]<br />
# Settings user and group are ignored when systemd is used.<br />
# If you need to run mysqld under different user or group, <br />
# customize your systemd unit file for mysqld according to the<br />
# instructions in http://fedoraproject.org/wiki/Systemd<br />
character-set-server=utf8<br />
collation-server=utf8_unicode_ci<br />
datadir=/var/lib/mysql<br />
socket=/var/lib/mysql/mysql.sock<br />
# Disabling symbolic-links is recommended to prevent assorted security risks<br />
symbolic-links=0<br />
<br />
[mysqld_safe]<br />
log-error=/var/log/mysqld.log<br />
pid-file=/var/run/mysqld/mysqld.pid<br />
<br />
= In order to make sure php is included when httpd comes up =<br />
<br />
make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following<br />
<br />
<IfModule prefork.c><br />
LoadModule php5_module modules/libphp5.so<br />
</IfModule> <IfModule worker.c><br />
LoadModule php5_module modules/libphp5-zts.so<br />
</IfModule><br />
AddHandler php5-script .php AddType text/html .php<br />
DirectoryIndex index.php<br />
<br />
<br />
At the time of writing 26-01-2012) (php-common should provide zip.so but it doesn't so I have put a copy here (http://moodle.org/mod/forum/discuss.php?d=194589))<br />
Attached to a forum post. Perhaps a wiki buff could fix that better.<br />
<br />
Once you have got zip.so, put it in /usr/lib/php/modules<br />
<br />
Also you need to add<br />
<br />
extension=zip.so<br />
<br />
to your php.ini (in /etc)<br />
<br />
= Create the database, database user and access rights =<br />
run<br />
<br />
mysql_secure_installation<br />
<br />
Answer all the questions conservatively. (e.g. You will not need test databases or for root to have any other mysql access than local.) This will create a root mysql pw for you. Mysql users are nothing whatsoever to do with you unix users.<br />
<br />
run<br />
mysql -u root -p<br />
<password you set above><br />
<br />
In mysql you need to <br />
<br />
1. make a database. The name can be anything you like. I used moodledb<br />
<br />
2. make a database user. The name can be anything you like. I used moodledbuser.<br />
<br />
3. give that user rights to access the database from the localhost. <br />
<br />
4. No db access is required by anyone from any other host than the localhost<br />
<br />
<br />
<br />
** Now you are in mysql and all the commands are mysql commands and could equally be run on a windows instance of mysql. Do not forget the ";" after each command.<br />
<br />
create database moodledb;<br />
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';<br />
quit<br />
<br />
TEST the above by doing<br />
<br />
mysql -u moodledbuser -p<br />
<password><br />
<br />
If you get connected OK then you can go on and quit.<br />
<br />
= Create moodledata folder =<br />
mkdir /var/www/moodledata<br />
<br />
The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.<br />
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.<br />
<br />
chown apache:apache /var/www/moodledata<br />
<br />
= Fetch moodle =<br />
<br />
cd /var/www/html<br />
git clone git://git.moodle.org/moodle.git<br />
<br />
This should put all of moodle in a directory called moodle in the correct folder /var/www/html. It takes a while but you get %age feedback.<br />
<br />
There are more sophisticated git commands, see git docs in moodle docs for more info.<br />
Also, you may give the apache user ownership of the site, this way, when you install, the script will be able to create the config.php file.<br />
If you leave the owner as root, you will have to paste the suggested config.php into /var/www/html/moodle<br />
<br />
To give apache ownership do<br />
<br />
chown -R apache:apache /var/www/html/moodle<br />
<br />
= Do the install =<br />
<br />
Visit http://<your amazon host>/moodle<br />
<br />
Well, it worked for me!<br />
<br />
= Other Resources = <br />
<br />
For another method of using Amazon EC2 for Moodle hosting you can utilize the free image created by Bitnami.org: http://bitnami.org/stack/moodle which makes creating a Moodle server on Amazon a snap (no command line necessary)<br />
<br />
[[ja:Amazon EC2クラウドサービスインストレーション]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Badges_settings&diff=113222Badges settings2014-06-19T15:16:21Z<p>Mits: </p>
<hr />
<div>{{Badges}}<br />
<br />
==Individual user settings==<br />
*A user can [[Managing badges|manage badges]] from ''Navigation>My profile>My badges''.<br />
*A user can view available course badges from ''Navigation>Current course>Badges''.<br />
<br />
{|<br />
|[[File:coursebadgenav1.png|thumb|Viewing course badges]]<br />
|}<br />
<br />
==Viewing the badges of other users==<br />
<br />
{{New features}}<br />
<br />
*A student can view other students' course badges by going to ''Navigation>Participants'' and clicking on the course profile of a chosen user. Badges are visible in the short (course) profile.<br />
<br />
==Course administration settings==<br />
*A teacher can add and manage badges in their course if the administrator has enabled course badges in ''Administration>Site administration>Badges settings.''<br />
*They will see a link to badges in ''Administration>Course administration>Badges.'' where badges may be [[Managing badges| managed]] and added.<br />
<br />
==Site administration settings==<br />
*Badges are enabled by default and can be disabled in ''Administration>Site administration>Advanced features.'' (Note that disabling the feature once badges have been awarded does not prevent those badges being verified by external backpacks.)<br />
*The site settings for badges are located in ''Administration>Site administration>Badges>Badges settings''<br />
===Default badge issuer===<br />
Here you set the name and email address of the issuer. The name will appear where the badges are displayed and might typically be the name of the organization.<br />
===Salt for hashing recipient's email address===<br />
If a hash is used (numbers and letters only) then backpack services can confirm a badge earner without exposing their email address.<br />
===Enable connection to external backpacks===<br />
This should be enabled in order to connect to, for example [http://openbadges.org/ Mozilla Open Badges]. Note that this will not work on a Moodle hosted locally/offline.<br />
===Enable course badges===<br />
Ticking this box will allow teachers to add and manage badges in their courses.<br />
<br />
==Badges capabilities==<br />
There are a number of capabilities associated with badges:<br />
<br />
*[[Capabilities/block/badges:addinstance|Add a new My latest badges block]]<br />
*[[Capabilities/block/badges:myaddinstance|Add a new My latest badges block to My home]]<br />
*[[Capabilities/moodle/badges:awardbadge| Award a badge]]<br />
*[[Capabilities/moodle/badges:configurecriteria|Set up criteria for awarding a badge]]<br />
*[[Capabilities/moodle/badges:configuredetails|Set up and edit badge details]]<br />
*[[Capabilities/moodle/badges:configuremessages|Configure badges messages]]<br />
*[[Capabilities/moodle/badges:createbadge| Create or duplicate badges]]<br />
*[[Capabilities/moodle/badges:deletebadge| Delete badges]]<br />
*[[Capabilities/moodle/badges:earnbadge|Earn badges]]<br />
*[[Capabilities/moodle/badges:manageglobalsettings | Manage badges site administration settings]]<br />
*[[Capabilities/moodle/badges:manageownbadges|View and manage your own earned badges]]<br />
*[[Capabilities/moodle/badges:viewawarded|View users who earned a specific badge without being able to award a badge]]<br />
*[[Capabilities/moodle/badges:viewbadges |View badges without earning them]]<br />
*[[Capabilities/moodle/badges:viewotherbadges|View public badges in other users' profiles]]<br />
<br />
[[de:Auszeichnungen konfigurieren]]<br />
[[es:Configuraciones de insignias]]<br />
[[ja:バッジ設定]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Badges_settings&diff=113221Badges settings2014-06-19T15:15:57Z<p>Mits: ja link</p>
<hr />
<div>{{Badges}}<br />
<br />
==Individual user settings==<br />
*A user can [[Managing badges|manage badges]] from ''Navigation>My profile>My badges''.<br />
*A user can view available course badges from ''Navigation>Current course>Badges''.<br />
<br />
{|<br />
|[[File:coursebadgenav1.png|thumb|Viewing course badges]]<br />
|}<br />
<br />
==Viewing the badges of other users==<br />
<br />
{{New features}}<br />
<br />
*A student can view other students' course badges by going to ''Navigation>Participants'' and clicking on the course profile of a chosen user. Badges are visible in the short (course) profile.<br />
<br />
==Course administration settings==<br />
*A teacher can add and manage badges in their course if the administrator has enabled course badges in ''Administration>Site administration>Badges settings.''<br />
*They will see a link to badges in ''Administration>Course administration>Badges.'' where badges may be [[Managing badges| managed]] and added.<br />
<br />
==Site administration settings==<br />
*Badges are enabled by default and can be disabled in ''Administration>Site administration>Advanced features.'' (Note that disabling the feature once badges have been awarded does not prevent those badges being verified by external backpacks.)<br />
*The site settings for badges are located in ''Administration>Site administration>Badges>Badges settings''<br />
===Default badge issuer===<br />
Here you set the name and email address of the issuer. The name will appear where the badges are displayed and might typically be the name of the organization.<br />
===Salt for hashing recipient's email address===<br />
If a hash is used (numbers and letters only) then backpack services can confirm a badge earner without exposing their email address.<br />
===Enable connection to external backpacks===<br />
This should be enabled in order to connect to, for example [http://openbadges.org/ Mozilla Open Badges]. Note that this will not work on a Moodle hosted locally/offline.<br />
===Enable course badges===<br />
Ticking this box will allow teachers to add and manage badges in their courses.<br />
<br />
==Badges capabilities==<br />
There are a number of capabilities associated with badges:<br />
<br />
*[[Capabilities/block/badges:addinstance|Add a new My latest badges block]]<br />
*[[Capabilities/block/badges:myaddinstance|Add a new My latest badges block to My home]]<br />
*[[Capabilities/moodle/badges:awardbadge| Award a badge]]<br />
*[[Capabilities/moodle/badges:configurecriteria|Set up criteria for awarding a badge]]<br />
*[[Capabilities/moodle/badges:configuredetails|Set up and edit badge details]]<br />
*[[Capabilities/moodle/badges:configuremessages|Configure badges messages]]<br />
*[[Capabilities/moodle/badges:createbadge| Create or duplicate badges]]<br />
*[[Capabilities/moodle/badges:deletebadge| Delete badges]]<br />
*[[Capabilities/moodle/badges:earnbadge|Earn badges]]<br />
*[[Capabilities/moodle/badges:manageglobalsettings | Manage badges site administration settings]]<br />
*[[Capabilities/moodle/badges:manageownbadges|View and manage your own earned badges]]<br />
*[[Capabilities/moodle/badges:viewawarded|View users who earned a specific badge without being able to award a badge]]<br />
*[[Capabilities/moodle/badges:viewbadges |View badges without earning them]]<br />
*[[Capabilities/moodle/badges:viewotherbadges|View public badges in other users' profiles]]<br />
<br />
[[de:Auszeichnungen konfigurieren]]<br />
[[es:Configuraciones de insignias]]<br />
[[en:バッジ設定]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:viewotherbadges&diff=113118Capabilities/moodle/badges:viewotherbadges2014-06-14T15:11:32Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to view public [[Badges|badges]] in other users' profiles<br />
* This capability is allowed for the default role of authenticated user <br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:viewotherbadges]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:viewbadges&diff=113037Capabilities/moodle/badges:viewbadges2014-06-10T15:25:03Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to view [[Badges|badges]] without earning them<br />
* This capability is allowed for the default roles of manager, student and authenticated user <br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:viewbadges]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:viewawarded&diff=112981Capabilities/moodle/badges:viewawarded2014-06-08T07:24:37Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to view users who earned a specific [[Badges|badge]] without being able to award a badge<br />
* This capability is allowed for the default roles of manager, teacher and non-editing teacher<br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:viewawarded]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:manageownbadges&diff=112869Capabilities/moodle/badges:manageownbadges2014-06-03T21:29:23Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to view and manage their own earned [[Badges|badges]]<br />
* This capability is allowed for the default role of authenticated user <br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:manageownbadges]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:manageglobalsettings&diff=112856Capabilities/moodle/badges:manageglobalsettings2014-06-01T05:36:34Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to manage [[Badges settings|badges site administration settings]]<br />
* This capability is allowed for the default role of manager and is prevented for the role of student<br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:manageglobalsettings]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:earnbadge&diff=112830Capabilities/moodle/badges:earnbadge2014-05-29T18:16:14Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to earn [[Badges|badges]]<br />
* This capability is allowed for the default roles of student and authenticated user <br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:earnbadge]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:createbadge&diff=112751Capabilities/moodle/badges:createbadge2014-05-26T04:12:47Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to create and duplicate [[Badges|badges]]<br />
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student<br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:createbadge]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:configuremessages&diff=112738Capabilities/moodle/badges:configuremessages2014-05-21T15:03:04Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to configure [[Badges|badge]] messages<br />
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student<br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:configuremessages]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:configuredetails&diff=112650Capabilities/moodle/badges:configuredetails2014-05-16T17:30:27Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to set up/edit [[Badges|badge]] details<br />
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student<br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:configuredetails]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:configuredetails&diff=112649Capabilities/moodle/badges:configuredetails2014-05-16T17:30:04Z<p>Mits: ja link</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to set up/edit [[Badges|badge]] details<br />
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student<br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja;ケイパビリティ/moodle/バッジ:configuredetails]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Capabilities/moodle/badges:configurecriteria&diff=112599Capabilities/moodle/badges:configurecriteria2014-05-13T02:43:56Z<p>Mits: </p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to set up/edit criteria of earning a [[Badges|badge]] <br />
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student<br />
<br />
[[Category:Badges]]<br />
[[Category:Capabilities|Badges]]<br />
<br />
[[ja:ケイパビリティ/moodle/バッジ:configurecriteria]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Badges&diff=108387Badges2013-12-15T15:06:56Z<p>Mits: ja link</p>
<hr />
<div>{{Tracking progress}}<br />
Badges are a good way of celebrating achievement and showing progress. Badges may be awarded based on a variety of chosen criteria and are fully compatible with [http://openbadges.org/ Mozilla Open Badges]. Badges created in Moodle may be displayed on a user's profile or pushed to their [https://backpack.openbadges.org/ Open Badges backpack] and public badge collections in their backpack will display in their Moodle profile.<br />
<br />
There are two categories of badges:<br />
* Site badges - available to users site-wide and related to the site wide activities, like finishing a set of courses.<br />
* Course badges - available to users enrolled in the course and related to the activities that happen inside the course.<br />
<br />
[[File:BadgesIntro2.png]]<br />
<br />
*[[Managing badges]]<br />
*[[Badges settings]]<br />
*[[Using badges]]<br />
*[[Badges FAQ]]<br />
<br />
[[Category:Badges]]<br />
<br />
[[de:Auszeichnungen]]<br />
[[es:Insignias]]<br />
[[ja:バッジ]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Web_services_FAQ&diff=108186Web services FAQ2013-12-03T22:14:07Z<p>Mits: ja link</p>
<hr />
<div>{{Web services}}<br />
This document lists some popular questions from the [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum].<br />
<br />
== What is the difference between web services and MNet ==<br />
<br />
[[MNet]] is used to authenticate some users from a Moodle A site into a Moodle B site.<br />
<br />
Web services are functions that can be called by external applications (via SOAP, XML-RPC, REST or AMF).<br />
<br />
== I see the term "Web services" used in different ways, what does it mean? ==<br />
<br />
# The entire system in Moodle is referred to as the Moodle Web Service system.<br />
# A particular action (like creating a user) is known as a Web service '''function'''.<br />
# The admin can enable groups of these functions for outside use, and these are known as a "Web service".<br />
<br />
== Where is the Web Service API documented? ==<br />
<br />
Since different Moodle sites can extend or restrict the API, and the API will evolve over time, the best way to see the exact API for a particular Moodle site is to look at the automatically generated documentation.<br />
<br />
'''Full API documentation'''<br />
# Connect as admin<br />
# Go to Administration Settings block > Plugins > Web services > API documentation<br />
<br />
'''Specific documentation to a user'''<br />
# Connect as admin, enable web service, create a service and add some Moodle functions to it. Also see [[How_to_create_and_enable_a_web_service]].<br />
# connect as non admin, and access the service documentation on your [[How_to_get_a_security_key|security keys page]].<br />
<br />
== Why are there not many functions in the API? ==<br />
<br />
We have been very careful when adding new functions because we don't want to be changing the API functions once they are implemented. The ones we have in Moodle 2.0 are the most commonly requested ones (for users, courses, groups and enrolments). <br />
<br />
We will add more functions to core over time, based on contributions from the community and feature requests. See the [[:dev:Web_services_Roadmap|web service roadmap]].<br />
<br />
You can also extend the API on your own Moodle site by creating your own API functions (see next question).<br />
<br />
== How can I create a new web service function? ==<br />
<br />
The easiest and recommended way to add a web service is to write a new Moodle local plugin and to implement the web service functions there. The Moodle administrator will just need to add the plugin in Moodle (copy the files in /local/), the web service functions will be automatically added. Please read /local/readme.txt for more information about plugin development. Finally read [[:dev:Creating_a_web_service_and_a_web_service_function|how to implement a web service and a web service function]].<br />
<br />
== How can I set up a web service? ==<br />
<br />
* See the document [[How_to_create_and_enable_a_web_service| How to create and enable a web service]]. <br />
* ''Settings > Site administration > Plugins > Web services > Overview'' explains two use cases.<br />
* Finally ask questions on the [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum]<br />
<br />
== Does the Moodle SOAP server work with JAVA or .NET? ==<br />
<br />
Unfortunately the generated WSDL isn't currently compatible with JAVA or .NET. See MDL-28988 and MDL-28989 for plans to create a JAVA-compatible SOAP WSDL.<br />
<br />
== How to get a user token from an external application? ==<br />
you can generate and retrieve user tokens with the /login/token.php file => [[:dev:Creating_a_web_service_client#How_to_get_a_user_token|How to get a user token]]<br />
<br />
== What is the 'Access control exception' error ==<br />
It means that one of this admin setting has failed:<br />
* authorised user: ip restriction fails to authenticate the user (Administration > Plugins > Web services > Manage services > Authorized users > click on user full name)<br />
* authorised user: valid date is expired (Administration > Plugins > Web services > Manage services > Authorized users > click on user full name)<br />
* admin created the token: ip restriction fails to authenticate the user (Administration > Plugins > Web services > Manage tokens > check the status)<br />
* admin created the token: valid date is expired (Administration > Plugins > Web services > Manage tokens > check the status)<br />
* the user is not listed in the authorized list (Administration > Plugins > Web services > Manage services > Authorized users)<br />
* the user hasn't the required capability (Administration > Plugins > Web services > Manage services > Edit service)<br />
* site in maintenance mode<br />
* user is suspended<br />
* user is not confirmed<br />
* user is deleted<br />
* the user authentication is set to nologin (edit the user profile)<br />
* password expired (most likely happens with external authentication like LDAP)<br />
* web service disabled (Administration > Advanced features)<br />
* user doesn't have the capability to use the used web service protocol (user should have the capability 'webservice/use:xmlrpc'/'webservice/use:rest'/..., on SYSTEM context).<br />
* the user token doesn't exist<br />
* the web service function is not included in the service<br />
<br />
Since Moodle 2.2, if the administrator turns Moodle debug mode >= NORMAL, then an explicit error message will be returned.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum]<br />
<br />
[[Category:MNet]]<br />
[[Category:FAQ]]<br />
<br />
[[ja:ウェブサービスFAQ]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Security_keys&diff=107975Security keys2013-11-24T15:26:48Z<p>Mits: ja link</p>
<hr />
<div>{{RSS feeds}}<br />
A security key or token enables other systems to access Moodle securely. A security key may be used for secure RSS feeds or web services.<br />
<br />
A user can obtain a security key via ''Settings > My profile settings > Security keys'' then enter the key in an external application accessing Moodle.<br />
<br />
At any time, a user can reset their key by clicking the reset link. A new different key is automatically generate which will then need to be entered in the external application.<br />
<br />
'''Note:''' The security keys page can not generate web service keys/tokens for admins. Admins can create a token manually from the administration block: ''Settings > Site administration > Plugins > Web services > Manage tokens''.<br />
<br />
==Secure RSS feeds==<br />
<br />
Secure RSS feeds are a way you can read [[Using_RSS_feeds|forum posts, blog entries, etc]] while you are offline, and without having to log in. For example, if you want to read the posts in a forum, you usually need to log in to Moodle. But if your site administrator has [[RSS_feeds_settings|enabled RSS]], these posts are available as a feed you can subscribe to with a [http://en.wikipedia.org/wiki/Comparison_of_feed_aggregators feed reader], and you can read entries even when you don't have access to the Internet.<br />
<br />
Secure RSS feeds allow your feed reader, which usually expects feeds to be publicly available, to download material from Moodle without having to log in.<br />
<br />
Whenever you are viewing an activity that provides an RSS feed, look in the "Settings" block for a link labelled "RSS feed of posts". This link is unique to your Moodle account. Paste it into your feed reader to have it obtain new entries for you automatically.<br />
<br />
If you ever think your RSS feed token has been compromised in some way, e.g. you have lost a mobile phone that subscribed to a news forum, you can request a new one by clicking the ''Reset'' link on the ''Security Keys'' page in your Moodle profile. This will disable the old feed token and generate a new one. You can then visit the activities you wish to subscribe to and copy the URL, which will contain your new security key.<br />
<br />
[[Category:Web Services]]<br />
<br />
[[ja:セキュリティキー]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Moodle_app_FAQ&diff=106765Moodle app FAQ2013-10-06T03:02:17Z<p>Mits: ja link</p>
<hr />
<div>{{Mobile}}<br />
== How can I use Moodle on mobile devices? ==<br />
There are currently 3 main ways to use Moodle on mobile devices:<br />
<br />
* Users can open Moodle sites in their mobile web browsers.<br />
* Users can download native apps for their mobile devices.<br />
* Admins can configure their Moodle site to be Mobile-accessible through server extensions.<br />
<br />
=== Mobile Apps ===<br />
* The official [[Mobile app]] developed by Juan Leyva with support from Jerome Mouneyrac, Moodle HQ and others.<br />
* [http://www.moodletouch.com MoodleTouch] (aka ''mTouch'') for iOS, created by Ali OzGur<br />
* [http://mpage.hk/ mPage] for iOS and Android (work in progress), created by Mass Media HK<br />
* [http://codeguild.org/app/mbot/ Mbot] for Android, created by Code Guild<br />
* The [https://docs.moodle.org/23/en/Mobile_app My Moodle app] for iPhone, created by Moodle HQ (no longer being developed)<br />
* [https://market.android.com/details?id=com.ivoid.droodle Droodle] - an Android client for the Moodle 2.1 platform<br />
<br />
=== Server-side ===<br />
* [http://www.mobilemoodle.org/momo18/ MoMo] (Moodle for Mobiles) - Requires a server extension and a client app; supports most mobile OSes including Symbian.<br />
* [http://code.google.com/p/moodbile/ Moodbile] - Reference implementation of Moodle Web Services. Under development.<br />
* [http://iphone.moodle.com.au iPhone4Moodle] - Under development.<br />
<br />
==Where can I download the official Mobile app for iPhone and Android?==<br />
<br />
The app can be downloaded for free from the Google Play Store and Apple app store.<br />
<br />
==How do I get the official Mobile app to work for my Moodle site?==<br />
<br />
Firstly, your Moodle site must be using Moodle 2.4 or later.<br />
<br />
Secondly mobile web services must be enabled. See [[Enable mobile web services]] for details. <br />
<br />
==Where can I select a theme for mobile devices?==<br />
<br />
In ''Site administration > Appearance > Themes > Theme selector''.<br />
<br />
New in Moodle 2.2 onwards is the MyMobile theme especially designed for mobile devices. <br />
<br />
== I can't access my Moodle site using the app ==<br />
<br />
Notice that by default Mobile access is disabled in Moodle. The administrator of your Moodle site (which must be version 2.4 or later) must enable mobile access.<br />
<br />
Also, authentication methods like Shibboleth, CAS or LDAP/SSO are not supported currently. See https://tracker.moodle.org/browse/MOBILE-113 for more information.<br />
<br />
== Moodle Mobile app says I need 2.4 or higher ==<br />
<br />
The administrator of your Moodle site (which must be version 2.4 or later) must enable mobile access as follows:<br />
<br />
In Site administration > Plugins > Web services > Mobile tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes.<br />
<br />
Some Moodle sites uses special authentication methods like Shibboleth, CAS or LDAP/SSO that currently are not supported. See https://tracker.moodle.org/browse/MOBILE-113 for more information.<br />
<br />
== How can I log out of the Mobile app current site? ==<br />
<br />
You can add a new site in Settings -> Sites -> Add a new site and then delete your previous site using the X button near your old site name.<br />
<br />
You can also reset completely the app using Settings -> Development -> Reset the application<br />
<br />
==I can't view the courses tab as an administrator==<br />
Moodle Mobile app is not suited for administrators ad the app displays only the courses you are enrolled in (not the courses you can see by capabilities).Note that the targeted user of the app is mainly a student or teacher.If you want to see the courses as an admin, you must be enrolled in the courses. You can use a non visible role or something similar.<br />
<br />
==See also==<br />
<br />
* [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum]<br />
* Tracker area [http://tracker.moodle.org/browse/MOBILE Moodle for Mobiles]<br />
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=162872 Proposal for Supporting Mobile Themes and Browser Detection] forum discussion<br />
* An open course, about "[http://tempus-efa.proj.ac.il/moodle/course/view.php?id=102 Teaching using Mobile - Best practices]"<br />
* [http://www.moodlenews.com/mobile/ Moodle News - Mobile] - a breakdown of the mobile projects and products available<br />
<br />
[[Category:FAQ]]<br />
<br />
[[fr:Moodle pour les mobiles]]<br />
[[ja:モバイルMoodle FAQ]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Mobile_web_services&diff=106617Mobile web services2013-09-13T15:11:24Z<p>Mits: ja link</p>
<hr />
<div>{{Web services}}<br />
Moodle comes with a built-in web service designed for mobile applications. It is required to run the official [[dev:Moodle Mobile]]. Enable it only if you want people to use the official app or if a third party app explicitly requires it.<br />
<br />
== Enabling mobile web services ==<br />
<br />
A site administrator first must enable mobile web services:<br />
<br />
*In ''Settings > Site administration > Plugins > Web services > Mobile'' <br />
*Check "Enable mobile web services" and then<br />
*Click Save.<br />
<br />
That's it! No other steps required.<br />
<br />
The rest of this document explains the "behind the scenes".<br />
<br />
== What happens when the service is enabled ==<br />
Enabling the mobile web services will automatically:<br />
* enable the web services system (''Settings > Site administration > 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 (for backward compatibility with unmaintained My Moodle app)<br />
* enable the rest protocol<br />
* allow the 'webservice/xmlrpc:use' capability for authenticated user role<br />
* allow the 'webservice/rest:use' capability for authenticated user role<br />
<br />
== Disabling 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 />
** disable the rest protocol<br />
** remove the 'webservice/xmlrpc:use' capability for authenticated user role<br />
** remove the 'webservice/rest:use' capability for authenticated user role<br />
<br />
==See also==<br />
* [[Mobile app]]<br />
<br />
[[Category:Mobile]]<br />
<br />
[[de:Mobile Webservices]]<br />
[[ja:モバイルウェブサービス]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Moodle_app&diff=106465Moodle app2013-08-28T17:14:03Z<p>Mits: ja link</p>
<hr />
<div>{{Mobile}}<br />
<p class="note">'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) replaces the old mobile app for iPhone, ''My Moodle''. It requires Moodle 2.4 or above.</p><br />
<br />
== Features ==<br />
* Responsive design for phone and tablets<br />
* Upload a picture into your private file area<br />
* Record an audio file and upload it into your private file area<br />
* Send a private message to a course participant (can be done offline)<br />
* Take a personal note about a course participant (can be done offline)<br />
* Add a course participant to your phone contact<br />
* Call a course participant touching the phone number<br />
* Locate a course participant address on Google map<br />
* Download and view some resources<br />
* Quick access to your course contents<br />
* Remote translation (see bellow)<br />
* Remote layout/style customization (see below)<br />
<br />
Notice that Moodle Mobile is not a replacement of the MyMobile or Bootstrap/Simple theme. Moodle Mobile offers offline contents, camera & audio features and (in a future) Push notifications.<br />
You can use Moodle Mobile app in combination with a Mobile theme.<br />
<br />
=== Screenshots ===<br />
<br />
'''Phone'''<br />
[[File:moodlemobile01.jpg]] [[File:moodlemobile02.jpg]] [[File:moodlemobile03.jpg]] [[File:moodlemobile04.jpg]] [[File:moodlemobile05.jpg]]<br />
<br />
<br />
'''Tablet'''<br />
[[File:moodlemobileipad01.jpg]] [[File:moodlemobileipad02.jpg]]<br />
<br />
<br />
=== Translation ===<br />
<br />
The app synchronizes the translation from your Moodle site. Upload to your lang/en folder (or to your moodledata/lang/mylang folder) a valid mobile.php file containing your translation, an example can be found [http://jsfiddle.net/jleyva/9AFKN/2/embedded/result/ here]<br />
<br />
=== Style customization ===<br />
<br />
The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can apply safely any CSS, CSS2 and CSS3 style.<br />
<br />
In your Moodle installation go to Plugins / Web services / Mobile and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles. The original styles to override can be found here: https://github.com/moodlehq/moodlemobile/tree/master/css<br />
<br />
The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin)<br />
<br />
Once the user is logged in the app, there is a periodical process that retrieves your remote CSS files for applying your custom styles. <br />
<br />
Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.<br />
<br />
==Moodle sites must be enabled for the app to access them==<br />
<br />
Moodle 2.4 or above is mandatory.<br />
<br />
The administrator of your Moodle site must enable mobile access as follows:<br />
<br />
* In ''Administration > Site administration > Plugins > Web services > Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes.<br />
<br />
==Installing the mobile app==<br />
<br />
Apps are available in Google Play and also Apple Store. You can install the app directly from your Mobile device, search for "Moodle Mobile" the author/owner must be "Moodle Pty Ltd"<br />
<br />
Android: https://play.google.com/store/apps/details?id=com.moodle.moodlemobile<br />
<br />
iOS: https://itunes.apple.com/es/app/moodle-mobile/id633359593<br />
<br />
You can find the app build for other Mobile OS (not supported officially) here:<br />
<br />
https://build.phonegap.com/apps/314601/builds<br />
<br />
==Testing the app on a demo site==<br />
<br />
In the login screen, type "teacher" or "student" in the Username field and click the Add button. You will be logged automatically to a Moodle demo site for testing the app.<br />
<br />
== Cache ==<br />
If you connect to your Moodle site and update/create/delete anything, and then go to your mobile app, the content will not be displayed. You will have to wait a couple of minutes. The cache time for the app is currently 5 minutes.<br />
<br />
There are developer options for purging the cache at any time (Settings -> Development)<br />
<br />
==How to report a bug==<br />
<br />
# Log in to the Moodle Mobile tracker [https://tracker.moodle.org/browse/MOBILE https://tracker.moodle.org/browse/MOBILE] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)<br />
# ''Check whether the issue has already been reported by [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE searching all the issues]''<br />
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle Mobile' as the project<br />
# Add a detailed description then click the Create button<br />
# Attach the following files to the issue by selecting 'Attach Files' in the 'More actions' dropdown menu:<br />
#* 'Device information' - this can be found in the app (Settings -> Development -> Device info, you can send yourself this information by email using the e-mail button at the bottom)<br />
#* App Log (''Settings -> Development -> Show Log'', again you can send yourself this information by email)<br />
<br />
=== Report a bug by email ===<br />
<br />
You can send us the same report by email using ''Settings -> Report a bug''. As the report is sent by email to mobile@moodle.com, the report will take more time to be filed in the tracker.<br />
<br />
== See also ==<br />
<br />
* [[:dev:Moodle Mobile|Moodle Mobile developer docs]]<br />
* [[Mobile web services]]<br />
<br />
[[ja:モバイルアプリ]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Migration_from_MyISAM_to_InnoDB&diff=105967Migration from MyISAM to InnoDB2013-07-09T21:33:51Z<p>Mits: </p>
<hr />
<div>{{Admin tools}}<br />
This page only applies to administrators using Moodle with a MySQL database as it's about migrating the [http://dev.mysql.com/doc/refman/5.1/en/storage-engines.html MySQL storage engine].<br />
<br />
== Why migrate to InnoDB? ==<br />
<br />
InnoDB is highly recommended rather than MyISAM because it works more robustly, performs better with big sites and allows better data integrity features (transactions).<br />
<br />
It is required if you want to use Moodle's [[Web services]] (for the [[Mobile app]] for example), and possibly for more features in future. <br />
<br />
== MySQL Configuration ==<br />
Before attempting to change the table type, you should:<br />
* '''check InnoDB is enabled'''. Log in to MySQL and run the command [http://dev.mysql.com/doc/refman/5.1/en/show-engines.html SHOW ENGINES]. Make sure that support for InnoDB shows either "YES" or "DEFAULT".<br />
* '''set innodb_file_per_table if required'''. [http://dev.mysql.com/doc/refman/5.1/en/innodb-multiple-tablespaces.html This setting] can be useful for large installations, but it only affects newly created tables and can't be applied retrospectively.<br />
<br />
== Various Methods described in Moodle forums (choose one)==<br />
* run the innodb script as a webpage <nowiki>http://www.YOUR_MOODLE_SITE/admin/tool/innodb</nowiki> (v2.2.1 You should be logged into your Moodle site as an administrator - there might be timeout issues on large databases) In earlier versions of Moodle 2.x the script was at <nowiki>http://www.YOUR_MOODLE_SITE/admin/innodb.php</nowiki><br />
* use the CLI script in admin/cli/mysql_engine.php (requires access to shell, and the config.php must only have one moodle instance, but has no timeout issues) <br />
* use PHPMyAdmin entering Structure view of a table and clicking Operations tab. Look for Storage Engine parameter. This is a tedious task due to the number of tables [http://moodle.org/mod/forum/discuss.php?d=162002]<br />
* perform a database dump (e.g. mysqldump moodle_database > dump.SQL), use an editor or sed/perl/awk command to find/replace , replacing MyISAM with InnoDB. Finally, restore back in the server. (e.g. mysql < dump.SQL or equivalent). '''If using this method, be very careful to use the same file encoding on both input and output.'''<br />
* Follow the process detailed here - https://sites.google.com/site/moodlemayhem/tcea2011-moodle-server-setup-basics/moodleacidtrip<br />
* Use the php script (Tested on 1.9 and 2.0/2.2) http://noveckg.blogspot.com/2012/04/moodle-php-script-to-convert-mysql.html<br />
<br />
==See also==<br />
<br />
* [http://tag1consulting.com/MySQL_Engines_MyISAM_vs_InnoDB MySQL Engines: MyISAM vs. InnoDB] article by Tag1 Consulting<br />
* [http://code.openark.org/blog/mysql/useful-sed-awk-liners-for-mysql An easy migration of MyISAM mysqldump to InnoDB]<br />
<br />
Using Moodle forum discussions:<br />
*[http://moodle.org/mod/forum/discuss.php?d=162871 Documentation for migration from MyISAM to InnoDB]<br />
*[http://moodle.org/mod/forum/discuss.php?d=117913 New moodle.org] <br />
<br />
[[fr:Migration de MyISAM vers InnoDB]]<br />
[[de:Migration von MyISAM zu InnoDB]]<br />
[[ja:MyISAMからInnoDBへの移行]]</div>Mitshttps://docs.moodle.org/37/en/index.php?title=Migration_from_MyISAM_to_InnoDB&diff=105966Migration from MyISAM to InnoDB2013-07-09T21:33:25Z<p>Mits: ja link</p>
<hr />
<div>{{Admin tools}}<br />
This page only applies to administrators using Moodle with a MySQL database as it's about migrating the [http://dev.mysql.com/doc/refman/5.1/en/storage-engines.html MySQL storage engine].<br />
<br />
== Why migrate to InnoDB? ==<br />
<br />
InnoDB is highly recommended rather than MyISAM because it works more robustly, performs better with big sites and allows better data integrity features (transactions).<br />
<br />
It is required if you want to use Moodle's [[Web services]] (for the [[Mobile app]] for example), and possibly for more features in future. <br />
<br />
== MySQL Configuration ==<br />
Before attempting to change the table type, you should:<br />
* '''check InnoDB is enabled'''. Log in to MySQL and run the command [http://dev.mysql.com/doc/refman/5.1/en/show-engines.html SHOW ENGINES]. Make sure that support for InnoDB shows either "YES" or "DEFAULT".<br />
* '''set innodb_file_per_table if required'''. [http://dev.mysql.com/doc/refman/5.1/en/innodb-multiple-tablespaces.html This setting] can be useful for large installations, but it only affects newly created tables and can't be applied retrospectively.<br />
<br />
== Various Methods described in Moodle forums (choose one)==<br />
* run the innodb script as a webpage <nowiki>http://www.YOUR_MOODLE_SITE/admin/tool/innodb</nowiki> (v2.2.1 You should be logged into your Moodle site as an administrator - there might be timeout issues on large databases) In earlier versions of Moodle 2.x the script was at <nowiki>http://www.YOUR_MOODLE_SITE/admin/innodb.php</nowiki><br />
* use the CLI script in admin/cli/mysql_engine.php (requires access to shell, and the config.php must only have one moodle instance, but has no timeout issues) <br />
* use PHPMyAdmin entering Structure view of a table and clicking Operations tab. Look for Storage Engine parameter. This is a tedious task due to the number of tables [http://moodle.org/mod/forum/discuss.php?d=162002]<br />
* perform a database dump (e.g. mysqldump moodle_database > dump.SQL), use an editor or sed/perl/awk command to find/replace , replacing MyISAM with InnoDB. Finally, restore back in the server. (e.g. mysql < dump.SQL or equivalent). '''If using this method, be very careful to use the same file encoding on both input and output.'''<br />
* Follow the process detailed here - https://sites.google.com/site/moodlemayhem/tcea2011-moodle-server-setup-basics/moodleacidtrip<br />
* Use the php script (Tested on 1.9 and 2.0/2.2) http://noveckg.blogspot.com/2012/04/moodle-php-script-to-convert-mysql.html<br />
<br />
==See also==<br />
<br />
* [http://tag1consulting.com/MySQL_Engines_MyISAM_vs_InnoDB MySQL Engines: MyISAM vs. InnoDB] article by Tag1 Consulting<br />
* [http://code.openark.org/blog/mysql/useful-sed-awk-liners-for-mysql An easy migration of MyISAM mysqldump to InnoDB]<br />
<br />
Using Moodle forum discussions:<br />
*[http://moodle.org/mod/forum/discuss.php?d=162871 Documentation for migration from MyISAM to InnoDB]<br />
*[http://moodle.org/mod/forum/discuss.php?d=117913 New moodle.org] <br />
<br />
[[fr:Migration de MyISAM vers InnoDB]]<br />
[[de:Migration von MyISAM zu InnoDB]]<br />
[[en:MyISAMからInnoDBへの移行]]</div>Mits