MoodleDocs - User contributions [en]

Upload courses

2013-10-31T09:09:23Z

Jmouneyrac: /* Short file example */

{{Courses}}

{{New features}}
An administrator can upload multiple courses using a text file.

There are many things you can do when using this tool:not only creating courses, but updating or deleting them. You can also update the course enrolment methods or import the content of another course.

==Uploading the file==

You can upload the file by navigating to ''Administration > Site administration > Courses > Upload courses'' and either dragging and dropping the csv file or clicking the button to upload from the file picker.

{|
|[[File:26uploadcourses.png|250px|thumb|Upload courses admin screen]]
|
|[[File:uploadcoursesresults.png|250px|thumb|Courses successfully uploaded]]
|}

''Note:'' It is also possible to use the command-line tool ''admin/tool/uploadcourse/cli/uploadcourse.php''.

When using the web interface, use the ''Preview'' option to see if any errors were detected in the previewed rows. If you proceed with the upload and there were something wrong detected with a course, it will be ignored.

=== Short file example ===
uploadcourse.csv:
<code bash>
shortname,fullname,category,summary,enrolment_1,enrolment_1_role,enrolment_1_enrolperiod,role_student
courserestored,Course restored,1,a summary,manual,student,1 month,
courserestored2,Course restored 2,1,a summary,,,,
courserestored3,Course restored 3,1,a summary,,,,padawan
courserestored4,Course restored 4,1,"a summary, with comma",manual,student,1 month,padawan
</code>
Notice there are no spaces between the arguments.

==Creating the text file==

The text file to upload courses must be a CSV file. It accepts the following columns which are divided in two categories, the course information, and the course actions.

===Course information fields===

Most of those settings are available on the settings page of a course. Please refer to [[Course settings]] for more information.

;shortname
: The shortname
;fullname
: The full name
;idnumber
: The ID number
;category
: The ID of the category to place the course in. This takes precedence over ''category_idnumber'' and ''category_path''.
;category_idnumber
: The ID number of the category to place the course in. This takes precedence over ''category_path''.
;category_path
: The path of the category to place the course in. If you want to place the course in a category named "Science-Fiction" which is located under the category "Movies", the value to provide is: <code>Movies > Science-Fiction</code>. Note that the separator must be <code>[space]>[space]</code>. Also note that the category MUST exist, it will not be created.
;visible
: 1 if the course is visible, 0 if hidden
;startdate
: The time at which the course starts. Please note that this value is passed to the PHP function [http://php.net/manual/en/function.strtotime.php strtotime] to generate a timestamp.
;summary
: The summary of the course
;format
: The course format to use, this must be a valid course format plugin name. E.g. ''weeks'', ''topics''.
;theme
: The theme to use
;lang
: The language to use
;newsitems
: The number of news items
;showgrades
: 1 to show the gradebook to students, 0 to hide it.
;showreports
: 1 to show the activity reports, 0 to hide it.
;legacyfiles
: 1 to enable the legacy course files, 0 not to.
;maxbytes
: The maximum upload size of the course in bytes. Use 0 for the site limit.
;groupmode
: 0 for ''No groups'', 1 for ''Separate groups'' and 2 for ''Visible groups''.
;groupmodeforce
: 1 to force the group mode, otherwise enter 0.
;enablecompletion
: 1 to enable the activity completion, 0 not to.

====Enrolment fields====

Some fields can be constructed to enable and configure enrolment methods. The fields must be named ''enrolment_[number]'' for the enrolment method name, and ''enrolment_[number]_property'' for its properties.

;enrolment_[number]
: The name of the enrolment method
;enrolment_[number]_delete
: 1 to delete this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_disable
: 1 to disable this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_startdate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enddate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enrolperiod
: Number of seconds, or if not a value understood by strtotime() such as "4 days".
;enrolment_[number]_role
: The role short name
:enrolment_[number]_[property]
; Where property is understood by the specified enrolment method

'''Example'''

enrolment_1: manual
enrolment_1_role: student
enrolment_1_enrolperiod: 1 month

enrolment_2: self
enrolment_2_startdate: 2013-01-30

====Role renaming====

To rename some roles, using the following pattern:

;role_[shortname]
: The new name of the role ''[shortname]''.

'''Example'''

role_student: Apprentice
role_teacher: Master
role_mycustomrole: Jedi

===Course action fields===

Those settings take precedence over the ''Course process'' parameters.

;delete
: 1 to delete the course
;rename
: The shortname to rename the course to
;backupfile
: An absolute path to a backup file (.mbz) to import in the course
;templatecourse
: The short name of a course to import the content from
;reset
: 1 to reset the course

===Mandatory fields===

;shortname
: This field is mandatory for every operation, with the only exception of creating new courses. See details on the course process parameter ''Shortname template'' for more information.
;fullname
: Required when creating a new course.
;category, category_idnumber, category_path
: One of these is required when creating a course.

===Import options===

To prevent unexpected behaviours, you have to specify what you want the tool to be able to do.

;Upload mode
: This allows you to specify if courses can be created and/or updated.
;Update mode
: If you allow courses to be updated, you also have to tell the tool what to update the courses with.
;Allow deletes
: Whether the ''delete'' field is accepted or not
;Allow renames
: Whether the ''rename'' field is accepted or not
;Allow resets
: Whether the ''reset'' field is accepted or not

===Course process===

This allows you to specify actions to be taken on every single courses uploaded.

;Shortname template
: If you are creating courses without a shortname, you can use this field to automatically generate a shortname. This field accepts two placeholders: %i for the ID number, %f for the summary.
;Restore file
: A backup file (.mbz) to import in the course after create/update.
;Restore from course
: The shortname of a course to import content from after create/update.
;Reset after upload
: Whether to reset the course after creating/updating it.

===Default course values===

Those are values that can be set in the web interface for all the fields that are not specified in the CSV file. Note that they are always used when creating a course, but only when specified during update (see ''Update mode'').

==Increasing speed==

When importing the content of a backup file, or another course, you are adviced to enable the setting ''keeptempdirectoriesonbackup''. This will considerably speed up the process of the upload if you are importing multiple times from the same source.

[[de:Kurse hochladen]]
[[es:Subir cursos]]

Upload courses

2013-10-31T08:37:41Z

Jmouneyrac: /* Short file example */

{{Courses}}

{{New features}}
An administrator can upload multiple courses using a text file.

There are many things you can do when using this tool:not only creating courses, but updating or deleting them. You can also update the course enrolment methods or import the content of another course.

==Uploading the file==

You can upload the file by navigating to ''Administration > Site administration > Courses > Upload courses'' and either dragging and dropping the csv file or clicking the button to upload from the file picker.

{|
|[[File:26uploadcourses.png|250px|thumb|Upload courses admin screen]]
|
|[[File:uploadcoursesresults.png|250px|thumb|Courses successfully uploaded]]
|}

''Note:'' It is also possible to use the command-line tool ''admin/tool/uploadcourse/cli/uploadcourse.php''.

When using the web interface, use the ''Preview'' option to see if any errors were detected in the previewed rows. If you proceed with the upload and there were something wrong detected with a course, it will be ignored.

=== Short file example ===
uploadcourse.csv:
<code bash>
shortname,fullname,category,summary,enrolment_1,enrolment_1_role,enrolment_1_enrolperiod,role_student
courserestored,Course restored,1,a summary,manual,student,1 month,
courserestored2,Course restored 2,1,a summary,,,,
courserestored3,Course restored 3,1,a summary,,,,padawan
courserestored4,Course restored 4,1,a summary,manual,student,1 month,padawan
</code>
Notice there are no spaces between the arguments.

==Creating the text file==

The text file to upload courses must be a CSV file. It accepts the following columns which are divided in two categories, the course information, and the course actions.

===Course information fields===

Most of those settings are available on the settings page of a course. Please refer to [[Course settings]] for more information.

;shortname
: The shortname
;fullname
: The full name
;idnumber
: The ID number
;category
: The ID of the category to place the course in. This takes precedence over ''category_idnumber'' and ''category_path''.
;category_idnumber
: The ID number of the category to place the course in. This takes precedence over ''category_path''.
;category_path
: The path of the category to place the course in. If you want to place the course in a category named "Science-Fiction" which is located under the category "Movies", the value to provide is: <code>Movies > Science-Fiction</code>. Note that the separator must be <code>[space]>[space]</code>. Also note that the category MUST exist, it will not be created.
;visible
: 1 if the course is visible, 0 if hidden
;startdate
: The time at which the course starts. Please note that this value is passed to the PHP function [http://php.net/manual/en/function.strtotime.php strtotime] to generate a timestamp.
;summary
: The summary of the course
;format
: The course format to use, this must be a valid course format plugin name. E.g. ''weeks'', ''topics''.
;theme
: The theme to use
;lang
: The language to use
;newsitems
: The number of news items
;showgrades
: 1 to show the gradebook to students, 0 to hide it.
;showreports
: 1 to show the activity reports, 0 to hide it.
;legacyfiles
: 1 to enable the legacy course files, 0 not to.
;maxbytes
: The maximum upload size of the course in bytes. Use 0 for the site limit.
;groupmode
: 0 for ''No groups'', 1 for ''Separate groups'' and 2 for ''Visible groups''.
;groupmodeforce
: 1 to force the group mode, otherwise enter 0.
;enablecompletion
: 1 to enable the activity completion, 0 not to.

====Enrolment fields====

Some fields can be constructed to enable and configure enrolment methods. The fields must be named ''enrolment_[number]'' for the enrolment method name, and ''enrolment_[number]_property'' for its properties.

;enrolment_[number]
: The name of the enrolment method
;enrolment_[number]_delete
: 1 to delete this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_disable
: 1 to disable this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_startdate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enddate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enrolperiod
: Number of seconds, or if not a value understood by strtotime() such as "4 days".
;enrolment_[number]_role
: The role short name
:enrolment_[number]_[property]
; Where property is understood by the specified enrolment method

'''Example'''

enrolment_1: manual
enrolment_1_role: student
enrolment_1_enrolperiod: 1 month

enrolment_2: self
enrolment_2_startdate: 2013-01-30

====Role renaming====

To rename some roles, using the following pattern:

;role_[shortname]
: The new name of the role ''[shortname]''.

'''Example'''

role_student: Apprentice
role_teacher: Master
role_mycustomrole: Jedi

===Course action fields===

Those settings take precedence over the ''Course process'' parameters.

;delete
: 1 to delete the course
;rename
: The shortname to rename the course to
;backupfile
: An absolute path to a backup file (.mbz) to import in the course
;templatecourse
: The short name of a course to import the content from
;reset
: 1 to reset the course

===Mandatory fields===

;shortname
: This field is mandatory for every operation, with the only exception of creating new courses. See details on the course process parameter ''Shortname template'' for more information.
;fullname
: Required when creating a new course.
;category, category_idnumber, category_path
: One of these is required when creating a course.

===Import options===

To prevent unexpected behaviours, you have to specify what you want the tool to be able to do.

;Upload mode
: This allows you to specify if courses can be created and/or updated.
;Update mode
: If you allow courses to be updated, you also have to tell the tool what to update the courses with.
;Allow deletes
: Whether the ''delete'' field is accepted or not
;Allow renames
: Whether the ''rename'' field is accepted or not
;Allow resets
: Whether the ''reset'' field is accepted or not

===Course process===

This allows you to specify actions to be taken on every single courses uploaded.

;Shortname template
: If you are creating courses without a shortname, you can use this field to automatically generate a shortname. This field accepts two placeholders: %i for the ID number, %f for the summary.
;Restore file
: A backup file (.mbz) to import in the course after create/update.
;Restore from course
: The shortname of a course to import content from after create/update.
;Reset after upload
: Whether to reset the course after creating/updating it.

===Default course values===

Those are values that can be set in the web interface for all the fields that are not specified in the CSV file. Note that they are always used when creating a course, but only when specified during update (see ''Update mode'').

==Increasing speed==

When importing the content of a backup file, or another course, you are adviced to enable the setting ''keeptempdirectoriesonbackup''. This will considerably speed up the process of the upload if you are importing multiple times from the same source.

[[de:Kurse hochladen]]
[[es:Subir cursos]]

Upload courses

2013-10-31T08:34:09Z

Jmouneyrac: /* Short file example */

{{Courses}}

{{New features}}
An administrator can upload multiple courses using a text file.

There are many things you can do when using this tool:not only creating courses, but updating or deleting them. You can also update the course enrolment methods or import the content of another course.

==Uploading the file==

You can upload the file by navigating to ''Administration > Site administration > Courses > Upload courses'' and either dragging and dropping the csv file or clicking the button to upload from the file picker.

{|
|[[File:26uploadcourses.png|250px|thumb|Upload courses admin screen]]
|
|[[File:uploadcoursesresults.png|250px|thumb|Courses successfully uploaded]]
|}

''Note:'' It is also possible to use the command-line tool ''admin/tool/uploadcourse/cli/uploadcourse.php''.

When using the web interface, use the ''Preview'' option to see if any errors were detected in the previewed rows. If you proceed with the upload and there were something wrong detected with a course, it will be ignored.

=== Short file example ===
uploadcourse.csv:
<code bash>
shortname,fullname,category,summary,enrolment_1,enrolment_1_role,enrolment_1_enrolperiod,role_student
courserestored,Course restored,1,xx,manual,student,1 month,
courserestored2,Course restored 2,1,xx,,,,
courserestored3,Course restored 3,1,xx,,,,padawan
courserestored4,Course restored 4,1,xx,manual,student,1 month,padawan
</code>
Notice there are no spaces between the arguments.

==Creating the text file==

The text file to upload courses must be a CSV file. It accepts the following columns which are divided in two categories, the course information, and the course actions.

===Course information fields===

Most of those settings are available on the settings page of a course. Please refer to [[Course settings]] for more information.

;shortname
: The shortname
;fullname
: The full name
;idnumber
: The ID number
;category
: The ID of the category to place the course in. This takes precedence over ''category_idnumber'' and ''category_path''.
;category_idnumber
: The ID number of the category to place the course in. This takes precedence over ''category_path''.
;category_path
: The path of the category to place the course in. If you want to place the course in a category named "Science-Fiction" which is located under the category "Movies", the value to provide is: <code>Movies > Science-Fiction</code>. Note that the separator must be <code>[space]>[space]</code>. Also note that the category MUST exist, it will not be created.
;visible
: 1 if the course is visible, 0 if hidden
;startdate
: The time at which the course starts. Please note that this value is passed to the PHP function [http://php.net/manual/en/function.strtotime.php strtotime] to generate a timestamp.
;summary
: The summary of the course
;format
: The course format to use, this must be a valid course format plugin name. E.g. ''weeks'', ''topics''.
;theme
: The theme to use
;lang
: The language to use
;newsitems
: The number of news items
;showgrades
: 1 to show the gradebook to students, 0 to hide it.
;showreports
: 1 to show the activity reports, 0 to hide it.
;legacyfiles
: 1 to enable the legacy course files, 0 not to.
;maxbytes
: The maximum upload size of the course in bytes. Use 0 for the site limit.
;groupmode
: 0 for ''No groups'', 1 for ''Separate groups'' and 2 for ''Visible groups''.
;groupmodeforce
: 1 to force the group mode, otherwise enter 0.
;enablecompletion
: 1 to enable the activity completion, 0 not to.

====Enrolment fields====

Some fields can be constructed to enable and configure enrolment methods. The fields must be named ''enrolment_[number]'' for the enrolment method name, and ''enrolment_[number]_property'' for its properties.

;enrolment_[number]
: The name of the enrolment method
;enrolment_[number]_delete
: 1 to delete this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_disable
: 1 to disable this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_startdate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enddate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enrolperiod
: Number of seconds, or if not a value understood by strtotime() such as "4 days".
;enrolment_[number]_role
: The role short name
:enrolment_[number]_[property]
; Where property is understood by the specified enrolment method

'''Example'''

enrolment_1: manual
enrolment_1_role: student
enrolment_1_enrolperiod: 1 month

enrolment_2: self
enrolment_2_startdate: 2013-01-30

====Role renaming====

To rename some roles, using the following pattern:

;role_[shortname]
: The new name of the role ''[shortname]''.

'''Example'''

role_student: Apprentice
role_teacher: Master
role_mycustomrole: Jedi

===Course action fields===

Those settings take precedence over the ''Course process'' parameters.

;delete
: 1 to delete the course
;rename
: The shortname to rename the course to
;backupfile
: An absolute path to a backup file (.mbz) to import in the course
;templatecourse
: The short name of a course to import the content from
;reset
: 1 to reset the course

===Mandatory fields===

;shortname
: This field is mandatory for every operation, with the only exception of creating new courses. See details on the course process parameter ''Shortname template'' for more information.
;fullname
: Required when creating a new course.
;category, category_idnumber, category_path
: One of these is required when creating a course.

===Import options===

To prevent unexpected behaviours, you have to specify what you want the tool to be able to do.

;Upload mode
: This allows you to specify if courses can be created and/or updated.
;Update mode
: If you allow courses to be updated, you also have to tell the tool what to update the courses with.
;Allow deletes
: Whether the ''delete'' field is accepted or not
;Allow renames
: Whether the ''rename'' field is accepted or not
;Allow resets
: Whether the ''reset'' field is accepted or not

===Course process===

This allows you to specify actions to be taken on every single courses uploaded.

;Shortname template
: If you are creating courses without a shortname, you can use this field to automatically generate a shortname. This field accepts two placeholders: %i for the ID number, %f for the summary.
;Restore file
: A backup file (.mbz) to import in the course after create/update.
;Restore from course
: The shortname of a course to import content from after create/update.
;Reset after upload
: Whether to reset the course after creating/updating it.

===Default course values===

Those are values that can be set in the web interface for all the fields that are not specified in the CSV file. Note that they are always used when creating a course, but only when specified during update (see ''Update mode'').

==Increasing speed==

When importing the content of a backup file, or another course, you are adviced to enable the setting ''keeptempdirectoriesonbackup''. This will considerably speed up the process of the upload if you are importing multiple times from the same source.

[[de:Kurse hochladen]]
[[es:Subir cursos]]

Upload courses

2013-10-31T08:27:36Z

Jmouneyrac: /* Short file example */

{{Courses}}

{{New features}}
An administrator can upload multiple courses using a text file.

There are many things you can do when using this tool:not only creating courses, but updating or deleting them. You can also update the course enrolment methods or import the content of another course.

==Uploading the file==

You can upload the file by navigating to ''Administration > Site administration > Courses > Upload courses'' and either dragging and dropping the csv file or clicking the button to upload from the file picker.

{|
|[[File:26uploadcourses.png|250px|thumb|Upload courses admin screen]]
|
|[[File:uploadcoursesresults.png|250px|thumb|Courses successfully uploaded]]
|}

''Note:'' It is also possible to use the command-line tool ''admin/tool/uploadcourse/cli/uploadcourse.php''.

When using the web interface, use the ''Preview'' option to see if any errors were detected in the previewed rows. If you proceed with the upload and there were something wrong detected with a course, it will be ignored.

=== Short file example ===
uploadcourse.csv:
<code bash>
shortname,fullname,category,summary, enrolment_1, enrolment_1_role, enrolment_1_enrolperiod, role_student
courserestored,Course 4,1,xx, manual, student, 1 month,
courserestored2,Course 4,1,xx,,,,
courserestored3,Course 4,1,xx,,,,padawan
courserestored4,Course 4,1,xx, manual, student, 1 month, padawan
</code>

==Creating the text file==

The text file to upload courses must be a CSV file. It accepts the following columns which are divided in two categories, the course information, and the course actions.

===Course information fields===

Most of those settings are available on the settings page of a course. Please refer to [[Course settings]] for more information.

;shortname
: The shortname
;fullname
: The full name
;idnumber
: The ID number
;category
: The ID of the category to place the course in. This takes precedence over ''category_idnumber'' and ''category_path''.
;category_idnumber
: The ID number of the category to place the course in. This takes precedence over ''category_path''.
;category_path
: The path of the category to place the course in. If you want to place the course in a category named "Science-Fiction" which is located under the category "Movies", the value to provide is: <code>Movies > Science-Fiction</code>. Note that the separator must be <code>[space]>[space]</code>. Also note that the category MUST exist, it will not be created.
;visible
: 1 if the course is visible, 0 if hidden
;startdate
: The time at which the course starts. Please note that this value is passed to the PHP function [http://php.net/manual/en/function.strtotime.php strtotime] to generate a timestamp.
;summary
: The summary of the course
;format
: The course format to use, this must be a valid course format plugin name. E.g. ''weeks'', ''topics''.
;theme
: The theme to use
;lang
: The language to use
;newsitems
: The number of news items
;showgrades
: 1 to show the gradebook to students, 0 to hide it.
;showreports
: 1 to show the activity reports, 0 to hide it.
;legacyfiles
: 1 to enable the legacy course files, 0 not to.
;maxbytes
: The maximum upload size of the course in bytes. Use 0 for the site limit.
;groupmode
: 0 for ''No groups'', 1 for ''Separate groups'' and 2 for ''Visible groups''.
;groupmodeforce
: 1 to force the group mode, otherwise enter 0.
;enablecompletion
: 1 to enable the activity completion, 0 not to.

====Enrolment fields====

Some fields can be constructed to enable and configure enrolment methods. The fields must be named ''enrolment_[number]'' for the enrolment method name, and ''enrolment_[number]_property'' for its properties.

;enrolment_[number]
: The name of the enrolment method
;enrolment_[number]_delete
: 1 to delete this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_disable
: 1 to disable this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_startdate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enddate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enrolperiod
: Number of seconds, or if not a value understood by strtotime() such as "4 days".
;enrolment_[number]_role
: The role short name
:enrolment_[number]_[property]
; Where property is understood by the specified enrolment method

'''Example'''

enrolment_1: manual
enrolment_1_role: student
enrolment_1_enrolperiod: 1 month

enrolment_2: self
enrolment_2_startdate: 2013-01-30

====Role renaming====

To rename some roles, using the following pattern:

;role_[shortname]
: The new name of the role ''[shortname]''.

'''Example'''

role_student: Apprentice
role_teacher: Master
role_mycustomrole: Jedi

===Course action fields===

Those settings take precedence over the ''Course process'' parameters.

;delete
: 1 to delete the course
;rename
: The shortname to rename the course to
;backupfile
: An absolute path to a backup file (.mbz) to import in the course
;templatecourse
: The short name of a course to import the content from
;reset
: 1 to reset the course

===Mandatory fields===

;shortname
: This field is mandatory for every operation, with the only exception of creating new courses. See details on the course process parameter ''Shortname template'' for more information.
;fullname
: Required when creating a new course.
;category, category_idnumber, category_path
: One of these is required when creating a course.

===Import options===

To prevent unexpected behaviours, you have to specify what you want the tool to be able to do.

;Upload mode
: This allows you to specify if courses can be created and/or updated.
;Update mode
: If you allow courses to be updated, you also have to tell the tool what to update the courses with.
;Allow deletes
: Whether the ''delete'' field is accepted or not
;Allow renames
: Whether the ''rename'' field is accepted or not
;Allow resets
: Whether the ''reset'' field is accepted or not

===Course process===

This allows you to specify actions to be taken on every single courses uploaded.

;Shortname template
: If you are creating courses without a shortname, you can use this field to automatically generate a shortname. This field accepts two placeholders: %i for the ID number, %f for the summary.
;Restore file
: A backup file (.mbz) to import in the course after create/update.
;Restore from course
: The shortname of a course to import content from after create/update.
;Reset after upload
: Whether to reset the course after creating/updating it.

===Default course values===

Those are values that can be set in the web interface for all the fields that are not specified in the CSV file. Note that they are always used when creating a course, but only when specified during update (see ''Update mode'').

==Increasing speed==

When importing the content of a backup file, or another course, you are adviced to enable the setting ''keeptempdirectoriesonbackup''. This will considerably speed up the process of the upload if you are importing multiple times from the same source.

[[de:Kurse hochladen]]
[[es:Subir cursos]]

Upload courses

2013-10-31T08:27:16Z

Jmouneyrac: /* Short file example */

{{Courses}}

{{New features}}
An administrator can upload multiple courses using a text file.

There are many things you can do when using this tool:not only creating courses, but updating or deleting them. You can also update the course enrolment methods or import the content of another course.

==Uploading the file==

You can upload the file by navigating to ''Administration > Site administration > Courses > Upload courses'' and either dragging and dropping the csv file or clicking the button to upload from the file picker.

{|
|[[File:26uploadcourses.png|250px|thumb|Upload courses admin screen]]
|
|[[File:uploadcoursesresults.png|250px|thumb|Courses successfully uploaded]]
|}

''Note:'' It is also possible to use the command-line tool ''admin/tool/uploadcourse/cli/uploadcourse.php''.

When using the web interface, use the ''Preview'' option to see if any errors were detected in the previewed rows. If you proceed with the upload and there were something wrong detected with a course, it will be ignored.

=== Short file example ===
uploadcourse.csv:
<code bash>
shortname,fullname,category,summary
shortname,fullname,category,summary, enrolment_1, enrolment_1_role, enrolment_1_enrolperiod, role_student
courserestored,Course 4,1,xx, manual, student, 1 month,
courserestored2,Course 4,1,xx,,,,
courserestored3,Course 4,1,xx,,,,padawan
courserestored4,Course 4,1,xx, manual, student, 1 month, padawan
</code>

==Creating the text file==

The text file to upload courses must be a CSV file. It accepts the following columns which are divided in two categories, the course information, and the course actions.

===Course information fields===

Most of those settings are available on the settings page of a course. Please refer to [[Course settings]] for more information.

;shortname
: The shortname
;fullname
: The full name
;idnumber
: The ID number
;category
: The ID of the category to place the course in. This takes precedence over ''category_idnumber'' and ''category_path''.
;category_idnumber
: The ID number of the category to place the course in. This takes precedence over ''category_path''.
;category_path
: The path of the category to place the course in. If you want to place the course in a category named "Science-Fiction" which is located under the category "Movies", the value to provide is: <code>Movies > Science-Fiction</code>. Note that the separator must be <code>[space]>[space]</code>. Also note that the category MUST exist, it will not be created.
;visible
: 1 if the course is visible, 0 if hidden
;startdate
: The time at which the course starts. Please note that this value is passed to the PHP function [http://php.net/manual/en/function.strtotime.php strtotime] to generate a timestamp.
;summary
: The summary of the course
;format
: The course format to use, this must be a valid course format plugin name. E.g. ''weeks'', ''topics''.
;theme
: The theme to use
;lang
: The language to use
;newsitems
: The number of news items
;showgrades
: 1 to show the gradebook to students, 0 to hide it.
;showreports
: 1 to show the activity reports, 0 to hide it.
;legacyfiles
: 1 to enable the legacy course files, 0 not to.
;maxbytes
: The maximum upload size of the course in bytes. Use 0 for the site limit.
;groupmode
: 0 for ''No groups'', 1 for ''Separate groups'' and 2 for ''Visible groups''.
;groupmodeforce
: 1 to force the group mode, otherwise enter 0.
;enablecompletion
: 1 to enable the activity completion, 0 not to.

====Enrolment fields====

Some fields can be constructed to enable and configure enrolment methods. The fields must be named ''enrolment_[number]'' for the enrolment method name, and ''enrolment_[number]_property'' for its properties.

;enrolment_[number]
: The name of the enrolment method
;enrolment_[number]_delete
: 1 to delete this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_disable
: 1 to disable this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_startdate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enddate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enrolperiod
: Number of seconds, or if not a value understood by strtotime() such as "4 days".
;enrolment_[number]_role
: The role short name
:enrolment_[number]_[property]
; Where property is understood by the specified enrolment method

'''Example'''

enrolment_1: manual
enrolment_1_role: student
enrolment_1_enrolperiod: 1 month

enrolment_2: self
enrolment_2_startdate: 2013-01-30

====Role renaming====

To rename some roles, using the following pattern:

;role_[shortname]
: The new name of the role ''[shortname]''.

'''Example'''

role_student: Apprentice
role_teacher: Master
role_mycustomrole: Jedi

===Course action fields===

Those settings take precedence over the ''Course process'' parameters.

;delete
: 1 to delete the course
;rename
: The shortname to rename the course to
;backupfile
: An absolute path to a backup file (.mbz) to import in the course
;templatecourse
: The short name of a course to import the content from
;reset
: 1 to reset the course

===Mandatory fields===

;shortname
: This field is mandatory for every operation, with the only exception of creating new courses. See details on the course process parameter ''Shortname template'' for more information.
;fullname
: Required when creating a new course.
;category, category_idnumber, category_path
: One of these is required when creating a course.

===Import options===

To prevent unexpected behaviours, you have to specify what you want the tool to be able to do.

;Upload mode
: This allows you to specify if courses can be created and/or updated.
;Update mode
: If you allow courses to be updated, you also have to tell the tool what to update the courses with.
;Allow deletes
: Whether the ''delete'' field is accepted or not
;Allow renames
: Whether the ''rename'' field is accepted or not
;Allow resets
: Whether the ''reset'' field is accepted or not

===Course process===

This allows you to specify actions to be taken on every single courses uploaded.

;Shortname template
: If you are creating courses without a shortname, you can use this field to automatically generate a shortname. This field accepts two placeholders: %i for the ID number, %f for the summary.
;Restore file
: A backup file (.mbz) to import in the course after create/update.
;Restore from course
: The shortname of a course to import content from after create/update.
;Reset after upload
: Whether to reset the course after creating/updating it.

===Default course values===

Those are values that can be set in the web interface for all the fields that are not specified in the CSV file. Note that they are always used when creating a course, but only when specified during update (see ''Update mode'').

==Increasing speed==

When importing the content of a backup file, or another course, you are adviced to enable the setting ''keeptempdirectoriesonbackup''. This will considerably speed up the process of the upload if you are importing multiple times from the same source.

[[de:Kurse hochladen]]
[[es:Subir cursos]]

Upload courses

2013-10-31T08:15:32Z

Jmouneyrac: /* Quick example */

{{Courses}}

{{New features}}
An administrator can upload multiple courses using a text file.

There are many things you can do when using this tool:not only creating courses, but updating or deleting them. You can also update the course enrolment methods or import the content of another course.

==Uploading the file==

You can upload the file by navigating to ''Administration > Site administration > Courses > Upload courses'' and either dragging and dropping the csv file or clicking the button to upload from the file picker.

{|
|[[File:26uploadcourses.png|250px|thumb|Upload courses admin screen]]
|
|[[File:uploadcoursesresults.png|250px|thumb|Courses successfully uploaded]]
|}

''Note:'' It is also possible to use the command-line tool ''admin/tool/uploadcourse/cli/uploadcourse.php''.

When using the web interface, use the ''Preview'' option to see if any errors were detected in the previewed rows. If you proceed with the upload and there were something wrong detected with a course, it will be ignored.

=== Short file example ===
uploadcourse.csv:
<code bash>
shortname,fullname,category,summary
courserestored,Course 4,1,xx
courserestored2,Course 4,1,xx
courserestored3,Course 4,1,xx
</code>

==Creating the text file==

The text file to upload courses must be a CSV file. It accepts the following columns which are divided in two categories, the course information, and the course actions.

===Course information fields===

Most of those settings are available on the settings page of a course. Please refer to [[Course settings]] for more information.

;shortname
: The shortname
;fullname
: The full name
;idnumber
: The ID number
;category
: The ID of the category to place the course in. This takes precedence over ''category_idnumber'' and ''category_path''.
;category_idnumber
: The ID number of the category to place the course in. This takes precedence over ''category_path''.
;category_path
: The path of the category to place the course in. If you want to place the course in a category named "Science-Fiction" which is located under the category "Movies", the value to provide is: <code>Movies > Science-Fiction</code>. Note that the separator must be <code>[space]>[space]</code>. Also note that the category MUST exist, it will not be created.
;visible
: 1 if the course is visible, 0 if hidden
;startdate
: The time at which the course starts. Please note that this value is passed to the PHP function [http://php.net/manual/en/function.strtotime.php strtotime] to generate a timestamp.
;summary
: The summary of the course
;format
: The course format to use, this must be a valid course format plugin name. E.g. ''weeks'', ''topics''.
;theme
: The theme to use
;lang
: The language to use
;newsitems
: The number of news items
;showgrades
: 1 to show the gradebook to students, 0 to hide it.
;showreports
: 1 to show the activity reports, 0 to hide it.
;legacyfiles
: 1 to enable the legacy course files, 0 not to.
;maxbytes
: The maximum upload size of the course in bytes. Use 0 for the site limit.
;groupmode
: 0 for ''No groups'', 1 for ''Separate groups'' and 2 for ''Visible groups''.
;groupmodeforce
: 1 to force the group mode, otherwise enter 0.
;enablecompletion
: 1 to enable the activity completion, 0 not to.

====Enrolment fields====

Some fields can be constructed to enable and configure enrolment methods. The fields must be named ''enrolment_[number]'' for the enrolment method name, and ''enrolment_[number]_property'' for its properties.

;enrolment_[number]
: The name of the enrolment method
;enrolment_[number]_delete
: 1 to delete this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_disable
: 1 to disable this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_startdate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enddate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enrolperiod
: Number of seconds, or if not a value understood by strtotime() such as "4 days".
;enrolment_[number]_role
: The role short name
:enrolment_[number]_[property]
; Where property is understood by the specified enrolment method

'''Example'''

enrolment_1: manual
enrolment_1_role: student
enrolment_1_enrolperiod: 1 month

enrolment_2: self
enrolment_2_startdate: 2013-01-30

====Role renaming====

To rename some roles, using the following pattern:

;role_[shortname]
: The new name of the role ''[shortname]''.

'''Example'''

role_student: Apprentice
role_teacher: Master
role_mycustomrole: Jedi

===Course action fields===

Those settings take precedence over the ''Course process'' parameters.

;delete
: 1 to delete the course
;rename
: The shortname to rename the course to
;backupfile
: An absolute path to a backup file (.mbz) to import in the course
;templatecourse
: The short name of a course to import the content from
;reset
: 1 to reset the course

===Mandatory fields===

;shortname
: This field is mandatory for every operation, with the only exception of creating new courses. See details on the course process parameter ''Shortname template'' for more information.
;fullname
: Required when creating a new course.
;category, category_idnumber, category_path
: One of these is required when creating a course.

===Import options===

To prevent unexpected behaviours, you have to specify what you want the tool to be able to do.

;Upload mode
: This allows you to specify if courses can be created and/or updated.
;Update mode
: If you allow courses to be updated, you also have to tell the tool what to update the courses with.
;Allow deletes
: Whether the ''delete'' field is accepted or not
;Allow renames
: Whether the ''rename'' field is accepted or not
;Allow resets
: Whether the ''reset'' field is accepted or not

===Course process===

This allows you to specify actions to be taken on every single courses uploaded.

;Shortname template
: If you are creating courses without a shortname, you can use this field to automatically generate a shortname. This field accepts two placeholders: %i for the ID number, %f for the summary.
;Restore file
: A backup file (.mbz) to import in the course after create/update.
;Restore from course
: The shortname of a course to import content from after create/update.
;Reset after upload
: Whether to reset the course after creating/updating it.

===Default course values===

Those are values that can be set in the web interface for all the fields that are not specified in the CSV file. Note that they are always used when creating a course, but only when specified during update (see ''Update mode'').

==Increasing speed==

When importing the content of a backup file, or another course, you are adviced to enable the setting ''keeptempdirectoriesonbackup''. This will considerably speed up the process of the upload if you are importing multiple times from the same source.

[[de:Kurse hochladen]]
[[es:Subir cursos]]

Upload courses

2013-10-31T08:14:58Z

Jmouneyrac: /* Uploading the file */

{{Courses}}

{{New features}}
An administrator can upload multiple courses using a text file.

There are many things you can do when using this tool:not only creating courses, but updating or deleting them. You can also update the course enrolment methods or import the content of another course.

==Uploading the file==

You can upload the file by navigating to ''Administration > Site administration > Courses > Upload courses'' and either dragging and dropping the csv file or clicking the button to upload from the file picker.

{|
|[[File:26uploadcourses.png|250px|thumb|Upload courses admin screen]]
|
|[[File:uploadcoursesresults.png|250px|thumb|Courses successfully uploaded]]
|}

''Note:'' It is also possible to use the command-line tool ''admin/tool/uploadcourse/cli/uploadcourse.php''.

When using the web interface, use the ''Preview'' option to see if any errors were detected in the previewed rows. If you proceed with the upload and there were something wrong detected with a course, it will be ignored.

=== Quick example ===
uploadcourse.csv
<code bash>
shortname,fullname,category,summary
courserestored,Course 4,1,xx
courserestored2,Course 4,1,xx
courserestored3,Course 4,1,xx
</code>

==Creating the text file==

The text file to upload courses must be a CSV file. It accepts the following columns which are divided in two categories, the course information, and the course actions.

===Course information fields===

Most of those settings are available on the settings page of a course. Please refer to [[Course settings]] for more information.

;shortname
: The shortname
;fullname
: The full name
;idnumber
: The ID number
;category
: The ID of the category to place the course in. This takes precedence over ''category_idnumber'' and ''category_path''.
;category_idnumber
: The ID number of the category to place the course in. This takes precedence over ''category_path''.
;category_path
: The path of the category to place the course in. If you want to place the course in a category named "Science-Fiction" which is located under the category "Movies", the value to provide is: <code>Movies > Science-Fiction</code>. Note that the separator must be <code>[space]>[space]</code>. Also note that the category MUST exist, it will not be created.
;visible
: 1 if the course is visible, 0 if hidden
;startdate
: The time at which the course starts. Please note that this value is passed to the PHP function [http://php.net/manual/en/function.strtotime.php strtotime] to generate a timestamp.
;summary
: The summary of the course
;format
: The course format to use, this must be a valid course format plugin name. E.g. ''weeks'', ''topics''.
;theme
: The theme to use
;lang
: The language to use
;newsitems
: The number of news items
;showgrades
: 1 to show the gradebook to students, 0 to hide it.
;showreports
: 1 to show the activity reports, 0 to hide it.
;legacyfiles
: 1 to enable the legacy course files, 0 not to.
;maxbytes
: The maximum upload size of the course in bytes. Use 0 for the site limit.
;groupmode
: 0 for ''No groups'', 1 for ''Separate groups'' and 2 for ''Visible groups''.
;groupmodeforce
: 1 to force the group mode, otherwise enter 0.
;enablecompletion
: 1 to enable the activity completion, 0 not to.

====Enrolment fields====

Some fields can be constructed to enable and configure enrolment methods. The fields must be named ''enrolment_[number]'' for the enrolment method name, and ''enrolment_[number]_property'' for its properties.

;enrolment_[number]
: The name of the enrolment method
;enrolment_[number]_delete
: 1 to delete this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_disable
: 1 to disable this enrolment method from the course, if set to 1 all the other properties will be ignored.
;enrolment_[number]_startdate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enddate
: The enrolment start date. This value is passed to the PHP function strtotime().
;enrolment_[number]_enrolperiod
: Number of seconds, or if not a value understood by strtotime() such as "4 days".
;enrolment_[number]_role
: The role short name
:enrolment_[number]_[property]
; Where property is understood by the specified enrolment method

'''Example'''

enrolment_1: manual
enrolment_1_role: student
enrolment_1_enrolperiod: 1 month

enrolment_2: self
enrolment_2_startdate: 2013-01-30

====Role renaming====

To rename some roles, using the following pattern:

;role_[shortname]
: The new name of the role ''[shortname]''.

'''Example'''

role_student: Apprentice
role_teacher: Master
role_mycustomrole: Jedi

===Course action fields===

Those settings take precedence over the ''Course process'' parameters.

;delete
: 1 to delete the course
;rename
: The shortname to rename the course to
;backupfile
: An absolute path to a backup file (.mbz) to import in the course
;templatecourse
: The short name of a course to import the content from
;reset
: 1 to reset the course

===Mandatory fields===

;shortname
: This field is mandatory for every operation, with the only exception of creating new courses. See details on the course process parameter ''Shortname template'' for more information.
;fullname
: Required when creating a new course.
;category, category_idnumber, category_path
: One of these is required when creating a course.

===Import options===

To prevent unexpected behaviours, you have to specify what you want the tool to be able to do.

;Upload mode
: This allows you to specify if courses can be created and/or updated.
;Update mode
: If you allow courses to be updated, you also have to tell the tool what to update the courses with.
;Allow deletes
: Whether the ''delete'' field is accepted or not
;Allow renames
: Whether the ''rename'' field is accepted or not
;Allow resets
: Whether the ''reset'' field is accepted or not

===Course process===

This allows you to specify actions to be taken on every single courses uploaded.

;Shortname template
: If you are creating courses without a shortname, you can use this field to automatically generate a shortname. This field accepts two placeholders: %i for the ID number, %f for the summary.
;Restore file
: A backup file (.mbz) to import in the course after create/update.
;Restore from course
: The shortname of a course to import content from after create/update.
;Reset after upload
: Whether to reset the course after creating/updating it.

===Default course values===

Those are values that can be set in the web interface for all the fields that are not specified in the CSV file. Note that they are always used when creating a course, but only when specified during update (see ''Update mode'').

==Increasing speed==

When importing the content of a backup file, or another course, you are adviced to enable the setting ''keeptempdirectoriesonbackup''. This will considerably speed up the process of the upload if you are importing multiple times from the same source.

[[de:Kurse hochladen]]
[[es:Subir cursos]]

Upgrading

2013-10-25T07:27:29Z

Jmouneyrac: /* Possible issues that may affect you in Moodle 2.6 */

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Check that your server meets all requirements for 2.6 in ''Administration > Site administration > Server > [[Environment]]''.

Note: You can only upgrade to Moodle 2.6 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.

==Before you upgrade your site for real==

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

== Backup important data ==

There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

==Put your site into maintenance mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in.

== Check for add-on updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed add-ons automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating add-ons manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.6 version available for any add-ons (including themes) that you have previously installed on your site. If so, download the add-on package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing add-ons]]).

The upgrade of the add-on will then happen as part of the Moodle upgrade process.

If an out-of-date add-on causes your upgrade to fail, you can usually delete the add-on code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

== Install the new Moodle software ==

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any custom add-ons on your site you should add them to the new code tree now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-2.6.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')

if necessary.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle 2.6 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.

== Finishing the upgrade ==

The last step is to trigger the upgrade processes within Moodle.

To do this just go to ''Administration > Site administration > Notifications''.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

==After upgrading==

The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 2.6 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.6 config-dist.php.

==Fatal error: Maximum execution time of 30 seconds exceeded...==

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598 .

==Possible issues that may affect you in Moodle 2.6==

* "My Mobile" theme has been removed (see MDL-40874).During the upgrade process "My Mobile" theme will be uninstalled and all its settings will be deleted. "My Mobile" theme and its extending themes will fallback to the mobile friendly "Clean" theme. If you wish to keep "My Mobile" theme and its settings, BEFORE UPGRADING you can copy the files from the unmaintained plugin into theme/mymobile. The unmaintained plugin can be downloaded on the [https://moodle.org/plugins/pluginversion.php?id=4563 Moodle.org plugins repository].

=== Moodle 2.3, 2.4 and 2.5 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3]
* [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4]
* [https://docs.moodle.org/25/en/Upgrading Upgrading to Moodle 2.5]

==See also==

* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[dev:Moodle 2.6 release notes|Moodle 2.6 release notes]]
* [[dev:Upgrade API|Upgrade API]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

error/local hub/freshmoodleregistrationerror2

2013-05-06T04:15:04Z

Jmouneyrac: Created page with "You are trying to register a site with a url that was previously used by another registered site. A request to register this url has already been sent to the site administrator o..."

You are trying to register a site with a url that was previously used by another registered site. A request to register this url has already been sent to the site administrator of this other site. This administrator (probably you) need to confirm the new registration.

== Also see ==
* https://docs.moodle.org/310/en/error/local_hub/freshmoodleregistrationerror

error/local hub/freshmoodleregistrationerror

2013-05-06T04:09:04Z

Jmouneyrac: Created page with "You are trying to register a site with a url that was previously used by a registered site. This alert is due to one of these cases: * you try to register a fresh moodle site o..."

You are trying to register a site with a url that was previously used by a registered site.

This alert is due to one of these cases:
* you try to register a fresh moodle site on a previously registered url
* you try to register a registered moodle site on a different address, this address having been registered too with a different site.

An email should have been sent to the previously registered site administrator to confirm that you are the real owner of the site. The hub only sends one email per day.

The previously registered site administrator will have the choice to delete the previous registration record from the hub. If he/she decide to do it, then you will be able to register your "new" site. Note that except if the site admin changed, you should be this previously registered administrator, but this step is required to avoid hacking. Thank you.

Hub administration

2013-04-08T10:04:49Z

Jmouneyrac: /* How to set up a Moodle Hub server */

{{Community hubs}}
==Deciding to run a Hub==

Running a hub server is not something you should undertake lightly.

As the hub administrator you are responsible for the content in the hub, and you need to put in place processes to:
* verify all the course content is clean (of porn or malicious javascript)
* manage registered sites and their status
* maintain the quality of the listings through editing

=== Minimal Requirements ===

Below is a list of Minimal requirements for running a Moodle Community Hub.

* MySQL - minimum version 5.0.25
* PHP 5.3.2
* Apache
* ensure that the site you will be registering does not use any upper case letters (even though those are perfectly valid). ''EG: moodle.org/2012-Spring will not work!''
* ensure that the following php.ini variables are set to "On"
** allow_url_fopen: This setting is required the hub to be able to register a site. If this option is not enabled, you will be given the [[error/local_hub/cannotregisternotavailablesite|cannotregisternotavailablesite]] error. Related tracker issue: https://tracker.moodle.org/browse/CONTRIB-3063
* mod_security in Apache version 1 and mod_security2 in Apache version 2 will return a 403 forbidden error when a URL that is not the local domain is passed as a get variable. mod_security on either the hub or client servers will block the completion of the client/hub registration process, even to MOOCH, as within the registration process URL's are passed as get variables a number of times. An exception can be added to mod_security in Apache version 1 via a local .htacess file. However, this ability was removed in mod_security2. In mod_security2 the exception must be added to mod_security.conf of /conf.d. Related forum discussion: http://moodle.org/mod/forum/discuss.php?d=188933

==How the hub software works==

The hub software is implemented as a separate "local" plugin designed to be added to a standard install of Moodle 2.0 or later. In this way the hub gets to use on all the features in the Moodle core API and benefits from maintenance of the core code.

Once installed the whole site gets a new frontpage with a simple search box (see http://hub.moodle.org/ for example).

Please don't add the hub capabilities to an existing Moodle site with real courses. Although it may work, there are some opportunities for GUI confusion and some unknowns when it comes to security, so please just avoid it. Moodle is free, so it's trivial to install another clean copy to build your hub with.

==How to set up a Moodle Hub server==

# Install Moodle 2.0 or later somewhere on a web server with a nice URL.
# Download the latest hub plugin from https://github.com/moodlehq/moodle-local_hub
# Save the zip into the /local directory of Moodle and unzip, producing /local/hub
# Visit the "Notifications" page in Moodle (/admin) to complete the upgrade and install the hub software.
# Uncheck password policy (search 'passwordpolicy' in admin search)
# Allow extended characters in usernames (search 'extendedusernamechars' in admin search)
# Enable web services for the hub (''Settings > Site Administration > Advanced features'')
# Enable the XML-RPC protocol (''Settings > Site Administration > Plugins > Web services > Manage protocols'')
# Set up the SMTP (''Settings > Site Administration > Plugins > Message outputs > Email'')
# Set up the recaptcha (''Settings > Site Administration > Plugins > Authentication > Manage authentication'')
# Set up your hub (''Settings > Site Administration > Hub > Settings'') Supply a description, enable the hub, supply a hub password.

Congratulations! You now have a working hub with no content!

==Site registration==

Only sites that are registered with the hub are allowed to publish content there.

Sites register on the hub via ''Settings > Site administration > Server > Hubs''.

==Hub registration==

You can also register your hub with the Moodle hub Directory, a listing of many hubs from around the world, enabling people from all over the world to find your hub and search the courses within it. You may want to wait until you have some content before you register.

==Managing sites==
In ''Settings > Site administration > Hub > Manage sites'', you can:
* Prioritise a site: during a search, course from prioritised sites appear on top of the list. A prioritised site is always trusted.
* Trust a site: when a site is trusted, any published course is immediately available
* Delete a site: delete a site from the database. A message will be sent to the site administrator.
* Settings: you can change some information as the name, the description, the language...
* Make a site visible: only site declared as visible appear on the the site list (currently the site list hasn't been implemented)

==Managing courses==
In ''Settings > Site administration > Hub > Manage course'', you can:
* Delete a course: delete a course from the database.
* Settings: you can change some information as the name, the description, the language...
* Make a course visible: decide if the course is displayed on search result

== Important things about roles, users and web services ==
A hub server uses intensively Moodle web service 2.0. For this reason it is important to understand the [https://docs.moodle.org/en/Web_Services web services administration], and what happens if you change some roles/users/services.

=== Roles ===
The hub server creates on the fly some roles that you should '''never delete/modify''':
* one role for the hub directory
* one role for registered sites
* one role for public sites

=== Users ===
The hub server creates on the fly some users that you should '''never delete/modify''':
* one user for the hub directory
* one user for public access
* as many users as registered sites

=== Services ===
The hub creates during installation some web services that you should '''never delete/modify''':
* one service for Hub directory
* one service for Registered sites
* one service for Public sites

It also creates tokens on the fly. These tokens are not displayed on the token management list, so you cannot accidentally delete them.

==See also==

*[[Site registration]]

[[ja:ハブ管理]]

Hub administration

2013-04-08T10:03:16Z

Jmouneyrac: /* How to set up a Moodle Hub server */

{{Community hubs}}
==Deciding to run a Hub==

Running a hub server is not something you should undertake lightly.

As the hub administrator you are responsible for the content in the hub, and you need to put in place processes to:
* verify all the course content is clean (of porn or malicious javascript)
* manage registered sites and their status
* maintain the quality of the listings through editing

=== Minimal Requirements ===

Below is a list of Minimal requirements for running a Moodle Community Hub.

* MySQL - minimum version 5.0.25
* PHP 5.3.2
* Apache
* ensure that the site you will be registering does not use any upper case letters (even though those are perfectly valid). ''EG: moodle.org/2012-Spring will not work!''
* ensure that the following php.ini variables are set to "On"
** allow_url_fopen: This setting is required the hub to be able to register a site. If this option is not enabled, you will be given the [[error/local_hub/cannotregisternotavailablesite|cannotregisternotavailablesite]] error. Related tracker issue: https://tracker.moodle.org/browse/CONTRIB-3063
* mod_security in Apache version 1 and mod_security2 in Apache version 2 will return a 403 forbidden error when a URL that is not the local domain is passed as a get variable. mod_security on either the hub or client servers will block the completion of the client/hub registration process, even to MOOCH, as within the registration process URL's are passed as get variables a number of times. An exception can be added to mod_security in Apache version 1 via a local .htacess file. However, this ability was removed in mod_security2. In mod_security2 the exception must be added to mod_security.conf of /conf.d. Related forum discussion: http://moodle.org/mod/forum/discuss.php?d=188933

==How the hub software works==

The hub software is implemented as a separate "local" plugin designed to be added to a standard install of Moodle 2.0 or later. In this way the hub gets to use on all the features in the Moodle core API and benefits from maintenance of the core code.

Once installed the whole site gets a new frontpage with a simple search box (see http://hub.moodle.org/ for example).

Please don't add the hub capabilities to an existing Moodle site with real courses. Although it may work, there are some opportunities for GUI confusion and some unknowns when it comes to security, so please just avoid it. Moodle is free, so it's trivial to install another clean copy to build your hub with.

==How to set up a Moodle Hub server==

# Install Moodle 2.0 or later somewhere on a web server with a nice URL.
# Download the latest hub plugin from https://github.com/moodlehq/moodle-local_hub
# Save the zip into the /local directory of Moodle and unzip, producing /local/hub
# Visit the "Notifications" page in Moodle (/admin) to complete the upgrade and install the hub software.
# Uncheck password policy (passwordpolicy)
# Allow extended characters in usernames (extendedusernamechars)
# Enable web services for the hub (''Settings > Site Administration > Advanced features'')
# Enable the XML-RPC protocol (''Settings > Site Administration > Plugins > Web services > Manage protocols'')
# Set up the SMTP (''Settings > Site Administration > Plugins > Message outputs > Email'')
# Set up the recaptcha (''Settings > Site Administration > Plugins > Authentication > Manage authentication'')
# Set up your hub (''Settings > Site Administration > Hub > Settings'') Supply a description, enable the hub, supply a hub password.

Congratulations! You now have a working hub with no content!

==Site registration==

Only sites that are registered with the hub are allowed to publish content there.

Sites register on the hub via ''Settings > Site administration > Server > Hubs''.

==Hub registration==

You can also register your hub with the Moodle hub Directory, a listing of many hubs from around the world, enabling people from all over the world to find your hub and search the courses within it. You may want to wait until you have some content before you register.

==Managing sites==
In ''Settings > Site administration > Hub > Manage sites'', you can:
* Prioritise a site: during a search, course from prioritised sites appear on top of the list. A prioritised site is always trusted.
* Trust a site: when a site is trusted, any published course is immediately available
* Delete a site: delete a site from the database. A message will be sent to the site administrator.
* Settings: you can change some information as the name, the description, the language...
* Make a site visible: only site declared as visible appear on the the site list (currently the site list hasn't been implemented)

==Managing courses==
In ''Settings > Site administration > Hub > Manage course'', you can:
* Delete a course: delete a course from the database.
* Settings: you can change some information as the name, the description, the language...
* Make a course visible: decide if the course is displayed on search result

== Important things about roles, users and web services ==
A hub server uses intensively Moodle web service 2.0. For this reason it is important to understand the [https://docs.moodle.org/en/Web_Services web services administration], and what happens if you change some roles/users/services.

=== Roles ===
The hub server creates on the fly some roles that you should '''never delete/modify''':
* one role for the hub directory
* one role for registered sites
* one role for public sites

=== Users ===
The hub server creates on the fly some users that you should '''never delete/modify''':
* one user for the hub directory
* one user for public access
* as many users as registered sites

=== Services ===
The hub creates during installation some web services that you should '''never delete/modify''':
* one service for Hub directory
* one service for Registered sites
* one service for Public sites

It also creates tokens on the fly. These tokens are not displayed on the token management list, so you cannot accidentally delete them.

==See also==

*[[Site registration]]

[[ja:ハブ管理]]

Hub administration

2013-04-08T09:46:01Z

Jmouneyrac: /* Minimal Requirements */

{{Community hubs}}
==Deciding to run a Hub==

Running a hub server is not something you should undertake lightly.

As the hub administrator you are responsible for the content in the hub, and you need to put in place processes to:
* verify all the course content is clean (of porn or malicious javascript)
* manage registered sites and their status
* maintain the quality of the listings through editing

=== Minimal Requirements ===

Below is a list of Minimal requirements for running a Moodle Community Hub.

* MySQL - minimum version 5.0.25
* PHP 5.3.2
* Apache
* ensure that the site you will be registering does not use any upper case letters (even though those are perfectly valid). ''EG: moodle.org/2012-Spring will not work!''
* ensure that the following php.ini variables are set to "On"
** allow_url_fopen: This setting is required the hub to be able to register a site. If this option is not enabled, you will be given the [[error/local_hub/cannotregisternotavailablesite|cannotregisternotavailablesite]] error. Related tracker issue: https://tracker.moodle.org/browse/CONTRIB-3063
* mod_security in Apache version 1 and mod_security2 in Apache version 2 will return a 403 forbidden error when a URL that is not the local domain is passed as a get variable. mod_security on either the hub or client servers will block the completion of the client/hub registration process, even to MOOCH, as within the registration process URL's are passed as get variables a number of times. An exception can be added to mod_security in Apache version 1 via a local .htacess file. However, this ability was removed in mod_security2. In mod_security2 the exception must be added to mod_security.conf of /conf.d. Related forum discussion: http://moodle.org/mod/forum/discuss.php?d=188933

==How the hub software works==

The hub software is implemented as a separate "local" plugin designed to be added to a standard install of Moodle 2.0 or later. In this way the hub gets to use on all the features in the Moodle core API and benefits from maintenance of the core code.

Once installed the whole site gets a new frontpage with a simple search box (see http://hub.moodle.org/ for example).

Please don't add the hub capabilities to an existing Moodle site with real courses. Although it may work, there are some opportunities for GUI confusion and some unknowns when it comes to security, so please just avoid it. Moodle is free, so it's trivial to install another clean copy to build your hub with.

==How to set up a Moodle Hub server==

# Install Moodle 2.0 or later somewhere on a web server with a nice URL.
# Download the latest hub plugin from https://github.com/moodlehq/moodle-local_hub
# Save the zip into the /local directory of Moodle and unzip, producing /local/hub
# Visit the "Notifications" page in Moodle (/admin) to complete the upgrade and install the hub software.
# Enable web services for the hub (''Settings > Site Administration > Advanced features'')
# Enable the XML-RPC protocol (''Settings > Site Administration > Plugins > Web services > Manage protocols'')
# Set up the SMTP (''Settings > Site Administration > Plugins > Message outputs > Email'')
# Set up the recaptcha (''Settings > Site Administration > Plugins > Authentication > Manage authentication'')
# Set up your hub (''Settings > Site Administration > Hub > Settings'') Supply a description, enable the hub, supply a hub password.

Congratulations! You now have a working hub with no content!

==Site registration==

Only sites that are registered with the hub are allowed to publish content there.

Sites register on the hub via ''Settings > Site administration > Server > Hubs''.

==Hub registration==

You can also register your hub with the Moodle hub Directory, a listing of many hubs from around the world, enabling people from all over the world to find your hub and search the courses within it. You may want to wait until you have some content before you register.

==Managing sites==
In ''Settings > Site administration > Hub > Manage sites'', you can:
* Prioritise a site: during a search, course from prioritised sites appear on top of the list. A prioritised site is always trusted.
* Trust a site: when a site is trusted, any published course is immediately available
* Delete a site: delete a site from the database. A message will be sent to the site administrator.
* Settings: you can change some information as the name, the description, the language...
* Make a site visible: only site declared as visible appear on the the site list (currently the site list hasn't been implemented)

==Managing courses==
In ''Settings > Site administration > Hub > Manage course'', you can:
* Delete a course: delete a course from the database.
* Settings: you can change some information as the name, the description, the language...
* Make a course visible: decide if the course is displayed on search result

== Important things about roles, users and web services ==
A hub server uses intensively Moodle web service 2.0. For this reason it is important to understand the [https://docs.moodle.org/en/Web_Services web services administration], and what happens if you change some roles/users/services.

=== Roles ===
The hub server creates on the fly some roles that you should '''never delete/modify''':
* one role for the hub directory
* one role for registered sites
* one role for public sites

=== Users ===
The hub server creates on the fly some users that you should '''never delete/modify''':
* one user for the hub directory
* one user for public access
* as many users as registered sites

=== Services ===
The hub creates during installation some web services that you should '''never delete/modify''':
* one service for Hub directory
* one service for Registered sites
* one service for Public sites

It also creates tokens on the fly. These tokens are not displayed on the token management list, so you cannot accidentally delete them.

==See also==

*[[Site registration]]

[[ja:ハブ管理]]

Hub administration

2013-04-08T09:44:09Z

Jmouneyrac: /* Minimal Requirements */

{{Community hubs}}
==Deciding to run a Hub==

Running a hub server is not something you should undertake lightly.

As the hub administrator you are responsible for the content in the hub, and you need to put in place processes to:
* verify all the course content is clean (of porn or malicious javascript)
* manage registered sites and their status
* maintain the quality of the listings through editing

=== Minimal Requirements ===

Below is a list of Minimal requirements for running a Moodle Community Hub.

* Apache 2+ / MySQL 5+ / PHP 5.2+
* verify the server meets the requirements to run the latest version of Moodle found in the documents at [[Installing_Moodle#Requirements|Installing_Moodle]] and [[PHP]]
* ensure that the site you will be registering does not use any upper case letters (even though those are perfectly valid). ''EG: moodle.org/2012-Spring will not work!''
* ensure that the following php.ini variables are set to "On"
** allow_url_fopen: This setting is required the hub to be able to register a site. If this option is not enabled, you will be given the [[error/local_hub/cannotregisternotavailablesite|cannotregisternotavailablesite]] error. Related tracker issue: https://tracker.moodle.org/browse/CONTRIB-3063
* mod_security in Apache version 1 and mod_security2 in Apache version 2 will return a 403 forbidden error when a URL that is not the local domain is passed as a get variable. mod_security on either the hub or client servers will block the completion of the client/hub registration process, even to MOOCH, as within the registration process URL's are passed as get variables a number of times. An exception can be added to mod_security in Apache version 1 via a local .htacess file. However, this ability was removed in mod_security2. In mod_security2 the exception must be added to mod_security.conf of /conf.d. Related forum discussion: http://moodle.org/mod/forum/discuss.php?d=188933

==How the hub software works==

The hub software is implemented as a separate "local" plugin designed to be added to a standard install of Moodle 2.0 or later. In this way the hub gets to use on all the features in the Moodle core API and benefits from maintenance of the core code.

Once installed the whole site gets a new frontpage with a simple search box (see http://hub.moodle.org/ for example).

Please don't add the hub capabilities to an existing Moodle site with real courses. Although it may work, there are some opportunities for GUI confusion and some unknowns when it comes to security, so please just avoid it. Moodle is free, so it's trivial to install another clean copy to build your hub with.

==How to set up a Moodle Hub server==

# Install Moodle 2.0 or later somewhere on a web server with a nice URL.
# Download the latest hub plugin from https://github.com/moodlehq/moodle-local_hub
# Save the zip into the /local directory of Moodle and unzip, producing /local/hub
# Visit the "Notifications" page in Moodle (/admin) to complete the upgrade and install the hub software.
# Enable web services for the hub (''Settings > Site Administration > Advanced features'')
# Enable the XML-RPC protocol (''Settings > Site Administration > Plugins > Web services > Manage protocols'')
# Set up the SMTP (''Settings > Site Administration > Plugins > Message outputs > Email'')
# Set up the recaptcha (''Settings > Site Administration > Plugins > Authentication > Manage authentication'')
# Set up your hub (''Settings > Site Administration > Hub > Settings'') Supply a description, enable the hub, supply a hub password.

Congratulations! You now have a working hub with no content!

==Site registration==

Only sites that are registered with the hub are allowed to publish content there.

Sites register on the hub via ''Settings > Site administration > Server > Hubs''.

==Hub registration==

You can also register your hub with the Moodle hub Directory, a listing of many hubs from around the world, enabling people from all over the world to find your hub and search the courses within it. You may want to wait until you have some content before you register.

==Managing sites==
In ''Settings > Site administration > Hub > Manage sites'', you can:
* Prioritise a site: during a search, course from prioritised sites appear on top of the list. A prioritised site is always trusted.
* Trust a site: when a site is trusted, any published course is immediately available
* Delete a site: delete a site from the database. A message will be sent to the site administrator.
* Settings: you can change some information as the name, the description, the language...
* Make a site visible: only site declared as visible appear on the the site list (currently the site list hasn't been implemented)

==Managing courses==
In ''Settings > Site administration > Hub > Manage course'', you can:
* Delete a course: delete a course from the database.
* Settings: you can change some information as the name, the description, the language...
* Make a course visible: decide if the course is displayed on search result

== Important things about roles, users and web services ==
A hub server uses intensively Moodle web service 2.0. For this reason it is important to understand the [https://docs.moodle.org/en/Web_Services web services administration], and what happens if you change some roles/users/services.

=== Roles ===
The hub server creates on the fly some roles that you should '''never delete/modify''':
* one role for the hub directory
* one role for registered sites
* one role for public sites

=== Users ===
The hub server creates on the fly some users that you should '''never delete/modify''':
* one user for the hub directory
* one user for public access
* as many users as registered sites

=== Services ===
The hub creates during installation some web services that you should '''never delete/modify''':
* one service for Hub directory
* one service for Registered sites
* one service for Public sites

It also creates tokens on the fly. These tokens are not displayed on the token management list, so you cannot accidentally delete them.

==See also==

*[[Site registration]]

[[ja:ハブ管理]]

Moodle app

2013-04-04T11:11:55Z

Jmouneyrac:

{{Mobile}}
'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.

== Features ==
* 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

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

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.

==Installing the mobile app==

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

iOS: Coming soon

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

==How to report a bug==

# Log in to the [http://tracker.moodle.org/ Moodle Tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# ''Check whether the issue has already been reported by searching''
# 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]]

Moodle app

2013-03-29T00:52:53Z

Jmouneyrac: /* Moodle sites must be enabled for the app to access them */

{{Mobile}}
'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.

== Features ==
* 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

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

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.

==Installing the mobile app==

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

iOS: Coming soon

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

==How to report a bug==

# Log in to the [http://tracker.moodle.org/ Moodle Tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# ''Check whether the issue has already been reported by searching''
# 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]]

Moodle app

2013-03-27T03:39:26Z

Jmouneyrac: /* Features */

{{Mobile}}
'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.

== Features ==
* 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

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

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

# In ''Settings > Site administration > Advanced features'' tick the 'Enable web services' checkbox, then click the button to save changes
# In ''Site administration > Plugins > Web services > Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes. (Ticking the 'Enable web services' checkbox should enable this also, but doesn't always.)

==Installing the mobile app==

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

iOS: Coming soon

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

==How to report a bug==

# Log in to the [http://tracker.moodle.org/ Moodle Tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# ''Check whether the issue has already been reported by searching''
# 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)

=== 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 filled in the tracker.

== See also ==

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

Moodle app

2013-03-27T03:29:03Z

Jmouneyrac:

{{Mobile}}
'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.

== Features ==
* 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 a PDF/DOC/Image/HTML resource

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

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

# In ''Settings > Site administration > Advanced features'' tick the 'Enable web services' checkbox, then click the button to save changes
# In ''Site administration > Plugins > Web services > Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes. (Ticking the 'Enable web services' checkbox should enable this also, but doesn't always.)

==Installing the mobile app==

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

iOS: Coming soon

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

==How to report a bug==

# Log in to the [http://tracker.moodle.org/ Moodle Tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# ''Check whether the issue has already been reported by searching''
# 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)

=== 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 filled in the tracker.

== See also ==

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

Moodle app

2013-03-22T03:05:20Z

Jmouneyrac: /* What is the app used for */

{{Mobile}}
'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.

== Features ==
* 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 a PDF/DOC/Image/HTML resource

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

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

# In ''Settings > Site administration > Advanced features'' tick the 'Enable web services' checkbox, then click the button to save changes
# In ''Site administration > Plugins > Web services > Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes. (Ticking the 'Enable web services' checkbox should enable this also, but doesn't always.)

==Installing the mobile app==

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

iOS: Coming soon

==Connecting to your Moodle site ==

==Browsing courses==

''Information coming soon...''

==Uploading photos and audio==

''Information coming soon...''

==Managing multiple Moodle sites==

==Notifications==

Currently not available

==Settings==

''Information coming soon...''

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

==How to report a bug==

# Log in to the [http://tracker.moodle.org/ Moodle Tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# ''Check whether the issue has already been reported by searching''
# 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 -> 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)

== See also ==

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

Moodle app

2013-03-22T02:48:06Z

Jmouneyrac:

{{Mobile}}
'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) is replacing the old mobile app for iPhone, ''My Moodle''.

== What is the app used for ==
The app offers few features which have for advantage to be done quicker than on the Moodle site or to be done offline.
* upload a picture into your private file (so you can use it in the file picker straight away)
* record an audio file and upload into your private file (so you can use it in the file picker straight away)
* send a private message to a student/teacher (faster than in Moodle + it works offline)
* take a personal/reminder note about someone else (faster than in Moodle + it works offline)
* add someone to your phone contact (you don’t need to copy/type details manually)
* call someone touching the phone number (you don’t need to copy/type the number in your dialapp)
* locate someone address on Google map (you don’t need to copy/type the address in the map)
* view a PDF/DOC/Image/HTML resource (some resources can be downloaded to be used offline on your phone)

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

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

# In ''Settings > Site administration > Advanced features'' tick the 'Enable web services' checkbox, then click the button to save changes
# In ''Site administration > Plugins > Web services > Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes. (Ticking the 'Enable web services' checkbox should enable this also, but doesn't always.)

==Installing the mobile app==

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

iOS: Coming soon

==Connecting to your Moodle site ==

==Browsing courses==

''Information coming soon...''

==Uploading photos and audio==

''Information coming soon...''

==Managing multiple Moodle sites==

==Notifications==

Currently not available

==Settings==

''Information coming soon...''

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

==How to report a bug==

# Log in to the [http://tracker.moodle.org/ Moodle Tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# ''Check whether the issue has already been reported by searching''
# 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 -> 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)

== See also ==

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

Mobile web services

2012-11-26T07:29:22Z

Jmouneyrac:

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

Mobile web services

2012-11-26T07:27:28Z

Jmouneyrac:

{{Web services}}
Moodle comes with a built-in web service designed for mobile applications. It is required to run the official [[Mobile app]]. 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]]

Hub administration

2012-05-16T06:53:05Z

Jmouneyrac: /* How to set up a Moodle Hub server */

{{Community hubs}}
==Deciding to run a Hub==

Running a hub server is not something you should undertake lightly.

As the hub administrator you are responsible for the content in the hub, and you need to put in place processes to:
* verify all the course content is clean (of porn or malicious javascript)
* manage registered sites and their status
* maintain the quality of the listings through editing

=== Minimal Requirements ===

Below is a list of Minimal requirements for running a Moodle Community Hub.

* verify the server meets the requirements to run the latest version of Moodle found in the documents at [[Installing_Moodle#Requirements|Installing_Moodle]] and [[PHP]]
* ensure that the following php.ini variables are set to "On"
** allow_url_fopen: This setting is required the hub to be able to register a site. If this option is not enabled, you will be given the [[error/local_hub/cannotregisternotavailablesite|cannotregisternotavailablesite]] error. Related tracker issue: https://tracker.moodle.org/browse/CONTRIB-3063
* mod_security in Apache version 1 and mod_security2 in Apache version 2 will return a 403 forbidden error when a URL that is not the local domain is passed as a get variable. mod_security on either the hub or client servers will block the completion of the client/hub registration process, even to MOOCH, as within the registration process URL's are passed as get variables a number of times. An exception can be added to mod_security in Apache version 1 via a local .htacess file. However, this ability was removed in mod_security2. In mod_security2 the exception must be added to mod_security.conf of /conf.d. Related forum discussion: http://moodle.org/mod/forum/discuss.php?d=188933

==How the hub software works==

The hub software is implemented as a separate "local" plugin designed to be added to a standard install of Moodle 2.0 or later. In this way the hub gets to use on all the features in the Moodle core API and benefits from maintenance of the core code.

Once installed the whole site gets a new frontpage with a simple search box (see http://hub.moodle.org/ for example).

Please don't add the hub capabilities to an existing Moodle site with real courses. Although it may work, there are some opportunities for GUI confusion and some unknowns when it comes to security, so please just avoid it. Moodle is free, so it's trivial to install another clean copy to build your hub with.

==How to set up a Moodle Hub server==

# Install Moodle 2.0 or later somewhere on a web server with a nice URL.
# Download the latest hub plugin from http://download.moodle.org/download.php/plugins/local/hub.zip
# Save the zip into the /local directory of Moodle and unzip, producing /local/hub
# Visit the "Notifications" page in Moodle (/admin) to complete the upgrade and install the hub software.
# Enable web services for the hub ('''Site Administration > Advanced features''')
# Enable the XML-RPC protocol ('''Site Administration > Plugins > Web services > Manage protocols''')
# Set up the SMTP ('''Site Administration > Plugins > Message outputs > Email''')
#Set up the recaptcha ('''Site Administration > Plugins > Authentication > Manage authentication''')
# Set up your hub ('''Site Administration > Hub > Settings''')
# In '''Site Administration > Security > Site policies''' enable ''Allow extended characters in usernames''. This step will be automatically executed when CONTRIB-3646 is done.

Congratulations! You now have a working hub with no content!

==Site registration==

Only sites that are registered with the hub are allowed to publish content there.

Sites register on the hub via '''Site Administration > Registration'''

==Hub registration==

You can also register your hub with the Moodle hub Directory, a listing of many hubs from around the world, enabling people from all over the world to find your hub and search the courses within it. You may want to wait until you have some content before you register.

==Managing sites==
In '''Administration > Hub > Manage sites''', you can:
* Prioritise a site: during a search, course from prioritised sites appear on top of the list. A prioritised site is always trusted.
* Trust a site: when a site is trusted, any published course is immediatly available
* Delete a site: delete a site from the database. A message will be sent to the site administrator.
* Settings: you can change some information as the name, the description, the language...
* Make a site visible: only site declared as visible appear on the the site list (currently the site list hasn't been implemented)

==Managing courses==
In '''Administration > Hub > Manage course''', you can:
* Delete a course: delete a course from the database.
* Settings: you can change some information as the name, the description, the language...
* Make a course visible: decide if the course is displayed on search result

== Important things about roles, users and web services ==
A hub server uses intensively Moodle web service 2.0. For this reason it is important to understand the [https://docs.moodle.org/en/Web_Services web services administration], and what happens if you change some roles/users/services.

=== Roles ===
The hub server creates on the fly some roles that you should '''never delete/modify''':
* one role for the hub directory
* one role for registered sites
* one role for public sites

=== Users ===
The hub server creates on the fly some users that you should '''never delete/modify''':
* one user for the hub directory
* one user for public access
* as many users as registered sites

=== Services ===
The hub creates during installation some web services that you should '''never delete/modify''':
* one service for Hub directory
* one service for Registered sites
* one service for Public sites

It also creates tokens on the fly. These tokens are not displayed on the token management list, so you cannot accidentally delete them.

==See also==

*[[Site registration]]

[[ja:ハブ管理]]

Moodle app FAQ

2012-01-24T02:31:49Z

Jmouneyrac: /* Where can I download the official Mobile app for iPhone? */

{{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 ===
* [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 official [[Mobile app]] for iPhone, created by Moodle HQ.
* [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://mle.sourceforge.net MLE-Moodle] - Allows course designers to make a separate set of Moodle pages for mobile users.
* [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 (My Moodle)?==

The Mobile app, My Moodle, can be downloaded for free from the Apple Online Store http://itunes.apple.com/ie/app/my-moodle/id461289000.

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

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

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

==When will there be an official Mobile app for Android?==

The Android app is expected to be ready around Christmas or soon after. (Source: [[:dev:Developer meeting November 2011|Nov 2011 developer meeting notes]])

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

==See also==

* [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum]
* 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]]

Hub administration

2011-12-12T03:43:02Z

Jmouneyrac: /* Minimal Requirements */

{{Community hubs}}
==Deciding to run a Hub==

Running a hub server is not something you should undertake lightly.

As the hub administrator you are responsible for the content in the hub, and you need to put in place processes to:
* verify all the course content is clean (of porn or malicious javascript)
* manage registered sites and their status
* maintain the quality of the listings through editing

=== Minimal Requirements ===

Below is a list of Minimal requirements for running a Moodle Community Hub.

* verify the server meets the requirements to run the latest version of Moodle found in the documents at [[Installing_Moodle#Requirements|Installing_Moodle]] and [[PHP]]
* ensure that the following php.ini variables are set to "On"
** allow_url_fopen: This setting is required the hub to be able to register a site. If this option is not enabled, you will be given the [[error/local_hub/cannotregisternotavailablesite|cannotregisternotavailablesite]] error. Related tracker issue: https://tracker.moodle.org/browse/CONTRIB-3063
* mod_security in Apache version 1 and mod_security2 in Apache version 2 will return a 403 forbidden error when a URL that is not the local domain is passed as a get variable. mod_security on either the hub or client servers will block the completion of the client/hub registration process, even to MOOCH, as within the registration process URL's are passed as get variables a number of times. An exception can be added to mod_security in Apache version 1 via a local .htacess file. However, this ability was removed in mod_security2. In mod_security2 the exception must be added to mod_security.conf of /conf.d. Related forum discussion: http://moodle.org/mod/forum/discuss.php?d=188933

==How the hub software works==

The hub software is implemented as a separate "local" plugin designed to be added to a standard install of Moodle 2.0 or later. In this way the hub gets to use on all the features in the Moodle core API and benefits from maintenance of the core code.

Once installed the whole site gets a new frontpage with a simple search box (see http://hub.moodle.org/ for example).

Please don't add the hub capabilities to an existing Moodle site with real courses. Although it may work, there are some opportunities for GUI confusion and some unknowns when it comes to security, so please just avoid it. Moodle is free, so it's trivial to install another clean copy to build your hub with.

==How to set up a Moodle Hub server==

# Install Moodle 2.0 or later somewhere on a web server with a nice URL.
# Download the latest hub plugin from http://download.moodle.org/download.php/plugins/local/hub.zip
# Save the zip into the /local directory of Moodle and unzip, producing /local/hub
# Visit the "Notifications" page in Moodle (/admin) to complete the upgrade and install the hub software.
# Enable web services for the hub ('''Site Administration > Advanced features''')
# Enable the XML-RPC protocol ('''Site Administration > Plugins > Web services > Manage protocols''')
# Set up the SMTP ('''Site Administration > Plugins > Message outputs > Email''')
#Set up the recaptcha ('''Site Administration > Plugins > Authentication > Manage authentication''')
# Set up your hub ('''Site Administration > Hub > Settings''')

Congratulations! You now have a working hub with no content!

==Site registration==

Only sites that are registered with the hub are allowed to publish content there.

Sites register on the hub via '''Site Administration > Registration'''

==Hub registration==

You can also register your hub with the Moodle hub Directory, a listing of many hubs from around the world, enabling people from all over the world to find your hub and search the courses within it. You may want to wait until you have some content before you register.

==Managing sites==
In '''Administration > Hub > Manage sites''', you can:
* Prioritise a site: during a search, course from prioritised sites appear on top of the list. A prioritised site is always trusted.
* Trust a site: when a site is trusted, any published course is immediatly available
* Delete a site: delete a site from the database. A message will be sent to the site administrator.
* Settings: you can change some information as the name, the description, the language...
* Make a site visible: only site declared as visible appear on the the site list (currently the site list hasn't been implemented)

==Managing courses==
In '''Administration > Hub > Manage course''', you can:
* Delete a course: delete a course from the database.
* Settings: you can change some information as the name, the description, the language...
* Make a course visible: decide if the course is displayed on search result

== Important things about roles, users and web services ==
A hub server uses intensively Moodle web service 2.0. For this reason it is important to understand the [https://docs.moodle.org/en/Web_Services web services administration], and what happens if you change some roles/users/services.

=== Roles ===
The hub server creates on the fly some roles that you should '''never delete/modify''':
* one role for the hub directory
* one role for registered sites
* one role for public sites

=== Users ===
The hub server creates on the fly some users that you should '''never delete/modify''':
* one user for the hub directory
* one user for public access
* as many users as registered sites

=== Services ===
The hub creates during installation some web services that you should '''never delete/modify''':
* one service for Hub directory
* one service for Registered sites
* one service for Public sites

It also creates tokens on the fly. These tokens are not displayed on the token management list, so you cannot accidentally delete them.

==See also==

*[[Site registration]]

[[ja:ハブ管理]]

Web services FAQ

2011-11-29T02:36:27Z

Jmouneyrac:

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

Since Moodle 2.2, if the administrator turns Moodle debug mode >= NORMAL, then a 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]]

Web services FAQ

2011-11-23T05:46:25Z

Jmouneyrac: /* How to get a user token from an external application? */

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

==See also==

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

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

Web services FAQ

2011-11-23T05:44:42Z

Jmouneyrac:

{{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? ==
In Moodle 2.2 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]]

The condition being that the service need a shortname. At the moment a service can have a shortname if you:
* create the service as a built-in service (in db/services.php files)
* add the shortname manually in the DB. Note: we'll add the admin UI for shortname later (MDL-30229)

Just for the info, the file login/token.php exists since 2.1 but for this Moodle version it can only generate token for the mobile service.

==See also==

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

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

Web services

2011-11-02T08:59:42Z

Jmouneyrac: /* See also */

Web services

2011-11-02T08:44:57Z

Jmouneyrac: /* See also */

Web services

2011-11-02T08:44:02Z

Jmouneyrac: /* See also */

Web services

2011-11-02T08:35:15Z

Jmouneyrac:

{{Managing a Moodle site}}
Web services enable other systems to login to Moodle and perform operations.

== Administrator documentation ==
* [[How_to_create_and_enable_a_web_service|How to create and enable a web service]]
* [[Enable mobile web services|How to enable the mobile web service]]

== User documentation ==
Most of the time, the client application will retrieve the key (token) for a user. However, it is still possible for a user to view the key and to regenerate it.
* [[Security keys|How to obtain a security key (token)]]

==See also==
Sharing knowledge:
* The official discussion [http://moodle.org/mod/forum/view.php?id=6971| forum is here]
* [[Web_services_FAQ|Web services FAQ]]

Developer documentation:
* [[Development:Web_services | Web services]]
* [[Development:External services security | External services security]]
* [[Development:External services description | External services description]]

Other implementations:
* [[:dev:Web_Services:OK_Tech_Web_Services|OK Tech Web Services]]

[[Category:Web Services]]

[[eu:Web-zerbitzuak]]
[[ja:ウェブサービス]]

2011-11-02T01:48:43Z

Jmouneyrac: /* Authorise only specific users */

{{Web services}}
This document explains how an administrator can set up a web service for users to access a service. Each user will have a specific and unique security key (also known as a "token") to access the service.

== Enabling web services==
[[Image:Enable_web_service.jpg|thumb|Enabling web services]]
# Access ''Settings > Site administration > Advanced features''
# Check 'Enable web services' then click 'Save Changes'

Note: For security reasons, web services should only be enabled if you intend to make use of it.

== Enabling protocols ==
[[Image:Enable_protocol.jpg|thumb|left|Enabling protocols]]
Usually external applications that users wish to use dictate which protocols should be enabled.

# Access ''Settings > Site administration > Plugins > Web services > Manage protocols''
# Enable the protocols (SOAP, REST, XMLRPC, AMF, ...) as required

== Enabling web service function documentation ==
[[Image:Security keys and documentation.jpg|thumb|Security keys page with documentation link]]
Enabling web service function documentation (also on the Manage protocols page) results in user-specific web service documentation being available for each user on their [[How_to_get_a_security_key|security keys]] page. This option is mainly useful to web service client developers. If nobody is creating a web service client, there is no need to enable this feature.

== Creating a service ==
If none of the pre-build web services match your needs, you can create a custom service i.e. select which of the standard web service functions are available via that service.

You can enable only the specific functions that you need to expose, so not compromising on security.
[[Image:Create a service.jpg|thumb|Creating a service|left]]
# Access ''Settings > Site administration > Plugins > Web services > External services''
# Click Add new custom service
#* 'Authorised users only' - If enabled, you will need to select the authorised users manually. Otherwise all users with appropriate permissions are allowed
#* 'Required capability' - If enabled, any user accessing the web service will be checked against this selected capability. (This is just an additional optional security layer.)
# Enter a name and check Enabled
# Click the button 'Add service'

==Adding functions to the service==
[[Image:Select a web service function.jpg|thumb|Adding functions to the service]]Your service is currently empty and doesn't do anything. Web service functions need to be added. Your choice will be dictated by what you allow the external application to do. For now, select 'Create group' as it is the function used as an example in [[Development:Creating_a_web_service_client|Creating a web service client]].

# Click 'Add functions' link
# Select 'create group' function and click the 'Add functions' button

You will then be returned to the service functions list. Opposite each function is a 'Required capabilities' field. Users need these capabilities to run each function. However there are exceptions - see the web service function documentation for details.

==Enabling capabilities==

The final step is to grant appropriate permissions. The following capabilities should be allowed:

* [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] - for allowing users to generate a security key
* [[Capabilities/webservice/rest:use | webservice/rest:use]], [[Capabilities/webservice/soap:use | webservice/soap:use]], [[Capabilities/webservice/xmlrpc:use | webservice/xmlrpc:use]], [[Capabilities/webservice/amf:use | webservice/amf:use]] which match the enabled protocols.
* The required capabilities for the web service functions. These required capabilities are listed when you add a function to the service.

Once done, the web service should be set up. Users can [[How_to_get_a_security_key|obtain a personal security key]] and copy it in an external application.

= Alternative settings =

== Authorise only specific users==
[[Image:Authorised users link.jpg|thumb]] [[Image:Authorised user selection page.jpg|thumb]]
# ''Settings > Site Administration > Plugins > Web services > External Services''
# Select '''Authorised users''' link (the service must have been set as '''Authorised users only''' in the '''Edit''' link)
# Select the created user and click '''Add'''

As you can see in the second screen capture, Moodle indicates if some capabilities need to be assigned to an authorised user. Moreover if you click on the authorised user you can setup some specific options: IP restriction and Valid until.

== Create a token ==
[[Image:Create_token.jpg|thumb]]
This feature allows you to create a token for specific user. It can be useful if a user doesn't have the moodle/create:token capability. This is also the only way to create a token for an administrator. For security reason, tokens are not automatically generated in the administrator security keys page.

# ''Settings > Site Administration > Plugins > Web services > Manage tokens''
# Click on '''Add'''
# Select the created user and service
# Click on '''Saves changes'''

== Enable capabilities for the user==
The last step, and the trickiest, is to grant the right permission to the external system user. It would need the following capabilities:
* "''webservice/rest:use'', ''webservice/soap:use'', ''webservice/xmlrpc:use'', ''webservice/amf:use''" matching the enabled protocols.
* the required capabilities by the web service functions. These required capabilities are listed when you add a function to the service.
As you previously created a token for the external system user, you do not need to assign "''moodle/webservice:createtoken''" to it.
For more information about roles and capabilities, read the [https://docs.moodle.org/en/Manage_roles Manage roles] documentation.

Using web services

2011-11-02T01:48:26Z

Jmouneyrac: /* Authorise only specific users */

{{Web services}}
This document explains how an administrator can set up a web service for users to access a service. Each user will have a specific and unique security key (also known as a "token") to access the service.

== Enabling web services==
[[Image:Enable_web_service.jpg|thumb|Enabling web services]]
# Access ''Settings > Site administration > Advanced features''
# Check 'Enable web services' then click 'Save Changes'

Note: For security reasons, web services should only be enabled if you intend to make use of it.

== Enabling protocols ==
[[Image:Enable_protocol.jpg|thumb|left|Enabling protocols]]
Usually external applications that users wish to use dictate which protocols should be enabled.

# Access ''Settings > Site administration > Plugins > Web services > Manage protocols''
# Enable the protocols (SOAP, REST, XMLRPC, AMF, ...) as required

== Enabling web service function documentation ==
[[Image:Security keys and documentation.jpg|thumb|Security keys page with documentation link]]
Enabling web service function documentation (also on the Manage protocols page) results in user-specific web service documentation being available for each user on their [[How_to_get_a_security_key|security keys]] page. This option is mainly useful to web service client developers. If nobody is creating a web service client, there is no need to enable this feature.

== Creating a service ==
If none of the pre-build web services match your needs, you can create a custom service i.e. select which of the standard web service functions are available via that service.

You can enable only the specific functions that you need to expose, so not compromising on security.
[[Image:Create a service.jpg|thumb|Creating a service|left]]
# Access ''Settings > Site administration > Plugins > Web services > External services''
# Click Add new custom service
#* 'Authorised users only' - If enabled, you will need to select the authorised users manually. Otherwise all users with appropriate permissions are allowed
#* 'Required capability' - If enabled, any user accessing the web service will be checked against this selected capability. (This is just an additional optional security layer.)
# Enter a name and check Enabled
# Click the button 'Add service'

==Adding functions to the service==
[[Image:Select a web service function.jpg|thumb|Adding functions to the service]]Your service is currently empty and doesn't do anything. Web service functions need to be added. Your choice will be dictated by what you allow the external application to do. For now, select 'Create group' as it is the function used as an example in [[Development:Creating_a_web_service_client|Creating a web service client]].

# Click 'Add functions' link
# Select 'create group' function and click the 'Add functions' button

You will then be returned to the service functions list. Opposite each function is a 'Required capabilities' field. Users need these capabilities to run each function. However there are exceptions - see the web service function documentation for details.

==Enabling capabilities==

The final step is to grant appropriate permissions. The following capabilities should be allowed:

* [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] - for allowing users to generate a security key
* [[Capabilities/webservice/rest:use | webservice/rest:use]], [[Capabilities/webservice/soap:use | webservice/soap:use]], [[Capabilities/webservice/xmlrpc:use | webservice/xmlrpc:use]], [[Capabilities/webservice/amf:use | webservice/amf:use]] which match the enabled protocols.
* The required capabilities for the web service functions. These required capabilities are listed when you add a function to the service.

Once done, the web service should be set up. Users can [[How_to_get_a_security_key|obtain a personal security key]] and copy it in an external application.

= Alternative settings =

== Authorise only specific users==
[[Image:Authorised users link.jpg|thumb]] [[Image:Authorised user selection page.jpg|thumb]]
# ''Settings > Site Administration > Plugins > Web services > External Services''
# Select '''Authorised users''' link (the service must have been set as 'Authorised users only' in the 'Edit' link)
# Select the created user and click '''Add'''

As you can see in the second screen capture, Moodle indicates if some capabilities need to be assigned to an authorised user. Moreover if you click on the authorised user you can setup some specific options: IP restriction and Valid until.

== Create a token ==
[[Image:Create_token.jpg|thumb]]
This feature allows you to create a token for specific user. It can be useful if a user doesn't have the moodle/create:token capability. This is also the only way to create a token for an administrator. For security reason, tokens are not automatically generated in the administrator security keys page.

# ''Settings > Site Administration > Plugins > Web services > Manage tokens''
# Click on '''Add'''
# Select the created user and service
# Click on '''Saves changes'''

== Enable capabilities for the user==
The last step, and the trickiest, is to grant the right permission to the external system user. It would need the following capabilities:
* "''webservice/rest:use'', ''webservice/soap:use'', ''webservice/xmlrpc:use'', ''webservice/amf:use''" matching the enabled protocols.
* the required capabilities by the web service functions. These required capabilities are listed when you add a function to the service.
As you previously created a token for the external system user, you do not need to assign "''moodle/webservice:createtoken''" to it.
For more information about roles and capabilities, read the [https://docs.moodle.org/en/Manage_roles Manage roles] documentation.

Using web services

2011-11-02T01:45:36Z

Jmouneyrac: /* Creating a service */

{{Web services}}
This document explains how an administrator can set up a web service for users to access a service. Each user will have a specific and unique security key (also known as a "token") to access the service.

== Enabling web services==
[[Image:Enable_web_service.jpg|thumb|Enabling web services]]
# Access ''Settings > Site administration > Advanced features''
# Check 'Enable web services' then click 'Save Changes'

Note: For security reasons, web services should only be enabled if you intend to make use of it.

== Enabling protocols ==
[[Image:Enable_protocol.jpg|thumb|left|Enabling protocols]]
Usually external applications that users wish to use dictate which protocols should be enabled.

# Access ''Settings > Site administration > Plugins > Web services > Manage protocols''
# Enable the protocols (SOAP, REST, XMLRPC, AMF, ...) as required

== Enabling web service function documentation ==
[[Image:Security keys and documentation.jpg|thumb|Security keys page with documentation link]]
Enabling web service function documentation (also on the Manage protocols page) results in user-specific web service documentation being available for each user on their [[How_to_get_a_security_key|security keys]] page. This option is mainly useful to web service client developers. If nobody is creating a web service client, there is no need to enable this feature.

== Creating a service ==
If none of the pre-build web services match your needs, you can create a custom service i.e. select which of the standard web service functions are available via that service.

You can enable only the specific functions that you need to expose, so not compromising on security.
[[Image:Create a service.jpg|thumb|Creating a service|left]]
# Access ''Settings > Site administration > Plugins > Web services > External services''
# Click Add new custom service
#* 'Authorised users only' - If enabled, you will need to select the authorised users manually. Otherwise all users with appropriate permissions are allowed
#* 'Required capability' - If enabled, any user accessing the web service will be checked against this selected capability. (This is just an additional optional security layer.)
# Enter a name and check Enabled
# Click the button 'Add service'

==Adding functions to the service==
[[Image:Select a web service function.jpg|thumb|Adding functions to the service]]Your service is currently empty and doesn't do anything. Web service functions need to be added. Your choice will be dictated by what you allow the external application to do. For now, select 'Create group' as it is the function used as an example in [[Development:Creating_a_web_service_client|Creating a web service client]].

# Click 'Add functions' link
# Select 'create group' function and click the 'Add functions' button

You will then be returned to the service functions list. Opposite each function is a 'Required capabilities' field. Users need these capabilities to run each function. However there are exceptions - see the web service function documentation for details.

==Enabling capabilities==

The final step is to grant appropriate permissions. The following capabilities should be allowed:

* [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] - for allowing users to generate a security key
* [[Capabilities/webservice/rest:use | webservice/rest:use]], [[Capabilities/webservice/soap:use | webservice/soap:use]], [[Capabilities/webservice/xmlrpc:use | webservice/xmlrpc:use]], [[Capabilities/webservice/amf:use | webservice/amf:use]] which match the enabled protocols.
* The required capabilities for the web service functions. These required capabilities are listed when you add a function to the service.

Once done, the web service should be set up. Users can [[How_to_get_a_security_key|obtain a personal security key]] and copy it in an external application.

= Alternative settings =

== Authorise only specific users==
[[Image:Authorised users link.jpg|thumb]] [[Image:Authorised user selection page.jpg|thumb]]
# ''Settings > Site Administration > Plugins > Web services > External Services''
# Select '''Authorised users''' link
# Select the created user and click '''Add'''

As you can see in the second screen capture, Moodle indicates if some capabilities need to be assigned to an authorised user. Moreover if you click on the authorised user you can setup some specific options: IP restriction and Valid until.

== Create a token ==
[[Image:Create_token.jpg|thumb]]
This feature allows you to create a token for specific user. It can be useful if a user doesn't have the moodle/create:token capability. This is also the only way to create a token for an administrator. For security reason, tokens are not automatically generated in the administrator security keys page.

# ''Settings > Site Administration > Plugins > Web services > Manage tokens''
# Click on '''Add'''
# Select the created user and service
# Click on '''Saves changes'''

== Enable capabilities for the user==
The last step, and the trickiest, is to grant the right permission to the external system user. It would need the following capabilities:
* "''webservice/rest:use'', ''webservice/soap:use'', ''webservice/xmlrpc:use'', ''webservice/amf:use''" matching the enabled protocols.
* the required capabilities by the web service functions. These required capabilities are listed when you add a function to the service.
As you previously created a token for the external system user, you do not need to assign "''moodle/webservice:createtoken''" to it.
For more information about roles and capabilities, read the [https://docs.moodle.org/en/Manage_roles Manage roles] documentation.