MoodleDocs - User contributions [en]

Additional name fields

2016-10-27T15:01:57Z

Mits: ja link

{{Accounts}}
As well as first name and surname, the following additional name fields may be used:

* First name - phonetic
* Surname - phonetic
* Middle name
* Alternate name

==Administration settings==

===Full name format===
[[File:participants-after.png|thumb|List of users with full names displayed]]
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:

* firstname
* lastname
* firstnamephonetic
* lastnamephonetic
* middlename
* alternatename

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

*John James Doe when 'Full name format' is set to ''firstname middlename lastname'' and
*Doe John (Dough Jon) when 'Full name format' is set to ''lastname firstname (lastnamephonetic firstnamephonetic)''

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.

Note for sites upgrading from an earlier version: The 'Full name format' setting was previously in ''Site policies''.

===Alternative full name format===

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.

==User profile settings==

Users can enter additional names by editing their profile in ''Administration > My profile settings > Edit profile''.

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.

{|
| [[File:name fields in general section.png|thumb|Name fields as specified in 'Full name format']]
| [[File:additional name fields.png|thumb|Additional name fields]]
|}

[[es:Campos de nombre adicionales]]
[[de:Zusätzliche Namen]]
[[ja:追加氏名フィールド]]

Metacourse examples of use

2016-10-25T15:09:29Z

Mits: ja link

{{Enrolment}}
[[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.

==Yearly intake ==
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

Foundation Degree (2009 intake) [course category]
Course 2009 Noticeboard (uses LDAP to enrol 2009 students)
Year 1 [course category]
:Module 1 (Metacourse linked to 2009 Noticeboard_
:Module 2 (Metacourse linked to 2009 Noticeboard_
:Module 3 (Metacourse linked to 2009 Noticeboard_
:etc.

Foundation Degree (2010 intake) [course category]
Course 2010 Noticeboard (uses LDAP to enrol 2010 students)
Year 1 [course category]
Module 1 (Metacourse linked to 2010 Noticeboard_
Module 2 (Metacourse linked to 2010 Noticeboard_
Module 3 (Metacourse linked to 2010 Noticeboard_

Jerome Di Pietro in [http://moodle.org/mod/forum/discuss.php?d=39438 Teaching Strategies forum]

==1 course that sends its enrolments to 4 other courses ==
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.

[[Image:Metacourses2_en.jpg|Upsidedown Meta course Usage|center]]

For example: this would be used, when all five courses are intended to have exactly the same students.

==1 course that gets its enrolment from 4 other courses==
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.

[[Image:Metacourses1_en.jpg|Standard Meta course usage|center]]

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.

=="Merged course" / 1 course that consolidates enrollment from multiple other courses==
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.

To create a "merged course," select one existing course/section that will become the merged metacourse. In that course:

#In the Settings module, navigate to Course administration -> Users -> Enrollment methods.
#Use the Add method drop-down menu to select Course meta link.
#Use the Link course drop-down menu to choose one of the other sections/courses you wish to merge into the metacourse.
#Repeat the preceding steps as necessary for additional sections/courses.

To make it clear which course is the merged metacourse, go to that course and:

#In the Settings module, navigate to Course administration -> Edit settings.
#Change the Course full name appropriately (consider "[Course Number] - [Course Name] - [Course Date]" e.g. "CSSE101 - Introduction to Computer Science - 201210")
#Click Save changes.

To hide the unused sections/courses, go to each course and:

#In the Settings module, navigate to Course administration -> Edit settings.
#Use the Availability drop-down menu to select This course is not available for students.
#Click Save changes.

==Meta course(s) used as libraries==
One or more meta courses are used as a library of resources and activities.

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".

==Expanding the library concept==
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.

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.

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.

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.

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).

Harold Kime [http://moodle.org/mod/forum/discuss.php?d=39438 Teaching strategies forum thread].

== Common department area==
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.

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.

Randy Orwin [http://moodle.org/mod/forum/discuss.php?d=39438 Teaching strategies forum thread].

==A Diploma course sends its enrolment to meta courses==
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.

==Core subjects with fees based upon course groupings==
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.

==One course, different student fees==
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.
==Two courses, combined teaching space==
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.
==Student Support Space for degree programme==
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.

[[Category:Examples of use]]

[[ja:メタコース使用例]]

Capabilities/moodle/user:viewlastip

2016-08-11T15:05:02Z

Mits: ja link

{{Capabilities}}
*This capability allows a user to view the last IP field in [[User profiles|user profiles]].
*It is set to 'Allow' for the default role of manager only and is not set for other roles.

[[Category:Capabilities|User]]
[[Category:Site administration]]

[[es:Capabilities/moodle/user:viewlastip]]
[[de:Capabilities/moodle/user:viewlastip]]
[[ja:ケイパビリティ/moodle/user:viewlastip]]

View profile

2016-08-10T15:03:39Z

Mits: ja link

{{Accounts}}
*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.
*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).
*An administrator may additionally access and view full profiles via ''Administration>Site administration>Users>Accounts>Browse list of users''.

==Full (site) profile==

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.

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.

==Course profile==
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:

==Viewing full profiles==

By default, only admins and managers can view full profiles.

To allow everyone i.e. all authenticated users to view full profiles:

# Go to ''Administration > Site administration > Users > Permissions > Define roles''
# Click the edit icon for authenticated user
# Enter moodle/user:viewdetails in the filter box, then tick the checkbox to allow this capability
# Click the 'Save changes' button

To allow teachers to view full profiles:

# Go to ''Administration > Site administration > Users > Permissions > Define roles'' and click the 'Add a new role' button
# Give the role a name, such as 'Full profile viewer' and tick System as the context type where the role may be assigned
# Copy and paste ''moodle/user:viewdetails'' into the filter box then tick the box to allow the capability
# Click the 'Create this role' button
# Go to ''Administration > Site administration > Users > Permissions > Assign system roles'' and click 'Full profile viewer'
# 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

==Site administration settings==

An administrator can set the defaults for certain user profile fields from ''Site administration>Users>Accounts>User default preferences''.

These are:
:Email display
:Email format
:Email digest type
:Forum auto-subscribe
:Forum tracking

==See also==
*[[User profiles]]
* [[Edit profile]]
*The capability [[Capabilities/moodle/user:viewdetails|moodle/user:viewdetails]]

[[cs:Profil uživatele]]
[[de:Nutzerprofil ansehen]]
[[eu:Informazio_pertsonala]]
[[fr:Voir le profil]]
[[es:Ver perfil]]
[[ja:ユーザプロファイル]]

Roles and permissions

2016-06-13T15:06:32Z

Mits: Updated ja link

{{Managing a Moodle site}}
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.

*[[Managing roles]]
*[[Assign roles]]
*[[User policies]]
*[[Using roles]]
*[[Standard roles]]
*[[Creating custom roles]]
*[[Role export and import]]
*[[Permissions]]
*[[Override permissions]]

==See also==

*[[Roles FAQ]]

[[Category:Roles]]

[[es:Roles y permisos]]
[[eu:Rolak]]
[[fr:Rôles et permissions]]
[[ja:ロールおよびパーミッション]]
[[de:Rollen und Rechte]]

Creating custom roles

2016-04-26T15:44:05Z

Mits:

{{Roles}}
==Creating a new role==

To create a custom role:
#Go to ''Administration > Site administration > Users > Permissions > Define roles''.
#Click the "Add a new role" button.
#Select template for the new role or upload a preset
#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).
#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.
#Give the role a description (optional).
#Select an appropriate role archetype (see below for further information).
#Select the contexts where the role may be assigned e.g. 'User' for Parent role.
#Set permissions as required.
#Scroll to the top or bottom of the page and click the "Create this role" button.

{|
|-
| [[Image:addinganewrole26.png|thumb|Adding a new role and setting context types]]
| [[Image:permissions125.png|thumb|Choose "Allow" where required]]
| [[Image:permissions225.png|thumb|Extra options with "Show advanced" enabled]]
|-
|}

==Role archetypes==

A role archetype

* Is a hard-coded template for a role
* Is used during upgrades when adding defaults for new capabilities - no archetype = no new capabilities during upgrade
* Is used during when resetting a role to determine the defaults - no archetype = reset removes all capabilities

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.

The archetypes (which relate directly to the built-in roles) are:
* manager
* coursecreator
* editingteacher
* teacher
* guest
* user
* frontpage

==Creating a duplicate role==

To create a duplicate role:
#Go to ''Administration > Site administration > Users > Permissions > Define roles''.
#Click the "Add a new role" button.
#Select existing role as a template
#Give a name and set permissions for your new role; scroll down and click "Create this role".

==New role considerations==

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"

==Testing a new role==
''Administration > Switch role to''
Use the "Switch role to" link to see what another role will see in that context.

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).

''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.

==Example custom roles==

*[[Parent role|Parent]] - for providing parents/mentors/tutors with permission to view certain information about their children/mentees/tutees
*[[Demo teacher role|Demo teacher]] - for providing a demonstration teacher account with a password which can't be changed
*[[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
*[[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.
*[[Calendar editor role|Calendar editor]] - for enabling a user to add site or course events to the calendar
*[[Blogger role|Blogger]] - for limiting blogging to specific users only
*[[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
*[[Question creator role|Question creator]] - for enabling students to create questions for use in quizzes
*[[Question sharer]] - for allowing teachers to share questions between courses
*[[Course requester role]] - for restricting users who can make course requests
*[[Feedback template creator]] - for allowing teachers to save as "Public" a Feedback template.
*[[Grading forms publisher]] for allowing teachers to share Advanced grading forms with others
*[[Grading forms manager]] for allowing teachers to share Advanced grading forms with others and to delete templates others have created.
*[[Grade viewer]] for allowing users to view but not edit grades.
*[[Gallery owner role]] - may be used to provide editing capabilities (add and edit gallery images) to users on individual Lightbox Galleries.
*[[Course tagger]] - for allowing users other than managers and editing teachers to tag courses.

==Uploading users to a system role==

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

==See also==

Using Moodle forum discussions:
* [http://moodle.org/mod/forum/discuss.php?d=66782 What happens if a user has multiple roles in a course?]
* [http://moodle.org/mod/forum/discuss.php?d=90140 logged in: what role am I?]
* For more information, Ask questions and get answers on the [http://moodle.org/mod/forum/view.php?id=6826 "Roles and Permissions"] forum.

[[Category:Site administration]]

[[de:Neue Rollen anlegen]]
[[es:Crear roles personalizados]]
[[fr:Création_de_rôles_personnalisés]]
[[ja:カスタムロールの作成]]

Course meta link

2016-04-16T15:08:07Z

Mits: ja link

{{Enrolment}}
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.

==Course settings for Course meta link==

*In a course, go to ''Administration > Course administration > Users > Enrolment methods''.
*Click the dropdown menu under the enrolment methods and select 'Course meta link'.
''
[[File:enrolmentmethods29c.png|thumb|center|300px]]
*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'.
[[File:newmetalink.png|thumb|center|400px]]

*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.
*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.)

:Note: ''A teacher in a course will only be able to choose from courses they are teachers in elsewhere.''

*The users from the source (child) course will now be enrolled in the current course - see the numbers in the screenshot below:

[[File:Addedmetacourse.png]]

*When new users are enrolled to the source (child) course, they will be automatically brought into the current target (meta)course.

==Site settings for Course meta link==

The Course meta link plugin may be enabled or disabled throughout the site in ''Administration > Site administration > Plugins > Enrolments > Manage enrol plugins''.

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'')

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.

==Course meta link capabilities==

*[[Capabilities/enrol/meta:config|Configure meta enrol instances]]
*[[Capabilities/enrol/meta:selectaslinked|Select course as meta linked]]

==Enabling teachers to add meta links==

An administrator can enable teachers to add course meta links as follows:

* Go to ''Site Administration > Users > Permissions > Define Roles''
* Select the Teacher Role and click on the Edit button
* Scroll down to Course Meta Link as shown in the images below:
{| class="nicetable"
|-
|[[Image:metacoursepermissionset00.png|Permission block for allowing Teachers to link Meta courses.]]
|-
| style="text-align: center;"| The default setting is "Not Set"
|-
|[[Image:metacoursepermissionset01.png|Permission changes for editing.]]
|-
| style="text-align: center;"| When the Edit button is clicked, the panel changes to "Allow" and a checkbox
|-
|[[Image:metacoursepermissionset02.png|Setting permission to allow Teachers to link Meta courses.]]
|-
| style="text-align: center;"| Change to "Allow" by a click on the checkbox.
|}
* Scroll to the bottom of the page to save your changes.

==Examples of meta-linked courses==

{| class="nicetable"
|-
![[Image:simplemetacourse0.png|thumb|left|200px|Created - a child course and a meta course.]]
![[Image:simplemetacourse1.png|thumb|left|200px|Associating one child course and one meta course.]]
|}

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.

{| class="nicetable"
|-
![[Image:simplemetacourse2.png|thumb|left|200px|2 child courses and a meta course.]]
![[Image:simplemetacourse3.png|thumb|left|200px|1 child course and 2 meta courses.]]
![[Image:simplemetacourse4a.png|thumb|left|200px|3 child courses and 2 meta courses.]]
|}

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]].)

==See also==

Some known issues:

* MDL-34938 - Important Open Issue: Enrolment expiration date settings in child course do not properly unenrol students from the Meta-course
* MDL-27628 - A workaround in the tracker for adding more than one course at a time

How to use:
* [https://moodle.org/mod/forum/discuss.php?d=316161#p1266891 Re: Help setting up meta link metacourses with parent child courses] forum post
* [http://www.youtube.com/watch?v=hA5QcTb13no&feature=player_embedded Screencast showing how to use the Course meta link plugin to make a Metacourse]
*[[Metacourse examples of use]]

[[de:Meta-Einschreibung]]
[[es:Enlace a metacurso]]
[[ja:コースメタリンク]]

Managing repositories

2016-04-10T14:02:33Z

Mits: ja link

{{Repositories}}
==Enabling repositories==

Repositories can be enabled by an administrator in ''Site administration > Plugins > Repositories > Manage repositories''.

A repository plugin may be set to one of three possible statuses:

* "Enabled and visible" means available for use in the [[File picker]]
* "Enabled and hidden" means not available in the [[File picker]]
* "Disabled" means not available for use and if content has been added to your site you will be given the following message:
<pre>
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.
</pre>
With options to Continue, Continue and download, or Cancel.

The order in which repositories are shown in the [[File picker|file picker]] may be set using the up and down arrows.

==Vocabulary==
'''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.

'''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).

*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...
*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:
#Common instances: The instances set by Moodle administrator in these same administration pages will be available into any file picker.
#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.

==Common repository settings==

Common repository settings can be set by an administrator in ''Site administration > Plugins > Repositories > Common Repository settings'':

===Cache expire===
You can specify how long in seconds file listings are cached locally when browsing external repositories.

===Timeout settings===

If users are reporting timeouts when using repositories, an admin can increase the timeout for downloading or synchronising files.

====Get file timeout====
Timeout in seconds for downloading an external file into Moodle. Defaults to 30.
====Sync file timeout====
Timeout in seconds for syncronising the external file size. Defaults to 1.
====Sync image timeout====
Timeout in seconds for downloading an image file from external repository during syncronisation. Defaults to 3.

===Allow external links===

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.

Defaults to Yes.

===Legacy course files in new courses===

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.

See [[Legacy course files]] for more details. This should not be enabled in sites not originally upgraded from Moodle 1.9.

Defaults to No.

===Allow adding to legacy course files===

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.

==Repository capabilities==

Authenticated user role:

*[[Capabilities/repository/alfresco:view|View Alfresco repository]]
*[[Capabilities/repository/areafiles:view|View Embedded files]]
*[[Capabilities/repository/boxnet:view|View Box repository]]
*[[Capabilities/repository/dropbox:view|View a Dropbox folder]]
*[[Capabilities/repository/flickr:view|View Flickr repository]]
*[[Capabilities/repository/flickr public:view|Use Flickr public repository in file picker]]
*[[Capabilities/repository/googledocs:view|View Google Drive repository]]
*[[Capabilities/repository/merlot:view|View the Merlot repository]]
*[[Capabilities/repository/picasa:view|View Picasa repository]]
*[[Capabilities/repository/recent:view|View Recent files]]
*[[Capabilities/repository/s3:view|View Amazon s3 repository]]
*[[Capabilities/repository/skydrive:view|View Microsoft OneDrive repository]]
*[[Capabilities/repository/upload:view|Use uploading in file picker]]
*[[Capabilities/repository/url:view|Use URL downloader in file picker]]
*[[Capabilities/repository/user:view|View use Private files]]
*[[Capabilities/repository/wikimedia:view|View Wikimedia repository]]
*[[Capabilities/repository/youtube:view|Use YouTube in file picker]]

Manager, Course creator, Teacher, Non-editing teacher Roles:

*[[Capabilities/repository/coursefiles:view|Use Legacy course files repository]]
*[[Capabilities/repository/filesystem:view|View File system repository]]
*[[Capabilities/repository/local:view|View Server repository]]
*[[Capabilities/repository/webdav:view|View WebDav repository]]

[[de:Repositories verwalten]]
[[es:Gestionando repositorios]]
[[ja:リポジトリ管理]]

Repositories FAQ

2016-01-30T15:38:39Z

Mits: ja link

{{Repositories}}
==What is a repository?==
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.

==How can I enable repositories in Moodle?==

Repositories can be enabled by a site administrator in ''Administration > Site administration > Plugins > Repositories > Manage repositories''.

All enabled and visible repositories will appear in the file picker.

==How can I delete an embedded file previously added using the file picker?==

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.

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)

See also the forum thread [https://moodle.org/mod/forum/discuss.php?d=317135#p1271171 Deleting uploaded files].

==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?==

No. The file will not be available.

==How do I create a new repository on my site?==
You can create a new repository that will show up on the file picker. See [[File system repository]].

==How can I prevent students from accessing the private files repository?==
If you want to prevent students from accessing it but still wish other users to access it, follow these steps:
#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)
#Search for and set the capabilities ''moodle/user:manageownfiles'' and ''repository/user:view'' to '''prohibit.'''
#In ''Administration>Site administration>Users>Permissions>Assign system roles'', give this role to the student(s) you do not wish to access private files.
#They may be enrolled as normal students in courses, but will not be able to use their private files.

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.

==What happens if a teacher adds a file from their Private files to the course and they later leave and their account is closed?==
As long as a file is used in a context, such as a course, the file should remains available in that context.

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]''

==I cannot access a student's repositories when logged in as that student==
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.

==See also==

* [[File picker FAQ]]
* [[File system repository FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=1807 Repositories forum]

[[Category:FAQ]]

[[de:Repositories FAQ]]
[[es:Repositorios FAQ]]
[[ja:リポジトリFAQ]]

Repositories

2015-12-08T15:03:08Z

Mits:

{{Managing content}}
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.

See [[Managing repositories]] for more on configuring and managing them.

==Standard repositories==

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.

===Repositories enabled by default===

* [[Embedded files repository|Embedded files]] - Allows linking to files and images available to the user that have been added/embedded in their course activities
* [[Server files repository|Server files]] - Gives access to files elsewhere on the Moodle site (limited by a user's permissions)
* [[Recent files repository|Recent files]] - Shows the last 50 files you have uploaded, according to the context
* [[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
* [[Private files]] - Enables access to a personal storage area for every user
* [[URL downloader repository|URL downloader]] - Allows downloading of files and images from a particular URL
* [[Wikimedia repository|Wikimedia]] - Let's users search for and insert media (images) from Wikipedia

===Additional standard repositories disabled by default===
These may be enabled and set to visible or hidden by a site administrator.

* [[Alfresco repository|Alfresco]] - link to or copy files from Alfresco into Moodle
* [[Box repository|Box]] - bring files in from your Box account
* [[Legacy course files]] - use the old system from 1.9 of "course files" (pertains to sites upgraded to 1.9)
* [[Dropbox repository|Dropbox]] - link to or copy files from Dropbox
* [[EQUELLA repository|EQUELLA]] - link to files in an EQUELLA installation
* [[File_system_repository|File system]] - access files uploaded to a folder on your server (by, eg FTP)
* [[Flickr repository|Flickr]] - search for and display images from your personal Flickr account
* [[Flickr public repository|Flickr public]] - search for and display images publicly available from Flickr
* [[Google Drive repository|Google Drive]] - bring files from your Google Drive account
* [[Merlot.org repository|Merlot.org]] - bring resources in from Merlot.org
* [[Picasa web album repository|Picasa web album]] - search for and display images from your Picasa account
* [[Amazon S3 repository|Amazon S3]] - enables users to copy files from Amazon S3 storage instances
* [[Skydrive repository|OneDrive]] bring in files from your Microsoft OneDrive
* [[WebDAV repository|WebDAV]] -bring in files from external sources using WebDAV protocol
* [[Youtube videos repository|Youtube videos]] - search for and display Youtube videos

==See also==

* [[Managing repositories]]
* [[Repositories FAQ]]
* [http://www.youtube.com/watch?v=zdrdyev82bU Repositories in Moodle 2.0 video]
* [http://www.somerandomthoughts.com/blog/whitepaper-moodle-2-repositories/ Whitepaper – Moodle 2 Repositories] by Gavin Henrick
* [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
* [[:dev:Repository plugins]] developer documentation
* [http://moodle.org/plugins/browse.php?list=category&id=25 Moodle Repository Plugins database]
* [http://moodle.org/mod/forum/view.php?id=1807 Moodle Repositories discussion forum]

[[Category:Repositories]]

[[es:Repositorios]]
[[eu:Biltegiak]]
[[de:Repositories]]
[[fr:Dépôts]]
[[ja:リポジトリ]]

Unenrolment

2015-11-30T04:22:21Z

Mits: ja link

{{Course enrolment}}
Unenrolment is the process of removing users from a course. It is controlled by one or more of the following:

* The enrolment duration, which suspends students after the specified time has elapsed. Some plugins include the option to unenrol users after enrolment expiration
* 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
* 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.

In addition, users with the appropriate permission can unenrol themself from a course.

==Enrolment duration==

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''.

The enrolment duration for self enrolment can be set in ''Administration > Course administration > Users > Enrolment methods > Self enrolment''.

==Bulk unenrolment==

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.

==Unenrolment and grade history==

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.

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''.

==Suspended or Unenrolled?==

'''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.

''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"''.

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.)

'''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.

==See also==
[http://www.screencast.com/t/XtPhA6w2SM Screencast: how to bulk unenrol students from a course.]

[[Category:Site administration]]

[[eu:Desmatrikulatzea]]
[[fr:Désinscription]]
[[de:Abmelden aus einem Kurs]]
[[es:Des-inscripción]]
[[ja:登録解除]]

Import course data

2015-09-01T15:02:59Z

Mits: ja link

{{Reusing activities}}
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]].

Import course data is similar to a backup and restore process and does not include any user data.

==How to import activities or resources==

*In ''Administration > Course Administration'', click on the ''Import'' link:

[[File:Importactivities.png]]

*Select the course you wish to import from and click ''Continue''.
*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.

[[File:Importsettings.png]]

*Select the elements you want to include in the import in the Schema settings step.

[[File:Includeforimport.png]]

*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.

[[File:Includeforimportconfirm.png]]

*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.

==Examples and tips==

*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.
*''Tip:'' Groups can also be imported as a batch from a file.
* ''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.

==Import course capabilities==

* [[Capabilities/moodle/backup:backuptargetimport|Backup for import]] - allows a user to backup a course ready for importing into another course
* [[Capabilities/moodle/restore:restoretargetimport|Restore from files targeted as import]] - allows a user to import activities or resources from another course

==See also==
*[[Course backup]] & [[Course restore]] - for a similar process

[[fr:Importation]]
[[de:Kursdaten importieren]]
[[es:Importar datos de curso]]
[[ja:コースデータをインポートする]]

Capabilities/moodle/restore:restoretargetimport

2015-08-31T15:03:18Z

Mits: ja link

{{Capabilities}}
*This allows a user to [[Import course data|import activities or resources from another course]]
*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)
*This capability is allowed for the default roles of manager and teacher

==See also==

* [[Reusing activities]]

[[Category:Capabilities|Backup]]
[[Category:Backup]]

[[es:Capabilities/moodle/restore:restoretargetimport]]
[[ja:ケイパビリティ/moodle/restore:restoretargetimport]]

Capabilities/moodle/backup:backuptargetimport

2015-08-24T15:32:35Z

Mits: ja link

{{Capabilities}}
*This allows a user to backup a course ready for importing into another course
*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)
*This capability is allowed for the default roles of manager and teacher

==See also==

* [[Reusing activities]]
* [[Import course data]]

[[Category:Capabilities|Backup]]
[[Category:Backup]]

[[ja:ケイパビリティ/moodle/backup:backuptargetimport]]

SSL certificate for moodle.org

2015-06-08T15:25:35Z

Mits: ja link

{{Security}}
== Synopsis ==

'''NOTE: This has been updated as of 04/11/2013 - Moodle has moved to the GeoTrust Certificate Authority'''

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.

The SSL certificate for moodle.org has been issued by the [http://www.geotrust.com/resources/root-certificates/ GeoTrust Certificate Authority].

== Problem ==

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.

A missing CA certificate results in an error when checking for available updates and attempting to install them.

== Solutions ==

=== Update your operating system (recommended) ===

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.

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.

=== Provide the CA certificate manually ===

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.

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).

Alternatively, the direct root certificate can be found here, which you may download and install on your system.
[http://www.geotrust.com/resources/root_certificates/certificates/GeoTrust_Primary_CA.pem GeoTrust Primary CA]

[[es:SSL certificate for moodle.org]]
[[ja:moodle.orgのSSL証明書]]

History

2015-04-09T17:47:01Z

Mits: ja link

{{About Moodle}}
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.

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.

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.]

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."

[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.

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])

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.

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.

[[es:Historia]]
[[de:Historie]]
[[ja:歴史]]

Amazon EC2 Cloud Services Installation

2015-01-02T15:48:47Z

Mits: ja link

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.
The assumptions are that you have an Amazon 32 bit EC2 Linux server setup and you have ssh & http access to it.

= Install all the requirements =
From the cli as root or sudo

yum install httpd
yum install mysql-server
yum install git
yum install php
yum install php-gd
yum install php-pear
yum install php-mbstring
yum install memcached
yum install php-mcrypt
yum install php-xmlrpc
yum install php-soap
yum install php-intl
yum install php-zip
yum install php-zts
yum install php-xml

Or save some typing and copy and paste this into the terminal. It will install everything one should need for a Moodle installation:

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

= To ensure that mysql and httpd come up on boot. =

chkconfig mysqld on
chkconfig httpd on

= To ensure that utf8 is used by mysql =

edit /etc/my.cnf to read as follows (I have found that the precise lines required seem to vary as time goes on)
Back up my.cnf first with
cp /etc/my.cnf /etc/mycnf.original

Then edit to read

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_ci
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[client]
default-character-set=utf8

Check that mysql restarts with
service mysqld restart

NB edit. Later with FC16 I found that I needed to make my.cnf read

[mysqld]
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under different user or group,
# customize your systemd unit file for mysqld according to the
# instructions in http://fedoraproject.org/wiki/Systemd
character-set-server=utf8
collation-server=utf8_unicode_ci
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

= In order to make sure php is included when httpd comes up =

make sure you have a file called /etc/httpd/conf.d/php.conf whose contents are like the following

<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
</IfModule> <IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>
AddHandler php5-script .php AddType text/html .php
DirectoryIndex index.php

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))
Attached to a forum post. Perhaps a wiki buff could fix that better.

Once you have got zip.so, put it in /usr/lib/php/modules

Also you need to add

extension=zip.so

to your php.ini (in /etc)

= Create the database, database user and access rights =
run

mysql_secure_installation

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.

run
mysql -u root -p
<password you set above>

In mysql you need to

1. make a database. The name can be anything you like. I used moodledb

2. make a database user. The name can be anything you like. I used moodledbuser.

3. give that user rights to access the database from the localhost.

4. No db access is required by anyone from any other host than the localhost

** 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.

create database moodledb;
grant all privileges on moodledb.* to moodledbuser@localhost identified by '<put a pw here>';
quit

TEST the above by doing

mysql -u moodledbuser -p
<password>

If you get connected OK then you can go on and quit.

= Create moodledata folder =
mkdir /var/www/moodledata

The default root folder for apache is /var/www/html and so moodledata is not accessible from the web.
Next, give the apache user all the access rights to moodledata. This is better than chmod 777 which some users seem to do.

chown apache:apache /var/www/moodledata

= Fetch moodle =

cd /var/www/html
git clone git://git.moodle.org/moodle.git

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.

There are more sophisticated git commands, see git docs in moodle docs for more info.
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.
If you leave the owner as root, you will have to paste the suggested config.php into /var/www/html/moodle

To give apache ownership do

chown -R apache:apache /var/www/html/moodle

= Do the install =

Visit http://<your amazon host>/moodle

Well, it worked for me!

= Other Resources =

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)

[[ja:Amazon EC2クラウドサービスインストレーション]]

Badges settings

2014-06-19T15:16:21Z

Mits:

{{Badges}}

==Individual user settings==
*A user can [[Managing badges|manage badges]] from ''Navigation>My profile>My badges''.
*A user can view available course badges from ''Navigation>Current course>Badges''.

{|
|[[File:coursebadgenav1.png|thumb|Viewing course badges]]
|}

==Viewing the badges of other users==

{{New features}}

*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.

==Course administration settings==
*A teacher can add and manage badges in their course if the administrator has enabled course badges in ''Administration>Site administration>Badges settings.''
*They will see a link to badges in ''Administration>Course administration>Badges.'' where badges may be [[Managing badges| managed]] and added.

==Site administration settings==
*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.)
*The site settings for badges are located in ''Administration>Site administration>Badges>Badges settings''
===Default badge issuer===
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.
===Salt for hashing recipient's email address===
If a hash is used (numbers and letters only) then backpack services can confirm a badge earner without exposing their email address.
===Enable connection to external backpacks===
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.
===Enable course badges===
Ticking this box will allow teachers to add and manage badges in their courses.

==Badges capabilities==
There are a number of capabilities associated with badges:

*[[Capabilities/block/badges:addinstance|Add a new My latest badges block]]
*[[Capabilities/block/badges:myaddinstance|Add a new My latest badges block to My home]]
*[[Capabilities/moodle/badges:awardbadge| Award a badge]]
*[[Capabilities/moodle/badges:configurecriteria|Set up criteria for awarding a badge]]
*[[Capabilities/moodle/badges:configuredetails|Set up and edit badge details]]
*[[Capabilities/moodle/badges:configuremessages|Configure badges messages]]
*[[Capabilities/moodle/badges:createbadge| Create or duplicate badges]]
*[[Capabilities/moodle/badges:deletebadge| Delete badges]]
*[[Capabilities/moodle/badges:earnbadge|Earn badges]]
*[[Capabilities/moodle/badges:manageglobalsettings | Manage badges site administration settings]]
*[[Capabilities/moodle/badges:manageownbadges|View and manage your own earned badges]]
*[[Capabilities/moodle/badges:viewawarded|View users who earned a specific badge without being able to award a badge]]
*[[Capabilities/moodle/badges:viewbadges |View badges without earning them]]
*[[Capabilities/moodle/badges:viewotherbadges|View public badges in other users' profiles]]

[[de:Auszeichnungen konfigurieren]]
[[es:Configuraciones de insignias]]
[[ja:バッジ設定]]

Badges settings

2014-06-19T15:15:57Z

Mits: ja link

Capabilities/moodle/badges:viewotherbadges

2014-06-14T15:11:32Z

Mits: ja link

{{Capabilities}}
* This allows a user to view public [[Badges|badges]] in other users' profiles
* This capability is allowed for the default role of authenticated user

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:viewotherbadges]]

Capabilities/moodle/badges:viewbadges

2014-06-10T15:25:03Z

Mits: ja link

{{Capabilities}}
* This allows a user to view [[Badges|badges]] without earning them
* This capability is allowed for the default roles of manager, student and authenticated user

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:viewbadges]]

Capabilities/moodle/badges:viewawarded

2014-06-08T07:24:37Z

Mits: ja link

{{Capabilities}}
* This allows a user to view users who earned a specific [[Badges|badge]] without being able to award a badge
* This capability is allowed for the default roles of manager, teacher and non-editing teacher

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:viewawarded]]

Capabilities/moodle/badges:manageownbadges

2014-06-03T21:29:23Z

Mits: ja link

{{Capabilities}}
* This allows a user to view and manage their own earned [[Badges|badges]]
* This capability is allowed for the default role of authenticated user

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:manageownbadges]]

Capabilities/moodle/badges:manageglobalsettings

2014-06-01T05:36:34Z

Mits: ja link

{{Capabilities}}
* This allows a user to manage [[Badges settings|badges site administration settings]]
* This capability is allowed for the default role of manager and is prevented for the role of student

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:manageglobalsettings]]

Capabilities/moodle/badges:earnbadge

2014-05-29T18:16:14Z

Mits: ja link

{{Capabilities}}
* This allows a user to earn [[Badges|badges]]
* This capability is allowed for the default roles of student and authenticated user

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:earnbadge]]

Capabilities/moodle/badges:createbadge

2014-05-26T04:12:47Z

Mits: ja link

{{Capabilities}}
* This allows a user to create and duplicate [[Badges|badges]]
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:createbadge]]

Capabilities/moodle/badges:configuremessages

2014-05-21T15:03:04Z

Mits: ja link

{{Capabilities}}
* This allows a user to configure [[Badges|badge]] messages
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:configuremessages]]

Capabilities/moodle/badges:configuredetails

2014-05-16T17:30:27Z

Mits: ja link

{{Capabilities}}
* This allows a user to set up/edit [[Badges|badge]] details
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:configuredetails]]

Capabilities/moodle/badges:configuredetails

2014-05-16T17:30:04Z

Mits: ja link

{{Capabilities}}
* This allows a user to set up/edit [[Badges|badge]] details
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja;ケイパビリティ/moodle/バッジ:configuredetails]]

Capabilities/moodle/badges:configurecriteria

2014-05-13T02:43:56Z

Mits:

{{Capabilities}}
* This allows a user to set up/edit criteria of earning a [[Badges|badge]]
* This capability is allowed for the default roles of manager, course creator and teacher, and is prevented for the role of student

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:configurecriteria]]

Badges

2013-12-15T15:06:56Z

Mits: ja link

{{Tracking progress}}
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.

There are two categories of badges:
* Site badges - available to users site-wide and related to the site wide activities, like finishing a set of courses.
* Course badges - available to users enrolled in the course and related to the activities that happen inside the course.

[[File:BadgesIntro2.png]]

*[[Managing badges]]
*[[Badges settings]]
*[[Using badges]]
*[[Badges FAQ]]

[[Category:Badges]]

[[de:Auszeichnungen]]
[[es:Insignias]]
[[ja:バッジ]]

Web services FAQ

2013-12-03T22:14:07Z

Mits: ja link

{{Web services}}
This document lists some popular questions from the [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum].

== What is the difference between web services and MNet ==

[[MNet]] is used to authenticate some users from a Moodle A site into a Moodle B site.

Web services are functions that can be called by external applications (via SOAP, XML-RPC, REST or AMF).

== I see the term "Web services" used in different ways, what does it mean? ==

# The entire system in Moodle is referred to as the Moodle Web Service system.
# A particular action (like creating a user) is known as a Web service '''function'''.
# The admin can enable groups of these functions for outside use, and these are known as a "Web service".

== Where is the Web Service API documented? ==

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.

'''Full API documentation'''
# Connect as admin
# Go to Administration Settings block > Plugins > Web services > API documentation

'''Specific documentation to a user'''
# 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]].
# connect as non admin, and access the service documentation on your [[How_to_get_a_security_key|security keys page]].

== Why are there not many functions in the API? ==

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).

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]].

You can also extend the API on your own Moodle site by creating your own API functions (see next question).

== How can I create a new web service function? ==

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]].

== How can I set up a web service? ==

* See the document [[How_to_create_and_enable_a_web_service| How to create and enable a web service]].
* ''Settings > Site administration > Plugins > Web services > Overview'' explains two use cases.
* Finally ask questions on the [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum]

== Does the Moodle SOAP server work with JAVA or .NET? ==

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.

== How to get a user token from an external application? ==
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]]

== What is the 'Access control exception' error ==
It means that one of this admin setting has failed:
* authorised user: ip restriction fails to authenticate the user (Administration > Plugins > Web services > Manage services > Authorized users > click on user full name)
* authorised user: valid date is expired (Administration > Plugins > Web services > Manage services > Authorized users > click on user full name)
* admin created the token: ip restriction fails to authenticate the user (Administration > Plugins > Web services > Manage tokens > check the status)
* admin created the token: valid date is expired (Administration > Plugins > Web services > Manage tokens > check the status)
* the user is not listed in the authorized list (Administration > Plugins > Web services > Manage services > Authorized users)
* the user hasn't the required capability (Administration > Plugins > Web services > Manage services > Edit service)
* site in maintenance mode
* user is suspended
* user is not confirmed
* user is deleted
* the user authentication is set to nologin (edit the user profile)
* password expired (most likely happens with external authentication like LDAP)
* web service disabled (Administration > Advanced features)
* 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).
* the user token doesn't exist
* the web service function is not included in the service

Since Moodle 2.2, if the administrator turns Moodle debug mode >= NORMAL, then an explicit error message will be returned.

==See also==

* Using Moodle [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum]

[[Category:MNet]]
[[Category:FAQ]]

[[ja:ウェブサービスFAQ]]

Security keys

2013-11-24T15:26:48Z

Mits: ja link

{{RSS feeds}}
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.

A user can obtain a security key via ''Settings > My profile settings > Security keys'' then enter the key in an external application accessing Moodle.

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.

'''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''.

==Secure RSS feeds==

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.

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.

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.

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.

[[Category:Web Services]]

[[ja:セキュリティキー]]

Moodle Mobile FAQ

2013-10-06T03:02:17Z

Mits: ja link

{{Mobile}}
== How can I use Moodle on mobile devices? ==
There are currently 3 main ways to use Moodle on mobile devices:

* Users can open Moodle sites in their mobile web browsers.
* Users can download native apps for their mobile devices.
* Admins can configure their Moodle site to be Mobile-accessible through server extensions.

=== Mobile Apps ===
* The official [[Mobile app]] developed by Juan Leyva with support from Jerome Mouneyrac, Moodle HQ and others.
* [http://www.moodletouch.com MoodleTouch] (aka ''mTouch'') for iOS, created by Ali OzGur
* [http://mpage.hk/ mPage] for iOS and Android (work in progress), created by Mass Media HK
* [http://codeguild.org/app/mbot/ Mbot] for Android, created by Code Guild
* The [https://docs.moodle.org/23/en/Mobile_app My Moodle app] for iPhone, created by Moodle HQ (no longer being developed)
* [https://market.android.com/details?id=com.ivoid.droodle Droodle] - an Android client for the Moodle 2.1 platform

=== Server-side ===
* [http://www.mobilemoodle.org/momo18/ MoMo] (Moodle for Mobiles) - Requires a server extension and a client app; supports most mobile OSes including Symbian.
* [http://code.google.com/p/moodbile/ Moodbile] - Reference implementation of Moodle Web Services. Under development.
* [http://iphone.moodle.com.au iPhone4Moodle] - Under development.

==Where can I download the official Mobile app for iPhone and Android?==

The app can be downloaded for free from the Google Play Store and Apple app store.

==How do I get the official Mobile app to work for my Moodle site?==

Firstly, your Moodle site must be using Moodle 2.4 or later.

Secondly mobile web services must be enabled. See [[Enable mobile web services]] for details.

==Where can I select a theme for mobile devices?==

In ''Site administration > Appearance > Themes > Theme selector''.

New in Moodle 2.2 onwards is the MyMobile theme especially designed for mobile devices.

== I can't access my Moodle site using the app ==

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.

Also, authentication methods like Shibboleth, CAS or LDAP/SSO are not supported currently. See https://tracker.moodle.org/browse/MOBILE-113 for more information.

== Moodle Mobile app says I need 2.4 or higher ==

The administrator of your Moodle site (which must be version 2.4 or later) must enable mobile access as follows:

In Site administration > Plugins > Web services > Mobile tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes.

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.

== How can I log out of the Mobile app current site? ==

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.

You can also reset completely the app using Settings -> Development -> Reset the application

==I can't view the courses tab as an administrator==
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.

==See also==

* [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum]
* Tracker area [http://tracker.moodle.org/browse/MOBILE Moodle for Mobiles]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=162872 Proposal for Supporting Mobile Themes and Browser Detection] forum discussion
* An open course, about "[http://tempus-efa.proj.ac.il/moodle/course/view.php?id=102 Teaching using Mobile - Best practices]"
* [http://www.moodlenews.com/mobile/ Moodle News - Mobile] - a breakdown of the mobile projects and products available

[[Category:FAQ]]

[[fr:Moodle pour les mobiles]]
[[ja:モバイルMoodle FAQ]]

Mobile web services

2013-09-13T15:11:24Z

Mits: ja link

{{Web services}}
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.

== Enabling mobile web services ==

A site administrator first must enable mobile web services:

*In ''Settings > Site administration > Plugins > Web services > Mobile''
*Check "Enable mobile web services" and then
*Click Save.

That's it! No other steps required.

The rest of this document explains the "behind the scenes".

== What happens when the service is enabled ==
Enabling the mobile web services will automatically:
* enable the web services system (''Settings > Site administration > Advanced features'')
* enable the built-in external service called 'Mobile web services' - you should see this new mobile service listed as enabled
* enable the xml-rpc protocol (for backward compatibility with unmaintained My Moodle app)
* enable the rest protocol
* allow the 'webservice/xmlrpc:use' capability for authenticated user role
* allow the 'webservice/rest:use' capability for authenticated user role

== Disabling mobile web services ==
When you uncheck 'Enable mobile web services', it will automatically:
* disable the external service called 'Mobile web services'.
*if 'Mobile web services' was the only external service enabled:
** disable the web services system
** disable the xml-rpc protocol
** disable the rest protocol
** remove the 'webservice/xmlrpc:use' capability for authenticated user role
** remove the 'webservice/rest:use' capability for authenticated user role

==See also==
* [[Mobile app]]

[[Category:Mobile]]

[[de:Mobile Webservices]]
[[ja:モバイルウェブサービス]]

Moodle Mobile

2013-08-28T17:14:03Z

Mits: ja link

{{Mobile}}
<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>

== Features ==
* Responsive design for phone and tablets
* Upload a picture into your private file area
* Record an audio file and upload it into your private file area
* Send a private message to a course participant (can be done offline)
* Take a personal note about a course participant (can be done offline)
* Add a course participant to your phone contact
* Call a course participant touching the phone number
* Locate a course participant address on Google map
* Download and view some resources
* Quick access to your course contents
* Remote translation (see bellow)
* Remote layout/style customization (see below)

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.
You can use Moodle Mobile app in combination with a Mobile theme.

=== Screenshots ===

'''Phone'''
[[File:moodlemobile01.jpg]] [[File:moodlemobile02.jpg]] [[File:moodlemobile03.jpg]] [[File:moodlemobile04.jpg]] [[File:moodlemobile05.jpg]]

'''Tablet'''
[[File:moodlemobileipad01.jpg]] [[File:moodlemobileipad02.jpg]]

=== Translation ===

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]

=== Style customization ===

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.

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

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin)

Once the user is logged in the app, there is a periodical process that retrieves your remote CSS files for applying your custom styles.

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.

==Moodle sites must be enabled for the app to access them==

Moodle 2.4 or above is mandatory.

The administrator of your Moodle site must enable mobile access as follows:

* In ''Administration > Site administration > Plugins > Web services > Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes.

==Installing the mobile app==

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"

Android: https://play.google.com/store/apps/details?id=com.moodle.moodlemobile

iOS: https://itunes.apple.com/es/app/moodle-mobile/id633359593

You can find the app build for other Mobile OS (not supported officially) here:

https://build.phonegap.com/apps/314601/builds

==Testing the app on a demo site==

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.

== Cache ==
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.

There are developer options for purging the cache at any time (Settings -> Development)

==How to report a bug==

# 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)
# ''Check whether the issue has already been reported by [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE searching all the issues]''
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle Mobile' as the project
# Add a detailed description then click the Create button
# Attach the following files to the issue by selecting 'Attach Files' in the 'More actions' dropdown menu:
#* '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)
#* App Log (''Settings -> Development -> Show Log'', again you can send yourself this information by email)

=== Report a bug by email ===

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.

== See also ==

* [[:dev:Moodle Mobile|Moodle Mobile developer docs]]
* [[Mobile web services]]

[[ja:モバイルアプリ]]

Migration from MyISAM to InnoDB

2013-07-09T21:33:51Z

Mits:

{{Admin tools}}
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].

== Why migrate to InnoDB? ==

InnoDB is highly recommended rather than MyISAM because it works more robustly, performs better with big sites and allows better data integrity features (transactions).

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.

== MySQL Configuration ==
Before attempting to change the table type, you should:
* '''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".
* '''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.

== Various Methods described in Moodle forums (choose one)==
* 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>
* 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)
* 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]
* 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.'''
* Follow the process detailed here - https://sites.google.com/site/moodlemayhem/tcea2011-moodle-server-setup-basics/moodleacidtrip
* 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

==See also==

* [http://tag1consulting.com/MySQL_Engines_MyISAM_vs_InnoDB MySQL Engines: MyISAM vs. InnoDB] article by Tag1 Consulting
* [http://code.openark.org/blog/mysql/useful-sed-awk-liners-for-mysql An easy migration of MyISAM mysqldump to InnoDB]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=162871 Documentation for migration from MyISAM to InnoDB]
*[http://moodle.org/mod/forum/discuss.php?d=117913 New moodle.org]

[[fr:Migration de MyISAM vers InnoDB]]
[[de:Migration von MyISAM zu InnoDB]]
[[ja:MyISAMからInnoDBへの移行]]

Migration from MyISAM to InnoDB

2013-07-09T21:33:25Z

Mits: ja link

Site notifications

2013-06-19T15:50:45Z

Mits: ja link

{{Security}}
==Update notifications==

An administrator can configure update notifications for both Moodle core code and any contributed plugins installed on the site in ''Settings > Site Administration > Server > Update notifications''. See [[Available update notifications]] for more details.

==Login failure notifications==

An administrator can set up login failure notification in ''Settings > Site Administration > Security > Notifications''.

===Display login failures to===

Set this to administrators to be warned of anyone attempting to steal student or teacher logins. When set, a link stating the number of failed logins appears in the top right corner of the page when an administrator logs in. Click the link to access the login error page.

===Email login failures===

If you're concerned about login failures, you can set up email notification for administrators or any/all users who can change the site configuration.

===Threshold for email notifications===

This sets the number of failed logins for a given user from a single computer that will trigger notification.

Note: The number of failed login attempts that result in account lockout may be set in ''Administration > Site administration > Security > Site policies'' (new in 2.5).

==Other notifications==

The version of Moodle used may be found in ''Settings > Site administration > Notifications''.

Other notifications listed on the page may include

* [[Upgrade warnings|"Alpha" development code warning]]
* [[Cron]] not run for at least 24 hours
* Database tables are using MyISAM database engine - see [[Migration from MyISAM to InnoDB]] for advice on what to do
* "Enabling the PHP setting display_errors is not recommended on production sites because some error messages may reveal sensitive information about your server." What you do about this is not explained. Making a php.ini file with "display_errors = off;" in it in the folder "with the script" (?) is one suggestion found by googling, but that may depend on your server.
* Site not yet [[Site registration|registered]]

==See also==

* [[:dev:Available update notifications|Available update notifications developer documentation]]

[[es:Notificaciones]]
[[eu:Jakinarazpenak]]
[[fr:Notifications]]
[[de:Benachrichtigungen]]
[[ja:通知]]

Upgrade overview

2013-03-26T17:46:42Z

Mits: ja link

<div class="navtrail">[[Main page]] ► [[Installation]] ► [[{{PAGENAME}}]]</div>
<span class="small-info-right">''Moodle 2.4<br />available now!''</span>
Start enjoying the cool features of the latest and greatest version of Moodle in four easy steps...
__NOTOC__
==Step 1: Make sure that your server can run Moodle 2.2==
[[File:checklist.png|right]]
(Note: You need to upgrade to Moodle 2.2 before upgrading to 2.4.)

Go to ''Settings > Site administration > Server > Environment''

Status OK for everything? Great! Go to step 2...

Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.

==Step 2: Be prepared!==
[[File:backup.png|right]]
As usual with any large upgrade, you should always be prepared to "roll back" if there's an issue with your data or some custom code you've added.

; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.

; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].

==Step 3: Replace your Moodle code==

At this point you can replace the Moodle code on your server with the version you downloaded.

; Check plugins: Any plugins you have installed will also to be replaced with a version for your new Moodle version. If there is not yet an updated version of the plugin available, it will need to be uninstalled before upgrading your site.

==Step 4: Perform the upgrade!==
[[File:gears.png|right]]
Trigger the upgrade by [[Upgrading#Finishing_the_upgrade|visiting the admin page]].

If you have a large site this may take hours, so we recommend [[Administration_via_command_line#Upgrading_via_command_line|upgrading via command line]].

==How did you go?==

; Yes - it worked!: Great! Repeat the process for Moodle 2.4, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!
; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.

==See also==

* [[Upgrading]] for full details of the process
* [[Upgrading FAQ]]

[[Category:Installation]]

[[de:Aktualisierung in Kürze]]
[[es:Visión general de actualización]]
[[ja:アップグレード概要]]

Gradebook

2013-03-06T15:05:55Z

Mits: ja link

{{Grades}}
All the grades for each student in a course can be found in the course gradebook, or 'Grader report' in ''Settings > Course administration > Grades''.

The grader report collects [[Grade_items|items]] that have been graded from the various parts of Moodle that are assessed, and allows you to view and change them as well as sort them out into [[Grade_categories|categories]] and calculate totals in various ways. When you add an assessed item in a Moodle course, the gradebook automatically creates space for the grades it will produce and also adds the grades themselves as they are generated, either by the system or by you.

The grades displayed are initially displayed as the raw marks from the assessments themselves, so will depend on how you set those up e.g. an essay out of 36 will appear as however many raw marks that student got, not a percentage (although this can be changed later, see below).

Note that various default options for the gradebook are set at system level by the administrator and can be marked as being overridable by you, or fixed. This means that the options will not always be set up the same way for every user when they see the grader report for the first time.

==Display==

Along the top of the grader report are several rows: first the course, then the category, then the columns for each graded activity (for example: Assignment, Quiz, Lesson). Any activities settings which were left "uncategorised" will appear in the general category which is named after the course by default (any category name can be changed).

You can add a row showing the range of possible scores by selecting 'Show ranges' in 'My report preferences.

There are three ways that the categories can be displayed:

* Grades only - without the category totals column
* Collapsed - Category total column only
* Full view - grades and the aggregates (the totals column for the category)

Each section has a small icon immediately to the right of its name. Clicking this will cycle through these display modes for that category. + goes to grades only view, o goes to full view and - goes to collapsed view.

[[Image:Grades grader report with categories 1.png]]

===Highlighting rows and columns===

When your gradebook starts to grow, it can be hard to keep track of which student and which assignment a cell refers to. Highlighting solves that.
* Clicking on empty space in the cell that contains the students name will toggle the highlighting of that entire row
* Clicking on empty space in the cell at the top of each column will toggle highlighting of the entire column
(Note: this requires Javascript to be enabled in your browser.)

===Sorting by columns===

You can sort by any column. Click the [[Image:Move.gif]] symbol near the top of a column to sort by that column. This will change the symbol to a single down arrow. Clicking again will sort lowest-to-highest, changing the symbol to an up arrow. The arrows will toggle between these two states until you click on a different column.

The student name columns do not have the [[Image:Move.gif]] symbol. Clicking on either the first or last name will cause the report to sort.

{| style="width:75%; border="0"
|[[Image:Grade Report unsorted column1.png|frame|center|Unsorted]]
||[[Image:Grade Report sorted column2.png|frame|center|Sorted]]
||[[Image:Grade Report unsorted name1.png|frame|center|Unsorted]]
||[[Image:Grade Report sorted lastname3.png|frame|center|Sorted ]]
|-
|}

===Highlighting scores that are either adequate or unacceptable in red and green===

Turn editing on and click on the edit icon in the controls cell at the top of the column. You can then (maybe need to click 'show advanced') see the option to enter a 'grade to pass'. Once set, any grades falling above this will be highlighted in green and any below will be highlighted in red.

Note that the highlighting will not show if the Grader report is viewed in the editing mode.

===Horizontal scrollbar===

A horizontal scrollbar enables teachers to scroll grades in the grader report. (Note that this feature is not available for IE6 users or for users who have have the screenreader setting in their profile set to Yes.)

[[Image:Gradebook horizontal scrollbar.png|thumb|Horizontal scrollbar]]

===Mouse-over tooltips===

Each grade cell in the table has a tooltip indicating the user and grade item to which the grade belongs.

===Filtering the gradebook by groups===
If you change the course settings Group mode to Visible groups or Separate groups a drop-down menu will appear in the gradebook to allow you to filter your students by groups.

==Editing==

Note: Editing anything in the gradebook refers to editing the grades '''only''' and none of the available operations bear any relationship to editing the main course page i.e. the appearance of your course page cannot be influenced by anything you do in the gradebook. The "Turn editing on" button functions separately from the main course one, so editing can be on in the gradebook, but simultaneously off when you switch back to course view. This is because editing grades and editing the course page are separate capabilities. Roles such as 'non-editing teacher' may only have one or the other.

===Altering the grades===
You can click "Turn editing on" at the top right to show an edit icon next to each grade. Clicking on the icon will bring up the editing screen for that grade which will allow you to set the grade, its written feedback and a number of other attributes.

Alternatively, you can choose "Quick grading" and "Quick feedback" in 'My preferences' to make the report appear with editable boxes containing each grade, so you can change many at once. This capability can be a real time saver, but make sure to save at reasonable intervals lest a pageful of changes be lost.

Note: If you make changes here, they are then shown highlighted to indicate grades which have been manually changed.

===Hiding columns or individual grades===
Turning on editing then clicking the "Show show/hide icons" link will give you the familiar show/hide eye icon next to each grade and at the top of each column. For more information, read about [[Grade_hiding|grade hiding]].

===Recalculating===
If you change any part of an assessment e.g. alter the maximum grade for one of the questions in a quiz, you may find that the columns do not yet reflect the change you have made. Click '''Turn editing on''' twice to force the gradebook to re-check.

==Gradebook capabilities==

There is just one gradebook capability, [[Capabilities/gradereport/grader:view|View the grader report]], which is allowed for the default roles of manager, teacher and non-editing teacher.

==See also==

*[http://www.youtube.com/watch?v=5hrLNbifiGQ Video explaining the different gradebook reports]

[[de:Bewertungen]]
[[fr:Carnet de notes]]
[[ja:評定表]]

Groups course settings

2013-02-13T15:20:32Z

Mits: ja link

{{Course admin}}
Enabling [[Groups]] will allow the teacher to create sets of students. By default, the groups settings are turned off in a course. Groups can be used in the [[Context]] of a course or in a specific course activity.

Most of this information is also repeated in the [[Course settings]] page under [[Course settings#Groups|Groups]] and on the [[Groups]] page.

==Group mode==
This settings defines the default [[Groups|group]] mode for all activities in the course, by a pull down menu. The group setting can affect what users see in the course [[Participants]] list. There are 3 group mode choices: Visible, Separate and No groups.

:''TIP:'' When force mode is set to no, group mode merely acts as a default setting for each new activity. However, when force mode is set to yes, then the course group mode overrides all activity group settings. There are some examples of the two force settings below.

:The course group mode is useful when the teacher is going to add several activities with the same group setting. In a course with many activities that have different group mode settings, a teacher might enter them in batches, using the group course setting to save time.

===Visible groups===
Each group works in their own group, but can also see other groups. The other groups' work is read-only.
[[Image:forceNo.png|frame|center|Group course settings, with result in visible mode not forced]]

:The above example shows the group section in the course settings and part of a course. The teacher wants the default activity group setting to be "visible" but has not "forced" this preference on all activities. This is show by the two forum activities, where one shows the visible group icon and the other the separate group icon.

===Separate groups===
Each group can only see their own group, others are invisible.

===No groups===
There are no sub groups, everyone is part of one big community. They can see other peoples activity and interact with them.

==Force==
A "force" group mode at the course-level, will override any individual activity "group mode" setting, with the one set in the course.

:In the course example show above in "group mode" we had two activities, one set for visible group mode and the other set for separate group and the course Force was set to "No". In the example below, the teacher changed the settings in the same course. The teacher put the course settings on visible group mode and said "yes" to the Force mode.

[[Image:[[Image:forceYes.png|frame|center|Force turned on, notice the group icons show the override]]

:''TIP:''The force setting is useful when the teacher wants to import activities from another course and not have to change each activities group settings.

==Default grouping==
Allows the teacher to set a default group.

:''TIP:'' To see other groups in this list, you will have to go to the Course administration>Groups tab and use the [[Auto-create groups]] button. One you set the auto create fields, then a group will appear under this heading in addition to "Default".

==Using groups in course or activity==

A group or grouping can be used on two levels:

* '''Course level''' - the group mode defined at the course level is the default mode for all activities defined within that course. Changing the force mode to yes, will override any individual activity group mode settings.

* '''Activity level''' - each activity that supports groups can also have its own group mode defined. The course setting under Groups must have "Force" set to "No" to allow individual activities to allow their own group settings to work.

==Tips and Tricks==

*Groups icon not showing? - remember to select something other than "none" in the Group mode.

==See Also==

*[[Groups]] for more information about how to setup and use this feature.

*[[Groups FAQ]] for some usual questions and answers about Groups

[[Category:Groups]]

[[ja:グループコース設定]]

Participants

2013-01-13T15:19:48Z

Mits: ja link

Participants are the teachers and students who are part of a course. The list of participants can be seen by clicking the ''Participants'' link in the [[Navigation block]]

[[File:mycourses.png]]

If it has been added, the'' Participants'' link in the [[People block]] will also show course participants.

The participants list may be restricted to display:
* Members of a particular [[Groups|group]]
* Users inactive for more than a particular period of time
* Users with a particular role, such as teacher

Teachers (or other users with appropriate permissions) may select particular users then perform any of the following actions:
* Send [[Messaging|message]]
* Add a [[Notes|new note]]
* Add a common note (for adding the same note to more than one user)

==See also==
''Settings>Course Administration>Users>Enrolled users'' for options to assign roles to participants or or unenrol them
[[fr:Participants]]
[[ca:Participants]]
[[de:Teilnehmerliste]]
[[ja:参加者]]

Common module settings

2012-12-18T20:54:12Z

Mits: ja link

{{Activities}}
On the settings page for many modules, there is a section called "Common module settings". This refers to settings that are common to many modules.

==Example - assignment activity==
Assignment activity has two items and a point of information in the common module setting. There is more information about [[Groups course settings]] and [[Groups]] for all activities.

=== Group mode - assignment activity===
When course group mode is turned on and force is set to no, the [[Groups|group mode]] can be one of three levels on the assignment activity level: no groups, separate groups or visible groups.

;No groups
:There are no groups and all students submit their assignments in one Assignment area

;Separate groups
:Students submit their assignments within a separate Group based submission area and teachers/trainers can sort submissions by Group or view All Participants.

;Visible groups
:All students submits their assignment within a single Assignment area but may choose which Group to associate their submission with before uploading. Teachers/trainers can sort submissions by Group or view All Participants.

=== Visible - assignment activity ===
Choose whether to Show or Hide the assignment

=== ID number - assignment activity===

Setting an ID number provides a way of identifying the assignment for grade calculation purposes. If the activity is not included in any grade calculation then the ID number field can be left blank.

The ID number can also be set on the edit grade calculation page in the [[Gradebook]], though it can only be edited on the update activity page of the module in a course context.

The ID number may also be used in integrations with other software.

==Common module settings are used in==
*[[Adding/editing an assignment]]
*[[Adding/editing a chat]]
*[[Adding/editing a choice]]
*[[Adding/editing a database]]
*[[Adding/editing a forum]]
*[[Adding/editing a glossary]]
*[[Adding/editing a lesson]]
*[[SCORM module]]
*[[Adding/editing a survey]] does not mention at all
*[[Adding/editing a quiz]]
*[[Adding/editing a wiki]]
*[[Groupings]]
*[[Grade export]]

==See also==

* [[Grade calculations#Assigning ID numbers|Assigning module ID numbers for Grade calculations]]

[[ja:共通モジュール設定]]

Using Lesson

2012-12-05T21:09:08Z

Mits: ja link

{{Lesson}}
This page outlines how students and teachers interact with Moodle lessons once they have been created. For details on how to set up and then organise a lesson, see [[Lesson settings]] and [[Building Lesson]]

== What the student sees ==
*A student clicking on a Lesson will see an introductory page with one or more buttons which they choose from to select the path they wish to take.
*The display may vary according to how the teacher has set up the lesson in [[Lesson settings]]. For example; there may or may not be a list of pages down the side; there may or may not be an ongoing score.
*Students progress through the lesson with either content pages (of information, which is not graded) or various types of question pages(which may be graded) When a question page is used, the following page gives the answer and feedback if offered:
[[File:studentviewoflesson.png]]
*The lesson is ended when the student has met the criteria set by the teacher. This could be answering a certain number of questions correctly, accessing a certain number of pages with content (text, audio or video) or following a certain navigational path. A final page appears where the student can check their score, if applicable, and return to the main course page.
[[File:studentendoflesson.png]]

==What the teacher sees==
*A teacher clicking on a lesson will see tabs at the top offering them the chance to preview, edit, view reports or grade essays in the lesson:
[[File:teacherviewoflesson.png]]
===Preview===
*The lesson opens up in preview mode for the teacher. However, it will not show the score unless the teacher switches their role to a student.
===Edit===
*The Edit tab allows teachers to alter the lesson once it has been set up. There are two views - Collapsed and Expanded. See [[Building Lesson]] for more details on editing the lesson.

===Reports===
*The reports tab shows the performance of students taking the lesson. There is a general "Overview" and a "Detailed Statistics" tab.
====Overview====
[[File:lessonreportsoverview1.png]]

By clicking on the specific attempt, the teacher can view the student's answers to specific questions. It is also possible to delete a student attempt by checking the attempt and using the pull down menu to change "Choose" to "Delete".

*Below the "Overview" can also be seen general statistics: Average score, Average time, High score, Low score, High time, Low time.
[[File:lessonreportstatistics.png]]

====Detailed Statistics====
More detailed reports on individual questions are available from this tab, as in the following screenshot:

[[File:lessonreportsdetailed.png]]

====Grade essays====
*Any essay questions which have been set in the lesson can be accessed and graded here.

==Grading lessons==
*Note that for a lesson to be graded, it must have at least one question where a student can receive a score and the lesson can not be a practice lesson. Grades are calculated when the student has completed a lesson. Grades are kept for every student attempt.

==Understanding Flow control==
*''Settings > Lesson administration > Edit settings > Flow control group''

*Here are some examples to help you understand the Lesson flow control settings. Please note:
*"Allow student review" setting applies to the review of a whole Lesson, whereas
*"Provide option to try a question again" setting applies to the review of an individual question page. When the student does not select the correct answer, 'Provide option to try a question again" setting will display 2 buttons. One will direct the student back to the question and the other to continue.
*"Maximum number of attempts" is designed to prevent a student from being stuck on "This page" where they continually put or select the wrong answer. It will override other settings, such as review or the option to try the question again. When exceeded, it will not allow a score to be recorded for that question.

====Case 1 ====
The teacher wants the student to be able to attempt any question no more than 3 times and be given the chance to answer the question again. The teacher wants the student to see the response attached to their answer.

:Flow control settings
::Allow student review '''Yes'''
::Provide option to try a question again '''No'''
::Maximum number of attempts '''3'''
::Display default feedback '''No'''
::Number of pages to show '''0'''
::Slideshow '''No'''

:Student selects wrong answer and will see:
:: "Response for the wrong answer" (if any is shown)
:: "Yes, I'd like to try again" button
:: "Continue" button.

:Student selects correct answer and will see:
:: "Response for the correct answer" (if any is shown)
:: "Continue" button

====Case 2 ====
The teacher wants to allow the student 3 attempts at all questions but not see any feedback except the site default feedback for wrong answers.
*Flow control settings
::Allow student review '''No'''
::Provide option to try a question again '''Yes'''
::Maximum number of attempts '''3'''
::Display default feedback '''No'''
::Number of pages to show '''0'''
::Slideshow '''No'''

*Student selects wrong answer and will see:
::''Not quite. Would you like to try again?'' as text over the
::"Yes, I'd like to try again" button
::'"No, I just want to go on to the next question" button

:''Note:'' If the wrong answer jump is set to "This page" and the number of attempts is under the maximum, then the student will return to the question, regardless if they select "No, I just want to go on".

*Student selects correct answer and will see:
:: "Your answer: {gives the student's answer)"
:: Response attached to the correct answer (if any)

==== Case 3 ====
"Speed bump for speed clickers". Teacher only wants the student to get once chance to record an answer on any question. They will only see the response the teacher provides for any question, or the default feedback if no response has been set for the answer the student selected.

*Flow control settings
::Allow student review '''No'''
::Provide option to try a question again '''No'''
::Maximum number of attempts '''1'''
::Display default feedback '''Yes'''
::Number of pages to show '''0'''
::Slideshow '''No'''

*Student selects wrong answer and will see:
:: "Response for the wrong answer" (if any is shown)
:: "Yes, I'd like to try again" button
:: "Continue" button.

: ''Note:'' When teacher sets the Jump to "This page" for a wrong answer, they will return to the page but their score will not change.

* Student
::"Response for the correct answer" (if any is show)
::"Continue" button

==Ideas for using Lessons==
*Because of its "branching" nature, the lesson module lends itself to a wide variety of activities, not all of which need to be graded. In addition to merely working through a list of question pages, here are some other suggestions:
====Self-directed learning of a new topic====
*Use the lesson to introduce a new topic. The learner starts out knowing nothing but can progress at his own pace, reviewing what he is not sure of and moving on when he feels ready. This can be much enhanced by...
====Allow for different learning styles====
*When using the lesson to introduce a new topic, offer pages that deliver the content in different ways, according to how the students prefer to learn. For example the button "do you prefer to read?" goes to a page of text; "do you prefer to watch a video?" goes to a screencast ; "do you prefer to listen to instructions?" -goes to a podcast and so on.
====Role play simulations/Decision-making exercises====
*Use the lesson to set up situations where the learner has to make a choice each time and the scenario changes according to their selection. This could be a medical emergency for example, deciding upon the correct treatment, or a customer relations exercise, learning how best to deal with an awkward client. In an educational establishment it could serve well in Humanities subjects considering moral/ethical issues.
====Interactive fiction====
*For younger (and not so younger!) students, the lesson can be used to create a "choose your own ending" type of story where the student reads a page (or even watches a video/listens to an audio file) and then decides upon the character's next move. Apart from the entertainment value of this, it could be used to help guide pre-teens to behave responsibly by taking decisions for a character who is in a potentially dangerous situation.
====Differentiated revision guides====
*Students can be taken to different sets of revision questions according to their answers, allowing them to progress from basic to intermediate to advanced according to their prior knowledge.
====More!====
*Have any other good ideas? Please add them here!

== See also ==

[http://school.demo.moodle.net/mod/lesson/view.php?id=1156&pageid=182&start A working example of a Lesson from the School demo site.]

*The following two tutorials refer to older versions of Moodle:
*[http://www.youtube.com/watch?v=nq3das503-Q Creating a Decision-Making exercise (role play) using a Lesson]
*[http://www.youtube.com/watch?v=4xjXelUZguw Creating a Lesson video tutorial]

[[fr:Afficher une leçon]]
[[de:Lektion nutzen]]
[[ja:レッスンの利用]]

Jumps

2012-10-03T18:22:21Z

Mits:

{{Lesson}}
}Jumps are a unique feature of the Lesson module. Jumps are links and determine what happens after a student makes a choice on a lesson page. There are two basic types of jumps - Relative and Absolute. The teacher uses a pull down menu to see a selection of all possible jumps.

For example, a teacher creates 10 Lesson pages and titles them P1 to P10.

P1, P2, P3, P4, '''P5''', P6, P7, P8, P9, P10.

On P5, the teacher may want to send the student to P7 for one student choice and to "Next Page" for other choices. In this example "P7" is an absolute jump and "Next Page is a relative jump.

== Absolute jumps ==
The absolute jump always goes to the same page that a teacher has created. In our example we used P7.

P1, P2, P3, P4, '''P5''', P6, '''P7''', P8, P9, P10.

Note that the teacher can decide to change the title of "P7" to "Grading" as the page title. The jump from P5 will automatically change.

P1, P2, P3, P4, '''P5''', P6, '''Grading''', P8, P9, P10.

Moving either page will not effect any absolute jumps. In the example below the absolute jump in P5 will now skip 4 pages in the logical order.

P1, P2, '''P5''', P3, P4, P6, P8, '''Grading''', P9, P10.

Pages can have the same title and this can be confusing when setting jumps. For example, it is a good practice to retitle an End of Branch page so you don't end up with 5 pages all called End of Branch.

== Relative jumps ==
These kinds of jumps go to a position or create an effect. In our example, a Next Page jump in P5 is the next page in the logical order of the lesson is P6.

P1, P2, P3, P4, '''P5''', '''P6''', P7, P8, P9, P10.

The teacher may decide that more information is needed for those students going to P6. The teacher can insert a page (called P5-b)immediately after P5 and the Next Page jump will now go to P5-b.

P1, P2, P3, P4, '''P5, P5-b''', P6, P7, P8, P9, P10.

Or the teacher can move another page to the position right after P5, and the Next page jump will go there. In the example below P10 has been moved and it has become the "Next page".

P1, P2, P3, P4, '''P5, P10''', P5-b, P6, P7, P8, P9.

If the teacher moves P5 to another location in the logical order, the relative jump will still look for the "Next page" in our example this will now be P10.

P1, P2, P3, P4, P6, P7, P8, P9, '''P5, P10'''.

Here are a few of the relative jumps that a teacher might find in a Lesson page.

The random relative jumps need to be planned with care. The were designed to be used within a segment of a lesson.

===Next page===
We have covered this relative jump in our above example. It is also the default jump for the first answer of any question or content (branch table) page choices.

===This page===
This page takes the student back to the page they just viewed. Lesson will usually use this jump as a default in most question and content pages, if it didn't use "Next page".

===Previous page===
The page which is in front of the current page in the logical order.

===End of lesson===
The end of lesson is the splash screen a student sees when they have completed the lesson. In the simple lesson, this follows the last page in the logical order. It may show their score, offer a link to the next lesson or just say that they have completed the lesson. This jump is often used as a content page choice to allow the student to end the lesson at that point in the Lesson.

=== Unseen question within a branch ===
This will link to a randomly chosen unseen (by the student in this attempt) question between this content page and the End of the Lesson or the next End of Branch. This might be used in a segment of a lesson, where it is used in as a jump in C2 in the example below. Use with care.

C1, '''C2, Q1, Q2, Q3, EoB''', C3, C4, C5, Q4, C6.

=== Random question within a branch ===
This will link to a randomly chosen question between the current content page and the End of Lesson or the next End of Branch. If the student has already seen the question and attempts are greater than 1, they will get another chance to earn the point(s) for that question. If attempts are set to 1, the question will be skipped and another random question shown. Use with care.

C1, '''C2, Q1, Q2, Q3, EoB''', C3, C4,C5, Q4,C6.

=== Random branch table ===
This will jump to a random Content page between the current Content page and the End of Lesson or the next End of Branch. It is used in a segment and is a jump in C2 shown below. Use with care.

C1, '''C2, C3, C4, C5 EoB''', Q1, Q2, Q3, Q4, C6.

==Lesson jump pulldown example==
[[Image:Lesson Jump pulldown 3.JPG|center]]

Here is a pull down of jumps in a demo lesson for 1.8. Notice the relative and absolute pages. The relative pages are listed at the top and the absolute pages underneath them. Depending upon the current pages in a Lesson, some of the relative jumps may not be shown.

[[Category:Teacher]]
[[Category:Lesson]]

[[fr:Sauts]]
[[de:Spr%C3%BCnge]]
[[ja:ジャンプ]]

Lesson clusters

2012-09-07T01:35:45Z

Mits: ja link

{{Lesson}}
'''Clusters''' are special group of pages in a [[Lesson_module]]. A "cluster" is formed by placing a special navigational "cluster" page at the start of the group and an "end cluster" page after the last page in the group. Clusters can be considered an advanced feature of Lesson.

== What are clusters? ==

The typical cluster group (or series of pages) contains question pages and we will focus our attention on this kind of cluster. It is a good practice to first add most of the content (branch table) and question pages in a lesson, then consider where to place the special navigation pages that define a cluster.

Consider a series of question pages: Q1, Q2, Q3, Q4, Q5, Q6, Q7, Q8. This represents 8 questions in a Lesson.

A cluster is started in the logical order with a cluster page. Clusters should be completed with an End of Cluster page for best results (otherwise they treat the End of Lesson as the End of Cluster).

The teacher might put some of them in a cluster, where C1 is the first "cluster" page and EC1 is the first "end cluster" page in the lesson.
*Q1, '''C1''', Q2, Q3, Q4, Q5, Q6, Q7, '''EC1''', Q8.

A cluster represents a set of pages from which one or more may be randomly chosen. Questions within a cluster are randomly selected by choosing "Random Question within a Cluster" as the jump in the "Start Cluster" page. Questions within a cluster may either link to the End of Cluster to exit the cluster, or jump to any other page in the lesson. They may also jump to an unseen question within the cluster but most commonly are directed back to the "Start Cluster" page.

==Sub-Clusters==

Clusters can contain sub-clusters by using Branch Tables and End of Branches. To implement this advanced feature, set up a cluster as normal with a Cluster page followed by question pages (with the jumps set up the same as above) and ended with an End of Cluster page.
* Q1, '''C1''', Q2, Q3, Q4, Q5, Q6, Q7, '''EC1''', Q8
To set up a sub-cluster, wrap a group of questions with a Branch Table and an End of Branch.
* Q1, '''C1''', Q2, Q3, '''B1''', Q4, Q5, Q6, '''EB1''', Q7, '''EC1''', Q8
Neither the content nor the jumps of the Branch Table and the End of Branch are seen by the student. Rather the two pages act as markers for the sub-cluster within the main cluster. When the student attempts the lesson, only one random question page within the sub-cluster will be displayed to the student.

==When to use a cluster?==
A cluster is used when the teacher wants a series of questions in a lesson to appear in a different random order for each student.

In the example: Q1, Q2, C1, Q3, Q4, Q5, EC1, Q6, Q7, Q8, when the student reaches C1, the teacher might set the jump to "go to an unseen question in the cluster". When a jump in Q3, Q4 and Q5 is set to go back to C1, the student will see a "new" question in the cluster. When the student has seen all the questions in the cluster, they will be sent to EC1. The student will never see EC1, just be redirected by the jump in EC1.

Any or all of the question answers inside a cluster, could exit the student from the cluster. For example, specific jumps in Q3, Q4 and Q5 could be set to Q6, thus the student would pass over EC1 and leave the cluster.

==Tips and tricks==
Remember clusters have their own adaptive logic. It is always a good idea to test a cluster when logged in as a student. New users of a cluster, might do well to create a simple lesson so they understand how clusters work when applied in a more complex adaptive lesson.

:''TIP:'' Setting an answer's jump to "Unseen question" may cause problems. For example, when a student has seen all the questions and is allowed to re-enter the cluster in the same lesson attempt. Clusters are an advanced feature and should be checked in a student role.

:''TIP:'' Looking for a page that redirects without the student seeing it? Alison Schubert discovered the start and end cluster pages are not seen by the student. The teacher can insert an "End of cluster" page in the edit order with a jump. This will automatically redirect a student to another page without the usual continue button.

==See also==
*[[Branch structures]]

[[es:Clusters]]
[[de:Cluster]]
[[fr:Groupes de questions]]
[[ja:クラスタ]]

Building Lesson

2012-08-21T19:01:11Z

Mits: ja link

{{Lesson}}
This page is about how to structure a Moodle lesson once you have created it with the [[Lesson settings]]. For information on how best to use a Moodle lesson and how students approach it, see [[Using Lesson]]

==Planning your lesson==
*A lesson is made up of pages which may have content for the student to read or questions for them to answer. The questions can be created by the teacher or imported. The teacher decides the order in which these pages appear.
*You need to have a clear idea beforehand of what you want to do with this lesson. Is it to be a graded, linear learning experience? Or an ungraded, non-linear practice session? Will students be able to go back and revisit areas or is it just a once-only opportunity?
*Even those who are very comfortable working directly online might find it useful to note down on paper the direction they want their lesson pages to go in, rather than having to remember and visualize the navigation in their head.
*For hints and ideas about using the Lesson module, look at [[Using Lesson]] and [[Lesson FAQ]]

==Adding content and questions to your lesson==
*When you have set up your lesson with the [[Lesson settings]],click "Save and display" and you will be taken to the screen in the screenshot below.
*If you click "Save and return to course" instead, then click the "update" icon next to the lesson on the page and click "edit" in the ''Settings block>Lesson Administration''
[[File:lessonbegin.png]]

===Import questions===
*If you have some questions in the following formats, you can import them to use in your lesson by clicking the Import questions link. For general information about these question types, see [[Import questions]]
[[File:importquestions.png]]

===Import a powerpoint===
*Although this setting is available, it really does not work and is not advised. See [[Import PowerPoint]] for alternatives.

===Add a cluster===
*A cluster is a group of question pages which will be offered randomly to a student as they work through the lesson.It is best if you have made the question pages beforehand and can then decide where to mark the start and end of the cluster. The start is marked by a "cluster" page and the end by an "end of cluster" page. See [[Clusters]] for more information.

===Add a content page===
*This is a page where a teacher can provide information to move the lesson forward but without requiring the student to answer specific questions.
*The student sees the page's title, some information and then one or more buttons at the bottom to select.
*When the student clicks on a button, they go to the next page but their choice is not scored.

====Title====
*The title of a content page appears to the student at the top of the page.
*A teacher will also see the title in the collapsed edit mode when they are working on the Lesson, and they will also be able to choose the title (and hence this page) from the drop down "jump" lists.
*The title in a content page is also used with the "display left menu" setting.

====Page contents====
*This is where the teacher can add information for the student, making use of the [[Text editor]] and its multimedia features.

====Content====
*Here the teacher writes the words they want the student to click on to get to the next part of the lesson.
*These words will appear to the student as a button.
*The teacher can check the box to have the buttons appear horizontally, or uncheck it for them to appear centered vertically.

====Format====
*There are 4 format types to choose from when editing text in the content description box. If you wish to have the usual rich text editing icons, choose HTML format. (Note - once you have selected an option, you cannot then go back and change your mind!)However, if you DO choose HTML format, be warned that the student will not see the changes (such as bold or different colours) in the button.

[[File:lessoncontentbuttons.png]]

====Number of options available====
*How many of these you have depends on your choice in the ''Maximum Number of Answers'' setting in [[Lesson settings]]

==== The Jump====
*Each Description in a Content page has a Jumps menu. "Jumps" take a student from one page to another.
*A "relative jump" is "next page" or "end of lesson" whereas an "absolute jump" gives the actual name of a page.
*The teacher chooses from the dropdown the correct page to send the student to if they click on the button that will be made from this particular description. Any pages created by the teacher will have their titles appear in this dropdown, allowing them to be selected.
*When a student clicks on a description button, they are sent to the page defined in the Jump associated with the button.
*See [[Jumps]] for more detailed information.

===Add a question page===
*From this link you can choose from a variety of question types which will then be added as pages to your lesson:
[[File:addquestionpage.png]]
*''(Note: These question types are not the same as for the [[Quiz]] and are in no way connected with quiz questions.)''

*The format of question pages is similar to content pages outlined in [[Building_Lesson#Add_a_content_page| Section 2.4]] above.
*A typical question page could include:
**'''Title''' - the name the student sees at the top of the question page.
**'''Page contents''' - the actual question
**[[File:examplequestion.png]]
**'''Answer/Response/Format/Jump/Score''' as in the screenshot below
**[[File:exampleanswer.png]]

===Question types===
====Multichoice====
*The student is given a question and a list of answers. The answer list will be shuffled every time the question is view by a student. By default they choose one answer but you can check the box "multiple answer" to allow them to choose more than one answer.
====Essay====
*Students can write a longer answer as part of the lesson and this can be graded manually by the teacher. If the main purpose of your lesson is for students to write an essay, consider the [[Assignment module]] instead.
====Matching====
*This allows you to set up lists which must be matched against other lists, for instance, words, pictures, numbers etc. The student must match all correctly to receive the score.
====Numerical====
*This requires a number as an answer. A number within a range may also be accepted as correct. The range separator to be used is the colon : For example, to accept as correct any number between 10 and 12 (10, 11 and 12) you would type 10:12 in the Answer box.
====Short answer====
*A student must provide a single word or short phrase answer. The teacher must anticipate the possible answers and enter them in the Jump dropdown boxes, using ** wild cards if appropriate.
====True/false====
*The student is given a sentence and must decide if it is true or false.

==Moving your lesson forward==
*Once you have added your first content or question page, you reach the next screen which displays your page title/type/jumps (ie where the responses take the student to) and actions you can take next:
[[File:lessonactions.png]]
*The '''Actions''' icons allow you to move (if you have more than one), edit, preview or delete your pages.
*The drop down allows you to create another page of your choice:
[[File:lessonactionsdropdown.png]]

*Note the different view options:

====Collapsed view====
*This gives a brief outline of the lesson structure as in the two screenshots above.

====Expanded view====
*This shows more detail as in the screenshot below:
[[File:expandedview.png]]
==Ending your lesson==
*To bring the lesson to a close, select the "End of Lesson" option from the Jump menu on any relevant pages.
*The student will then see a generic message as in the next screenshot, with a direction back to the main course page or to view their grades:
[[File:endoflesson1.png]]

[[de:Lektion erstellen]]
[[ja:レッスンの作成]]

Lesson settings

2012-07-11T15:39:02Z

Mits: ja link

{{Lesson}}

This page explains the settings involved when first creating a lesson.
To add a lesson to your Moodle course page:
*With the editing turned on,in the section you wish to add your lesson, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu )and choose ''Lesson''
*This will take you to the Lesson settings page.

==Lesson administration settings==

===General===
*''Note: Click the "Show Advanced" button to the right if you don't see all the options below.''
====Name====
*The name you add here will be the link the students click on to get to your Lesson.

====Time limit====
[[Image:Lesson Timer.png|right]]
*This allows you to set a time limit on the lesson. Students will see a count down counter as they work.The timer does not stop them doing the the lesson when the time is up, but correct answers are no longer scored.
====Available from/Deadline====
*Here you can set a start and end date and time for your Lesson.
====Maximum Number of Answers====
*Here you can set the default number of answer boxes available when you add your question or content pages. For instance, if you are only going to use True/False, you would only need 2. You can change this at any time so it's not crucial.

====Password protected====
*Change to "Yes" and enter the password if you want students only to access it when they know the password.

===Grade===
*Set a grade and grade category here.

===Grade options===
====Practice lesson====
*Use this if you don't need the lesson to be scored/graded but just need students to work through some pages.

====Custom Scoring====
*Use this to give a particular number score (negative or positive) to each answer

====Re-takes allowed====
*Choose this if you want your students to be able to do the lesson more than once.

====Handling of re-takes====
*If you allow your students to re-take the lesson, then decide here if the grade for all lesson attempts is the mean or the maximum.

:Note that the Question Analysis always uses the answers from the first tries of the lesson. Re-takes by students are ignored.

====Display ongoing score====
*Choose this to let students see their score as they work through the lesson.

===Flow Control===

*''Note: Click the "Show Advanced" toggle button to the right if you don't see all the options below.''
*[[Using Lesson]] gives examples of how these settings may be put to best effect.
====Allow Student Review====
*This puts a "Review Lesson" button on the last screen of the lesson to encourage the student to navigate through the lesson again from the start. Be sure to check other settings to allow them to change their answers.

====Provide option to try a question again====
*This displays a button after an incorrectly answered question so that the student can try again (but not get credit for it)

:''TIP:'' Leave this off if you are using essay questions.
====Maximum Number of Attempts====
*Decide here how many times you want students to be able to attempt each question. When they reach the maximum, they will be taken automatically to the next page.

====Action after a Correct Answer====
*Choose here where you want a student to be sent to if they get a question right. See [[Using Lesson]] for more details on this setting. The options are:
**the next part of the Lesson (default setting)
**a random, unexpected page
**a random page which they have not yet answered.

====Display default feedback====
*Choose this if you want to show a set phrase regardless of their answer. If you have set your own default feedback such as "well done; correct" or "never mind; better luck next time" etc it will appear. If you have not, then Moodle's default feedback will appear.
====Progress bar====
*Choose this to show a bar at the bottom of the page showing how far into the lesson the student has got.
''*Note: There are currently some issues with the lesson progress bar not displaying as expected. MDL-26016''

====Display left menu====
*Choose this if you want to show a list of the pages in the Lesson so a student can see what is coming up.
====Display left menu only if grade greater than ...%====
*Choose this if you want the student to go through the lesson (and get a grade) once and then, on review, to be able to see and navigate through all the different pages.
====Number of pages to show====
*You only need this if you have set "Action after a correct answer" to show an unseen or unanswered page. Otherwise, all pages will be seen.
====Minimum Number of Questions====
*Set here the minimum number of questions that will be used to calculate a student's score.Students will be told how many they have answered and how many more they need to answer.
*If you are using Content pages, then set this to 0.
*If you use this setting, then add some explanatory text at the start of the lesson so the student knows how many questions they must answer as a minimum. (They may answer more.
====Slideshow====
*Choose this if you want your Lesson displayed as a slideshow with fixed width, height and custom background colour. The administrator sets the defaults for these in ''Settings>Site Administration>Plugins>Activity modules>Lesson.''

====Link to an activity====
*Choose this to give students a link to another activity when they reach the end of the lesson. ''(Note: this can also be achieved using [[Conditional activities]])''

===Pop-up to file or web page===
*If you want to include a link to a file on the lesson page for students to refer to, upload it here.

===Dependent on===
*This allows access to the lesson to be dependent on students' performance in another lesson in the same course. ''(Note: this can also be achieved with [[Conditional activities]])''

==Other settings==
There are the usual [[Common module settings]] and - if admin has enabled them - the Restrict access settings and Activity Completion settings in [[Conditional activities]].

==Site administration settings==

The lesson module has additional settings which may be changed by an administrator in ''Settings > Site administration > Plugins > Activity modules > Lesson''.

===Slideshow width===
Sets the width of the slideshow only when this feature is enabled in a Lesson's "Change settings".
*Variable name: lesson_slideshowwidth, Default 640.

===Slideshow height===
Sets the height of the slideshow only when this feature is enabled in a Lesson's "Change settings".
*Variable name: lesson_slideshowheight, Default 480.

===Slideshow background colour===
Background colour to for the slideshow if it is enabled.
*Variable name: lesson_slideshowbgcolor, Default #FFFFFF.

===Popup window width===
Sets the width of the popup displayed for a linked media file
*Variable name: lesson_mediawidth, Default 640.

===Popup window height===
Sets the height of the popup displayed for a linked media file
*Variable name: lesson_mediaheight, Default 480.

===Show close button:===
Displays a close button as part of the popup generated for a linked media file
*Variable name: lesson_mediaclose, Default No.

===Number of high scores displayed===
Sets the number of high scores to display
*Variable name: lesson_maxhighscores, Default: 10

===Maximum number of answers===
Default maximum number of answers per page for site
*Variable name: lesson_maxanswers, Default: 4.

===Action after correct answer===
The default action to take after a correct answer
*Variable name: lesson_defaultnextpage, Default: Normal - follow lesson path

==See also==

[[de:Lektion konfigurieren]]
[[fr:Ajouter/modifier une leçon]]
[[ja:レッスンの設定]]

Upgrading to Moodle 2.2

2012-05-15T15:31:55Z

Mits:

{{Installing Moodle}}
You can upgrade to Moodle 2.2 from Moodle 2.1, 2.0 or 1.9. If you are upgrading from 2.0, please also read [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to Moodle 2.1] . If upgrading from 1.9, please also read that and [https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to Moodle 2.0]. After reading this you can upgrade directly to 2.2.

If you are using an earlier version of Moodle, you must upgrade to the latest Moodle 1.9.x first.

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

==System requirements==

* PHP must be '''5.3.2''' or later
** Required PHP extensions: iconv, curl, ctype, zip, simplexml, spl, pcre, dom, xml, json
** Required PHP memory_limit at least 40MB (64MB or more recommended if you have a choice)
* Databases should be one of the following:
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)
** PostgreSQL 8.3 or later
** Oracle 10.2 or later
** MS SQL 2005 or later
* Any standards-supporting browser from the past few years, for example:
** Firefox 3 or later
** Safari 3 or later
** Google Chrome 4 or later
** Opera 9 or later
** MS Internet Explorer 7 or later

Note: The above system requirements are unchanged from Moodle 2.1.

==Before upgrading please... ==

'''NOTE''': The upgrade process will irreversibly modify the contents of your database '''and''' your moodledata file storage area. If something goes wrong you '''cannot''' go back. It is vital that you take good backups of both moodledata and the database in case you have problems with the upgrade. If you are not sure how see [[Site backup]] or ask in the moodle.org forums (explaining what your operating system is).

* Read the [[:dev:Moodle 2.2 release notes|Moodle 2.2 release notes]] and check the [[:Category:New features|list of new features]]
* Check your site to make sure it meets all system requirements for 2.2 in ''Settings > Site administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* '''Do a full moodledata backup'''
* '''Check your backups carefully'''
* Remember to purge PHP cache if using any PHP accelerator

==Possible issues that may affect you==

* If you have custom reports, there have been changes that may require (simple) changes to be made to their code. See the developer documentation [[:dev:General report plugins]] for details.
* Global search has been removed from core as it was broken. (A new global search is being written for 2.3.)
* Some web service functions have been deprecated. They still work, but check any web service connections you may have to your Moodle for the future.

==Checking database schema - old sites==

If your Moodle site has been upgraded through many prior versions it is possible that there will be some problems with the database schema (compared to a fresh 2.0 installation). This may cause the upgrade to fail. If your site started life prior to Moodle 2.0 it is a very good idea to check and correct the database schema before upgrading. See [[Verify Database Schema]]. You should also run the database integrity checks in the XMLDB editor, see the 'See also' for a link to extra scripts to check for other discrepancies.

==Now upgrade==

Once you have satisfied the requirements for Moodle 2.2, follow the instructions on the [[Upgrading|upgrading]] page.

On Linux servers, Moodle 2.2 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

==After upgrade==

The config.php file from your 2.0 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.0 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.2 config-dist.php.

==See also==

* [[dev:Moodle 2.2 release notes|Moodle 2.2 release notes]]

[[fr:Mise à jour à Moodle 2.2]]
[[ja:Moodle2.2へのアップグレード]]